https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMzY2IiwiaGFzaCI6IjkxY2Q0ODg2LTQyNzQtNDEwNy1iY2MxLTdjNDU1NmJkOGUyZiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Unable to install VAC management agent on Cloud Connect server after VAC migration

Challenge

After migrating your Veeam Availability Console (VAC) installation to a new server, the following error message pops up when trying to add an existing Veeam Cloud Connect (VCC) server that was managed by the previous installation:
 
Failed to install management agent on the Cloud Connect server

Cause

Adding the VCC server installs the VAC management agent on it which is required for communication between the two products. The error above means that the VAC service was unable to re-register the existing management agent. 

Solution

1. Manually remove the existing VAC Communication Agent from the Control Panel snap-in on the VCC server: 

User-added image

2. Add the Cloud Connect server in VAC UI:

User-added image

More information

If you have any questions, contact Veeam Support.
KB ID:
2366
Product:
Veeam Service Provider Console
Version:
2.x
Published:
2017-11-14
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later