Re-register EAM extension to vCenter

Products

• VMware vCenter Server 7.0
• VMware vCenter Server 8.0

Issue/Introduction

The purpose of this article is to provide instructions on how to re-register the EAM extension to vCenter. Please note, if EAM is non-functional but still appears in the web client, this procedure will not resolve the issue.

Symptoms:

• The EAM extension has been removed from vCenter in the Administration - Solutions - vCenter Server Extensions
• EAM is no longer able to manage agent installs on ESXi hosts from vCenter or products connected to vCenter, such as NSX.
• The below KBs to update the certificate of the EAM extension do not help - 
  • Upgrading or Patching vCenter Server to 8.0 U2 fails with precheck error "Source vSphere ESX Agent Manager (EAM) upgrade failed to obtain EAM URLs to check against trusted certificates by the System"
  • How to Replace Expired Certificates on vCenter Server using Fixcerts Python Script(322249)

Environment

• VMware vCenter Server 8.0.x
• VMware vCenter Server 7.0.x

Cause

• The EAM extension was accidentally unregistered from the vSphere HTML5 client.

Resolution

This is an issue with accidental deletion of EAM extension.
Hence, please reach out to Broadcom support team for further assistance on this issue.

Additional Information