LB 2003 to 2010 Exchange Migration p4

I went in to remove the Exchange 2003 server from the LB office and have the following observations.

The public folders went fairly smoothly, in that the "MoveAllReplicas" script seemed to do its job and clear the old server of all its replicas.

A new internet connector needed to be created for internet-bound email because ownership can't be given to the new server (due to it being in a different routing group).

The RUS service needs to be handed to the new server, which I didn't mention in past posts.

So after removing one system e-mail account (something to do with Free / Busy, but not sure what since this functionality should be derived from public folders...) the 2003 uninstall was ready to proceed. And so it did, but it also failed quite spectacularly and so, outlined below, is a guide on how to manually remove an orphaned Exchange 2003 server from AD:

1. Go into ADSIedit and delete the server object.

You should be able to run the BPA with no errors, and if you do have errors then they can probably be fixed by copying and pasting the DN from one field, in AD, to another. Not graceful, but there you go.

LB 2003 to 2010 Exchange Migration p2

Yesterday I copied and pasted a screed of unformated text which formed my attack plan for the migration. Today I have been at the company and gotten underway with the whole thing. So, inevitably with IT, my list wasn't comprehensive and certain problems have slowed the progress of the installation.

When Exchange 5.5 was around it used a thing called the "Active Directory Connector" which was for syncing with AD. 2003 did away with it and began using the recipient update service and the ADC was rendered redundant. Exchange 2007 / 2010 will not proceed with installation if there are any traces of the ADC left. Additionally, the Exchange orgnisation was in "mixed mode" and should have been in "native mode". So how do you remove these traces of ADC and change the mode of the organisation?

Firstly, uninstall the ADC service. In the case of this company it was installed on a DC. Uninstall failed citing "additional connectors". From here the ADC connectors need to be manually deleted from ADSIEdit. So go to Config > Services > Exchange > AD Connectors and delete the connectors not related to the ADC service. Once this is done the uninstall will proceed.

Some pesky ADC were still lingering, however. These we simply deleted. This can be achieved from ADSIEdit, as mentioned above, or AD Sites and Services (remember to show the hidden service options from the toolbar).

Now we thought we would be able to change to native mode, but still it was greyed out. The next thing to be done is to stop and disable the "Site replication service" on Exchange 2003. Still native mode was greyed out.

Finally we deleted the "Site replication service" in Exchange system manager under Tools. At last we could change to native mode and begin to prepare Legacy permissions (setup /pl), the schema (setup /ps) and the domain (setup /prepareAD).