[HCX] Understanding HCX VM Cutover Schedule Behavior Based on Local Time Configuration
search cancel

[HCX] Understanding HCX VM Cutover Schedule Behavior Based on Local Time Configuration

book

Article ID: 323660

calendar_today

Updated On:

Products

VMware HCX VMware Cloud on AWS

Issue/Introduction

This knowledge base article aims to clarify this behavior and its dependency on local time settings.


Symptoms:
The customer will observe the scheduled cutover time for an HCX migration relies upon the browser's set timezone.

Cause

The cutover time scheduled through the HCX UI is intricately linked to the timezone configuration of the machine from which the HCX dashboard is accessed. This means that the time you see in the HCX dashboard reflects the timezone of your local system or the timezone of the machine acting as the jump box.

 

For instance, if your local machine's timezone is set to GMT, the cutover schedule displayed in the HCX dashboard will be in GMT. Conversely, if another user's system is configured with an EST timezone, they will observe the cutover schedule in line with the EST timezone.

Resolution

This is an expected behavior by design.

The cutover time displayed in the HCX dashboard is closely tied to the timezone configuration of the machine you are using to access HCX. By understanding this relationship and ensuring consistent timezone settings, you can effectively schedule and coordinate VM cutover activities across different timezones, promoting accurate planning and successful migration operations.