Order of installation for 2nd DC & Exchange replacement server

Currently the domain has a single DC (computer name: DATA) running
Windows Server 2000 SP4, Exchange 2003 SP1. We've recently purchased
a Windows Server 2003 machine (computer name: EMAIL) that I'd like to
promote to be a DC as well as running Exchange.

If I could, I'd like to confirm that my order of actions is correct -
any and all feedback/info is much appreciated:

A) Install Exchange Server 2003 SP2 on DATA
B) adprep /forestprep (on DATA)
C) adprep /domainprep (on DATA)
D) Join EMAIL to domain
E) DCPROMO of EMAIL
F) Make sure EMAIL is a GC (Global Catalog server)
G) Install IIS on EMAIL
H) Install Exchange on EMAIL & Patch to SP2
I) Move the mailboxes from DATA to EMAIL via the "Move mailbox"
functionality - first by testing test accounts, then moving user
accounts.


1) Please let me know if anyone can see any problems with above.
2) I'm unclear as to when I should install IIS on EMAIL. According
to http://support.microsoft.com/kb/332097 - running DCPROMO after
install IIS breaks IIS. But this MS tech note just details how to
recover from that situation - it doesn't say how to avoid it.

Thanks again for any info or feedback

.

Relevant Pages

  • How do Install IIS 6 on my Win2003 server?
    ... How do Install IIS 6 on my Win2003 server? ... I am getting ready to install Exchange 2003 on my new ... Windows 2003 server and it wants IIS on there. ...
    (microsoft.public.inetserver.iis)
  • Re: Exchange Server 2003 Fails install at Step 6 of checklist (For
    ... I am attempting to install Exchange Server 2003 on my Win Server 2003 std. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.exchange.setup)
  • Re: Exchange Server 2003 Fails install at Step 6 of checklist (For
    ... I am attempting to install Exchange Server 2003 on my Win Server 2003 std. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.exchange.setup)
  • Re: Error 1332: No mapping between account names and security IDs was done - after dcpromo
    ... That is mean, if you installed Exchange 2003 on a member server, please ... This secure code will be valid for 6 months ... able to update your profile and access the the partner newsgroups. ... For example, if you install Exchange ...
    (microsoft.public.windows.server.migration)
  • Re: Exchange 2007 on a domain controller
    ... "Jetze Mellema (MS MVP)" wrote in message ... For security and performance reasons, we recommend that you install Exchange 2007 only on member servers, and not on Active Directory directory servers. ... After Exchange 2007 is installed, changing its role from a member server to a directory server, or vice versa, is not supported. ...
    (microsoft.public.exchange.design)