I have recently shifted my FSMO roles from old server 2000 SP4 PDC to new server 2008R2 so all 5 FSMO roles are now on server 2008 R2 confirmed. i have ensured that server 2008 R2 is configured as reliable time server for my forest and have condifured it NTP and changed the reg key on Old Server 2000 DC "type" key to NT5DS. when i stop and restart the time service on server 2008 R2 it log the 143, 139 event "The time service has started advertising as a good time source" and as a time source. and in about a minute it logs the warning "The time service has stopped advertising as a good time source" and event 35 saying "the time service is now synchronizing the system time with the time source "old 2000 DC server". I want to decomission the old DC server 2000 SP4 this is the last step that is not working out. any ideas why server 2008 Is probaly behaving like this.Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...

Hello, why you configured your 2008 R2 server as a NTP server? If it is the PDC emulator then your domain computers / servers will sync time with it. I recommand that you configure it as a NTP client so that it will sync time with a public time server but don't configure domain computers / servers as NTP clients because they will sync with the PDC Emulator holder. Have a look to this Microsoft article about how to change Windows time service configuration on the previous PDC emulator: http://technet.microsoft.com/fr-fr/library/cc738042(WS.10).aspx This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

All I wanted to configure is My PDC sync time with external time source & All client computers sync time with my PDC. I had this setup in server 2000 SP4 which was the only DC and FSMO holder, i recently migrated to server 2008 R2 and now wants it to be main source for time for all clinet computers in the forest/domain. can you please clarify is this is correct terminology.Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...

I tried running that on previous PDC emulator server and here is the results nothing happens, looks like command is new and command file is old. C:\Documents and Settings\Administrator>w32tm /config /syncfromflags:domhier /re liable:no /updatew32tm /config /syncfromflags:domhier /reliable:no /update w32tm [ -tz | -s [computer] | -adj | -adjoff | -source | -once ] [-test] [-v] [-p <port>] [-period <freq>] Primary options: -tz print the local time zone info and exit. -s [<computer>] force the given computer (or the local computer if none is given) to resynchronize, then exit. -adj set the computer's system clock frequency to the last frequency determined during synchronization, then exit. -adjoff set the computer's system clock frequency the system default, then exit -source choose a synchronization source, then exit. Note that a source is chosen before each synchronization, so this is useful only in showing that a source could be found. Remember to use -v to see the output. -once do only one synchronization, then exit. Otherwise, run continuously as a client, synchronizing the local clock until ctrl-c is pressed. The program will also run as a server any time the service would (when it is on a DC, or when the registry flag is set). The following options can be used in conjunction with the above: -test prevent the time on the local system from actually being modified. -v print out a verbose description of what the program is doing. This is usually needed since otherwise the program produces no output. The exceptions are -s and -tz. -p <port> set the server port. -period <freq> set the sync period just as in the registry. That is: 0 == once a day 65535 == once every 2 days 65534 == once every 3 days 65533 == once every week (7 days) 65532 == once every 45 min until we get 3 good syncs, then once every 8 hrs (3/day) 65531 == once every 45 min until we get 1 good sync, then once every day Otherwise, <freq> times per day. C:\Documents and Settings\Administrator>Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...

You will get the needed information from Meinolf article in his blog: http://msmvps.com/blogs/mweber/archive/2010/06/27/time-configuration-in-a-windows-domain.aspx To configure your PDC as NTP client you can proceed by two ways: Use registry modifications: To configure a NTP client, you can do it by proceeding to modify these register entries: SYSTEM\CurrentControlSet\services\W32time\Config\AnnounceFlags= 0 SYSTEM\CurrentControlSet\services\W32time\Parameters\NtpServer = the IP address or the DNS name of your NTP server SYSTEM\CurrentControlSet\services\W32time\Parameters\Type = NTP Use w32tm commands: http://technet.microsoft.com/fr-ch/library/w32tm(v=WS.10).aspx Like I told you, I recommand that: All your client computers to sync with the PDC emulator Your PDC Emulator sync with a public time server This is the best terminology that I see. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

K so i did exact as you mentioend i and i configured my new PDC to sync with "time.nrc.ca" it went find and same shit after a minute or so it stops and start syncing with my old PDC emulator which is no more a PDC emulator and all FSMO are on new server 2008. here are the events i have highligted bold lines. ----------------------------------------- Log Name: System Source: Microsoft-Windows-Time-Service Date: 05/04/2011 12:54:26 PM Event ID: 139 Task Category: None Level: Information Keywords: User: LOCAL SERVICE Computer: abc.domain.com Description: The time service has started advertising as a time source. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Time-Service" Guid="{xxxxCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" /> <EventID>139</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2011-04-05T16:54:26.793375000Z" /> <EventRecordID>3169</EventRecordID> <Correlation /> <Execution ProcessID="876" ThreadID="520" /> <Channel>System</Channel> <Computer>abc.domain.com</Computer> <Security UserID="S-1-5-19" /> </System> <EventData Name="TMP_EVENT_START_ADVERTISING"> </EventData> </Event> ----------------------------------------- Log Name: System Source: Microsoft-Windows-Time-Service Date: 05/04/2011 12:54:26 PM Event ID: 143 Task Category: None Level: Information Keywords: User: LOCAL SERVICE Computer: abc.domain.com Description: The time service has started advertising as a good time source. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Time-Service" Guid="{0000CFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" /> <EventID>143</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2011-04-05T16:54:26.793375000Z" /> <EventRecordID>3170</EventRecordID> <Correlation /> <Execution ProcessID="876" ThreadID="520" /> <Channel>System</Channel> <Computer>abc.domain.com</Computer> <Security UserID="S-1-5-19" /> </System> <EventData Name="TMP_EVENT_START_ADVERTISING_GT"> </EventData> </Event> ------------------------------------ Log Name: System Source: Microsoft-Windows-Time-Service Date: 05/04/2011 12:54:42 PM Event ID: 144 Task Category: None Level: Warning Keywords: User: LOCAL SERVICE Computer: abc.domain.com Description: The time service has stopped advertising as a good time source. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Time-Service" Guid="{0000CFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" /> <EventID>144</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2011-04-05T16:54:42.809000000Z" /> <EventRecordID>3172</EventRecordID> <Correlation /> <Execution ProcessID="876" ThreadID="3032" /> <Channel>System</Channel> <Computer>abc.domain.com </Computer> <Security UserID="S-1-5-19" /> </System> <EventData Name="TMP_EVENT_STOP_ADVERTISING_GT"> </EventData> </Event> ------------------------------- Log Name: System Source: Microsoft-Windows-Time-Service Date: 05/04/2011 12:54:42 PM Event ID: 35 Task Category: None Level: Information Keywords: User: LOCAL SERVICE Computer: abc.domain.com Description: The time service is now synchronizing the system time with the time source oldpdc.domain.com (ntp.d|0.0.0.0:123->10.240.43.3:123). Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Time-Service" Guid="{0000CFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" /> <EventID>35</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2011-04-05T16:54:42.809000000Z" /> <EventRecordID>3173</EventRecordID> <Correlation /> <Execution ProcessID="876" ThreadID="3032" /> <Channel>System</Channel> <Computer>abc.domain.com </Computer> <Security UserID="S-1-5-19" /> </System> <EventData Name="TMP_EVENT_TIME_SOURCE_CHOSEN"> <Data Name="TimeSource">oldpdc.domain.com(ntp.d|0.0.0.0:123-&gt;10.240.43.3:123)</Data> </EventData> </Event> ----------------------------------- Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...

Before you took away the time service role from the 2000 server did you use the TZEdit application to adjust the daylight savings time start/end dates? When I moved my time service from a 2000 to a 2008 server I had to adjust this and then take away the FSMO roles or I got this same error message as have posted about. I actually had to reassign the role to the 2000 server, use tzedit, and then take the role back away and decommission the server.

Hi, Please refer to the following Microsoft KB article to configure the Windows Server 2008 R2 Domain Controller as an authoritative time server. How to configure an authoritative time server in Windows Server http://support.microsoft.com/kb/816042 If it does not work, please also refer to the following Microsoft TechNet articles for further troubleshooting information. Event ID 144 — Time Service Advertisement http://technet.microsoft.com/en-us/library/cc756457(WS.10).aspx Event ID 145 — Time Service Advertisement http://technet.microsoft.com/en-us/library/cc756468(WS.10).aspx Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Wow... Tanner thats so surprising... but i am sure there must be a way i dont find any such article at microsoft for what you did above... i am sure MVPs shoudl test this in theri lab and put up an article for us to follow, because if above is the case then its rediculas behaviour... such an advance OS not able to obay the commandments of Administrators... hah... Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...

Ok non help though arthur_Li suggetion to enable debugging of evetn id 145 helped identify that my PDC is trying where to sync time from ... and it was same old server ... so i decided to give a try on my wild thought... i stopped the time service on my Old DC and stop/start time service on new PDC. and waited about 10 minute it remained as a good time source. and after i started the time serive on old dc and guess what ..... my new server 2008 is now a good time rsouce it remained so no issues i will monitor this for the rest of the day. my new server 2008 must remain as a good time source and should not stop and begin sync with my old server 2000. MS to digg in to this and prep the article and fix for this.Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...

Hello, i never had problems reconfiguring the time service from an old Windows 2000 PDCEmulator to Windows server 2003 or higher OS version with the command line, w32tm, on the new ones and changing the one registry key on Windows 2000. So i can't say the documentation is wrong. Often i have seen that improper registry changes are the reason for this. Unfortunal the KB article for the time configuration change relise on modifying the registry instead using the basic w32tm commands which fully enuogh to change the time settings in the domain. Registry changes are only recommended for having specific requirements which is also specified in http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx under "Windows Time Service Registry Entries".Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hello, i never had problems reconfiguring the time service from an old Windows 2000 PDCEmulator to Windows server 2003 or higher OS version with the command line, w32tm, on the new ones and changing the one registry key on Windows 2000. So i can't say the documentation is wrong. Often i have seen that improper registry changes are the reason for this. Unfortunal the KB article for the time configuration change relies on modifying the registry instead using the basic w32tm commands which fully enough to change the time settings in the domain. Registry changes are only recommended for having specific requirements which is also specified in http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx under "Windows Time Service Registry Entries". Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Meinolf i have posted the results above to prove the issue, and the resolution i made is intact till now since this morning. I exactly followed your steps in the blog article you wrote and i only had the hitch with this step so definitely something is wrong there. Maybe you can repeat the scenario in lab environment. And registry modification i was very careful with while making so honestly speaking it’s not just what you wrote for time registry key for new PDC emulator, I feel like this will be a challenge for you.Je jeevan ma masti nathi te jeevan ni hasti nathi ane masti vali jindagi malvi kai sasti nathi...