Skip to main content

Hi.  I looked in the community for this situation but couldn't find it exactly.  I'm using the Commcell Console on my Azure virtual desktop (Windows 10 Enterprise).  The AVD is in the central US region and my desktop shows that it is in the US central time zone (UTC - 6 hours).  

Times for all jobs in the Job Controller, Restore History, Backup History, and the Schedule next run time are all showing as UTC.  

On my laptop, also in US central time zone, when I view the same Job Controller, Restore History, Backup History, and schedules, the times are all properly displaying as US central time.  

I tried clearing the cache on my Java (version 8, update 231) but it didn't make a difference.  I have one coworker with the same conditions and another who seems to be unaffected.  

Any suggestions? 

Thanks! 

Hi ​@swaldrop 

Request to review below settings and time zone used on the Commserv.

  1. From the CommCell Console ribbon, on the Tools tab, click User Preferences.

  2. On the Date and Time formats tab, select the date and time formats to use in the CommCell Console.

    https://documentation.commvault.com/11.20/modifying_look_and_feel_of_commcell_console.html 


Hi Pradeep.  Good idea, thank you.  I compared the User Preferences>Date and Time formats just now. 

The settings on my Azure virtual desktop are identical to the settings on my laptop.  Under Time Zone, Current system time zone is checked.  If I switch my Azure VD to User defined time zone, the Time Zone is properly identified as UTC-6:00 US central time. 

After switching the setting to User defined time zone, the job controller, job reports, and schedules all show the time correctly.  I am in the same time zone as our CommServe server so the times also display properly if I switch the setting to use the CommServe time zone. 

Either of these is a valid work-around for me but it is interesting that the system time zone on the Azure VD is being read by Commcell Console as UTC. 


Hi ​@swaldrop 

If the settings are not defined properly, its expected to use system time zone.


Reply