Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows Server 2003 / Active Directory / July 2005

Tip: Looking for answers? Try searching our database.

2 Existing DC's on 2k, replaced by 2 new DCs on 2k3, FAQ?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
A Transfinite Number of Monkeys - 29 Jul 2005 21:01 GMT
Here's the scenario going on at our church...

3 servers, all running 2k.  2 of them are DCs, the other is just a
member server.  One of the DCs is already an Exchange 2000 server.

We received a donation of 2 nicely packed out servers.  We'd like to
re-purpose our existing hardware, so a migration seems to be in order
here.

Thus far, here's what I've done:

1. changed from Domain Mode to Native Mode on the AD, and verified that
the changes replicated to the other DC.

2. sometime after the work day's done today, I'm changing the Exchange
2000 from Mixed Mode to Native Mode and rebooting that system.

What I think needs to be done as next steps..  Feel free to slap me
about the head if I'm doing something stupid or leaving something out...

1. Install 2k3 Server on one of the new systems, make sure it's happy

2. On the DC that holds the Exchange 2k and the schema (since it's the
first 2k server that was installed, the schema is there, right?), do
what scenario #2 on mskb # 325379 says to do (make some ldif, run a
couple of commands from the command line, then adprep /forestprep and
adprep /domainprep)

3. Run dcpromo on the new 2k3 server, turn it into a DC

4. Install Exch2k3 on the new 2k3 server.
  - Do I install this as an additional server in the site?

5. Migrate mailboxes
  - How do I get the GAL, and other shared stuff to reside on the new
server?
  - How do I move the users' mailboxes over to the new server?
  - Do their Outlook clients get automatically updated to point to the
new server when they next startup?

What I've done thus far has been very simple and straightforward, but
the many kb articles and dozens of write-ups on the yet-to-do stuff, all
with different information make me long for the simplicity of openldap,
cyrus & postfix. :-)

Thanks for any pointers...

--j
Ulf B. Simon-Weidner [MVP] - 29 Jul 2005 23:38 GMT
Hi,

I snipped the message and answered inline

> Here's the scenario going on at our church...
[..]
Everything OK so far

> 2. On the DC that holds the Exchange 2k and the schema (since it's the
> first 2k server that was installed, the schema is there, right?),

You can find out who's the schema fsmo owner, one way is to type the command
"netdom query fsmo".

> do what scenario #2 on mskb # 325379 says to do (make some ldif, run a
> couple of commands from the command line, then adprep /forestprep and
> adprep /domainprep)

Yes

> 3. Run dcpromo on the new 2k3 server, turn it into a DC

Yes - keep your network settings for name resolution in mind: Configure the
DNS-Client prior to DCPromo.

> 4. Install Exch2k3 on the new 2k3 server.
>   - Do I install this as an additional server in the site?

Yes. Do you install Exchange on the DC or on a different server? If I
remember correctly it's recommended to keep Exchange on a Memberserver if
possible.

> 5. Migrate mailboxes
>   - How do I get the GAL, and other shared stuff to reside on the new
> server?

As far as I know the GAL will be synced automatically, other shared stuff
(like public folders) will have to be configured by you (set up public
folder replication)

>   - How do I move the users' mailboxes over to the new server?

This is directly done in the GUI as far as I know, you can even schedule
this.

>   - Do their Outlook clients get automatically updated to point to the
> new server when they next startup?

Yes it will (assuming that you use current versions of Outlook)

> What I've done thus far has been very simple and straightforward, but
> the many kb articles and dozens of write-ups on the yet-to-do stuff, all
> with different information make me long for the simplicity of openldap,
> cyrus & postfix. :-)

Thanks for that smile ;-)

Sorry - I'm not very deep into Exchange, so if you need instructions where
exactly to configure the stuff maybe someone else will step in or you can
reask those questions in the Exchange Newsgroup.

If you want to demote the old servers later make sure of the DNS-Servers,
transfer FSMO-roles, make sure the time service is reconfigured, export and
save the private certificate of the EFS-Recoveryagent (usually default
domain-admin on the first box you ever had).

Signature

Gruesse - Sincerely,

Ulf B. Simon-Weidner

 MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
 Weblog: http://msmvps.org/UlfBSimonWeidner
 Website: http://www.windowsserverfaq.org 

Hank Arnold - 30 Jul 2005 10:35 GMT
If it's possible, I'd keep the DC w/o Exchange intact. Set up one new server
as Exchange 2003 and the other as a DC. Migrate the Exchange 2000 mailboxes,
etc., over to the new Exchange box and de-commission the old server.

Obviously, somewhere in all this, you will be upgrading the domain to
W2K03....

You'll be much better off IMNSHO, with Exchange being on a separate server
from a DC.....

Signature

Regards,
Hank Arnold

> Here's the scenario going on at our church...
>
[quoted text clipped - 44 lines]
>
> --j
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.