Time Service

  • Thread starter Thread starter dan
  • Start date Start date
D

dan

When a W2K/WXP client is in a workgroup the client is configured to use
time.windows.com for time sync. When the client joins an AD domain is
switches to use the domain hierarchy. We seem to have a random number of
client who when joined to the domain are unable to time sync and are
actually still attempting to sync to time.windows.com still.

Can someone tell me what time service setting (registry or other) are
modified by the act joining a domain and what those settings are changed to.
If others have experienced this scenario what did you do to correct this bad
behavior.

Thanks in advance.
Please CC replies to (e-mail address removed)
Dan Rhoads
 
When a W2K/WXP client is in a workgroup the client is configured to use
time.windows.com for time sync. When the client joins an AD domain is
switches to use the domain hierarchy. We seem to have a random number of
client who when joined to the domain are unable to time sync and are
actually still attempting to sync to time.windows.com still.

Can someone tell me what time service setting (registry or other) are
modified by the act joining a domain and what those settings are changed to.
If others have experienced this scenario what did you do to correct this bad
behavior.

Thanks in advance.
Please CC replies to (e-mail address removed)
Dan Rhoads
Click to expand...
See Type at tip 2273 in the 'Tips & Tricks' at http://www.jsiinc.com

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
Back
Top