Go Premium for a chance to win a PS4. Enter to Win


Migrations from SBS2003 exchange to hosted exchange cleanup

Posted on 2014-02-10
Medium Priority
Last Modified: 2016-05-22
We have migrated some customers from SBS 2003 to third party non 365 hosted exchange accounts. What is still present is the original sbs outlook configuration. We have multiple networks that have some issues.
One network was migrated due to an AD failure. We had to do an AD restore form a corrupt backup with the assistance of a third party contractor. He was able to rebuild AD in a server 2008 environment, however there are still occasional references to the old SBS, particularly regarding folder redirection, but that has been cleaned up.
We still have issues with this network and some other post sbs 2003 networks where new client setups obtain the outlook configuration for the old sbs.
The network we are currently dealing with is mid migration to a 2008 domain. We migrated the email to the hosted Exchange friday and are doing client cleanups now.
We have our autodiscover A record entry present and new mobile clients have no issue configuring.
The outlook environment is a mix of clients from 2003 to 2013.
We can create a new mail profile and configure the clients without incident. However local archives require a manual spf export/import.
There is a PRF present on the SBS and in the C:\Program Files)\Microsoft Windows Small Business Server\Clients on the client machines
C:\Program Files (x86)\Microsoft Windows Small Business Server\Clients\sbsclientapps.log shows that the setup.exe that runs as part of the sbs login script is still apparently trying to reconfigure outlook using the sbs2003 deployment configuration

I have found multiple references to issues when migrating out of sbs2003 to hosted exchange and end users having issues with clients still trying to use the sbs or reconfiguring.

In and ideal environment we would be able to cleanup AD and remove all references to the SBS regarding exchange and client configurations, however I have been unable to find any clear guide or MS article.

We are well aware that it is cleaner in the long run just to wipe a domain and restart new, but that is not an option.

Any advice would be greatly appreciated in clearing out the sbs references for outlook.

Ideally we would make the change and push them out via GPO or script to clean up the outlook profiles without recreating new ones.

One big issue is the client machines to which multiple users occasionally log on. When they access an older cached profile they will still have the original outlook profile.

Using ADSI edit I see many references to the old exchange server, but it is outside my scope to begin making alterations as I do not know what the long term impact is.

This particular network state is pending SBS demotion and removal, I just want to clear up any issues before we dont have the SBS to reference anymore (as would have been very handy when we were clearing up the folder redirection on the first network mentioned)
Question by:RB_adcom
LVL 37

Expert Comment

by:Jamie McKillop
ID: 39850030

You can use the removeorg switch with the Exchange 2003 setup program to completely remove Exchange from your Active Directory. Here are the instructions - http://support.microsoft.com/kb/830185

Exchange 2003 doesn't use autodiscover though, so your clients shouldn't be automatically attempting to connect to your old SBS server when your run through the new profile creation wizard in Outlook.


Author Comment

ID: 39850848
I dont think its got to do with autodiscover, I think its a mechanism of Small Business Server autoconfiguration.
I know that setup.exe in the client folder executes the PRF import or something to that effect, but there is no clear documentation on what setup.exe does
Once the domain is migrated away from SBS it will be cleanable.
I will look at this link however, it may add some insight
LVL 74

Accepted Solution

Jeffrey Kane - TechSoEasy earned 2000 total points
ID: 39889828
There is an autoconfiguration component in SBS 2003 for Outlook -- and yes, setup.exe is the culprit.

You'll find that in all user accounts there is a login script entry for SBS_Login_script.bat.

The quickest way to resolve this issue is to just REM out the "\\<network directory>\clients\setup\setup.exe /s <server-name>" line in the SBS_Login_script.bat file which you'll find in the SYSVOL folder on your server.

Or bulk edit your AD User objects and remove the SBS_Login_script.bat from the script field.


Featured Post

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

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
Many of my clients call in with monstrous Gmail overloading issues with Outlook. A quick tip is to turn off the All Mail and Important folders from synching. Here is a quick video I made to show you how to turn off these and other folders in Gmail s…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses
Course of the Month10 days, 13 hours left to enroll

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question