removing Exchange 5.5 after upgrading to 2003 2

[cahelmster]

I recently migrated my one Exchange 5.5 server to a new Exchange 2003 box. Everything is working correctly. I now need to remove the 5.5 box from the loop. I've found a couple Microsoft documents on removing the last 5.5 server and switching to native mode, but the documents seem to contradict themselves. Can anyone point me in the right direction on how to remove my one and only 5.5 server and convert over to native mode?



----------------
Thanks!
CH

 

[jamescoyle]

Here use this one only..

http://support.microsoft.com/default.aspx?scid=kb;en-us;822450

I have used this many times as I work as a migration consultant for AD/Exchange and this works.

 

[DColcl]

Bless you, James for answering this and to you, CH, for posting it. I, too, am about to remove my old Exchange 5.5 and bid it "good ridence". Just surfing this site to make sure I have my ducks in a row.

Dan

 

[MalcolmS]

cahelmster,

I concur with jamescoyle's article.

However, the procedure is virtually irreversible. Prior to executing the removal procedure, disconnect the exchange 5.5 server's ethernet cord. Leave the 5.5 server running, with ethernet cord out. Monitor Exchange 2003 operations for at least three days (I prefer a week.) You want to wait long enough to give all your users a chance to access exchange resources and report any difficulties back to you.

What this process does is provide you with a immediate recovery method should a problem occur. If any anomalies occur, simple restore the ethernet connection and then troubleshoot the problem. This is a safe method for validating all exchange objects and services are functioning on 2003 before executing the final removal procedure.

 

[DColcl]

oh, VERY smart!

 

[cahelmster]

I'm getting the following message now in the Event Viewer on my Exchange 2003 box after unplugging the 5.5 box:

An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 11, Windows 2000/MTA error code: 1722. Comms error 1722, Bind error 0, Remote Server Name XXXXXXX [MAIN BASE 1 500 %10] (14)

Everything seems to still work though. Any ideas?

----------------
Thanks!
CH

 

[MalcolmS]

cahelmster

The rpc warning is normal as the Exch2003 server is still expecting to communicate with 5.5 server. You can safely ignore this for now. But continue to monitor the application log.

While you are waiting with sweaty palms, try replicating some client task. Access the public folders, grab a laptop open outlook while connected to exchange and update the address book. Then open outlook offline and verify you can still access the address book (GAL) and that the copy has recently updated contacts (you can add a contact before running this test to as a benchmark), access OWA. Also, send meeting requests verifying you calendar updates and deletions are functioning. Add any other test of services that may concern you. The most common issues I see is public folder replication, free/busy connector and offline address book issues. The test I have listed will cover these.

Also, don't forget to update your backup set. You will have backup failure messages from attempts to backup the 5.5 server that is not connected to the LAN.

M~

 

[cahelmster]

cool..thanks for all info!

Looking over KB-822450, it says to move any connectors from 5.5 to an SRS server in the site (step #12). Is this necessary beyond a normal "Exchange Deployment Tools" migration? I have a simple one Exchange box organization. I've already migrated over the public folders (using pfmigrate) and the mailboxes and I've also established SMTP connectivity on the 2003 box.

----------------
Thanks!
CH

 

[MalcolmS]

The SRS server in your case is the new 2003 server. If you have site and/or X.400 connectors configured on the 5.5 server, then Yes you have to perform step 12 (my guess is you didn't). Also, you must configure the SMTP connector on 2003 to replace 5.5's IMS. Since you have already unplugged the 5.5 server and email is flowing, you've obviously done this.

M~

 

[cahelmster]

The only connectors listed on the 5.5 box are the old SMTP connector, a MS Mail connector, and a connector for cc:Mail. I'm not sure if I even need the MS Mail or cc:Mail connectors. I don't use Lotus.

----------------
Thanks!
CH

 

[DColcl]

Cahel,
When I did this step, All I had to do (once I setup my 2k3 server with an SMTP and pointed my firwall to the 2k3 IP) was to.\
0. Shut down the IMC service on the 5.5 and made sure that Internet Email was flowing to and from the new 2k3 server.

1. Delete the SMTP Instance that is located within the Connector. Then,

2. Delete the actual SMTP connector.

This way you wont have any Orphan (Legacy) connectors on your 2k3 ESM.

 

[asktheman]

q for dcolcl when you say remove the network cable from the exchange 5.5 server, before reoving the 5.5 object from the exchange org. how are you going to use this fall back when the exchange org thinks that the 5.5 server is gone for good. And the 5.5 server thinks it still part of it...

 

[DColcl]

by removing the network cable, you will get errors regarding the x.400 connection, etc. on the Admin side of life. However, if things are done correctly, any issues will be oblivious to the end user. However, if there are issues that we may have forgotten it can be easily discovered and reversed before an adverse effect on the network. We can connect the NIC, fix tthe issue, then try again.

I think that's what you are getting at, no? Sorry, my English comprehsion is not too adjusted so forgive my lack of language skills, please.

Dan

 

[cahelmster]

I removed my 5.5 server from the loop today according to article 822450. Everything seems to be working (for now at least!). Thanks for all info!

My next step is to convert over to native mode...

----------------
Thanks!
CH