Veeam Availability Orchestrator cannot add vCenter Server or standalone host due to time difference
| KB ID: | 2656 |
| Product: | Veeam Disaster Recovery Orchestrator |
| Version: | 1.x |
| Published: | 2018-05-22 |
| Last Modified: | 2020-08-13 |
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:
4. Start Veeam ONE Monitor and Veeam ONE Reporter services.
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 Disaster Recovery Orchestrator |
| Version: | 1.x |
| Published: | 2018-05-22 |
| Last Modified: | 2020-08-13 |
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!
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
