Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

ozzy01 opened this issue Mar 20, 2020 · 0 comments


Copy link

@ozzy01 ozzy01 commented Mar 20, 2020

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.