We want to upgrade to E2K on W2K, and prefer to do an in-place upgrade. However, in our test lab we've had inconsistent results upgrading our PowerEdge servers from NT4/SP6a to W2K, and I don't want to blow up my Exchange server in a failed W2K upgrade. MS Knowledge Base (Q280770 and Q224977) seems to suggest an alternative...
In our test lab I installed W2K Server, and Exc 5.5/Sp4, with my edbs in the same structure as the source machine. I also set the services not to start on boot. I shut down Exchange on source machine, made file backups of the directore and store files, and copied them to the server in the test lab. Next I ran eseutil /d on the priv and pub edbs; then I started the Directory service and ran isinteg -patch.
Both eseutil and isinteg ran OK. All services started OK. Everything looks OK. Has anyone else done this and was it successful?
In our test lab I installed W2K Server, and Exc 5.5/Sp4, with my edbs in the same structure as the source machine. I also set the services not to start on boot. I shut down Exchange on source machine, made file backups of the directore and store files, and copied them to the server in the test lab. Next I ran eseutil /d on the priv and pub edbs; then I started the Directory service and ran isinteg -patch.
Both eseutil and isinteg ran OK. All services started OK. Everything looks OK. Has anyone else done this and was it successful?