VMware View TS-Client name or TS-Client IP address is not displayed correctly in RES Workspace Manager Console

Version 1

    Problem

    When consulting the User Sessions overview in RES Workspace Manager Console it is possible that the TS-Client name or TS-Client IP address is not displayed correctly.

    In rare circumstances the VMware View IP address and name are displayed instead of the Client`s name and IP address. Issue can occur in both PCoIP and RDP sessions.


    Cause

    RES Workspace Manager will check the VMware View Registry entries in "HKEY_CURRENT_USER\Volatile Environment", these values are filled by the VMware View client.

    If these values are, for some reason e.g. a 3G connection, are not present yet RES Workspace Manager will fall back to the VDI name and IP address.


    Solution

    If the volatile environment data of VMware View is not being filled before the RES Workspace Manager managed session starts you can add "WaitForVMware" to the registry.

    The number of seconds to wait depends per environment, please 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 value`s must not be present in a new session, if they are present the "WaitForVMware" feature will not work.

    32-bit:

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\RES\Workspace Manager
    Value: WaitForVMware
    Type: REG_DWORD
    Data: max #seconds to wait for volatile registry to be filled with info

    64-bit:

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RES\Workspace Manager
    Value: WaitForVMware
    Type: REG_DWORD
    Data: max #seconds to wait for volatile registry to be filled with info

    Note:

    - This key is supported since RES Workspace Manager 2012 SR1 Fix Pack2
    - The registry keys can also be applied on HKEY_CURRENT_USER