Re: Decommision Domain Controller

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Todd hobdey (hobdey_at_bmhcdotcom.com)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 10:55:08 -0700

I'm sure there are other issues as well, but three come to mind: DNS, FSMO
roles and tombstone age.

The moved domain controller will need a DNS server on the new network that
has the right entries. Your production DCs will also be generating errors
trying to replicate to what is essentially a "down" DC.

When you remove the DC from your production network, you need to make sure
the FSMO roles are all held by other DCs, but in the test environment the
migrated server would need to seize those roles. When you go to put it back
in the production network you'd have role conflicts.

If the moved DC is off the production network for more than the tombstone
age (60 days, I believe), it won't be able to resync with the production
DCs.

Like I said, I'm sure there are more issues than this. The bottom line is I
wouldn't be inclined to try it - I think your chances of screwing up your
production environment are pretty high.

What you might consider instead is to build a test environment from scratch
and use ldifde to export your users and import them into the new
environment.

"Joe" <anonymous@discussions.microsoft.com> wrote in message
news:16a1a01c417b5$aab95a90$a301280a@phx.gbl...
> Sorry, realised that I haven't given enough info.
>
> What I would like to do is to create a test environment
> where I can test our disaster recovery procedure for our
> Exchange server.
>
> My plan is:
> 1. Create a new DC on the Domain.
> 2. Remove the DC from the network and place it on a
> private network.
> 3. Attach a W2k server to the private network.
> 4. Restore Exchange to the W2k server.
> --- Assuming the restore works fine ---
> 5. Return the DC to the corporate network.
> 6. Decomission the DC.
> 7. Reformat the restored Exchange server.
>
> If anyone can point me to a detailed procedure for doing
> this or something similar I would be very grateful. Any
> other advice would be most welcome too.
>
> Thanks,
> Joe
>

Relevant Pages

  • Re: Decommision Domain Controller
    ... >When you remove the DC from your production network, ... >in the production network you'd have role conflicts. ... >> What I would like to do is to create a test environment ... Reformat the restored Exchange server. ...
    (microsoft.public.win2000.active_directory)
  • Re: Front End/Back End communication
    ... Taking all of Devin's ideas into consideration, one can also use ISA Server ... utilizing a perimeter network relationship on the "internal" facing ISA ... This topology extends the protected network "out," allowing you to ... the benefits of the FE Exchange Server in the DMZ are ...
    (Focus-Microsoft)
  • Re: RPC over HTTPS woes
    ... I have gone over just about every article in my attempt to set up RPC ... on the on the exchange server: ... directory tab> application name rpc> execute permissions: ... Outside the the network, i receive the logon but never connects, ...
    (microsoft.public.exchange.admin)
  • Re: Activesync OTA OK but USB fails - partnership issues?
    ... Have you tried Activesync 4.2 (I've heard some flakiness with 4.5 ... Have you downloaded the White paper on using WM5 in an SBS network? ... I want to be able to use the existing Exchange Server settings ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook 2007 cant connect to exchange 2000
    ... WINS and DNS settings? ... >> resolved' when entering the Microsoft Exchange Server. ... >> another machine and create an Outlook profile that works. ... >> There are no other network issues with this machine - that I can tell. ...
    (microsoft.public.exchange.connectivity)