Our config is currently:

  • 1 Windows 2000 domain controller running ISA2000, dhcp, dns
  • 1 Windows 2003 domain controller as main file server, prob cert server as well, dhcp, dns
  • 1 Windows 2008/Exchange2010 domain controller as Exchange server, DHCP,DNS

Currently getting FRS errors on files server journalwrap error Currently getting FRS errors on other DC's can't replicate from above

Exchange DC holds Schema, rid, pdc, and infrastructure roles File Server holds Domain naming operation master role

WOW, I didn't set this up, just inherited it. Am I right to assume that fixing the FRS errors is #1, what do I need to do for that? set enable journalwrap auto restore in registry?

Demote W2000 domain controller, should that have any implications for ISA? We have Forefront to be deployed but that's another day

Transfer Domain Naming Role to Exchange server (I know or think having an Exchange server as DC isn't best practice) We will be getting another server W2008 to replace current file server and I thought it could takeover all roles once deployed

Demote W2k3 file server and then raise functional domain level to 2008

Am I missing anything other that the sense to walk away?


  • How large is the AD organization? # of users/computers/groups/objects? Are those all of the servers or just the ones with DC roles? I ask because my first thought is (if possible) to look at consolidation, clean up of roles, and using ADMT to move everything to a new clean domain structure. – TheCleaner Dec 17 '12 at 17:13
  • How is this even possible as Exchange 2010 is not supposed to install if there is a windows 2000 DC in the domain.. – Rex Dec 17 '12 at 17:25
  • 4
    Don't walk away. RUN. – Massimo Dec 17 '12 at 17:44
  • 2
    I've always told myself that "create a new forest and migrate accounts and data over to it" is rarely the right answer to a domain upgrade, but you've certainly managed to show me an exception to that. I'd not even think about upgrading this mess until you've sorted out precisely what is going on and got it stable. – Rob Moir Dec 17 '12 at 19:09
  • Either migrate to a new domain and have the clients deal with the down time or run away from the environment ASAP. – MDMarra Dec 20 '12 at 13:27

Please refer these link..

Hope it helps for you




Hope it helps for you.

  • 4
    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference. – Scott Pack Dec 20 '12 at 13:25
  • 1
    Well if the person would read the links he would get the essentials part of the answer but anyways i got this i would keep in mind to post the essentila part and then the link – Richard Wilson Dec 24 '12 at 8:55
  • 1
    The point of StackExchange is to actually have the content directly. In 6 months those links might not work anymore, at which point, this answer is completely irrelevant. Or even worse, and I've seen this happen frequently, the site admins change something and those links go someplace else entirely! Damn dirty sticky wickets. – Scott Pack Dec 24 '12 at 13:36
  • agreeing to your statement trully its true after 6 months link might not work any more – Richard Wilson Dec 27 '12 at 12:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.