Transitioned SBS server 2003 to 2010
Hi All,
We started off our company very simply, 1 server running Windows SBS 2003. Over time we grew, and ended up hitting the 75 user max, and so had to apply the Transition pack.
Recently, we deployed Exchange 2010 into a nice new shiny environment, by a 3rd party company doing the installation. The mailboxes were transferred away from the 2003 server, and the Exchange server was left behind basically so as to not impact that server.
Months have now passed and this weekend I tried to complete the job. All I had to do, apparently, was to follow the steps
here, for Recipient Update Services removal, and then the exchange s/w removal.
The RUS went well, removing a Domain and Enterprise rule, no problems. I hit a wall with removing Exchange, as it was not listed in the Add/remove programs. Instead, I had to start setup.exe from the CD and try to remove from that.
As part of that, it complained about bridge-heads, and I had to try and remove the bridge head links that had been created to link our 2010 environment. After that, the setup would continue the removal, but, for some reason failed to remove some services,
although they won't start as they're in Manual or disabled state anyway (these are Exchange MTA Stacks, Exchange System Attendant, Software Shadow Copy Provider). I've had to believe at this point that the exchange servers now dead...
So after all this, I've moved back to looking at the 2010 environment to make sure it was happy and I hadn't broken something badly. I get Event Id 5020 messages:
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 oldserver.mydomain.local in Routing Group CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=First Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=local in routing tables with the timestamp 06/02/2012 11:00:47.
So clearly theres still something to remove - but I can't see how.
Also, when I run the Exchange Health checks, they're still showing the old original server, under the old organisation forest, and I'm wondering - how do I clean that up ??
Any advice appreciated,
February 6th, 2012 8:39am
Check the adsiedit and see if you see old exchange server.
Check in the routingGroup Exchange Administrative Group properties and see if you have any entries of old server in any of the connectorGulab Prasad,
MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
MCITP: Lync Server 2010 | MCITP: Windows Server 2008
My Blog |
Z-Hire Employee Provisioning App
Skype: Exchange.Ranger
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2012 9:25am
If you Still have Routing Groups - Remove It.
Get-RoutingGroupConnector
RoutingGroups are no more Used in Exchange 2010.
So If you don't have Exchange 2003 Servers
Run Get-RoutingGroupConnector | Remove-RoutingGroupConnector
Now All Your Routing Groups are Gone.
Open Adsidedit.msc. Choose Connect to - Choose Configuration Partition -
Start the Flow in Reverse Direction - You can Safely Remove First Routing Group From there.
Do not Remove First Administrative Group - You might face Free busy issues
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 oldserver.mydomain.local in Routing Group
CN=first routing group,
CN=Routing Groups,
CN=first administrative group,
CN=Administrative Groups,
CN=First Organization
,CN=Microsoft Exchange,
CN=Services,
CN=Configuration,
DC=mydomain,DC=localSatheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you
February 6th, 2012 10:56am
Hi,
looks like my routinggroups have been removed as it comes back blank.
[PS] C:\Windows\system32>Get-RoutingGroupConnector
[PS] C:\Windows\system32>
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2012 12:08pm
Can you Open Adsidedit.msc , An Update me what routing groups you see there ?
Might be there some entries
Open Adsidedit.msc. Choose Connect to - Choose Configuration Partition -
Start the Flow in Reverse Direction - You can Safely Remove First Routing Group From there.
Do not Remove First Administrative Group - You might face Free busy issues
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 oldserver.mydomain.local in Routing Group
CN=first routing group,
CN=Routing Groups,
CN=first administrative group,
CN=Administrative Groups,
CN=First Organization
,CN=Microsoft Exchange,
CN=Services,
CN=Configuration,
DC=mydomain,DC=localSatheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you
February 6th, 2012 12:09pm
Hi,
I'm having problems finding the area that your looking for.
I start ADSIEdit, connect to. I choose "Configuration" under "Select a well known naming context", under Connection Point. Is that right?
From there I see CN=Configuration,DC=mydomain,DC=local.
I found Services -> CN=Microsoft Exchange, CN=First organization, CN=Administrative Groups, CN=first administrative group, CN=Routing Groups, CN=first routing group, CN=connections - but nothing shows under there, its blank. I'm logged in as a domain
admin.
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2012 12:23pm
Yes
Below Link :
Kind of Nearest Location with Screen Shots.
http://careexchange.in/removing-recipient-update-services-using-adsiedit-msc/Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you
February 6th, 2012 12:25pm
Check the same thing at the below location
CN=Microsoft Exchange, CN=First organization, CN=Administrative Groups, CN=Exchange administrative groupGulab Prasad,
MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
MCITP: Lync Server 2010 | MCITP: Windows Server 2008
My Blog |
Z-Hire Employee Provisioning App
Skype: Exchange.Ranger
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2012 12:28pm