This message was deleted.
# citrix-wem
s
s
thanks for information! could you help to get the agent host debug log so we can check? https://docs.citrix.com/en-us/workspace-environment-management/current-release/reference/view-log-files#logs-related-to-the-agent
r
@Jonathan Pitre I am noticing this more and more myself. I had this issue a while back, as well @Marco Hofmann recently here https://worldofeuc.slack.com/archives/CKJADBQM6/p1696431578068859?thread_ts=1695905736.920749&cid=CKJADBQM6 In my experience, to get the GPO to apply the way GPMC does. I had to enable this. https://docs.citrix.com/en-us/workspace-environment-management/current-release/install-and-configure/agent-host.html#system-settings Copied from the link above: • SyncForegroundPolicy. Lets you configure the SyncForegroundPolicy registry value during agent installation. This policy setting determines whether Group Policy processing is synchronous. Accepted values: 0, 1. 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. If you set the value to 1, Citrix WEM Agent User Logon Service delays logons until the processing of user Group Policy settings completes. By default, the value does not change during installation.
IMPORTANT:
If Group Policy settings are processed in the background, Windows Shell (Windows Explorer) might start before all policy settings are processed. Therefore, some settings might not take effect the first time a user logs on. If you want all policy settings to be processed the first time a user logs on, set the value to 1.
1
👀 1
The only downside is this " If you set the value to 1"Citrix WEM Agent User Logon Service" delays logons until the processing of user Group Policy settings completes. By default, the value does not change during installation." Not to sure if this is something that others are seeing too.
@Ray Davis thanks for sharing, I have changed the registry value of SyncForegroundPolicy to 1, reinitialize the WEM Cache and rebooted. The issue still persists. If you take a look at the log, it looks like some registry values are perceived as environment variable and WEM try to convert them and for some reason they don't get applied. This is a brand new environment and I see the same issues with multiple customers.
s
Thanks for the information! we check the logs and can't find any failed GPO information. Some logs like "DynamicTokensController.ReplaceDynamicTokens() : Replacing Split Operations -> no match found for : DisablePersonalDirChange" just means that the WEM is trying to replace the dynamic token but can't find the dynamic token definition. It works as designed since there are no dynamic tokens in the GPO values. this won't impact the GPO process.
Currently, you still find the issue. The warning WEM event log was printed on Oct 3. The log files started from Oct 5th and can't find any failed information from them. From the Windows event log, it just said that the user GPO policy failed, and no more information. We don't know which GPOs are not applied successfully. Could you help export the failed GPOs and dump event logs within a time range around the corresponding error event log? thanks in advance!
If you'd like, you can enable the actions processing result for GPO and then get the detailed GPO report from the WEM web console easily. https://docs.citrix.com/en-us/workspace-environment-management/service/manage/configuration-sets/advanced-settings#monitoring-preferences
j
I believe I enabled that option already, I'll get back to you with the logs next week, thanks
🙌 1
r
@Jonathan Pitre any headway on this? I’m curious because I seeing this from others. I’m not sure if we are doing something wrong or perhaps the concept of GPO via WEM has different parts that we need to understand and tweak more. I have migrated GPO to WEM a couple times before. I had this same issue in 2 environments. One where the customer had to go to Citrix support and then Citrix told them it’s a MS issue. @Sharp Guo was kind enough to help me with logs too and give me some pointers that helped me. Second one was that we needed to do the sync delay option. Then the 3rd one was a small subset of GPOs and thing were okay. To me it seems like anything profile related or something that needs to apply fast doesn’t always apply fast. So I leave the computers GPO in GPMC myself. But the user side is usually on point. WEM has made some huge improvements imho. They will continue to do so and I’m sure anything around the GPO concept will get better in time. In my lab at home I took all of my gpos and put them in WEM and things were fine. So it’s super odd. Each environmental has its own gremlins at times, but gremlins or not it’s up to us to figure it out for the customers.
j
Nope, I had 0 time to invest in troubleshooting the issue sadly, I got more pressing matters but just like you bruh I really want this to work and ditch GPOs. I'll get back to it when time permits!
👌 1
r
Cool man, totally get it. Keep us posted when you get back to it.