This message was deleted.

For Single-Session OS VDA yes

You are reading it right. But the setting is for server and the description highlighted is for vdi. It says use server time zone. Not service..

It says: Use server timezone NOT service

It's a bit confusing. I have some users that are on win10 vda, that need the the backend time zone. I thought by reading it "use service time zone" it would.

But it doesn’t say use service time zone….

crap, I mean server. Yea

You may have other policies taking precedence. What happens if you uncheck the default and select use server?

testing it now with a client.

Try to set the Policy „Use local time of client“ to „time zone of the user session“ (server time zone) And enable the Allow time zone redirection setting in the GPO (User Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection)

Does that GPO apply in RDSH only? The way it reads I mean. If I set the use local time of client, would it use the time zone they are coming in as from the local device? For these Windows 10 device, they want them to match the CST time which is where there DC is located.

You highlighted the default in the picture and it is „Use Client Time“ for XenDesktop aka Single Session VDA. But you are right it makes no sense.

Check this out LOL

🤔 ok that explains it

Just don't know what Reg_None means yet

@Mike Streetz (O_P) and i talk a little bit about it here: https://worldofeuc.slack.com/archives/CKJADBQM6/p1659633290682279?thread_ts=1659464348.829229&cid=CKJADBQM6

It’s broken in the latest versions from what I can tell, you need that reg key to tell it to process policy

Hmmm thanks for sharing that. Yea it’s acting odd for sure. They way I understand it or the way it used to be is you use server time zone for single session vda aka win 10 was if use server time zone it would use the time zone from the source or the datacenter they hit. So for example if the VDA are in a CST time zone the sessions would have CST. If Use client time zone was use the local client time zone where the client os located, the VDA would switch the time zone to the location they are at such as EST or MST. This is in 2203 CU1 as well. What I don’t understand is the use default setting (use server time zone) which is the same setting as the use server time zone option in the drop down. If I set the default it uses the local client time zone. If I set it to use server time zone it seemed to work. Now that was only tested with one login. Chances are the client will hit me up today and say it’s not working again. Based on Mikes results. I read the older post and seems like you guys removed users from the GPO and it uses server times zone but then stopped working again. I’m wondering if this is a bug in 2203cu1 as well?

I thought 2203 worked but we had a hell of a time with this and I changed jobs before I saw it fully resolved. The reg key to process policy was supposed to fix it though.