Windows Server 2012 keeping time issue on HP Blade
I have installed Windows Server 2012 on an old Blade Server (BL460c G1). HP only support 2012 on there newer servers - but I thought I would give it a whirl as the hardware seemed fine.
It is working a treat except it can't keep time (big issue). It is hard to pinpoint a pattern to its failure to keep correct time. It may be fine for a day and then lose an hour or slowly start to lose time.
I have worked around issue by setting a task to automatically sync with an internet time service, but was wondering if anyone had seen such an animal.
It is working a treat except it can't keep time (big issue). It is hard to pinpoint a pattern to its failure to keep correct time. It may be fine for a day and then lose an hour or slowly start to lose time.
I have worked around issue by setting a task to automatically sync with an internet time service, but was wondering if anyone had seen such an animal.
David Johnson, CD
I would contact HP Support it still under warranty. Is this the primary domain controller? Windows Servers sync with the PDC normally.. it might be something as simple as replacing a cmos battery.
ASKER
Thanks ve3ofa,
No unit is quite old and no longer under warranty. And as mentioned Win2012 is actually not supported on BL460cG1 by HP.
No it is not a PDC - it as actually just a member server for running HyperV. It was previously a storage server - but with 20GB of RAM and plenty of disks is ripe for use as a VM Host.
The CMOS battery is for system clock which is different to Windows Time keeping as far as I understand. I did replace the battery (just for the sake of $1 - I thought it would be crazy not to try). Still same.
Crazy part is the random nature of it. It will sometimes keep time no problem then all of a sudden have a bit of a slow moment.
No unit is quite old and no longer under warranty. And as mentioned Win2012 is actually not supported on BL460cG1 by HP.
No it is not a PDC - it as actually just a member server for running HyperV. It was previously a storage server - but with 20GB of RAM and plenty of disks is ripe for use as a VM Host.
The CMOS battery is for system clock which is different to Windows Time keeping as far as I understand. I did replace the battery (just for the sake of $1 - I thought it would be crazy not to try). Still same.
Crazy part is the random nature of it. It will sometimes keep time no problem then all of a sudden have a bit of a slow moment.
What's the time setting on the blade enclosure OA?
ASKER
Hi andyalder,
I am embarrased to say I had not checked the OA time. I can't say that I see a relationship between OA and Blade in relation to time patterns - but to be honest I was trying all the easy things first and this should be right up there at the top...
Anyway just checked the OA time and it was wrong and set to manual config. So I have set to correct time and region.
See if this change has any bearing - but as luck would have it the time has been fine since I posted this issue (proir to that it would occur at least once a day).
** Does the OA have an onboard battery to hold this time on power off?
I am embarrased to say I had not checked the OA time. I can't say that I see a relationship between OA and Blade in relation to time patterns - but to be honest I was trying all the easy things first and this should be right up there at the top...
Anyway just checked the OA time and it was wrong and set to manual config. So I have set to correct time and region.
See if this change has any bearing - but as luck would have it the time has been fine since I posted this issue (proir to that it would occur at least once a day).
** Does the OA have an onboard battery to hold this time on power off?
I'm not sure about the OA having a battery, I suppose it must have or everything would be a mess after a power outage. Normally I set it to use an NTP server.
I did install some Windows servers without setting the OA clock and after a a reboot they had the wrong time as the blades had set their RTCs from the OA, makes you wonder why they bother to put a battery on each blade.
I did install some Windows servers without setting the OA clock and after a a reboot they had the wrong time as the blades had set their RTCs from the OA, makes you wonder why they bother to put a battery on each blade.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Provided suitable workaround but in no way offered reason for issue.