RE: Disaster Recovery Planning for Exchange

  • From: "Carl Houseman" <c.houseman@xxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 22 Sep 2005 13:07:00 -0400

I should say, this is the simplified method.  The details would have more
steps, e.g. replicate/re-home public folders and other "first exchange
server" stuff.  The general idea remains as stated.  You should not demote a
domain controller (or promote to a DC) while Exchange is installed.

-----Original Message-----
From: Carl Houseman [mailto:c.houseman@xxxxxxxxx] 
Sent: Thursday, September 22, 2005 1:00 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Disaster Recovery Planning for Exchange

1. Install Exchange on a member server in the same organization.
2. Move mailboxes from original to new Exchange server.
3. Remove Exchange from domain controller. 

-----Original Message-----
From: Scott Clarke [mailto:scott.clarke@xxxxxxxxxxxx] 
Sent: Thursday, September 22, 2005 9:36 AM
To: [ExchangeList]
Subject: [exchangelist] Disaster Recovery Planning for Exchange

Hi all,

We are in the process of completing a DR plan.  Our Exchange 2000 server
was installed about two years ago and was the first W2K server to be
installed...thus it is the root domain controller and DNS server for the
domain.

Personally, I do not like this setup.  Does anyone know the best way to
have the Exchange server NOT be the DC for the domain?


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
webelists-exchangelist@xxxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx



Other related posts: