Service Discovery not collecting or in "Warning" state

Products

• VCF Operations
• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Issues with Service Discovery
  
  
• VM Service discovery collection not working
  
  
• VM object in Inventory: Properties|Guest OS Services| Authentication Method has switched to "Guest Alias"
  
  
• VMs Running VMTools 13.0.5 show SDMP as failed and the Collection Status is grayed out
  
  
• You may see errors for the VMs in the collector for the Service Discovery adapter (or cloud proxy) similar to the following:
  
  YYYY-MM-DDTHH:MM:SS,MS+0000 ERROR [pool-#-thread-#] (<ID>) com.vmware.adapter#.applicationdiscovery.activeprobe.controller.DiscoveryTaskRunner.runNetworkProbes - [<fqdn>] Received authentication error from VM : <VM Name>. Ignoring rest of the probes
YYYY-MM-DDTHH:MM:SS,MS+0000 ERROR [pool-#-thread-#] (<ID>) com.vmware.adapter#.applicationdiscovery.guestoperation.impl.WindowsRemoteGuestOperationImpl.runProgramIn
Guest - [ Host: <fqdn>, VM moid: vm-#####] Failed to start Program in Guest
com.vmware.vim.binding.vim.fault.InvalidGuestLogin: Failed to authenticate with the guest operating system using the supplied credentials.


• In the Events log in vCenter for the affected virtual machines, you may see this error: com.vmware.vc.guestOperations.GuestOperationAuthFailure

Environment

Aria Operations 8.18.x

VCF Operations 9.0.x

Cause

An issue in the formatting of the namespace value in com.vmware.vrops.sdmp

This issue has been found with VMs running 13.0.5 and 12.5.x versions of VMware Tools.

Resolution

For Linux VMs

• Open VM Tools (open-vm-tools) Service Discovery Plugin is the recommended method for Linux based service discovery collection.
  
  
• Follow the VMware vRealize Operations 8.2.x and Later section of Credential-less Service Discovery functionality in vRealize Operations 8.1.x and later 
  
  

For Windows VMs

• Delete the Namespace from the VM in the vCenter MOB using Credential-less Service Discovery is not working post VMTools 13.0.5 upgrade
  
  
• For multiple Windows VMs, use the script attached in the Additional Information Section.
  
  
  • The script will remove the namespace for all VMs associated in the vCenter.
    
    
  • To address the service discovery in multiple vCenters, just run the script multiple times addressing each vCenter at a time.
    
    
  • Linux VMs will be unaffected