conf.adm file in the default domain controller's policy

  • Thread starter Thread starter Corey
  • Start date Start date
C

Corey

After promoting a windows 2000 server to a domain
controller, I get an error saying that replication has
stopped because the event time associated with a file is
too far in the future. The file is conf.adm which is an
adminstrative template for netmeeting, I took the file
out of the default domain controller's policy and insured
that the file date was the same on all my dc's, but
replication still bombs out with same error. Has anyone
ever had this problem. All my dc's have the latest
updates and all are windows 2000 servers with sp4.
 
Hello Corey.

Please take a look at the following knowledge base article. It details file
replication issues resulting from having the clock set incorrectly and how
to fix them:
289668 Advancing Time on Production Computers and the Effect on Active
http://support.microsoft.com/?id=289668

David Fisher
Enterprise Platform Support
 
Back
Top