Latest release - issue/feature request with Ivanti Workspace Control Agent (10.x)

[ozzy01]

Is your feature request related to a problem? Please describe. This feature request is related to issue. The generalization breaks being able to log into the image at all due to whatever it is doing to the Ivanti Workspace Control (aka labeled RES here but we are Ivanti Workspace Control now) It appears to try to redirect the cache or do something with it which then breaks being able to log in locally with any account. Ultimately, I am not sure what it is trying to do and if that is important, but need to be able to tell it to not try and do anything there. I just don't know what it is actually doing to create the situation to say whether or not that is something I would want it to try and do if maybe we didn't already have our cache redirected?.

Describe the solution you'd like ADMX needs a policy setting to control (similar to Ivanti Automation) BIS-F trying to do anything with the Ivanti Workspace Control cache (or whatever it is doing in the image) - message shown in screenshot appears to show touching the cache directory.

Describe alternatives you've considered

Additional context This is a Citrix PVS (7.15 LTSR) environment. Windows 10 1903. RES cache is already redirected to PVS Write Cache drive.

What it does:

Leading to this at any login next time which then doesn't go any further and kicks you back to login screen:

[kyriansaxum]

we've seen the same. issue resolved itself by waiting a little longer or force a cache update from ivanti Console.

ivanti WC 10.3.190 Windows 10 1909 PVS 1912 BIS-F 1912.2

[ozzy01]

yea, would be good to just have the ability to disable it via ADMX as there are situations where we don't need cache cleared or want that. I will test trying to force it to push cache down again and then see if I can login again in the meantime. Thanks

[kyriansaxum]

after you run BIS-F, restart the Ivanti service, wait for the cache to be updated and then close the image. might help as well