How do I clean up Exchange seeing old server

I have a server that was migrated from SBS 2003 to SBS 2008. The old server was demoted and the migration completed except for uninstalling Exchange. It has not been turned on for about 6 months.

When I run the Exchange BPA, I see:
Exchange Administrative Group with the new server name
First Administrative Group with the old server name

If I run the Routing log viewer, I see:
First Routing Group is NEWSERVER-OLDSERVER and the old server is still listed under 'Servers' along with the new server.
Under Routing Group Connectors, I see:

Mail has seemed to be flowing fine until recently a couple employees have stated that some of their emails they send are not getting to the recipient and I'm thinking it could be these routing connectors and references to the old server. Another employee can send to the same recipient and it goes through.

How do I get this cleaned up so the old server references are gone from Exchange on the new server?
LVL 13
Who is Participating?
Antonio VargasConnect With a Mentor Microsoft Senior Cloud ConsultantCommented:
If you only have one exchange server now (the new one).. you can delete both routing group connectors. you dont need routing group connectors now.

Also go to active directory and do a find, adding the exchangeserver attribute to the search. The idea is to see if you have any accounts still associated to the old server. If so see what are the accounts and if you can delete them.

After these two steps you can test again for mail flow problems.. and the next step will be to delete the administrative group and the old server.. i would say that using adsiedit is the best way to do it.
Old UserCommented:
See this question, it contains a link to a useful article
notacomputergeekAuthor Commented:
When I try to remove the routing groups with EMS:
Get-RoutingGroupConnector | Remove-RoutingGroupConnector -confirm:$false
I get the error: Cannot find computer object in Active Directory for server 'OLDSERVER'.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

notacomputergeekAuthor Commented:
In searching AD, the only reference to the old server is a 'SystemMailbox{GUID}'.

Is this safe to delete?
notacomputergeekAuthor Commented:
Can I just delete the 'first administrative group' in adsiedit under 'Configuration' -> 'Services' -> domain -> 'Administrative Groups'?
Antonio VargasConnect With a Mentor Microsoft Senior Cloud ConsultantCommented:
It's safe to delete that system mailbox.

it's also safe to delete the administrative group that has the old server.

Does the computer object for the oldserver still exists on AD?

If not use also adsiedit to remove the connectors. but just those that are on the old organization.

I would first do a backup of one dc system state, then use adsiedit to remove the routing-group connectors scrolling to the folder were they are on the old organization. then test mail flow to see if its ok.

finally remove the systemmailbox associated with the older server from ad..

another backup..

and remove the old organization...
notacomputergeekAuthor Commented:
Sorry, I've been away on vacation. Will try suggestions today.
notacomputergeekAuthor Commented:
OK. Went to work on this today and didn't see any of the routing groups I mentioned earlier. I don't recall changing anything, so I'm not sure what happened to them.

I went ahead and removed the First Administrative Group with ADSIEDIT, which referenced the old server. Mail still flowed, but that took out my Public Folders. After a bit of research, I found this ( and followed the steps to recreate the Folder Heirarchy. This worked great and my Public Folders were now mounted again.

E-mail was still flowing, but more employees have been stating that some of the e-mail they send isn't being received. I started doing some tests and found I could not e-mail to one of my personal accounts from the office. The message tracking says it sent it, but I never get it in my personal account. We've been using our ISP smart host to send e-mail, so I decided to change Exchange to use DNS - same results. I still couldn't send to my personal account.

I think I have the same problem I started with, but I don't think it's a routing  issue and this may need to be a seperate thread, but now I guess I need some tools suggested to find out why I can't send e-mail from one address to another. Again, most e-mail is sending fine.

I have also made sure that we are not on any blacklists and none of the e-mail is being sent back as a nondeliverable.
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
You need to check on the queue viewer to see if the e-mails are getting stuvk on queue and not leaving the organization. also can you run a get-sendconnector |fl and post the result? we need to check if you have a send connector to the internet correctly configured.
notacomputergeekAuthor Commented:
Nothing in the queue.

AddressSpaces                : {smtp:*;1}
AuthenticationCredential     : System.Management.Automation.PSCredential
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut  : 00:10:00
DNSRoutingEnabled            : False
DomainSecureEnabled          : False
Enabled                      : True
ForceHELO                    : False
Fqdn                         :
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : SERVER
Identity                     : Windows SBS Internet Send SERVER
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
LinkedReceiveConnector       :
MaxMessageSize               : 10MB
Name                         : Windows SBS Internet Send SERVER
Port                         : 25
ProtocolLoggingLevel         : None
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SourceIPAddress              :
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {SERVER}
UseExternalDNSServersEnabled : False
notacomputergeekAuthor Commented:
The suggestions got my routes cleaned up, but disabled Public Folders. However, my e-mail still wasn't flowing. The main problem has been resolved and the solution addressed in this question (

Thanks for your help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.