What to do after migration (SBS2011 to Exchange 2013)

After migration I see in my ECP lots of "old stuff", like

- a SBS receive connector
- a SBS send connector
- a SBS e-mail policy

Is it save to delete all that stuff or do I have to keep them?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
You need to review them carefully to see what they are used for.
Send Connector for example are org wide - delete it and you lose outbound email if you don't have another connector.
Same for the email address policy - that is an org wide setting - which controls the email addresses the end users get. Just because they have SBS in the name doesn't mean they aren't being used.

Receive connectors are per server, and therefore can probably be removed. Have you uninstalled the old SBS Server?

hanskoensAuthor Commented:
Hi Simon

Yes, the SBS is turned off for a while now and everything works fine. The reason I like to remove the old settings is because, f.e., when I create a mail rule, Exchange 2013 returnes a warning concerning SBS:

"There are Exchange servers in the organization running an older version of Microsoft Exchange which cannot evaluate the rule 'Adres van afzender bevat '****@***.com''. This rule will still be evaluated by Exchange servers running a version of Exchange that is compatible with the rule."

I realize its not a big issue but I prefer a "clean" installation.

Thx, Sander
Simon Butler (Sembee)ConsultantCommented:
The reason you are getting that error is because the old server is still present.
To remove the error you need to remove Exchange from the other server. Turning off the server to see what doesn't work will always cause problems because Exchange expects the other server to be there - hence the error.

Therefore before you do anything, complete the migration by removing Exchange from the old server using add/remove programs. You can then DCPROMO the server out and be done.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.