As part of the Horizon View 6.1 upgrade, there is a new feature to enable enhanced security on the JMS traffic between Security server and Connection Server. For upgrades to 6.1, this feature needs to be enabled. For new installs, its enabled by default.
To enable this after upgrading from a prior version, the setting can be changed in the View Admin page under global settings, security, edit settings. There is a drop down to change from the current version to Enhanced.
When attempting to change this setting, the following message popped up:
The pod is not ready to enable enhanced message security. Click "OK" to force enabling the enhanced mode, or "Cancel" to cancel the operation
With no additional information to work from, i found a section in the Horizon View 6.1 documentation on using the vdmutil to configure this setting.
Using the following command i was able to get more detail on what was going on.
vdmutil.cmd --setMsgSecMode --msgSecMode ENHANCED --authAs --authDomain --authPassword
I received the following output:
All connection servers are ready for ENHANCED mode All security servers are ready for ENHANCED mode All RDS servers are ready for ENHANCED mode One or more machines are not ready for ENHANCED mode Cannot enter ENHANCED mode. Some components are not ready. Complete, returnCode=1
To fix this issue, I had to make sure no desktops were in a provisioned status and that all desktops indicated a View Agent version of 6.1 or higher. If the View Agent was below 6.1 or no View Agent was displayed, ENHANCED mode cannot be activated.
Once this issue was resolved, I ran the above command again and saw the following output and the web page :
All connection servers are ready for ENHANCED mode All security servers are ready for ENHANCED mode All RDS servers are ready for ENHANCED mode All machines are ready for ENHANCED mode
The view admin page then indicated that i needed to restart the message bus service on the connection servers and once the service was restarted ENHANCED mode became greyed out indicating it was now being activated.