This message was deleted.

WEM GPO(with cache) is one of the key factors to build faster logon

Hmm.. initial testing not so good, a lot faster with AD GPO's.

have you tried this configuration?

"If the value is not set or you set the value to 0, Citrix WEM Agent User Logon Service does not delay logons, and user Group Policy settings are processed in the background." I have not done anything so I guess I have the correct setup.

The WEM agent queries the Group Policy settings from the WEM infrastructure service and processes them locally. The process mechanism is the same as the AD GPO's. the difference is from where to get the GPO. One is from the WEM infrastructure service, and another is from the AD. And we can use the local cache to reduce the query operations for WEM.

I'm confused about the SyncForegroundPolicy option. Is this an option that WEM can set during installation or is WEM looking for it at installation? I'm reading if the value is 0 or not set, the WEM Agent User Logon Service will not delay logons, but certain policies may not apply the first time because of the Windows Shell loading faster than Group Policies can apply. I do not have the SyncForegroundPolicy reg value and the WEM Agent User Logon Service slows down the first logon to a XenApp server by 20-30 seconds. Every logon to the same server are not held up.

I have not had good luck with this feature to be honest. As of now I wouldn’t depend on it. Use computer policy’s where you can, the. Put everything else the is user base in WEM. I’m not sure why it’s hit and miss but it works and then it doesn’t . It did make them faster, but it added complexity for the clients. This was the reg setting set to 1. As 0 delayed logins. Not saying it’s a bad product as I love WEM. But my experiences with this has been rough.

Thanks @Ray Davis!

Also the WEM team has made this product awesome, in time I’m sure they will tweak things to make it even better. But overall I love WEM.

the SyncForegroundPolicy is not set by wem. for the first time logon, wem may need to pull configuration from the infrastructure service. if the cache is enabled and exists, it can reduce the configuration syncup time. if you can provide the wem log, we can investigate what takes the logon time. @Robert Berggren

@Sharp Guo he should enable the debug log too in my opinion to get more data. What do you think?

yes, please enable the debug so we can get the details. thanks, Ray

I have just ditched this idea for now. I'll stick with my language and regional settings related user policies for now.