Every day we get phone calls with some users that can not login on their PCIOP boxes.
They login, select the pool the want, get a black screen and then get kicked back to the login prompt.
I am able to get them in by resetting the virtual machines in the pool that are not being used, once they reset they can then login without an issue.
Below are the logs that are made when they try to connect.
Severity | Time | Module | Message |
Audit success | 7/25/2016 7:51 | Connection Server | User CLARKNT\Tiffan has logged out |
Info | 7/25/2016 7:51 | Connection Server | User CLARKNT\Tiffan requested Pool dss, allocated machine DSS-703V |
Info | 7/25/2016 7:51 | Connection Server | User CLARKNT\Tiffan requested Pool dss |
Info | 7/25/2016 7:51 | Agent | The agent running on machine DSS-703V has accepted an allocated session for user CLARKNT\tiffan@co.us |
Audit success | 7/25/2016 7:51 | Connection Server | User CLARKNT\Tiffan has logged in |
Audit success | 7/25/2016 7:50 | Connection Server | User CLARKNT\Tiffan has logged out |
Info | 7/25/2016 7:50 | Connection Server | User CLARKNT\Tiffan requested Pool dss, allocated machine DSS-703V |
Info | 7/25/2016 7:50 | Connection Server | User CLARKNT\Tiffan requested Pool dss |
Info | 7/25/2016 7:50 | Agent | The agent running on machine DSS-703V has accepted an allocated session for user CLARKNT\tiffan@co.us |
Audit success | 7/25/2016 7:50 | Connection Server | User CLARKNT\Tiffan has logged in |
What version of view are you running and are you using any vGPUs to offload anything or using std svga?
reminds me of an issue we recently had.
are all of the desktops running the same agent version?
If you try to connect with windows view client lower than 3.5.2 to a virtual desktop with view agent 6.2.1 or higher it will exactly show this issue.
this is due to vmware dropping TLS1.0 support with vmware view agent 6.2.1, which is still being used by windows view clients older than 3.5.2.
just guessing into the blue without more information 🙂