I have to resolve the issue where users might log into the connection broker, see a list of pools, NOT choose a pool, and walk away.
This leaves thier thin client open to be used by another person that could now use thier credentials to go nuts in teh VDI environment.
I used the SOO timeout feature...
- Start the ADSI Edit utility on your View Connection Server host.
- Select or connect to DC=vdi, DC=vmware, DC=int.
- On the object CN=Common, OU=Global, OU=Properties, set the pae-SSOCredentialCacheTimeout attribute to the new SSO timeout limit in minutes.
The default value is -1, which means that no SSO timeout limit is set. A value of 0 disables SSO.
On remote desktops, the new SSO timeout limit takes effect immediately. You do not need to restart the View Connection Server service or the client computer.
On desktops that run in local mode, the new SSO timeout limit takes effect the next time a client computer that hosts the local desktop sends a heartbeat message to View Connection Server.
But this isn't taking effect.
I set it to 1.
changed from -1
Has anyone seen this?
