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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNjU2IiwiaGFzaCI6ImIwYzgwZjFlLTllNTAtNDkzYi1iMWU5LTZkMmRhYjZkZmE4NyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam Availability Orchestrator cannot add vCenter Server or standalone host due to time difference

Challenge

When you try to add a VMware vCenter Server or a standalone VMware ESXi with a different time zone, the operation may fail with an error informing that time difference between Veeam Availability Orchestrator and the remote host is too large.

Solution

To resolve the issue, follow the next steps:

1. Stop Veeam ONE Monitor and Veeam ONE Reporter services.

2. Open the registry and navigate to the HKEY_LOCAL_MACHINE\Software\Veeam\Veeam ONE Monitor\Service registry key.

3. Create a new entry with the following parameters or modify if exists:
 
Name: MaxTimeDiff
Type: DWORD
Value: the value that can cover the time difference in seconds

4. Start Veeam ONE Monitor and Veeam ONE Reporter services.
KB ID:
2656
Product:
Veeam Availability Orchestrator
Version:
1.x
Published:
2018-05-22
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