Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.
Disable Time Sync on Windows server on Domain
I have a supplier of software who wants to test some date related functions within MS SQL2008R2
Their stored procedures use GETDATE() and GETUTCDATE() to get the date, which reads from the underlying Windows 2012 server with MSSQL.
Their solution is to change the system date on the SQL server whenever they want to do their testing of date functions.
However, the Active Directory, quite rightly, changes the system time back to the correct PDC emulator time within 10-20 minutes.
Ive tried moving the AD object into a Test OU and block all Group Policy inheritence to ensure it isnt a GPO that is changing the time
Is there anyway, apart from dropping the server off the domain, that I can stop the Windows 2012 server from syncing its time from the Active Directory?
The server needs to remain on the domain for other parts of the software testing.
Their stored procedures use GETDATE() and GETUTCDATE() to get the date, which reads from the underlying Windows 2012 server with MSSQL.
Their solution is to change the system date on the SQL server whenever they want to do their testing of date functions.
However, the Active Directory, quite rightly, changes the system time back to the correct PDC emulator time within 10-20 minutes.
Ive tried moving the AD object into a Test OU and block all Group Policy inheritence to ensure it isnt a GPO that is changing the time
Is there anyway, apart from dropping the server off the domain, that I can stop the Windows 2012 server from syncing its time from the Active Directory?
The server needs to remain on the domain for other parts of the software testing.
Asked:
-
4
2
- +1
3 Solutions
Hi Kaffiend,
I understand that we will break the ability to login with a domain account while the time is incorrect.
The idea is that just during the testing, the date is changed.
They DO NOT log out of the machine while the date is incorrect.
They change it back to correct time before they logout
A reboot or logging in with a local account to re-adjust the time will allow domain accounts to log back in, if they forget to change it or get booted off for some reason.
What would the registry change be to set the server as its own time source?
I understand that we will break the ability to login with a domain account while the time is incorrect.
The idea is that just during the testing, the date is changed.
They DO NOT log out of the machine while the date is incorrect.
They change it back to correct time before they logout
A reboot or logging in with a local account to re-adjust the time will allow domain accounts to log back in, if they forget to change it or get booted off for some reason.
What would the registry change be to set the server as its own time source?
Sorry I don't remember what the change is. It's in notes that I have kept through the years but it's at home and thus, not handy : (
This article (even easier than regedit) will help you achieve the same thing:
https://technet.microsoft.com/en-us/library/cc757721(v=ws.10).aspx
This article (even easier than regedit) will help you achieve the same thing:
https://technet.microsoft.com/en-us/library/cc757721(v=ws.10).aspx
Go to CMD, run the following:
That will set the w32tm service to stop syncing. Running this will return it to normal:
w32tm /config /syncfromflags:no /update
That will set the w32tm service to stop syncing. Running this will return it to normal:
w32tm /config /syncfromflags:domhier /update
You will not want to reconfigure the time service for that; that change is permanent, so if for whatever reason the change isn't undone, a reboot won't cure the problem.
If they continue with that, it's best to just stop (and I mean "Stop", not set to "Disabled") the time service, either with services.msc (Windows Time), or in an elevated command prompt or Powershell: net.exe stop W32Time.
That said, instead of changing the system time, they should consider using a wrapper function to get the time, and set the wrapper function to either return the true time or an offset time based on whatever debugging arguments they need.
If they continue with that, it's best to just stop (and I mean "Stop", not set to "Disabled") the time service, either with services.msc (Windows Time), or in an elevated command prompt or Powershell: net.exe stop W32Time.
That said, instead of changing the system time, they should consider using a wrapper function to get the time, and set the wrapper function to either return the true time or an offset time based on whatever debugging arguments they need.
Hi all
Thanks for the help.
@oBdA - A reboot does fix the time when ive reconfigured the syncfromflag.
Maybe its a group policy we have, but a reboot resets the time to the correct time
But, stopping the service also works.
@acbrown2010 - Thanks, w32tm /config /syncfromflags:no /update worked fine for me.
@kaffiend - thanks for pointing me in the right direction to look it up myself. Teach a man to fish etc...
Thanks for the help.
@oBdA - A reboot does fix the time when ive reconfigured the syncfromflag.
Maybe its a group policy we have, but a reboot resets the time to the correct time
But, stopping the service also works.
@acbrown2010 - Thanks, w32tm /config /syncfromflags:no /update worked fine for me.
@kaffiend - thanks for pointing me in the right direction to look it up myself. Teach a man to fish etc...
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
So, if you don't need any kind of authentication or security tokens, you might be able to get away with doing this.
A registry change to make the server use itself as a time source would probably work (but remember to keep in mind my first 2 statements)