Hi,
I am trying Immidio on Windows 8.1. I configured everything following the admin guide. It is running on vSphere 6 and Horizon 6.1 with App Volumes.
Without Immidio I can logon to the desktop and everything works normally.
As soon as I enable Immidio via GPO (logon script or run as group policy extension) the logon hangs on "preparing windows". I can never logon.
I checked the Immidio logs and everything seems ok. No errors are reported.
When I logon without Immidio and I start flexengine.exe -r manually, I get the configuration (shortcuts and so on). So I know my config is ok.
Anyone has seen this issue?
We are aware of an issue with the View Agent Smartcard Redirection feature.
Please try to remove the Smartcard Redirection feature and let me know if that solves the issue.
Hi
I believe this has been resolved if not could you attach the flexengine logs looks like group policy configuration
Regards
Gaurav
i am running into the exact same issue. It has not been resolved for me.
Hi,
I am also running into the same issue. Horzion View 6.1, UEM 8.6, Windows 8.1.
FlexEngine log files states that actions are successfully executed. However desktop hangs on a black screen.
When disabling th UEM policy I am able to log on.
Thanks in advance
Regards
I install Immidio 8.7, but still I am having the same issue.
This is very annoying...
We are aware of an issue with the View Agent Smartcard Redirection feature.
Please try to remove the Smartcard Redirection feature and let me know if that solves the issue.
This is also described in the UEM 8.7 release notes:
http://pubs.vmware.com/Release_Notes/en/uem/87/uem-870-release-notes.html
New Horizon Views displays a black screen after logging on to Windows 8.1 or Windows 10.
This issue might occur under the following conditions:
You are running Horizon View on Windows 8.1 or Windows 10.
You have the Horizon View smartcard redirection feature installed.
You have User Environment Manager installed, configured, and enabled.
Removing the smartcard redirection did the trick! Thanks a lot Pim!
I should have read the 8.7 release notes, but the issue was already there in 8.6 and nothing was mentioned in those notes.