Operational Defect Database
BugZero found this defect 3566 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1918
Uninstalling Veeam Collectors if a System Resource Pool Was Used for Auto-Deployment
Last update date:
11/19/2020
Affected products:
Veeam Management Pack for Microsoft System Center
Affected releases:
9.0
Fixed releases:
No fixed releases provided.
Description:
Purpose
If during auto-deployment of Veeam Collectors one of the system resource pools was used (All Management Servers Resource Pool, Notifications Resource Pool or AD Assignment Resource Pool), you will need to use the workaround described below to remove all collectors automatically.
Cause
Uninstallation of all collectors is required.
Solution
Log on to Veeam Extensions Server (VES) and run regedit. Locate the following key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Virtualization Extensions for VMware\Managerand set the value ResourcePool to a blank value. This will trigger uninstallation of all collectors, which can take up to 8 hours depending on the size of your infrastructure. To speed it up, you can restart HealthService on the VES Server.
More Information
If you have any questions, please, contact Veeam Support.
