Exchange Server

Wade PHILLIPS · Guest

I apologize if this has been asked already. But we are trying to upgrade a
2 node windows 2000 cluster running exchange 2003 to a 2 node windows 2003
cluster running exchange 2003 sp1. What would be the best route to
accomplish this task. Any help would be appreciated.

Thanks

Rodney R. Fournier [MVP] · Guest

I think you want this article
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/rllupnet.mspx
Its how to do a rolling upgrade to Exchange 2003. Great article with
pictures :)

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"Wade PHILLIPS" <WadePHILLIPS@discussions.microsoft.com> wrote in message
news:F87E3748-63AB-442A-B2EC-56FD0E50F6FD@microsoft.com...

Scott Schnoll [MSFT] · Guest

Hi,

I would hold off on that article because it only covers the OS upgrade. You
actually need to upgrade Exchange before you can upgrade the OS, as Exchange
2000 cannot run on Windows 2003.

You can do a rolling upgrade of Exchange if you want, but the best practice
recommendation is a clean install using the following process:

1. Temporarily remove passive node.
2. Re-build evicted passive node as standalone server.
3. Move mailboxes, etc. to new standalone.
4. Rebuild active node as new Windows 2003/Exchange 2003 system.
5. Move mailboxes, etc. to new active node.
6. Rebuild standalone as new passive node.

That said, if you want to do a rolling upgrade of Exchange, we support that,
too. To do that you would:

1. Upgrade any front-end servers you have to Exchange 2003. You have to
upgrade the FEs before you upgrade back-end servers.
2. If existing nodes are DCs, run dcpromo and demote them (we don't
support Exchange running on nodes that are DCs).
3. In this is an Active/Active Exchange cluster, move both EVS’ to one
node (Might be a good time to convert from A/A to A/P).
4. Run Setup.exe on passive node (restart as necessary).
5. Move the EVS to upgraded node.
6. Take Exchange offline temporarily; Disk, Network Name and IP resources
need to be online for the upgrade.
7. On the upgraded node, right-click the System Attendant Resource in
Cluster Administrator and select “Upgrade Exchange Virtual Server”
8. Run Setup.exe on other node (restart as necessary).
9. Redistribute EVS’ (if applicable).

Then, proceed with the rolling upgrade of Windows as desired.

After you do the OS upgrade, there are three important tasks you'll want to
do to make sure the IIS 5 to IIS 6 upgrade was complete:

1. Verify Worker Process Isolation Mode. Use this script, which should
return FALSE:
cscript \inetpub\adminscripts\adsutil.vbs get
w3svc\IIs5IsolationModeEnabled

2. Verify Exchange DAV is IIS 6.0 worker process. Use this command line
function, which should show davex.dll running under w3wp and not inetinfo:
tasklist -m davex.dll

3. Verify ISAPI extensions are enabled. Use the following scripts:
cscript \inetpub\adminscripts\adsutil.vbs get
w3svc\ApplicationDependencies
Should list "Microsoft Exchange Server;MSEXCHANGE,ASP“

cscript \inetpub\adminscripts\adsutil.vbs get
w3svc\WebSvcExtRestrictionList
Should see several Exchange entries (davex, exprox, MasSync,
exwform, owaspell and owaauth)

Hope this helps.
--
Scott Schnoll
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.

"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:uRv%2346D6EHA.3612@TK2MSFTNGP14.phx.gbl...

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1