Solved

Windows 2003 Default Domain Controller Policy Time Sync issues

Posted on 2010-11-23
3
1,152 Views
Last Modified: 2012-08-14
I am trying to clean up 2003 directory services. I am getting W32Time errors all over the domain controllers and clients. On the domain controllers, I have the default domain policy pointing at time.apple.com; NTP; defaults- and the time server enabled for directory services which does not seem to be working, I'm guessing I may have overlooked something and need a second opinion. We have mac's in house and management thought this was a better approach than the default windows time server.

My default domain policy aims at my PDC with 0x02 to round robin to all domain controllers, but I have a domain controller that was demoted and is in the environment as a member server hosting a critical web app, for some reason clients are trying to target this server as a time source and domain controller. Can I perform a partial metadata cleanup of some sort to remove the pointer to it as a replication/time partner without destroying the computer object to retain the web application?
0
Comment
Question by:mlarivie
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 15

Assisted Solution

by:Lee Osborne
Lee Osborne earned 75 total points
ID: 34199894
I used this article a couple of weeks ago to tidy up my forest and time sync:

http://robsilver.org/ad/demystifying-time-in-a-forest/

I now have a perfectly sync'd forest, DC's and workstations, and everything is tidy! A couple of things I noted which were handy, were to remove any GPO settings for time sync and keep them as default, and to reset the w32tm configs on the servers and then set them up accordingly (W32tm /unregister, W32tm /register).

Lee
0
 
LVL 31

Accepted Solution

by:
Justin Owens earned 350 total points
ID: 34199898
In a typical AD scenario, here is how your time hierarchy should work:

1. PDCe Points to the Internet

Your server hosting the PDCe Role points to the Internet somewhere (I like tick and tock, the USNavy's servers).  You can find them here.

2. All Other Domain Controllers Point to the PDCe

In a typical AD, your other DCs should automatically point to your PDCe.

3. AD Members Point to Their Logon Server

Member servers and workstation should get their time from the DC which authenticates them onto the network.
If this is not how you are set up, I would change it to this functionality.  I would avoid using Apple as a time server for a Windows AD on general principle.  Though I have no proof, I have seen too many cases where it messes up to trust Apple to not be doing something screwy to make Windows machines not work correctly.

On your PDCe, you can set the time server from the command line by typing:

NET TIME /SETSNTP:tick.usno.navy.mil (or whatever public time server you wish to use)

In the event that your PDCe is not in the domain as the authoritative time server, follow the directions in this document:

http://support.microsoft.com/kb/816042

Let me know how those changes affect your scenario.

DrU
0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 75 total points
ID: 34200403
Here is a great link from tigermatt on setting up Time for AD.

http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/

I would not use a GPO to sync time
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
Had a business requirement to store the mobile number in an environmental variable. This is just a quick article on how this was done.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question