Strange problem with BIOS time

[goppi]

Today I tried to create a new VM and was wondering why unattended installation of Windows no longer works. I found out that this was caused by Kerberos failure as a consequece of inaccurate system time.

Then I boot into the VMs BIOS and found that the time is one hour off the local time and also one hour off the time which is displayed in vSphere client for the ESXi host.

This has worked flawlessly in the past there was no need to adjust the BIOS time after creating a new VM.

Any idea why the BIOS time of the newly created VM is one hour off compared to local time?

Thanks.

Cheers.

[DSTAVERT]

ESXi uses UTC. Make sure the time on the ESXi host is correct and is using NTP to sync it's own time.

[goppi]

So maybe I'm on the wrong track.

If timesync is working properly (which seems to be the case here as all machines including ESXi have the correct time) what time should be displayed for a newly created VM when you enter the BIOS on first boot.

Thanks.

Cheers.

[Cocheese21]

I would check the the BIOS time on the host, this may be where you're VM is pulling it's initial time from during creation. 

Hope this helps!

[MauroBonder]

see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1436

in my opinion the problem is clock of hardware. in this kb have a command to sync date and hour the system with hardware

[goppi]

Can anyone else confirm what time a newly created VM shows in it's environment when it is first booted into it's BIOS after creation?

Does it show UTC or local time or anything else?

Thanks.

[goppi]

come on please :smileycry:

Anybody out there who can create a new VM, boot into BIOS and see what time the BIOS shows (local or UTC)

Thanks.

Cheers.

[DSTAVERT · Accepted solution]

UTC time in BIOS on start.

[goppi]

THX