WaitForVMware
Workspace Control checks the VMware View Registry entries in HKEY_CURRENT_USER\Volatile Environment, filled in by the VMware View client.
If, for some reason e.g. a 3G connection, these values are not being filled in before the Workspace Control managed session starts, Workspace Control will fall back to the VDI name and IP address. If this happens, you can configure the WaitForVMware registry setting.
The number of seconds to wait depends per environment so you need to check the registry and measure how long it takes before the VMware Client sets the values in HKEY_CURRENT_USER\Volatile Environment in the VDI.
The WaitForVMware feature will not work if there's already a value present.
|
Key |
|
|
Value |
WaitForVMware |
|
Type |
REG_DWORD |
|
Data |
The maximum number of seconds to wait for volatile registry to be filled with info. |