This message was deleted.
# citrix-wem
s
This message was deleted.
b
Agentcacheutility.exe -refreshcache applies everything immediately.
r
For this reason, I still put in the Agentcacheutility.exe scripts by @James Kindon
👍 1
j
How are sealing/prepping your image. As kind as Ray is, those scripts should be dead and gone with native product capability now (worked hard to see that come to life!)
b
WS2022, sealing with BISF 1912.7, no config of WEM in the master image, AgentCache not redirected. PVS Target Device Config via BISF, CTX Optimizer with Autoselect and 3rd Party Components. First customer I have this issue at. Even upgraded to WEM 2212.
j
Try setting this in your BIS-F Config
r
I should have put clarification around my answer more. Because I am in many different WEM verisons, I still use the script. But on newer ones I would definitely use BISF portion on WEM. Good call on that.
b
Not sure if the following settings is set, I've asked the customer to check ie4uinit.exe bypass. https://support.citrix.com/article/CTX228669/wem-profile-settings-are-very-delayed-in-applying-to-an-end-user-session Thank you for your input. Keep you updated.
The BIS-F setting would be a workaround 🙂
Bypass ie4uinit Check fixed it 👌
👍 1
😳 1
j
Nice work - didn’t see that coming
r
Just to fill in on that ie4uinit thing. If you delete the stub path in "Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4383}" you will have to use the WEM bypass, otherwise not.
👍 2
b
good to know. Stubpaths have been deleted 😂