WEM - CPU Optimization Hello all, I have a little question about CPU Spike Optimization. Often I let the Automatically prevent CPU spikes option do the job. But I have a customer with physical servers with 2 x 40 CPU (means 160 logical cores). I wonder if I must use a customize CPU Spike configuration. I don't really understand the option Set limit relative to single CPU core. Is there someone to help ? Currenlty WEM agent seems to have a negative impact on the system. I ask myself if he can manage this type of CPU.

I have setup WEM Web Console, health check shows everything is okay, but unable to logon with same user used for configuration. Also, when trying the native console, it says the database configuration is wrong. Just the localhost\sqlexpress database which was created successfully. Latest version, anyone?

Are you sure its running as the full fat version? It defaults to the lite version unless you set specific group policy settings.

Upgrade from WEM 2411 to 2511 fails: "Infrastructure Service Configuration Error saving Infrastructure Service Configuration! Error while trying to configure Infrastructure service registry permissions! This access control list is not in canonical form and therefore cannot be modified." I am pretty sure someone else posted that already but I cannot find it neither in slack nor linen.dev. Maybe someone have a hint or two?

Does anyone if there was a change in recent WEM versions to force gpupdate to run? I had reports of "logging in twice" when I figured out what was being reported, the user is seeing CWA login process -> App -> WEM agent UI processing. We have used WEM for a long time, apps are launched with VUEMAppCmd with a delay of 2000. In testing I am the delay working. For the agent launch process I see Citrix.Wem.Agent.ProcessUtility.exe launches gpupdate /target:user /force /wait:0 then waits before starting VUEMUIAgent.exe. With the /wait:0 I think the command should almost instantly finish, but it is taking ~6 seconds for the command to run. Not sure running the gpupdate thing is a newer WEM thing (I think the first report was after upgrading to 2511), or if the gpupdate taking multiple seconds is something new.

Where do I find this WEM Migration Tool? On-Prem to Cloud migration? Nowhere to be found.

I'm having an issue in one environment where LAS isn't working with WEM. CVAD has been successfully migrated to LAS. The ports, etc., are open to the license server. However, WEM keeps defaulting to legacy mode. The certificate message also doesn't appear when I click “Save Configuration” under Licensing. WEM is 2511 but it also doesn't work with 2507.1 144501 Event -> LASClient.InitializeAndStart() : LICENSING: LAS service is not enabled or failed to check entitlement. 144501 Event -> LicensingHelper.UpdateLicensingState() : Finished checking activation from Citrix Licensing Service (Legacy), license valid: True 144501 Event -> LicensingHelper.UpdateLicensingState() : Finished checking activation from Citrix Licensing Service (Legacy), license valid: True

@Ben Wadnizak joined #citrix-wem. They’re also new to World of EUC.

@Daniel E. joined #citrix-wem. They’re also new to World of EUC.

I'm working on a new PowerShell module that works with both On-Premises and Cloud versions of WEM. Also with this PowerShell version it's possible to migrate configuration (Applications, Environment vars, Printers, DriveMaps, Policies and Registry) from Ivanti Workspace Control to WEM. Is there anyone who likes to test this and give feedback? https://www.powershellgallery.com/packages/JBC.CitrixWEM/

Some documentation on how to start can be found here: https://github.com/j81blog/JBC.CitrixWEM

Hello, We have a strange issue on our hundred of VDA linked to Citrix Cloud and WEM Service. Yesterday, VDA agent upgraded to version 2604 automatically. Today, some customers call us to report that session logoff isn't working. We found that a script CitrixLogoff.bat exists in C:\Windows\System32\GroupPolicy\User\Scripts\Logoff\ but not on all VDA. The script is used in local policy as LogoffScript. Content of this script : call "C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\VUEMCmdAgent.exe" "logoff" We don't know what happens because we have no GPO and no WEM External Task who push this script. On the screen you can see multiple entries. To resolve the logoff issue, we have to delete all the script in LogoffScript Task, or copy then rename script.ini file as .bak and delete all the content in the file. Corrupted script.ini file on C:\Windows\System32\GroupPolicy\User\Scripts shows as the second print screen. Normal file has only the 3 first lines. Do you have a similar issue ? Bug on 2604 Wem Agent version ? Thanks

@cst has left the channel

How are you guys handling Application assignments in WEM in W11/S25? We have quite a lot of applications that we used to put into folders for W10/S16, but with folders no longer being an option, we don't want 100+ shortcuts just scattered throughout the Start menu. So I'm curious to hear what others are doing.

VUEMUIAgent doesn't auto start when user logs on. VDA is PVS target and the PVS master vm is not part of config set. How do we force the process to start on user logon?

I am curious if anyone is successful running File Info View from WEM Tools Hub. The on prem version would provide Publisher, Product and file info. This does not appear to do anything except copy the path. (Which I already have.) Are my expectations set to high or did I miss the point of the tool?

Citrix documentation is wrong unfortunately. This feature is still just WEM service, not on-prem. https://docs.citrix.com/en-us/workspace-environment-management/current-release/whats-new#enhancement-to-group-policy-migration-tool

We are using Citrix DaaS with WEM (Workspace Environment Management). After installing the new WEM Agent version 2603.1.100.1, sealing the vDisk, and rolling it out, the WEM Agent fails to register with Citrix DaaS. The error shown in the log is: "Client not authenticated." We attempted to delete the Site Key from the WEM registry entries, but this did not resolve the issue. Does anyone have any ideas or suggestions?

Have you ever seen the file/folder structure for WEM vanish from a VDA? all the registry stuff is still present. Dependent services like netlogon still think it's there and of course this causes netlogon to fail to start. this is the 3rd time i've seen it happen.

WEM - Helpdesk Option - Custom Link. Hi everyone, Does anyone use the support link in the Helpdesk option ? I a facing an issue (a bug I think). I configure powershell -file \\server\share\script.ps1; the VUEMRSAV show me the configuration. When I click on Support, nothing happen. I do a Procmon and I see that the UNC path is "corrupt". The \\ become \ so the script can't be launch. I use WEM Service and agent version 2605. I try different way to launch the Powershell script but always the same result. If I only set \\server\hare\script.ps1, it works but my script is opened by notepad (logic). Thank you for any help

@Anthony Shi: any idea ?

Has anyone ever faced this speicific issue? WEM Admin Console hangs while refreshing Agent Cache for some Agents via Console I have neve seen this before except for one customer now and I don't want to mess with the Windows default port range because of WEM

Really hoped this would be fixed. Can whoever is in charge of the WEM Web Console Configuration get rid of the fixed windows size on the Configuration Wizard? On the standard RDP session window size the buttons are hidden behind the task bar.

Hi Everyone, Is anyone else running into issues with the WEM agent getting bound to multiple configuration sets in Citrix DaaS? It looks like a recent update forces a new default setting during catalog setup. In our environment, we map one Machine Catalog to multiple Delivery Groups. When building a new catalog now, the "Experience Optimization" section defaults to "Apply default settings". This auto-binds the VDAs to WEM's "Unbound Agents" config set. The issue is that we already assign specific config sets by linking our Active Directory OUs inside WEM. Because of this new feature, our recent agents are getting choked up by binding to two configuration sets at once. We only see this on catalogs built over the last few weeks—older catalogs have that optimization field completely blank and work perfectly. Has anyone seen this and found a workaround to prevent this auto-assignment? Changing it to "Apply Custom Settings" will not solve it for us. Because a single catalog supplies VDAs to different delivery groups, we can't just pick one blanket WEM config set for the whole catalog. Slack Conversation

did you upgrade your VDA recently? for one customer, we saw the default optimizations overriding the OU WEM assignment's and had to go back to each MC and set the configuration set there.

No, MCs were created recently and default optimizations are turned on automatically earlier it was optional.

Anyone else not see the agent download anymore in WEM service Utilities tab?

Heads up if you are using Citrix WEM Cloud with older Configuration Sets! We recently found a Windows 11 Start Menu issue where several Win32 apps were missing, while packaged apps worked as expected. The cause was a legacy WEM setting: HideCommonPrograms -> True The setting was still applied by the WEM Agent, but was not visible in the WEM Web Console. It was only exposed in the Legacy Console, which will be retired on December 11, 2026. After disabling it, the affected apps returned in Get-StartApps and the Start Menu pins worked again - without changing the JSON. Key takeaway: Older WEM Configuration Sets may still contain active legacy settings that are not visible in the Web Console, so review them before the Legacy Console is retired.

Do I need to worry about the warning in agent log about the start menu cleanup? "Programme" in the path is German, the message with the path in English is working afterwards

Hey WEM folks! Do you find the memory and CPU optimization helping ? With the cost of hardware, w25, I need to optimize even more what we have. I wasn't impressed years ago with CPU clamping, memory wasn't an issue back in the time. Thanks!!