On Wed, Oct 7, 2009 at 11:15 AM, Free, Bob <[email protected]> wrote: > W2K? I Thought you were doing this on 2003.
No, I am doing this as preparation of testing upgrading my Win2000 AD to Win2003 AD. And the testing has already revealed deficiencies in my production settings (such as links between sites, etc) that is paying off ... Next step is the forest/schema prep, and then the big one - DCPROMOing of a member Win2003 server (in the parent domain), and see if it works. Followed by a similar procedure on a Win2003 server in the child domain ... > Sounds like a symptom of > Replication Metadata Preservation. They *should* go away in 2 weeks. > > > http://blogs.dirteam.com/blogs/jorge/archive/2008/02/09/rpc-errors-and-w > eird-repadmin-output-after-demotion.aspx > > http://technet.microsoft.com/en-us/library/cc772726(WS.10).aspx > > How Replication Metadata is Preserved in Windows Server 2003 > The period of time during which the replication metadata of the NTDS > Settings object is maintained after Active Directory is removed from the > respective domain controller is determined by an attribute of the > Directory Service object (cn=Directory Service,cn=Windows > NT,cn=Services,cn=Configuration,dc=ForestRootDomainName). This > attribute, replTopologyStayOfExecution, has a default value of 14 days > and a maximum value of half the tombstone lifetime. Yep, sounds like me. Thanks! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
