Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration.

My first tip Migration Tip #1 – Source Server Health can be found here: https://demazter.wordpress.com/2011/06/12/migration-tip-1-source-server-health/

My second tip Migration Tip #2 – The Practice Run can be found here: https://demazter.wordpress.com/2011/06/14/migration-tip-2-%e2%80%93-the-practice-run/

So, we now have a healthy source server and you have practice until the match sticks snap what next?

My third tip is about making sure you are prepared for the task ahead. Any type of migration needs to be taken seriously, it is a business critical operation you are about to embark on. If you are in any doubt about it at all, now is the time to say so, and if necessary call in help.

If you are happy with the process and confident you are able to complete the steps to achieve your goal then the next thing we need to do is plan a time to do it.

Most migrations are not time limited other than SBS to SBS migrations that have a limit of 21 days where both SBS servers can co-exist at the same time.

Make people aware of what you are doing, involve them, explain that you are expecting to have teething problems but would prefer if they collated them and then passed them to you when you ask for them. The last thing you want is to try trouble shooting whilst trying to complete a migration.

Find out if there is anything business critical happening (a big bid/contract etc that needs to be out just when you take the mail system offline) that could be delayed by the work you are carrying out, and if so, delay your migration. Talk to absolutely every member of staff. Manage Expectation.

In reality, if you get it bang on, the end users shouldn’t even notice and I would say 99% of the migrations I have done this has been the case. But there is always the odd one.

Have a recovery plan, know how to back out of what you are doing if it does go pear shaped. If you need to lock and migrate huge amounts of data then make sure you plan this stage of the migration for when people aren’t going to be using the system as heavily.

Document what you are doing, make notes of which stage you have got to and what action you have just taken.  This might seem like a waste of time, but take it from someone who has picked up a few failed migrations from people just like yourself, it’s not.  Knowing exactly what stage you are at will help a consultant very quickly get to grips with the situation and this means a faster resolution.

And, most importantly of all, make sure you have backups! Take more than one, take one off-site, and do it different ways. I like to have a backup on either removable storage so I can access it quickly but also on tape just to be sure.

Watch out for tip Migration Tip #4 – The Migration

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self-signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com/


Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration.

My first tip Migration Tip #1 – Source Server Health can be found here: https://demazter.wordpress.com/2011/06/12/migration-tip-1-source-server-health/

My second tip is about making sure you are familiar with the technology you are migrating to.

For many people, migrating to a new technology will be the first and only time they perform this task. So, it’s always a good idea to familiarise yourself with the setup process before you do it for real.  With the use of virtualisation technologies we can install and test new products without the need for new hardware and without the possible impact on our live environment.

There are a number of virtualisation products that will allow you to do this on your desktop/laptop computer. You need to consider that most new products (if not all) will be based on x64 bit architecture. This does limit the virtualisation technologies that you can use on the desktop. Some of my favourites are listed below.

VMWare Workstation, this is a paid product but worth its weight in gold: http://store.vmware.com/store/vmwde/en_IE/pd/productID.166452200/Currency.GBP/?src=PaidSearch_Google_PersonalDesktop_WKSN_EMEA_UK_EN_Brand
VMWare Server, this is free for use and technically should only be used on a Server Operating System, but it does work on Desktop OS for testing purposes: http://www.vmware.com/products/server/overview.html
Virtual Box: http://www.sun.com/software/products/virtualbox/get.jsp

Whichever technology you use, virtualisation will allow you to install the new software in a test environment, and keep installing it until you are happy with the process. Run through it 2, 3 even 4 times. Make sure you are familiar with the screens and what answers you are going to provide to the wizards. Take notes, even write a step-by-step of what you encountered and when you encountered it. Remember, the more you do now when you are in a safe “sandbox” environment, the easier and less pressurised the real thing will be. Don’t pay too much attention to the actual data you are entering as some of this will change when you do a migration as opposed to a new installation.

For the actual Migration Pick a migration guide for your technologies, it’s always best to use one that’s recommended by others and they have had good success with.  You will find my migration guides here: https://demazter.wordpress.com/category/migration-guides/ I use my guides in my own migrations and update them with any changes as often as possible.  Read the guide thoroughly before you start the migration.   It’s easier to get answers when you are not under pressure to fix things.

If you have the time and the inclination I would also suggest that you convert your physical source server to a virtual one. This will allow you to do a test migration with your actual source server. There are many tools for performing the capture and they depend on the virtualisation technology you are using and whether you want a free or paid product. Some examples of methods that can be used to convert physical machines to virtual ones can be found here: http://4sysops.com/archives/p2v-for-vmware-six-ways-to-convert-physical-to-virtual/

Doing a virtual migration with a virtual copy of your actual source server is a great way to identify any problems you may encounter during the real live migration. You then have the opportunity to rectify these issues and then try the migration again. Once you are happy the migration has worked you are then in a position to do the live backup. I would be doing 3 to 4 virtual migrations just to be absolutely sure.

Watch out for tip Migration Tip #3 – Preparing for Live Migration in the next day or two.

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self-signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com/

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration.

My first tip is around source server preparation.

No migration is an easy migration, there is always potential for something to go wrong. All we can do is try to minimize this risk.

The biggest risk comes from the system we already have in place, the integrity of this system is paramount in ensuring a successful migration.

Making sure your source system is healthy and configured correctly will go a long way to ensuring you have a smooth migration.

Use analyzers and health check tools that are available from the vendor. Microsoft, for example, have a number of best practice analyzer tools. These can be used to identify any problems the system may have and provide advice on how to resolve them. Some of the ones I use regularly are listed below:

Small Business Server 2003 BPA: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3874527a-de19-49bb-800f-352f3b6f2922&displaylang=en
Small Business Server 2008 BPA: http://www.microsoft.com/downloads/en/details.aspx?familyid=86a1aa32-9814-484e-bd43-3e42aec7f731&displaylang=en
Exchange Server BPA (not for Exchange 2007 or 2010, the built in BPA should be used): http://www.microsoft.com/downloads/en/details.aspx?familyid=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en
Internet Security and Acceleration Server BPA: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d22ec2b9-4cd3-4bb6-91ec-0829e5f84063
SQL Server 2005 BPA: http://www.microsoft.com/downloads/en/details.aspx?familyid=da0531e4-e94c-4991-82fa-f0e3fbd05e63&displaylang=en

In a Microsoft migration I will use tools like DCDIAG, NETDIAG, REPLMON and REPADMIN to check for errors, even if it’s a single server. You would be surprised how easy it is to misconfigure a single server. Further details on the usage of these tools can be found here:

DCDIAG: http://technet.microsoft.com/en-us/library/cc773199(WS.10).aspx
NETDIAG: http://technet.microsoft.com/en-us/library/cc782085(WS.10).aspx
REPLMON: http://technet.microsoft.com/en-us/library/cc772954(WS.10).aspx
REPADMIN: http://technet.microsoft.com/en-us/library/cc755360(WS.10).aspx

Make sure the source system is up-to-date. All updates, service packs etc need to be applied. This may seem like a waste of time on a system that you are soon to be migrating out of your network but really it isn’t. New products from the same vendor normally rely on the source system being up-to-date. I have been known to spend hours installing service packs and updates on a source server.

It’s worth spending the time getting this part of the migration perfect. There are no timescales in play here you can take your time, once you start migrating there are pressures at play that will make the slightest hiccup seem like your whole world is imploding. I would consider this part of the migration process the most important, and therefore if you are not comfortable with this process, hire someone who is. Buying in consulting services to make sure the server is health can save you a lot of money.

Watch out for tip Migration Tip #2 – The Practice Run in the next day or two.

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com/

This guide is intended to provide step by step inbeen written using the preview version of SBS2011 therefore some structions on how to migrate from Small Business Server 2003 to Small Business Server 2011.

NOTE: This guide has of the screens may look slightly different on the final release.

Steps required:

  1. Health Checks on Small Business Server 2003
  2. Configure SBS2003 for single NIC
  3. Run Migration Preparation tool on SBS2003 & Create Answerfile
  4. Administrative User Creation
  5. Setting data locations
  6. Configure the Network
  7. Configure the Internet Address
  8. Migrate Exchange Mailboxes and Settings
  9. Remove Legacy Group Policies and Logon Settings
  10. Migrate users’ Shared Data
  11. Migrate Fax Data
  12. Migrate Users and Groups
  13. Uninstall Exchange 2003 from Small Business Server 2003
  14. Check Transfer of the 5 FSMO roles to SBS2011
  15. DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network

Step 1. Health Checks on Small Business Server 2003

The absolute first thing you need to do is take a SYSTEM STATE backup of your Small Business Server as well as a full system backup. There is little chance of the data getting lost but the SYSTEM STATE backup backs up Active Directory so that if it all goes wrong we can recover it if needed.

To do this from using your preferred backup product ensure that System Stare is selected from the selection list then run a backup.

What you then need to do on the SBS 2003 server is to make sure you have all the latest available updates. This means you should at a minimum have:

  • Windows 2003 Service Pack 2 – verify this by right clicking on My Computer and select properties. It should tell you here the Windows Service Pack
  • Windows Small Business Server Service Pack 1 – verify this by checking the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\ServicePackNumber you are looking for a value of 1 in the bracket.
  • Microsoft Exchange 2003 Service Pack 2 – verify this using the Exchange System Manager. Navigate to first administrative > Servers. With the Servers folder highlighted on the right hand side you will see the SBS2003 servername with the service pack version listed.

Once you have installed all of the above, run Windows Update and make sure you select the option in the blue banner bar across the top for Microsoft Update. Microsoft Update will then allow you to update all Microsoft products installed on the server providing a more comprehensive update solution. Keep running the check and installing all updates until there are no more available. Further details on this process can be found in my article here: https://demazter.wordpress.com/2010/06/21/get-more-from-windows-updates/

Check the health of your Active Directory by running DCDIAG, if there is anything reported as an error fix it before moving on.

A common problem that can cause this migration to fail is that the SBS 2003 server does not have its own IP address listed for DNS in the network properties under TCP/IP. If this is the case, update it so that it does (do not use the loopback address).

Step 2 – Configure SBS2003 for single NIC

Before you can migrate from SBS2003 it needs to be configured in a single NIC configuration and ISA server (if in use) needs to be removed.

To do this uninstall the ISA components from Add/Remove programmes.

You may also need an additional internet router appropriate for the type of connection you use. This should support NAT and needs to be configured with an IP address to match the internal NIC on your server.

Once you have done this, disable the second NIC and then run the Connect to the Internet Wizard to ensure SBS2003 is configured correctly.

I would then suggest a reboot to ensure that all these changes are taken in to effect.

Step 3. Run Migration Preparation tool on SBS2003 & Create Answerfile

As part of the Migration Preparation tool it will run the best practice analyzer to identify any issues with the current setup. Before you run the tool you will need to download and install from Microsoft Baseline Configuration Analyzer which can be downloaded from: http://www.microsoft.com/downloads/en/details.aspx?familyid=1B6E9026-F505-403E-84C3-A5DEA704EC67&displaylang=en

We can then run the wizard by inserting the SBS2011 DVD in to the SBS2003 server drive. Allow it to autoplay and you should see the following screen. If you don’t have a DVD drive in the SBS2003 server then there are a few options. Either use a USB DVD Drive, share the drive out from another workstation that does have a DVD drive, or copy the contents of the SBS2011 DVD to the SBS2003 server hard drive. The folders you require specifically are TOOLS and SOURCES. If you copy these 2 folders then instead of seeing the link below you will need to run the SourceTool installer from the TOOLS folder.

From here we need to select the option for Install the Migration Preparation Tool. The first screen we will see asks about getting and installing installation updates. My recommendation here would be to not install updates unless you are encountering an issue that has been identified by the SBS team and you are following specific advice regarding this. (screen below)

Once you have made your choice, the following screen will ask you to confirm that you have an adequate backup of the SBS system. Obviously the data needs to be backed up. But the important thing that needs to be backed up that is often missed is the System State Backup. This includes Active Directory and will be needed to recover with should the migration fail. (screen below)

Once you check the box to say you have a backup and click next you will see the screen below. This is preparing Exchange and Active Directory for the introduction of your new SBS2011 server. We are looking for 4 green ticks here.

Once this has completed click next. The next stage is the Migration Wizard will use the baseline analyzer tools you installed earlier to check the organisation for any misconfigurations that should cause the migration to fail (screen below)

This could take a few minutes but what we are hoping to see is the screen below that says we have no errors. This means we are ready to proceed with the introduction of the new server.

Clicking Next to move on will tell us the source server has been successfully (image below) prepared and give us the option to view the migration guide. At time of writing this article there was no migration content on the link provided.

The second option is to create an answer file. This is essential for the successful migration to SBS2011 so click this option and complete with the detail as illustrated below. The reason I select these options is that it then asks you to confirm some information at the installation stage. Almost like a second check before proceeding. One of the key options is not to perform any updates. This can be done after the migration, and with my experience from SBS2008 migrations these updates have been known to make changes which cause the migration to fail.

Now we need to save the answer file using the save option. Once done, copy it to a USB drive and place this in your new server along with the SBS2011 DVD and post up.

The first screen we see is the language and keyboard selection screen (image below)

Make the appropriate selections and click next.

We then see the screen below. Click Install Now

We are then presented with the usual License Agreement screen (below). Put a check in the check box and click Next. Obviously only if you agree to the licensing terms as set out by Microsoft.

The following screen (below) provides any storage that has already been configured on your new hardware. If you don’t see anything here you will need to load 3rd party drivers from your vendor using the Load Driver option. If you still don’t see anything listed then you may need to configure your RAID Controller so that there is a volume, most will do this by default on first boot if you don’t select to configure yourself, but some might not.

Once you have made the appropriate selections click next and we will see the usual Windows 2008 R2 component configuration and file copy screen as below.

Once this has finished the server will reboot and display the screen below. As this is a migration we will be selecting Server Migration and then click next.

The screen below is the time zone and date/time selection screen. It is absolutely essential that this matches the source server otherwise connection to the domain and promotion to a domain controller will fail.

Verify the time zone and date/time then click Next.

The screen below asks you to verify the source server IP address, the IP address you wish to assign the new server and the gateway address. Confirm the details and then click next.

The next screen is more confirmation. This time it is the source server name and internal domain name along with the administrative user details and the source server name.

Confirm the details, and even retype the password just to be sure. Then click Next.

We then see the update screen below. Again, my recommendation here would be to not install udates. And then click next.

The screen below is your company details, this will be used on Companyweb/Remote Web Workplace. Fill in the form an click next.

We then see the screen below which is the start of the SBS2011 component installation, this could take around 30-45 minutes and you can expect the server to reboot at least once during this phase.

Once this has finished you should be presented with the SBS2011 desktop and the screen below. This means that the installation phase of the migration has been completed.

If there were any problems with the migration you would see a troubleshooting assistant informing you of what has failed and how to correct it.

Step 4. Administrative User Creation

Now that SBS2011 has been successfully installed and you have logged in for the first time we will see SBS console. Those of you familiar with SBS2008 will notice that not much has changed.

As with SBS2008 most of the tasks we need to complete need to be performed with an Administrative user other than the built in Administrator account. This was not the case with SBS2003 and you probably do not have another Administrative user. If this is not completed we will receive the error below when trying to launch the Migration Wizard.

So the first step is to create this user.

Using the SBS Console select the Users and Groups option across the top of the console. You will then see the screen as illustrated below.

There will be no users listed here, don’t panic, this is perfectly normal. You will not see the existing users in the SBS Console until the migration is complete.

Click on the Add a new user account on the right hand side. This will launch the new user wizard.

Enter the details for your user. The important part is that you select Network Administrator as the User Role. Once you are done click next.

The following screen we are asked to enter a password for the user, enter a password and click Add User Account.

We then see the following screen, this can take a few minutes to complete but what we are looking for is 5 green ticks. If for any reason any of the stages fail the final screen will tell you what failed and why.

The following screen allows us to associate computers with this user or add an additional computer. There is no need to do this for the new Administrative User. Click finish to exit the wizard. From the SBS Console select the Home section and click Migrate to Windows SBS to start the migration tasks.

Step 5. Setting data locations

When launching the migration wizard there is a list of tasks to complete. These should be done in the order they are presented. As illustrated below.

The first task is to set the data locations for Exchange, Sharepoint, Shared Folders, Redirected My Documents and Windows Software Update Services. The wizards are the same for each so this guide will only run through one of them.

NOTE: If you don’t have a second volume configured there is no need to run this part. If you try to you will receive the following error.

If you do not have a second volume and don’t intend to have one, then on the first screen of the wizard put a check in the Task Complete radio and click next.

To run the wizards click the hyperlinks on the above screen one by one. The first screen (below) is simply the summary of what you will be doing, click next when ready.

The next screen runs a check of the configuration, one of the tasks this is completing is checking for available volumes and disk space for the files to be moved to.

Once this is complete we are given the options of locations to select from. At this stage because we have not configured a backup you will see an error that this has not been done. Click OK to continue.

Make the drive selection and then click Move. What we want to see is the screen below indicating that the move has been successful. Click finish and then move on to the next hyperlink to continue setting the data locations.

Step 6. Configure the Network

The next task the wizards want us to complete is the Configure the Network wizard. This is the Connect to the Internet Wizard.

When launched, the first screen we see is the one below. From here we need to select the Start the Connect to the Internet Wizard hyper link.

The following screen will give you a summary of some information that will be required to allow the wizard to be completed.

Make sure you have this information to hand and click Next.

The next screen does a check of the network configuration and will attempt to discover among other things your router. Part of these checks will also detect if there are any other DHCP services running on the network.

The wizard will not continue if another DHCP service is detected (see image below). Therefore if you plan to use another device for DHCP then this must be temporarily disabled to allow you to complete this task. I would however recommend that you do use SBS2011 for DHCP rather than another device.

Once you have disabled any DHCP services the wizard will move on and display what it has detected from your network configuration.

Check the information is correct and if so click Next. If not make any appropriate changes before clicking next.

Once done, we are looking for the big green tick as illustrated below that says our network has been configured.

Step 7. Configure the Internet Address

The 3rd task in the migration wizard is to Configure the Internet Address this wizard is for configuring the external domain you intend to use with the SBS2011 server.

The first screen we see is a summary screen explaining what the wizard will do.

Click the hyperlink for Start the Internet Address Wizard and then read the guidance on the screen below.

As this is a migration you will probably already have an external domain name and it will already be configured. The rest of this guide will assume you have a domain name registered and that you will use the control panel from your ISP to manage your External DNS. Click Next to start the configuration.

On the following screen, select the I already have a domain name that I want to use and click Next.

On this screen select the I want to manage the domain name myself and click Next.

The following screen we need to enter the external domain name we will be using, this will be the domain name used in the hyperlink for Remote Web Workplace, Outlook Web App, ActiveSync and will be used to create your email address.

Clicking the Advanced Settings link will allow us to reconfigure the name that appears in the self-signed SSL certificate from remote.domainname.com to something else. If you have mail.domainname.com or owa.domainname.com setup currently then this is where you would enter this information.

Once done click the configure button and the wizard will make the necessary changes. Once completed we want to see the summary screen as below. We are looking for 3 green ticks to say it has been successful.

Step 8. Migrate Exchange Mailboxes and Settings

The next step of the Migration process is to migrate the Exchange Mailboxes and Public Folders. When we launch the wizard for this task we see the following screen.

Clicking the hyperlink (at time of writing) takes you to the technet article for Migrating Mailboxes. To do this, we need to delve in to the Exchange Management Console. Click Start > All Programs > Microsoft Exchange Server 2010 and select Exchange Management Console.

Once the console has launched, navigate to Recipient Configuration > Mailbox. Here we should see all our mailboxes listed. All the mailboxes that appear as Legacy Mailbox are currently located on the SBS2003 servers mailstore.

You can either batch select the mailboxes using SHIFT or CTRL or do each mailbox one by one. Once you have selected the mailboxes to move, from the Action Pane on the right hand side select New Local Move Request. This will start the move mailbox wizard.

From the first screen click the browse button to select the Mailbox Store on the new SBS2011 Server. Once you have done this click Next.

For this screen, leave it at defaults for the first run. If you find that mailboxes fail to move due to corrupt items you may have to increase the value here to allow those corrupt items to be skipped and for the mailbox to move successfully.

The screen above is simply a summary of what task you will be performing, clicking the New button will start the mailbox moves.

Once complete, we are looking for the following screen, all green ticks.

If you are moving the mailboxes in batches then repeat this task until all mailboxes have been moved to the SBS2011 server.

The next stage is to migrate the Public Folders. To do this, complete the following steps on the SBS 2003 Server:

  1. Click Start > All Programs > Microsoft Exchange Server > System Manager
  2. Navigate to Administrative Groups > First Administrative Group > Servers > Servername > First Storage Group
  3. Right click on the Public Folder Store and select Move All Replicas. The only option that should appear in the list is your Exchange 2010 server. Click OK.

Now that we have moved the data to the SBS2011 server it’s best to leave the Exchange Settings as is for a day or so to a) make sure all the data is moved before we perform any other Exchange related tasks. b) Allow all the outlook clients to update automatically with the new server settings. We can now continue with the rest of the migration.

Step 9. Remove Legacy Group Policies and Logon Settings

The next step is to remove any Legacy Group Policies and Logon Configurations that are incompatible with SBS2011. The recommendation here is that any logon scripts in use should be migrated to Group Policies and/or Group Policy preferences. However in my experience it doesn’t cause any problems if this is not done.

Further information on these processes can be found here:

Remove old logon scripts for Windows SBS migration: http://technet.microsoft.com/en-us/library/cc527605(WS.10).aspx

Remove old Active Directory Group Policy objects for Windows SBS 2008 migration: http://technet.microsoft.com/en-us/library/cc527585(WS.10).aspx

Step 10. Migrate users’ Shared Data

This is another task where you need to perform the configuration manually. The steps required can be found here: http://technet.microsoft.com/en-us/library/cc527517(WS.10).aspx

Once you have the shares configured a simple backup of the SBS2003 server and restore to the 2011 server will restore all data with associated permissions.

Alternatively you could use robocopy which is part of the Windows 2003 Resource Kit which can be downloaded from: http://www.microsoft.com/downloads/en/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

There is also command line reference for robocopy here: http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx

Step 11. Migrate Fax Data

There is no fax function in SBS2011 (this may change in the final release) but if you already have Fax data stored on the SBS2003 server you will need to migrate this data.

Launching the wizard will display the following screen.

Clicking the hyperlink Click to start Migrating your fax data this will move the data to the new server. At this stage if there is no fax services installed/configured on the SBS2003 server you will receive the error displayed below.

This is not a problem and can be ignored, mark this task as complete.

Step 12. Migrate Users and Groups

As part of joining the SBS2011 server to the domain which contains SBS2003 and making it a Domain Controller it has already got a copy of the Active Directory and all the users and groups.

However, they will not appear in the SBS Console, this is normal and can be resolved following the instructions here.

To allow the users to be seen a new role needs to be applied. To do this on the first screen the wizard shows a hyperlink to Run the change user role wizard as illustrated below.

Click this link, to start the wizard. From the list displayed select the role you wish to assign to these users.

On the following screen put a check in the box for Display all user accounts in the Active Directory as illustrated below. This will display all of the users. Highlight your existing user then click the Add button to move them to the right hand side.

Click the change user role button. We are looking for a screen similar to the one below with lots of green ticks to confirm the roles have changed.

Step 13 – Uninstall Exchange 2003 from Small Business Server 2003

Hopefully you are arriving at this step a day or two after you have migrated all the mailboxes, if not then I would recommend you leave it for a day or two just to allow all client computers to automatically update the Exchange server setting in outlook. If you uninstall Exchange 2003 from the Small Business Server and this hasn’t happened then the clients will have to be changed manually.

To perform this task we will need Small Business Server 2003 CD 2, which will be asked for during the uninstallation. Before we can do this though, there are a few steps we need to perform otherwise we will not be able to uninstall it.

If you use Recipient Policies that are Manage Mailbox policies, then these will need to be removed. Likewise, if you have Recipient Policies that are used for both e-mail address definition and mailbox management, the settings defined under Mailbox Manager Settings will need to be removed. You DO NOT need to remove your e-mail address policies.

The Recipient Update Service is not used in Exchange 2010 and is therefore not required, so it can be removed. To do this you will need to use ADSI Edit. This can be done by using the following procedure:

  1. Click Start > Run > MMC > Click OK
  2. Select File then Add/Remove Snap-in
  3. Click Add and select ADSI Edit and click Add, then close and OK
  4. Right click on the ADSI Edit and select ‘Connect to’. From the drop down under ‘Select a well known Naming Context’, select Configuration and click OK
  5. Expand Configuration > Services > Microsoft Exchange > Organisation Name > Address List Container > Recipient Update Services

Right click on Recipient Update Service (Enterprise Configuration) and select Delete. There may also be a Recipient Update Service (ORGNAME) this also needs to be deleted

Only delete the Recipient Update Service entries under the container; DO NOT delete the container itself or any other entries

The final step in preparation for uninstalling Exchange Server 2003 is to delete the routing group connectors that would have been created as part of the installation. I have highlighted them in the image below. Simply right click on each connector and select delete.

We are now ready to uninstall Exchange 2003. To do this, navigate to Start > Control Panel > Add or Remove Programs. From the list of installed applications, highlight Windows Small Business Server 2003 and click Change/Remove.

Click next on the Welcome screen, and next on the screen that follows. Once the component screen opens pull down the drop down next to Exchange Server and select remove, as shown below. Then click next and next again.

Step 14. Check Transfer of the 5 FSMO roles to SBS2011

All of the 5 FSMO roles should already have been transferred to the SBS2011 as part of the installation process but it’s always worth a check. The steps below will give instructions on how to do this if required.

Caution needs to be taken when performing this next step.[/b] I would advise that ALL of the previous steps need to be completed before this is done as Small Business Server MUST hold all 5 FSMO roles.

Once you are ready, the roles can be transferred as follows. Working on the Windows 2008 server do the following:

  1. Click Start > Administrative Tools > Active Directory Users and Computers
  2. Right click on the domain name and select Operations Masters. You will see the screen below.
  3. On each tab (RID, PDC & Infrastructure) click the change button.
  4. Accept the confirmation that you want each role to be transferred.

That is 3 of the 5 roles transferred. To do the next one, which is the Domain Naming Master we need to do the following:

  1. Click Start > Administrative Tools > Active Directory Domains and Trusts.
  2. Right click where it says Active Directory Domains and Trusts and select Operations Master.
  3. Once again click the Change button and say yes to the notification dialog.

4 down with 1 to go. To move the Schema Master role we need to do the following:

  1. Click Start > Run and type regsvr32 schmmgmt.dll
  2. Click OK to the confirmation
  3. Click Start > Run and type MMC and click OK
  4. Select File > Add/Remove Snap-in from the console
  5. From the list select Active Directory Schema, click Add
  6. Click Close and OK.
  7. Right click on Active Directory Schema and select Change Active Directory Domain Controller
  8. Choose the Windows 2008 Server from the list and click OK
  9. Click OK on the warning Dialog box.
  10. Right click on Active Directory Schema and select Operations Master
  11. Click the Change button and say yes to the notification dialog

That’s all the FSMO roles transferred from the Small Business 2003 Server. The next and final step is to demote the server from being a Domain Controller.

Step 15. DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network

This is the final step of the migration process. If you have made it this far, well done! This is the easy bit!

At this point it is worth double checking that both the SBS2003 and SBS2011 server are both configured to use the SBS2011 server for DNS in the TCP/IP properties of the NIC. The only DNS entry should be the IP address of the SBS2011 server.

The first thing we need to do is make sure the SBS2003 is no longer a Global Catalog Server. Click on Start > Administrative Tools > Active Directory Sites and Services. Locate the Small Business Server

Right click on NTDS settings located under the Small Business Server and select properties. Remove the check from the Global Catalog check box and click OK. Close Active Directory Sites and Services snap-in.

The final step is to run DCPROMO. To do this, do the following:

Click Start > Run and type DCPROMO and click OK

Click next on the Welcome screen

DO NOT check the box that says “This server is the last domain controller in the domain” and Click next

Enter a new administrator password for the local administrator user and click next

The server will then remove Active Directory Services from the SBS2003 server and it will no longer be a Domain Controller.

Once this has finished, allow the server to restart, login and then shut it down. You have now completed the migration.

If you are still with me, well done! There are a few sections of additional reading below if you would like to know some more detail about some of the processes we have just completed. There is an excellent article from EE Expert tigermatt around the purpose of the FSMO roles which you will find under the further reading section.

Further Reading

You will also need a trusted SSL Certificate which can be purchased from http://www.exchangecertificates.com

Move/Migrate Sharepoint Services: http://technet.microsoft.com/en-us/library/cc288664.aspx

Move last legacy Exchange Server: http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

Demystifying the Active Directory FSMO Roles by tigermatt: http://www.experts-exchange.com/articles/Software/Server_Software/File_Servers/Active_Directory/Demystifying-the-Active-Directory-FSMO-Roles.html


Domain Names are a critical part of your Windows Environment.  The DNS (Domain Name System) is a foundation upon which Active Directories and Resources rely upon.  It can be a real problem if you need to go back and change your Domain Name.

So, before building your Windows domain it is important to choose the “correct” domain name.  Wherever possible you need to try and plan ahead, of course you cannot plan for company name changes or, a take over in years to come, because you simply don’t know about them. But….we can plan to be flexible, and we must consider technical and ownership issues at the same time.

Choosing your domain name

Whilst most people believe that the internal windows domain name needs to be something.local this isn’t strictly true.  While it is often easier if the suffix is .local, strictly speaking, it doesn’t have to be.  Let’s consider that point…

Some of the largest enterprises in the world use their external domain name on their internal network.  The most important consideration is that if you use domainname.com that you actually own domainname.com.

Why is this important? One of the main reasons that this is becoming a problem in recent days is because of 3rd Party SSL Certificates that are used to secure Small Business Server and/or Exchange 2007/2010. One of the default requirements for these systems is using the internal fully qualified domain name of your Exchange Server.

So by way of example let’s say you have an internal domain name of virtualdomain.com and your external domain name is abc.com.

When setting up an Exchange 2007/2010 server you would need to request an SSL Certificate that contained the following names:

  • Autodiscover.abc.com
  • owa.abc.com
  • exchangeserver.virtualdomain.com

When you request a certificate with these names in the first thing the Certificate Authority (CA) will do is perform a WHOIS lookup on the names you have requested. Anything .abc.com will show as your company owning the registration.

However when the CA performs a WHOIS lookup on exchangserver.virtualdomain.com they find that the registrant of this domain is a different company and therefore send them a request to authorise the name. Worse, if they don’t find a registrant for the domain then it is removed from the certificate request.

Can you see the problem?  If you own virtualdomain.com then by all means use it in your internal domain name.  If you don’t own it then don’t use it.

This is why most consultants will opt to use the .local suffix on internal domains.  Because when the CA receives a request .local they know it’s not an internet suffix and they will authorise it.

Now what about the dreaded company rename?…..Another common misconception is that when setting up a Windows Domain you must use the domain name for which you want to receive email for.  This is completely untrue.

You can configure Small Business Server and all versions of Microsoft Exchange Server to receive emails for any domain name, regardless of your internal domain name.  So let us now consider calling your internal domain name mydomain.local?

  • It is not linked to a specific company name
  • it will allow you to receive emails for your abc.com email domain
  • if you change your company name you don’t need to worry about trying to change the domain name so the new owner (or existing one) doesn’t have to see the old company name day in day out?
  • because it has a .local suffix you will never run in to problems in the future with SSL Certificates


With wider use of SSL certificates and a few common misconceptions created by the industry, it is important to deliberate over your internal domain name selection.  It’s also important to think ahead.

What might be a good idea or even a bit of a laugh now, could come back to bite you in the rear in a few year’s time.  So, be careful and conservative when choosing your name.

I personally like to give my domains something non-descript, because I do a lot of work for small businesses which can and often do get taken over.  I had one company that was bought out twice within the space of 3 years. I also had one company that split in to 2 companies and then both renamed themselves.

It can get messy and especially with Small Business Server where the internal domain name cannot be renamed, it can be impractical to use company specific domain names.

Of course there is always the case where the owner wants this but it’s our job as consultants to advise them why this isn’t a good idea.  And if they still want it then get it in writing 🙂

2010 in review

Posted: January 2, 2011 in Exchange Server

The stats helper monkeys at WordPress.com mulled over how this blog did in 2010, and here’s a high level summary of its overall blog health:

Healthy blog!

The Blog-Health-o-Meter™ reads Wow.

Crunchy numbers

Featured image

About 3 million people visit the Taj Mahal every year. This blog was viewed about 39,000 times in 2010. If it were the Taj Mahal, it would take about 5 days for that many people to see it.

In 2010, there were 38 new posts, not bad for the first year! There were 190 pictures uploaded, taking up a total of 13mb. That’s about 4 pictures per week.

The busiest day of the year was October 5th with 376 views. The most popular post that day was About.

Where did they come from?

The top referring sites in 2010 were experts-exchange.com, forums.msexchange.org, uksbsguy.com, google.com, and gfi.com.

Some visitors came searching, mostly for exchange 2010 offline defrag, import pst exchange 2010, exchange 2010 import pst, import pst in exchange 2010, and exchange 2010 cannot receive email.

Attractions in 2010

These are the posts and pages that got the most views in 2010.


About March 2010


Outlook continually prompting for username and password February 2010


Exchange DNS Configuration February 2010
5 comments and 1 Like on WordPress.com,


Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2 April 2010
7 comments and 1 Like on WordPress.com,


Importing PST files in to Exchange 2010 March 2010
1 comment

Since Exchange 2010 Service Pack 1 we have been promised an update for Microsoft Outlook 2007 that will provide support for the Personal Archive feature of Exchange 2010.

Previously this was only available using Outlook Web App or Microsoft Outlook 2010.

The update to allow this support in Microsoft Outlook 2007 is now available.

See here for further details: http://msexchangeteam.com/archive/2010/12/20/457238.aspx

I have written a guide here on how to resolve a common authentication problem when using Exchange 2007: https://demazter.wordpress.com/2010/02/09/outlook-continually-prompting-for-username-and-password-2/

Through my own problems I have also identified a configuration problem which can cause Outlook when used with Exchange 2010 to cause a similar issue.

This is caused by a mismatch in the configuration of Exchange and Outlook.

If one is set to Basic Authentication for RPC-HTTPS and the other for NTLM authentication it will cause this problem.

To resolve this, using the Exchange Management Console under Server Configuration right click on the server providing the Client Access role and select properties.  Under the Outlook Anywhere tab check the authentication methods.  Make a note of how it’s set.

Then, in Outlook goto Tools > Account Settings.  Highlight the account configured to use Microsoft Exchange and select properties.

Under advanced and connection settings at the bottom of the screen is the authentication setting in use.

Make sure they are the same.

After deciding to use my FTMG server for Spam Protection using the Microsoft Exchange Edge Transport syncronisation I proceeded to follow the configuration guides on Technet.

Everything seemed to be working excellently, SPAM was reduced considerably.  Then out of nowhere a number of people contacted me to say that they were receiving Non Deliverable Reports when trying to send me emails.  The content of the NDR was:

#< #5.7.1 SMTP; 550 5.7.1 External client with IP address w.x.y.z does not have permissions to submit to this server. Visit http://support.microsoft.com/kb/928123 for more information.> #SMTP#

I thought this was a bit odd because it had been working without issue for nearly a week.  Upon investigation I found the Forefront TMG Managed Control Service was not started on my FTMG Server.  This service controls the integration of the FTMG E-Mail Policy with the Exchange Edge Transport server.  Trying to start the service simply failed with an error of:

Windows Could not Start the “Microsoft ForeFront TMG Managed Control” service on Local Computer
Error 0x80070057 : Parameter is incorrect

I did a bit of searching and found that this could be caused by the IP Block List in the Exchange Management Console filling up with IP addresses.  My first thought was why the IP Block List on FTMG was not reflecting this?  Maybe that’s one for the FTMG Product Team. 

I opened the Exchange Management Console and checked the IP Block List, which was enabled, to see what was listed.  This didn’t go so well.  I received the following error message:

Obviously this was not good! I couldn’t control Exchange through the FTMG Console (which is where all configuration changes are supposed to be made.  But worse, I couldn’t control it through the Exchange Management Console either. 

Last resort, I tried the Exchange Management Shell.  Running the following command: Get-IPBlockListEntry provided me with a list of over 100 IP addresses that had been blocked.  Excellent, at least I now knew I could do something via the EMS.  Running Get-IPBlockListEntry | Remove-IPBlockListEntry removed all the IP Addresses.  I was then able to start the Forefront TMG Managed Control Service.

First thing I did was disable the IP Block List – using the FTMG console of course! My server has now been running happily for nearly 24 hours again.

This kind of begs the question as to how and why the IP Block List on the Edge Transport server is filling up with IP addresses, and I guess more importantly, why the same IP Block List in FTMG does not reflect the contents of the Edge Transport Server?

Exchange 2010 Service Pack 1 Rollup 1 available.  This can be downloaded from: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a371fa96-e85b-4a4f-8242-15d56595d0ec&displaylang=en

This mainly resolves a public folder replication issue but the full listing can be found here: http://support.microsoft.com/?kbid=2407028