Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Unable to add ESX 5.5 vCenter servers to Orion server on Windows 2003 SP2

Unable to add ESX 5.5 vCenter servers to Orion server on Windows 2003 SP2

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 842 Votes: 0 Revisions: 6

Issue:

Unable to add ESX 5.5 vCenter to an Orion server running on Windows 2003 SP2 for Network Performance Manager (NPM). 

Cause:

The Orion server was not able to connect to VMware Management Web Service components due to increased security of the cipher strengths introduced in vSphere 5.1. Older Windows operating systems such as Windows 2003 SP2 do not support higher cipher strength.

Resolution:

To build the cipher strength to accept new higher certificates (2048KB), install the hotfix for Server 2003. For more information, refer to the Microsoft KB article An update is available to add support for the TLS_RSA_WITH_AES_128_CBC_SHA AES128-SHA and TLS_RSA_WITH_AES_256_CBC_SHA AES256-SHA AES cipher suites in Windows Server 2003.

Last modified

Tags

Classifications

Public