Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Issues when Horizon View Servers when deployed with dissimilar FIPS mode configurations (67009)

Last Updated: 1/23/2023Categories: TroubleshootingTotal Views: 11212Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Connection Servers in the same POD deployed with different FIPS modes configurations are unable to communicate.

Recent Connection Server  software deployment installation logs contain lines similar to:

(C:\ProgramData\VMware\logs\vmmsi.log_YYYYMMDD_xxxxxx.log ) contain "VDM_FIPS_ENABLED = 0"

Registry Key

"HKLM\Software\VMware, Inc.\VMware VDM\FipsMode"
Value: 1 if installed or 0 if not installed

The View Admin console will not come up on a Connection Server if deployed into a Horizon View POD with FIPS mode enabled, but FIPS mode was not selected as an option during deployment on this server,

Messages similar to the following are seen in connection server logs :

vdm-logs/debug-YYYY-MM-DD-XXXXXX.txt

2023-01-26T17:55:00.942-05:00 DEBUG (10E8-13D0) <Outbound JMS Error Responder Thread> [JMSRouter] Error creating topic config for topic: IceTunnelTopic com.vmware.vdi.logger.Logger.debug(Logger.java:44)
javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1002)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)

Messages similar to the following are seen in vdm-logs/messagebus/info.log:

2023-01-26 17:55:58.351/[NioTCPListener, swiftlet=sys$jms, port=4002]/INFORMATION/connection accepted: 127.0.0.1
2023-01-26 17:55:58.374/127.0.0.1:53240/NioHandler/INFORMATION/SSL Handshake exception, initiating delayed EXIT (1000ms): javax.net.ssl.SSLHandshakeException: no cipher suites in common
2023-01-26 17:55:59.401/127.0.0.1:53240/NioHandler/INFORMATION/close

Purpose

To identify if an existing Connection Server / Security Server has FIPS mode enabled in order to confirm all deployed Connection Server / Security Server components are operating with FIPS mode enabled (or disabled).

Cause

A non-functional environment is expected when Connection Servers are deployed in different FIPS mode configurations.

If a FIPS mode deployment is intended, all Connection Servers and View Agents are expected to also be in FIPS mode.

If a FIPS mode deployment is not intended, all Connection Servers and View Agents are expected to not be deployed in FIPS mode.

Impact / Risks

View Desktops must run the same FIPS mode configuration as all the Connection Servers.

Switching FIPS mode deployments may require that View Agent software be redeployed to match the FIPS mode deployment model.

Resolution

Before deploying a Connection Server or Security Server in FIPS mode, FIPS mode must be enabled at the Windows OS level. More information from Microsoft on FIPS can be found here:FIPS 140-2 Validation

Typically FIPS mode configuration is deployed by GPO, it can also be turned on by setting the following registry key:

HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled = 1

Confirm your intended deployment configuration (FIPS mode enabled/disabled).

Identify Connection Server(s) / Security Server(s) that were deployed with incorrect FIPS mode configuration.

Uninstall Connection Server / Security Server software on those servers

Reinstall Connection Server / Security Server software and deploy with the correct FIPS mode configuration.

Related Information

If a Connection Server was deployed with FIPS mode enabled, you can expect to see log messages from the log-YYYY-MM-DD.txt (or debug-YYYY-MM-DD.txt) file that look like the following:

INFO  (0D4C-165C) <localhost-startStop-1> [ServerConfigurationFilter] Broker started in FIPS mode
INFO  (155C-1734) <Thread-2> [Ice] Server started in FIPS mode

If FIPS is enabled in the GuestOS (regardless of if FIPS was enabled when the Connection Server / Security Server was deployed), you can expect to see the following log entry in log-YYYY-MM-DD.txt (or debug-YYYY-MM-DD.txt):

INFO  (1240-2ED8) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault: Initiating in FIPS mode

To reiterate, the "KeyVault: Initiating in FIPS mode" log message is only an indication that the GuestOS has FIPS enabled. It does not suggest (and should not be used to indicate) that the Connection Server was deployed with FIPS enabled.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
View Client でデフォルト プリンタのリダイレクトを無効にする (2012770)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
登录到 vCenter Server Appliance 失败并显示错误：无法对用户进行身份验证 (2147174)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant