Before you begin, take a snapshot/backup of the vCenter server before making changes.
This KB is for removing the vProxy based "Dell EMC NetWorker" vSphere plug-in. For instructions on removing the legacy VBA "EMC Backup and Recovery" plug-in, see NetWorker: How-To Remove VBA EMC Backup and Recovery (EBR) plug-in from vCenter Server
- Log in to the vCenter mob extension manager at https://<vCenter FQDN or IP>/mob/?moid=ExtensionManager
- Use your normal vCenter web client credentials
- Unregister the following VBA plug-in extensions:
- com.dell.emc.nw
- com.emc.networker.backup
- com.emc.networker.recover
- com.emc.vproxy.visd
- Check the following locations on the vCenter server, remove any entries associated with Dell or EMC.
WARNING: Double check all commands before removing files from the vCenter server. This process must be completed by the VMware vCenter Administrator.
- /etc/vmware-vpx/locale/
- /etc/vmware-vpx/extensions/
- /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/
- /etc/vmware/vsphere-ui/cmCatalog/
Example of vCenter 7.0.x with NetWorker 19.9.x plug-in installed:
root@vcsa [ ~ ]# ls -l /etc/vmware-vpx/locale/ | grep "dell\|emc"
-rw-r--r-- 1 root root 40157 May 16 16:35 com.dell.emc.nw_catalog.zip
-rw-r--r-- 1 root root 372 Jul 11 2023 com.emc.networker.backup_catalog.zip
-rw-r--r-- 1 root root 377 Jul 11 2023 com.emc.networker.recover_catalog.zip
root@vcsa [ ~ ]#
root@vcsa [ ~ ]# ls -l /etc/vmware-vpx/extensions/ | grep "dell\|emc"
drwxr-xr-x 3 root root 4096 May 16 16:35 com.dell.emc.nw
drwxr-xr-x 3 root root 4096 Jul 11 2023 com.emc.networker.backup
drwxr-xr-x 3 root root 4096 Jul 11 2023 com.emc.networker.recover
root@vcsa [ ~ ]#
root@vcsa [ ~ ]# ls -l /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/ | grep "dell\|emc"
drwxr-xr-x 2 vsphere-ui users 4096 May 16 16:35 com.dell.emc.nw-19.9.0.29
root@vcsa [ ~ ]#
root@vcsa [ ~ ]# ls -l /etc/vmware/vsphere-ui/cmCatalog/ | grep "dell\|emc"
-rw-r--r-- 1 vsphere-ui users 40157 May 16 16:36 com.vmware.cis.com.dell.emc.nw.zip
-rw-r--r-- 1 vsphere-ui users 372 May 15 20:50 com.vmware.cis.com.emc.networker.backup.zip
-rw-r--r-- 1 vsphere-ui users 377 May 15 20:50 com.vmware.cis.com.emc.networker.recover.zip
- Restart the vSphere web client service
- service-control --status vsphere-client
- service-control --stop vsphere-client
- service-control --start vsphere-client
- Clear browser cache and cookies
- Open a fresh browser
- Log back into vCenter web client at https://<vCenter FQDN or IP>
For EOSL NetWorker configurations using a Windows vCenter Server.
NOTE: The following steps must be completed by the VMware vCenter Administrator. These steps are not to be performed by NetWorker support.
Windows vCenter Server
1. log in to the vCenter mob extension manager at
https://<vCenter FQDN or IP>/mob/?moid=ExtensionManager
- Use your normal vCenter web client credentials
2. Unregister NetWorker vProxy plug-in extensions if present
- com.emc.networker.backup
- com.emc.networker.recover
- com.emc.networker
- com.dell.emc.nw
- com.emc.vproxy.visd
3. Remove all NetWorker and vProxy related entries from vSphere web client catalog
- The vSphere web client catalog is located at \ProgramData\VMware\vSphere Web Client\catalog\VirtualCenter\5.5.0\en on vCenter 5.5
- The vSphere web client catalog is located at \ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog on vCenter 6.0
4. Remove all NetWorker related entries (ex: com.emc.networker, com.emc.networker.backup, com.emc.networker.recover) from the vCenter server vc-packages directory
- vCenter server 5.5 vc-packages directory: \ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity
- vCenter server 6.x vc-packages directory: \ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity
5. Reset the SerenityDB on the vCenter server
- SerenityDB is located at \ProgramData\VMware\vSphere Web Client\SerenityDB\serenity on vCenter 5.5.
- SerenityDB is located at \ProgramData\VMware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity on vCenter 6.0.
- There should be no entries remaining after this has been cleared.
- This is vCenter web client user cache, similar to Windows C:\Users directories.
- The only impact is that each user will experience a slight delay the next time they log in, as this is being re-created.
6. Restart the vSphere web client service
- This can be done through services.msc.
- Allow 5-10 minutes to pass after starting service before continuing.
- Restarting this service only temporarily prevents access to the vCenter using the web client while service is restarted.
7. Clear browser cache
8. Open a fresh browser
9. Log back into vCenter web client at
https://<vCenter FQDN or IP>:9443/vsphere-client/