RE: Windows 2003 Active Directory

  • From: "adrian bolzan" <abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 8 Mar 2005 15:17:38 +1100

> -----Original Message-----
> From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx]
> Sent: Tuesday, 8 March 2005 10:40 AM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Windows 2003 Active Directory
> > When I upgraded to AD from NDS I did not really understand the
> > ramifications of using one of my public domain names as our
> AD domain
> > name, nor did the service integrator I engaged.  Nor did
> they realise
> > that exchange should not be installed on a DC.  As such I am now
> > planning a domain rename, as well as demoting the DC with
> exchange to
> > a member server,
> Well, I hate to be the bearer of bad news, but demoting a
> server that is both a DC and Exchange will cause additional
> problems. (Like you really want
> more.) The problem is Exchange has to connect to a DC, and
> one that is a GC.
> If Exchange is installed on a DC, it will look to itself for
> AD only. You will need to research this as there are KB on
> how to change the DC Exchange looks for.

Do not fear, you are not the bearer of bad news.
I have read docs (and will re-read, anyway) and queried this list, as
We have two DC's, one hosting exchange.  The plan is to:
- Build another Exchange server (Exchange2) as a member server
- move mailboxes to the new server (Exchange2)
- uninstall Exchange from the DC
- demote the DC to a member server
- install exchange again on this server
- move mailboxes back to the newly installed exchange
- decommission the temporary Exchange server (Exchange2)

This leaves us with only one DC but we only have about 100 staff
accessing this DC.

Hopefully this will be a relatively smooth transition.


IMPORTANT - This email and any attachments is confidential.
If received in error, please contact the sender and delete
all copies of this email. Please note that any use,
dissemination, further distribution or reproduction of this
message in any form is strictly prohibited. Before opening or
using attachments, check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused
by the negligence of the sender or not, resulting directly or
indirectly from the use of any attached files, our liability
is limited to resupplying any affected attachments. 
Any representations or opinions expressed in this email are
those of the individual sender, and not necessarily those
of the Capital Transport Group.

Other related posts: