w32time service on windows 2003 PDC

  • Thread starter Thread starter Igor Karasik
  • Start date Start date
I

Igor Karasik

Hi,
Recently we add two windows 2003 Domain controllers to our Active Directory
domain and transferred domain PDC role to windows 2003 R2 server.
We configure windows 2003 PDC to use an internal hardware clock according :
http://support.microsoft.com/kb/816042
(I set AnnounceFlags to "A")

I set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
to "NoSync" as well.
http://technet2.microsoft.com/Windo...9b9b-44e7-a7f3-f89c2fca87ea1033.mspx?mfr=true


I also disable NTP client
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\Enabled
= 0

The problem: I still have event id 36 "The time service has not
synchronized the system time for 86400 seconds because none of the time
service providers provided a usable time stamp. The time service is no
longer synchronized and cannot provide the time to other clients or update
the system clock. Monitor the system events displayed in the Event Viewer
to make sure that a more serious problem does not exist" in system events.

Is it normal behaviour ?

Thanks, Igor

P.S. With windows 2000 DC we just configure "net time /setsntp:DCName", but
I understand it's not relevant for windows 2003
 
Jorge,
I did registry changes as you wrote in blog,
but today I again receive event 36.
Any more suggestions ?
Thanks, Igor

Igor Karasik said:
Jorge, Thanks !

I will try recommendations from your blog.
Can you explain why in http://support.microsoft.com/kb/816042
AnnounceFlags
recommended settings is "A" ?

Thanks, Igor

"Jorge de Almeida Pinto [MVP - DS]"
see:
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/111.aspx

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
Click to expand...
Click to expand...
 
http://www.eventid.net/display.asp?eventid=36&eventno=1405&source=W32Time&phase=1

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Igor Karasik said:
Jorge,
I did registry changes as you wrote in blog,
but today I again receive event 36.
Any more suggestions ?
Thanks, Igor

Igor Karasik said:
Jorge, Thanks !

I will try recommendations from your blog.
Can you explain why in http://support.microsoft.com/kb/816042
AnnounceFlags
recommended settings is "A" ?

Thanks, Igor

"Jorge de Almeida Pinto [MVP - DS]"
see:
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/111.aspx

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Hi,
Recently we add two windows 2003 Domain controllers to our Active
Directory domain and transferred domain PDC role to windows 2003 R2
server.
We configure windows 2003 PDC to use an internal hardware clock
according :
http://support.microsoft.com/kb/816042
(I set AnnounceFlags to "A")

I set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
to "NoSync" as well.
http://technet2.microsoft.com/Windo...9b9b-44e7-a7f3-f89c2fca87ea1033.mspx?mfr=true


I also disable NTP client
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\Enabled
= 0

The problem: I still have event id 36 "The time service has not
synchronized the system time for 86400 seconds because none of the
time service providers provided a usable time stamp. The time service
is no longer synchronized and cannot provide the time to other clients
or update the system clock. Monitor the system events displayed in the
Event Viewer to make sure that a more serious problem does not exist"
in system events.

Is it normal behaviour ?

Thanks, Igor

P.S. With windows 2000 DC we just configure "net time
/setsntp:DCName", but I understand it's not relevant for windows 2003
Click to expand...
Click to expand...
Click to expand...
 
Jorge, thanks
I saw this link but it's not help me prevent event 36....
Igor

"Jorge de Almeida Pinto [MVP - DS]"
http://www.eventid.net/display.asp?eventid=36&eventno=1405&source=W32Time&phase=1

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Igor Karasik said:
Jorge,
I did registry changes as you wrote in blog,
but today I again receive event 36.
Any more suggestions ?
Thanks, Igor

Igor Karasik said:
Jorge, Thanks !

I will try recommendations from your blog.
Can you explain why in http://support.microsoft.com/kb/816042
AnnounceFlags
recommended settings is "A" ?

Thanks, Igor

"Jorge de Almeida Pinto [MVP - DS]"
see:
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/19/111.aspx

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Hi,
Recently we add two windows 2003 Domain controllers to our Active
Directory domain and transferred domain PDC role to windows 2003 R2
server.
We configure windows 2003 PDC to use an internal hardware clock
according :
http://support.microsoft.com/kb/816042
(I set AnnounceFlags to "A")

I set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
to "NoSync" as well.
http://technet2.microsoft.com/Windo...9b9b-44e7-a7f3-f89c2fca87ea1033.mspx?mfr=true


I also disable NTP client
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\Enabled
= 0

The problem: I still have event id 36 "The time service has not
synchronized the system time for 86400 seconds because none of the
time service providers provided a usable time stamp. The time service
is no longer synchronized and cannot provide the time to other
clients or update the system clock. Monitor the system events
displayed in the Event Viewer to make sure that a more serious
problem does not exist" in system events.

Is it normal behaviour ?

Thanks, Igor

P.S. With windows 2000 DC we just configure "net time
/setsntp:DCName", but I understand it's not relevant for windows 2003
Click to expand...
Click to expand...
Click to expand...
 
Back
Top