New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?

Votes:

0

Your Vote:

Up

Down

Since upgrading to VCSA version 6.5 Update 1, my VMware sensors are in a Down status due to invalid credentials. How can I fix this?

prtg vmware vmwaresensor

Created on Feb 28, 2018 2:45:19 PM by  Brandy Mauff [Paessler Support]

Last change on Mar 2, 2018 11:25:19 AM by  Brandy Mauff [Paessler Support]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor version 17 or later

AD Authentication Not Working with VCSA 6.5 Update 1

If you have issues with VMware sensors in a Down status because of invalid credentials since updating to VCSA 6.5 Update 1, this may be because VMware modified the Identity Source settings.

As of this version, Active Directory (Integrated Windows Authentication) is now set by default. With this setting, the sensors can no longer authenticate themselves with the vCenter Server using the AD credentials by default and are therefore in a Down status. Because the sensors are using username/password for authentication, you have to explicitly enable LDAP integration for the identity source as this authenticates based on the given credentials.

Configure a New Identity Source with LDAP Integration in vCenter

  • Log in to the vSphere Web Client interface as Single Sign-On administrator. For example, as administrator@vsphere.local.
  • Go to Administration | Single Sign-On | Configuration.
  • On the Identity Sources tab, click the + button to add a new identity source.
  • Make sure to select Active Directory as an LDAP Server.

Active Directory as an LDAP Server Setting

  • Configure the identity source as usual using your AD information.
  • Click OK to save the new identity source.
  • Click Test Connection to check the connection to the new identity source.

Your VMware sensors can now successfully authenticate themselves and will return to an Up status.

Note: Alternatively, you can configure a local user in your vSphere environment. Then you do not have to change the LDAP settings manually.

More

For more detailed information, see the VMware documentation.

Created on Feb 28, 2018 4:44:33 PM by  Brandy Mauff [Paessler Support]

Last change on Mar 6, 2018 1:26:40 PM by  Gerald Schoch [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.