Quest vWorkspace 6.x offers enhanced security to allow connections from only version 6.x of the Quest client. In some cases it is required to turn off this option, for example if you wanted to connect to the Farm from a Sunray terminal or a Wyse Thin OS based terminal. To enable compatibility mode you are required to add the following registry key on each server running the ‘Quest Connection Broker’ service:

HKLMSoftwareProvision NetworksCommonLoad And License Manager

CompatibilityMode = 1  REG_DWORD

Whilst we are looking at the compatibility mode it is also worth covering the setup for configuring Wyse Thin OS devices from the Quest vWorkspace server rather than using an FTP server.

Once you have configured your WNOS.INI andor your RDP.INI files you need to store them on a broker server in “C:Program FilesQuestvWorkspaceWYSEWNOS”, if you plan to use custom bitmaps for wallpapers, logon screen, icons etc. they would need to be stored in “C:Program FilesQuestvWorkspaceWYSEWNOSitmap”. Once you have the INI files in place you can configure the terminals manually or use DHCP tags to automate this process. For the purposes of the example we will assume that the broker is using port 8080 and has an IP address of 192.168.1.1 (NB. You could also use the servers DNS name as long as it is resolvable).

If you want to configure the terminals using DHCP option tags you would need to create 161 and 188 (both with string values), 161 is the file server and 188 is the VDI broker. It is quite possible that in this environment that 161 and 188 are identical, however they are both still required. An example would be ‘http://192.168.1.1:8080’. If you wanted to configure the terminal manually you need to edit the Network Settings, click on the Servers tab and enter the File Server and VDI broker information in the relevant fields, again an example would be ‘http://192.168.1.1:8080’