Re: Upgrading from 2000 Server w/ Exchange 5.5

OK thanks so much, 1 more question though :)

"I'm assuming that Exchange 2000 schema updates have not been applied to the
domain. If they have, pay special attention to the article above."

I'm not sure what updates this is referring to and although I dont think its
been done how would I check to verify?

Thanks!


"Oli Restorick [MVP]" wrote:

Hi there

This is probably the easiest of the three scenarios to do -- certainly from
the point of view of being able to migrate step by step and to have the
option of stepping back if things don't go to plan.

So, your first step would be to get some hardware and install Windows Server
2003 on it. Of course, you will need to buy the server license and get
Windows Server 2003 CALs if you don't already have those.

You'd be buying Windows Server 2003 R2 now, but if you don't need the extra
functionality of R2, just install from CD 1 (which is essentially Windows
Server 2003 SP1) and ignore CD 2. The CALs required for R2 are the same as
those for Windows Server 2003.

Before you make the Windows Server 2003 box a domain controller, you must
run adprep /forestprep and adprep /domainprep on the existing domain
controller. If you're installing R2, use the adprep version from the second
CD not the one from the first CD.

Upgrading from a Windows 2000 domain
http://technet2.microsoft.com/WindowsServer/en/Library/bc5ebbdb-a8d7-4761-b38a-e207baa734191033.mspx

I'm assuming that Exchange 2000 schema updates have not been applied to the
domain. If they have, pay special attention to the article above.

I'd also set the original DC to AD-integrated DNS if it is not already
configured this way.

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/kb/237675/en-us

Once you've done that, you can dcpromo the Windows Server 2003 (or R2) box
into the existing domain.

One that's done, test that DNS is correctly configured and is replicating
properly between the domain controllers. In particular, ensure you have a
DNS forwarded set up for your new server to allow resolution of Internet DNS
names.

Assuming everything looks good, you will want to update the DHCP server to
point clients at both DNS servers (the new one as a primary and the old one
as a secondary).

Enable the new server as a global catalogue. You will then want to transfer
the FSMO roles (operation master roles) to the new server.

Ensure your backup routine is backing up both servers. From here, migrate
any files, folders, shares and printers as needed to the new server.

Then you want to set about migrating from Exchange 5.5 to Exchange Server
2003. Go for Exchange 2003 SP2 to take advantage of the 75Gb limit
(increased from 16Gb) in Standard Edition.

Once everything's migrated, you should be able to temporarily shut down the
old box and test that there are no bad effects from it being switched off.
Depending on whether you want to upgrade this box to Windows Server 2003,
you will want to dcpromo it out of the domain before rebuilding it. When
dcpromoing a DC that uses AD-integrated DNS out of a domain, be aware that
the lack of a DNS database on the machine after you've done that will mean
that the server will forward all queries out to the Internet (including ones
for your internal DNS domain).

As for fault-tolerance, by having two DCs, you automatically have failover
for the AD side of things. This is a good thing. Losing your AD is
definitely not something you want to do. If you get R2 on both machines,
you may as well replicate all user files between the two servers using DFS
Replication.

DFS Management
http://technet2.microsoft.com/WindowsServer/en/Library/bc5ebbdb-a8d7-4761-b38a-e207baa734191033.mspx

As you seem to appreciate already, providing a fault-tolerant Exchange setup
isn't quite so easy.

One option (which I have yet to investigate properly) is to use something
like Symantec LiveState Recovery.

Another option is something like NeverFail, but it's priced out of the reach
of a lot of small businesses. Again, I haven't used NeverFail, so I'm
mentioning it for your awareness that than recommending it.

You may want to do some reading about the Exchange part of the upgrade and
perhaps post any Exchange-specific follow-up questions to an Exchange group.

Hope this helps

Oli






"MHTB Matt" <MHTBMatt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:991A567A-A994-4A52-A489-1CCA7B65DC5D@xxxxxxxxxxxxxxxx
Thanks for the reply and to clarify:

The end result is to end up with Windows Server 2003 and Exchange 2003 on
the same system.

A little more info for you is that the customer would like to have a
backup
system(just hardware) set aside incase the main server crashes. So with
that
in mind, the preference would be to upgrade them to 2003 Server with 2003
Exchange as well as migrate to new hardware and then use the old system
for a
backup system to recover to with backup tapes if needed.

Basically the request for a backup system is what I need to figure out but
they arent going to want to go with the cost of mirrored servers with
failover etc. And I dont think buying a new server box with no OS is going
to
work as a backup considering they currently are running Windows 2000 and
Exchange 5.5. From what I've read already, restoring there current server
to
new hardware isnt going to work becasue of different hardware etc. Plus I
would like to get them off Exchange 5.5.

Thanks again.

"Oli Restorick [MVP]" wrote:

Are you looking to upgrade the operating system from Windows 2000 Server
to
Windows Server 2003 (or R2), or to go from Exchange 5.5 to Exchange 2003
while leaving the server as is?

Or perhaps you are looking to move the complete installation to new
hardware
while retaining the software you have.

If you're looking to go for the first option, be aware that Exchange 5.5
does not run under Windows Server 2003. If you are looking to use
Windows
Server 2003 but not upgrade Exchange, you'd have to deploy Windows Server
2003 on a different server. You'd probably want to end up with the
Windows
Server 2003 box being an additional domain controller in the current
domain.

If you clarify your question, we can provide some specific advice.

Regards

Oli



"MHTB Matt" <MHTBMatt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4EF0B17A-9712-451A-AEB8-35B8FD2C6D18@xxxxxxxxxxxxxxxx
Hello, I'm looking for info on upgrading a single server currently
running
Windows 2000 Standard server with Exchange 5.5. This is the only server
for a
small business so it is also the DC. If anyone has any tips and can
point
me
to any docs to help me with this scenerio I would apreaciate it. All
the
info
im digging up from Microsoft support docs are talking about updating
NT4
with
Exchange 5.5 but not 2000 with Exchange 5.5.

Thanks!






.

Relevant Pages

  • Re: Exchange 2003 installation
    ... Configured on the NIC of the server. ... "Meinolf Weber" wrote: ... Is the ISP's DNS ... Old exchange removed - I don't know the ...
    (microsoft.public.win2000.active_directory)
  • RE: Exchange Fails to start after a reboot.
    ... this problem appears to be caused by DNS ... please try the steps below on Exchange server. ... Microsoft Online Partner Support ...
    (microsoft.public.exchange.admin)
  • Exchange 2003 SP2 - able to send but not receive email
    ... OWA already setup and running - My whole goal is to setup this server to ... DNS has example.org setup in Forward lookup zone along with MX record / A ... Now onto Exchange System Manager ... SMTP - Started - Settings below ...
    (microsoft.public.exchange.admin)
  • Re: Backup domain controller?
    ... Microsoft MVP - Windows Server - Directory Services ... > with DNS and DHCP installed, and is the primary file sharing box. ... > second machine is the mail and Internet gateway server, running Exchange ... Also install DNS. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
Loading