Small Business Server 2003 R2 Standard, Migration to Small Business Server 2011 Essentials (Continued)

Back to our migration now and more preparation to our source server…

I am running another BPA scan to showup which issues remain to be resolved.


So as you can see we are now down to only 12 highlighted issues.

Let’s tackle the functional level of Exchange first, we need to load up the Exchange System Manager, which you can launch from the SBS Server management console, or navigate to it.


When System Manager opens up,  right click the Servername at the top of the tree, and click on Properties.


On the properties page, you will see the details about which mode you are currently in, and also which Exchange Server versions this mode supports.


In the unlikely event you, a) have additional exchange servers, and b) they are running a Version other than 2003 (or newer), please make sure to migrate these out prior to changing this setting. It is one way, and cannot be changed back (without restoring the server)

SO when you are happy, click on ‘Change Mode’


A warning is displayed detailing the change and that it cannot be reversed, this is your last chance to back out, so make sure you are sure. I am sure you are sure, you wouldn’t be doing it otherwise right?

On clicking on Yes, you are returned to the properties page. Click OK to close the page and your changes will apply.


Next we can move onto fixing the WSUS warnings.

First we will load up the native WSUS console. Changing too many settings here can lead to the ‘blue shield’ state which was quite difficult to recover from in SBS 2003, in later version it is a lot easier. What did this state mean? just that the default settings for SBS/WSUS integration were changed. WSUS still functioned perfectly well but the integration with he SBS console and reports was broken. More info on that here.

Click on Start, Administrative Tools, then on Windows Server Update Services.

When the console opens, we will go to the Products and Classifications section first. We need to add ‘Service Packs’ to be downloaded.


Click on Products and Classifications, then on the Classifications tab.


Check the box marked ‘Service Packs’ and click Ok. Next move to ‘Automatic Approvals’


Click to Edit the ‘Default Automatic Approval Rule’


On the edit page, click the hyperlinked option ‘When an Update is in..’


Put a check next to ‘Service Packs’ and click Ok. Click Ok to close down the Default Automatic Approval Rule page, and close the WSUS Console.



AutoApprove.exe Is not Updated.

We need to install an update now to resolve this next issue, so we will need to load up Windows Update on the server.

Open up IE, and click Tools, then Windows Update.

Choose to run a Custom check..


Well, after waiting for WU to check my server, it didn’t actually offer me the update in question. Luckily in the system tray was the Updates icon and it was top of the list. As i only want to install this one update at the moment i had to manually deselect all the other 100+ updates being offered. Tip here is the down arrow and the space bar!


Click on Install to kick off the installation.. it is a small update and it installs quite quickly.

You will need to acknowledge a message about what will happen to unselected updates.


Click on OK and the updates will stay in the system tray for Installation at a later date.

Pop3 Connector has not been updated.

Again we will run a WU check to see if i we can download this update.

It seems this update is also not being offered to me by MU at this time either, and i cannot see it in my System tray updates notification window.

When i re-read the KB article, it states ‘Microsoft Update’ not Windows Update.

So we need to upgrade our server to use MU instead of WU.

Navigate to this link on your server,


Click on ‘Start Now’

You will need to review the license agreement, and click to continue if you agree.


A new ActiveX is required to be installed..


Install the ActiveX.


And check for updates…


You’ll find the POP3 Update under ‘Software, Optional’ and then under, Microsoft Windows Small Business Server 2003


Make sure to clear all the security updates, and only select the POP3 connector update.


Click on Review and Install updates, and then on Install updates.


Installation should complete quite quickly.


Next we will tackle the Daylight Saving Time updates.

About Robert Pearman
Robert Pearman is a UK based Small Business Server enthusiast. He has been working within the SMB IT Industry for what feels like forever. Robert likes Piña colada and taking walks in the rain, on occasion he also enjoys writing about Small Business Technology like Windows Server Essentials or more recently writing PowerShell Scripts. If you're in trouble, and you can find him, maybe you can ask him a question.

Leave a reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: