This message was deleted.

I don't use WEM for GPOs, but can you remove half of them to see if that delay is removed? Perhaps it's only one setting causing this.

Oh yea, Good Point. that was one thing I need to do. going to do is remove the GPO stuff and the Actions.

You still have to assign the policies in Assignments, right? I'd remove them from there. If you have a test account you can do this with, first thing I'd do is remove all of them but leave GPO processing enabled just to confirm that it's one of the policies.

Yea, sorry. That is what I meant by saying actions. Really meant Assignments.

Hmm. I've experienced some strange things with "Citrix WEM User Logon Service" and logon times. Disable it, and logon times are back to normal. "Citrix WEM User Logon Service" is, and I quote Citrix Support, only used for CEM.

Funny enough, we used to have to disable that service many builds ago because of an issue where it slowed down logons significantly.

So Removed all assignments, all GPOs. It Still did it. I ran out of Time. But I am having them redo the client. Nothing is applied other the CPU optimizations. The log files show nothing so far either. I told them to disable the user login service as well to test. What is funny, is on the other windows 10 image it works like it should. So something they did between the time of my fresh deploy/setup until when they built a new image.

Is that not needed for GPO processing?

The docs state it processes user gpos. “For WEM agents to process Group Policy settings properly, verify that Citrix WEM User Logon Service is enabled on them.” I told them not to go to production like this until we have more time to figure out what changed .

what did you do

Lol yep

"Citrix WEM User Logon Service" will check the cache status, process the GPOs/logon scripts/etc. to ensure the WEM agent works properly. Maybe you can check the SyncForegroundPolicy configuration. This determines whether the Citrix WEM Agent Logon Service delays logons until the processing completes.

I missed this somehow. Ahh under agent settings. I will check this key and see what’s set. Thanks for the little nugget