Exchange Server Forums

Straightforward upgrade 5.5/2000

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Installation >> Straightforward upgrade 5.5/2000

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Straightforward upgrade 5.5/2000 - 25.Feb.2001 8:57:00 PM

zetorboy

Posts: 3
Joined: 25.Feb.2001
From: Finland
Status: offline

We want to try in our test server straightforward upgrading from Exsrv5.5 to 2000, at the same fysical piece of server.
At the same time ofcourse we would move this server from NT4.0 to W2k server. MS staff said at one seminarium that this is no problem, but I am not that sure about it. Any suggestion on the upgrade order NT first or EXsrv first. Is this possible at all or total madness?

best regards

Mika Suni

Post #: 1

Featured Links*

RE: Straightforward upgrade 5.5/2000 - 26.Feb.2001 1:18:00 PM

robert

Posts: 434
Joined: 24.Jan.2001
From: Malta
Status: offline

I wouldn't recommend such an installation but if you are doing it first upgrade the nt to 2000 and then upgrade the exchange cause microsoft exchange 2000 is not supported on Windows NT4, though this means to install the 2000 first than the exchange. I have other upgrade tactics but they are to long to explain them here. If you want just mail me. Thanks

------------------
Regards
Robert Abela
robert@gfi.com

(in reply to zetorboy)

Post #: 2

RE: Straightforward upgrade 5.5/2000 - 26.Feb.2001 11:06:00 PM

Taps

Posts: 13
Joined: 30.Nov.2000
From: Atlanta GA
Status: offline

It isnt so much a problem with it not being supported. its more of a problem with it not working at all. Unless you have another exchange 2000 Domain controller in your network that is running active directory, there is no way to get exchange 2000 installed.

But from personal experience, I would suggest you do the following:

1 - If you dont already have one, install a new Windows 2000 Server and promote it to a domain controller.

2 - Build a second machine and install Exchange 2000 fresh. Create a few test users and verify that all is working properly. (To do this, you will also have to creat a connection between the old Exchange 5.5 server and the Active diretory. This will allow the two to share information indirectly).

3 - Once testing is finished and you have confirmed the E2K server is fully operational, begin moving users over in small groups. 3-4 at a time. possibly more depending on the size of your organization.

4 - Once all users are moved to the new exchange server, let it sit for a while. Make sure all users are now using the exchange server. if an outlook client is never shut down (You know htere is always one guy who never logs off and hasnt seen anything updated in months because you put updates and stuff in logon scripts, etc etc), then it will not be able to change to the new server until it is closed and reopend.

5 - after an acceptable amount of time, when you are sure that all users are using the correct server, you can remove the Active Directory Connector and uninstall the Exchange 5.5 server.

6 - At this point you are able to switch Exchange 2000 into Native mode. This will help in the future with administration from a visual standpoint if nothing else.

Its not like its a 5 minute process and poof you are on E2K. not even close. Also, I dont think I have to go through and emphasize the need for backups at as many steps as you need to feel comfortable. Nor do I expect you to take this as a be-all/end-all solution. There is much more involved than the 6 items above, my main suggestion is to read help files, white papers, newsgroups, readme.txts, and once you think you have a firm grasp on what you are about to do..... Go back and read them all again.