Domain time did not fall back -- Server 2008R2
Our Server 2008R2 Domain did not fall back over the weekend and the domain is now an hour ahead. PCD emulator is not sync'd to an outside time server. How can I get the domain back in time sync with out disrupting service or crashing the domain?
2008R2 should have the 2007 DST fix. Was this upgraded from 2003?
The problem is, if everything is happy, that means that the 1 hour off is machine time correct. If you move the clock, you're going to have domain issues. I'd wait until after hours....
If you have to, set your time zone off one hour so the user sees the correct time.
The problem is, if everything is happy, that means that the 1 hour off is machine time correct. If you move the clock, you're going to have domain issues. I'd wait until after hours....
If you have to, set your time zone off one hour so the user sees the correct time.
ASKER
This is not an upgrade, so I am pretty sure the DST fix is not an issue.
Strangely, when one opens the clock from the task bar, it says "Daylight Savings Time ended on Sunday, November 01, 2015 at 2:00 AM. The clock went back 1 hour at that time.", but it obviously did not.
Strangely, when one opens the clock from the task bar, it says "Daylight Savings Time ended on Sunday, November 01, 2015 at 2:00 AM. The clock went back 1 hour at that time.", but it obviously did not.
Have you tried to restart the Windows Time service on the PDC?
I would also be checking the Event Viewer as well to see if there is any reference to the time issue on your server.
Will.
I would also be checking the Event Viewer as well to see if there is any reference to the time issue on your server.
Will.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
THis is very odd, like other experts as stated this should not be an issue expecially with an upgrade. Have you checked your event logs and/ or checked to see your time services to see if it is running
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Compdigit44 -
Just keep in mind that OTHER applications don't always utilize UTC only. I had a time issue with a system and got it sorted out, but Exchange hub transport went crazy and we needed to restart it (Minor, but fyi.) Same deal with Goldmine on the same server.
Just keep in mind that OTHER applications don't always utilize UTC only. I had a time issue with a system and got it sorted out, but Exchange hub transport went crazy and we needed to restart it (Minor, but fyi.) Same deal with Goldmine on the same server.
ASKER
So. Without knowing what would happen by just going back an hour on the PDC emulator, I have been going back 3 minutes at a time (a normal file stamp error fudge, I have read) and letting everything sync back up. This has been going well, even though this maybe a gorky solution.
The larger issue is indeed that the PDC was only syncing to "LOCL", and will change that to the ntp.org as suggested by dipersp, since we use ntp.org in our xenserver hosts.
Will let you know how it all goes ultimately.
The larger issue is indeed that the PDC was only syncing to "LOCL", and will change that to the ntp.org as suggested by dipersp, since we use ntp.org in our xenserver hosts.
Will let you know how it all goes ultimately.
ASKER
It's been stable now for a week, and things look ok.
Synced to ntp.org timeservers.
Adjusting the time back incrementally ultimately worked fine but was a pain.
Root cause, I believe was that the FSMO roles were transferred to this machine at some point and time services were not reconfigured for the authoritive time server role that the machine became.
Thanks for the help!
Synced to ntp.org timeservers.
Adjusting the time back incrementally ultimately worked fine but was a pain.
Root cause, I believe was that the FSMO roles were transferred to this machine at some point and time services were not reconfigured for the authoritive time server role that the machine became.
Thanks for the help!
Just checking - any reason for the b grade? Anything that could have been done better?
ASKER
I guess while we were hitting all around the fixes we never got to a definitive "when this happens do this" ... Nothing bad, just thought we were all incomplete.
Make sense?
Make sense?
ASKER