Network Time Server Settings Used in Domain after FSMO Transfer?
I just finished transferring FSMO roles from at 2003 domain controller to a 2012 domain controller. Everything seems to be ok. I am just wondering, do all of the NTP time server source settings migrate to the new FSMO domain controller, or do I need to set this up again?
What are the commands to check what IP address active directory (or is it a particular DC) is pulling NTP updates from?
Running the w32tm /query /configuration on the older server 2003 R2 DC states that the command is not recognized. I vaguely remember having to use some other depreciated command to on the old DC to get this info in the past, but I cant remember what this was. I think it was the Net time command, which I would execute to quickly find out, but there is a caution about running this command on a server that is using Windows Time Service.
Executing the w32tm command on the 2012 DC, displays a bunch of technocratic data that is particularly useful. IE no listing of any NTP servers in the output.
I found the following link, but take a look at the minuscule size of the scroll bar! LOL, I don't want to have to read through that just to find a OS consistent command to list current NTP sources. Argggggle!
I ran the following command on my computer w32tm /query /source and the results show one of the older non PDCEs. Then I log into the new server 2012 PDCE and run the same command and it points to the previous 2003 PDCE, that has since had this role transferred. I then run the following command on it net time /querysntp and it has a list of 4 ntp servers.
Executing the w32tm command on the 2012 DC, displays a bunch of technocratic data that is particularly useful. IE no listing of any NTP servers in the output.
I found the following link, but take a look at the minuscule size of the scroll bar! LOL, I don't want to have to read through that just to find a OS consistent command to list current NTP sources. Argggggle!
Link...
https://technet.microsoft.com/en-us/library/71e76587-28f4-4272-a3d7-7f44ca50c018
Thanks again for your efforts :-)