Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > 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: 867 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