Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2 - Exchange 2010 Migration, SBS2003, Small Business Server 2003, migration to Exchange 2010

Start FREE Trial Contact Us Member Login

Enter Your Search Terms

Home Software Server Software Email Servers Exchange Migrate Small Business Server 2003 to Exchange 2010 and Windows 200...

ID: 2881

Migrate Small Business Server 2003 to

Exchange 2010 and Windows 2008 R2

demazterPosted on 04/16/10 at 4:03 AM71 of 71 members found this article helpful.

This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows2008 R2 with Exchange 2010.

For this migration to work you will need the following software:

Windows Small Business Server 2003 (SBS 2003)Windows 2008 Server or Windows 2008 R2 ServerExchange Server 2010Microsoft Office Filter Pack from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=60c92a37-719c-4077-b5c6-cac34f4227cc&displaylang=enWindows SharePoint Services 3.0 with integrated Service Pack 2.Only the version with Integrated Service Pack 2 willinstall on Windows 2008 R2. You can download it from here: http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=enMicrosoft SQL Server Management Studio Express which can be downloaded from: http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796&displaylang=en You will need to download both the32bit and 64bit versions

Steps required:1. Health Checks on Small Business Server 20032. Join new Windows 2008 Server to the domain as a member server3. Prepare Active Directory for Windows 2008 R2 Server4. Make Windows 2008 R2 Server a Domain Controller of the Existing Small Business Server 2003 Domain5. Transfer DHCP Service6. Install Exchange 20107. Installing Exchange 2010 SSL Certificate8. Migrate Exchange Data9. Migrate SharePoint Services10. Migrate shared user data11. Uninstall Exchange 2003 from Small Business Server 200312. Transfer all 5 FSMO roles to Windows 2008 Domain Controller13. DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network

It’s important that the steps are followed in order as different stages make different changes to the way in which your serveroperates. For example you MUST make the 2008 server a domain controller before you install Exchange.

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 fullsystem backup. There is little chance of the data getting lost but the SYSTEM STATE backup backs up Active Directory sothat if it all goes wrong we can recover it if needed.

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

Windows 2003 Service Pack 2Windows Small Business Server Service Pack 1Microsoft Exchange 2003 Service Pack 2

Once you have installed all of the above, run Windows Update and make sure you select the option in the blue banner baracross the top for Microsoft Update. Microsoft Update will then allow you to update all Microsoft products installed on theserver providing a more comprehensive update solution. Keep running the check and installing all updates until there are nomore available.

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

Run the Small Business Server 2003 Best Practices Analyser from here: http://www.microsoft.com/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Make sure you fix any problems the analyser identifies. If you cannot, then why not raise a question on EE to have our Expertshelp you?

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

Step 2 - Join new Windows 2008 Server to the domain as a member server

Remember Me

Username or Email

Password

Sign Up Forgot Password?

ADVERTISEMENT

Migrate Small Business Server 2003 to Exchange 2010 and Windows 2... http://www.experts-exchange.com/Software/Server_Software/Email_S...

1 of 31 23/12/2010 12:31 PM

ADDS-Wizard-01.jpg (68 KB) (File Type Details)

To join a Windows 2008 Server to the Small Business Server domain we need to first ensure that it is receiving a correct IPAddress

Allow the Windows 2008 Server to receive a DHCP Address from your Small Business Server. Run an IPCONFIG /ALL tocheck this. The DNS Server entry is probably the most important. This should be configured to use the IP Address of yourSmall Business Server for DNS.

To test, it might be worth just pinging the SBS 2003 server from a command prompt just to check the name can be resolved bydoing the following:

Click Start > Run > type CMD and then click OKtype PING SBS2003SERVERNAME

If you get a good response then we can try and join the 2008 server to the domain.

To Join the Server to the Domain, do the following:Click Start and right click on Computer and select propertiesFrom the screen that opens under the section called Computer name, domain, and workgroup settings click Changesettings. Then click on ChangeAt this point if you haven’t already specified the name of your new server you can do soCheck the radio button next to where it says Domain and enter the domain name that the Small Business Server 2003 belongs toClick OKAt which point you will be prompted for a username and password for a user that has permissions to add the computer tothe domainOnce you have added your credentials and click OK you will then be informed the server requires restarting. Pleaserestart to resume the migration

Step 3 - Prepare Active Directory for Windows 2008 R2 Server

The first step of this process is to raise the Functional Levels of the SBS 2003 server. This involves raising the domain andforest functional level of Active Directory and the Operational mode of Exchange Server.

To raise the Domain Functional Level do the following:Click Start > Administrative Tools > Active Directory Users and ComputersRight click on the domain name and select Raise Domain Functional LevelIn the drop down box select Windows Server 2003 and click OK (if this has already been done don’t worry)

To raise the Forest Functional Level do the following:Click Start > Administrative Tools > Active Directory Domains and TrustsRight click where it says Active Directory Domains and Trusts and select Raise Forest Functional Level.

And we also need to raise the Exchange Operational Mode. To do this, you need to do the following:Click Start > All Programs > Microsoft Exchange > System ManagerRight click on the Organisation name right at the top of the list and select propertiesIn the dialogue box check the Operational Mode, if it says Mixed Mode click the Change Mode button and say yes to thedialogue box asking if you want to change to native mode

Before we can add the Windows 2008 Server as a domain controller to the SBS 2003 domain, we need to prepare ActiveDirectory.To do this use the following procedure whilst working on the Small Business Server

Insert the Windows 2008 DVD in to the Small Business Server. Ignore the autorun message that appears telling you thisversion is incompatible by clicking OKOpen a command prompt (Start > Run > CMD) and run the commands below

NOTE: X: refers to the drive letter that has been assigned to your DVD Drive.X:\support\adprep\adprep32 /forestprep

After the above command you will be prompted to confirm you wish to proceed by typing the letter C and pressing

Enter

X:\support\adprep\adprep32 /domainprepX:\support\adprep\adprep32 /domainprep /gpprepX:\support\adprep\adprep32 /rodcprep

Step 4 - Make Windows 2008 R2 Server a Domain Controller of the Existing Small Business Server

2003 Domain

To make the Windows 2008 Server a Domain Controller is fairly straight forward, we simply click Start > Run and typeDCPROMO click OK.

This will check that the Active Directory Services Binaries are installed and if they are not, it will install them. It will then startthe Active Directory Domain Services Installation Wizard.

ADDS-Wizard-01.jpg

1. demazter 2,376,422

2. alanhardisty 2,307,304

3. Akhater 2,167,491

4. endital1... 1,147,972

5. sunnyc7 1,134,187

6. shreedhar 965,637

7. busbar 859,751

8. MegaNuk3 642,834

9. shauncro... 519,138

10. jjmck 492,084

11. EndureKona 472,408

12. SatyaPathak 423,674

13. AshwinR... 294,645

14. BlueDevilF... 290,154

15. Chris-Dent 287,638

16. bryon44... 284,988

17. jjdurrant 244,887

18. JuusoCon... 242,749

19. Hilal1924 226,361

20. Narayan... 218,062

21. Mestha 217,967

22. Raheem05 195,847

23. Tony1044 195,357

24. Spec01 190,368

25. cgaliher 179,765

1. Sembee 19,666,085

2. Mestha 6,959,258

3. demazter 3,752,607

4. alanhardisty 3,644,927

5. rakeshmig... 2,521,226

6. Akhater 2,484,171

7. redseatec... 2,342,875

8. tigermatt 1,968,847

9. gupnit 1,770,113

10. LeeDerby... 1,713,483

11. endital1... 1,410,830

12. Exchange... 1,327,609

13. kieran_b 1,285,184

14. mass2612 1,270,104

15. busbar 1,266,804

16. Vahik 1,265,183

17. shauncro... 1,231,146

18. Chris-Dent 1,223,391

19. flyguybob 1,182,799

20. Kidego 1,171,155

21. sunnyc7 1,134,187

22. TechSoEasy 1,107,068

23. ATIG 989,109

24. shreedhar 965,637

25. BlueDevilF... 930,304


2 of 31 23/12/2010 12:31 PM



On the first screen, there is no need to check the 'Use Advanced mode Installation' check box, just simply click next. On theoperating System Compatibility screen click next.

ADDS-Wizard-02.jpg

On the 'Choose a Deployment Configuration' screen, select the radio box for Existing Forest and Add a domain controller to anexisting domain. Then Click next.

ADDS-Wizard-03.jpg


3 of 31 23/12/2010 12:31 PM


On the 'Network credentials' screen, the name of the domain should have been detected automatically. Check this is correct. If you are logged in as a user that has domain admin privileges then you can use the My Current logged on credentials option. If not, click the set button and add the username and password that has domain admin privileges as shown in the screenabove. Click Next.

The following screen will give you the results of a domain search and ask you which domain you want to add this domaincontroller to. As you are upgrading Small Business Server there should only be one. Click Next.The next screen will give you an option to select the site for the new domain controller. If you have more than one ActiveDirectory Site ensure that you select the correct one if it hasn’t been done by default. Click next.

ADDS-Wizard-04.jpg

On the 'Additional Domain Controller Options' screen, make sure that both the DNS Server and the Global Catalog options areboth checked. Click Next. The error message regarding DNS Delegation can safely be ignored. Click Yes on this dialog tocontinue.

If you have separate folders where you want to store your log files, SYSVOL share and the Active Directory database thenthese can be specified on the next screen. To be honest I keep them all as defaults. Once done, click Next.

On the following screen, you are asked to set a password for Directory Services Restore Mode Administrator (DSRM). Pleasenote this is NOT the Domain Administrator password. This password is used to boot the Domain Controller into DirectoryServices Restore Mode which is used for recovering corrupt/deleted/failed Domain Controllers. Make a note of this passwordand keep it somewhere safe (in a fire safe for example).


4 of 31 23/12/2010 12:31 PM

DHCP-Service-01.jpg (103 KB) (File Type Details)


Click Next on the following 2 screens. The wizard will then start the promotion of the server to a domain controller (I alwayscheck the box on this screen to reboot on completion - This way you can leave it and come back to it knowing that it will beready to continue).

Once rebooted your new server will be a domain controller, DNS server and Global Catalog server in your Small BusinessServer Domain.

Step 5 - Transfer DHCP Service

By default the Small Business Server will be the DHCP Server (if it isn’t and you're using something else for DHCP, then youwill simply need to update the DNS configuration this device is giving out so that it points to the 2008 Server instead of the2003 Server) we will need to transfer this to the new server.

We can start this process by installing the DHCP Service.

DHCP-Service-01.jpg

To install DHCP, open up Server Manager and under Roles, click Add Role. From the list, select DHCP Server and click Nextthen next on the Introduction to DHCP Server screen.

On the network Connection Bindings screen you should have your primary IP address listed. As you will be installingExchange on this server it’s not recommended to have a multi-homed server but if you do make sure the LAN card and IP is theonly one selected. Click next.

NOTE: A multi-homed server is a server that has multiple IP addresses assigned to multiple Network Interface Cards. Normallythese types of servers would be used as routers. Whilst Exchange can be made to work in this environment, it's notrecommended.

DHCP-Service-02.jpg

On the Specify IPv4 DNS Server Settings check the following settings:Check the parent domain name is correct


5 of 31 23/12/2010 12:31 PM



Make sure that the IP Address listed for Preferred DNS server IPv4 Address is the address of the new Windows 2008ServerRemove any entry in the Alternate DNS Server IPv4 Settings as these will not be requiredClick next

Click next accepting the default settings on the WINS screen.

On the Add or Edit DHCP Scopes screen, click Add. This will present you with the Add Scope dialog box.

DHCP-Service-03.jpg

On this screen enter the following details:scope namethe start IP addressthe end IP address

(This should be the same as the DHCP Scope you have configured on the Small Business Server).Uncheck the box that says Activate this scope (we don’t want it just yet)The subnet mask should have been calculated automatically but if it isn’t correct then please change it to ensure it isEnter the default gateway; this will be the router on your network

You will notice in the scope I am creating, I have started from 192.168.10.15 this is so that I have 15 addresses that I canassign to fixed addresses. My Small Business Server and Windows 2003 server will have an address below 192.168.10.15but I might also have printers, photocopiers, and wireless access points that also need fixed IP addresses. I have also left192.168.10.254 available to use for my router.

Once you have completed all the details, click OK and then Next.

Accept the default setting on the 'Configure DHCPv6 Stateless Mode' and the Specify IPv6 DNS Server Settings.

On the 'Authorize DHCP Server' screen, select to use the current credentials and click Next, then Install on the confirmationscreen.

The DHCP Server service is now installed on the Windows 2008 server.

Before we can switch over, we need to make some changes to the Small Business Server DHCP settings. Whilst we can justturn one off and turn the other on this will cause you to have to release and renew the settings on the client machines manuallyfor them to pick up the new DHCP Service. The alternative is to wait the 4 days before your client machines request an IPaddress renewal.

To make the required changes, do the following on the Small Business Server:Navigate to Start > Administrative Tools > DHCP this will open the DHCP snap-inRight click on the Scope listed under your Small Business Server and select properties

DHCP-Service-04.jpg


6 of 31 23/12/2010 12:31 PM

In the section titled 'Lease duration for DHCP clients' we are going to change it to 2 hours from the default of 8 days. Click OK

Then under Address Leases, highlight all DHCP Leases, right click and select delete. NOTE: If you have any reservedaddresses make sure they are not highlighted otherwise they will be deleted also.

This action will cause all DHCP clients to renew their addresses and gain an address that has a 2 hour lease. Check theAddress Leases and refresh until you are happy that all the clients now have an IP address. (You might want to leave thisovernight just to make absolutely sure)

Once you are happy that all the clients have now got a 2 hour lease from the Windows 2008 server do the following:Navigate to Start > Administrative Tools > DHCPExpand the Windows 2008 servername and IPv4 then right click on the scope listedSelect Activate

This will start the DHCP Service on the 2008 server and deactivate the service on the Small Business Server (this will happenautomatically because when Small Business Server detects another DHCP server on the network it shuts its own down).

You will now find that in approximately 1 to 2 hours time, all your clients will start picking up IP addresses from the Windows2008 Server.

You can now disable the DHCP Server service on the Small Business Server. DO NOT disable the DHCP Client service, asthis plays a part in DNS registration.

Now that all the clients are using the new Windows 2008 Server for DHCP and DNS, we need to make sure that the SmallBusiness Server is also using the Windows 2008 Server for DNS. To do this modify the TCP/IP properties of the network cardand change the Primary DNS servers IP address to that of the Windows 2008 Server. Do not enter anything in the SecondaryDNS server.

Once you have done this restart the NETLOGON service so that the DNS entries are added to the Windows 2008 DNS.

Step 6 - Install Exchange 2010

Because we performed all the diagnostic checks at the start, the installation of Exchange 2010 should be fairly straight forward. Please note that even though the installation of any version of Exchange Server on a domain controller is supported byMicrosoft, it is not a recommended configuration. But since we are migrating from Small Business Server the chances are youstill want to stick with a single server configuration.

The first step is to install the pre-requisites on Windows 2008 to allow the Exchange 2010 installation to complete. This can bedone very easily using the Windows PowerShell.

To do this, please use the following steps:Click Start > All Programs > Accessories > Windows PowerShell

Once the PowerShell is opened run the following commands:Import-Module ServerManager

There is no notification this has completed you will just see a flashing cursor waiting for input. This command will allow us toadd server roles and features via the PowerShell command.

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

This command will install all the pre-requisites for the Mailbox, Hub Transport and Client Access roles on to the Windows 2008Server. This will replicate what you currently have on the Small Business Server.Once the server has restarted after the above command, launch the Windows Powershell again and run the followingcommand:

Set-Service NetTcpPortSharing -StartupType Automatic

This will set the Net.Tcp Port Sharing Service to Automatic instead of Manual

Install the Microsoft Office Filter Pack (which you should have downloaded earlier from the top list of required software).

Once we have done this, we need to prepare Active Directory for the Exchange 2010 installation.

Unlike previous versions, Exchange 2010 will detect if the schema updates have been done and do them if not, I prefer to see


7 of 31 23/12/2010 12:31 PM

Exchange-Setup-01.jpg (91 KB) (File Type Details)


this happen.

To prepare Active Directory for Exchange 2010 we need to do the following:Insert the Exchange 2010 DVD in to the Windows 2008 ServerOpen a command prompt (Start > Run > CMD)Run D:\setup /PrepareLegacyExchangePermissionsRun D:\setup /PrepareSchemaThere is an additional command which is: setup /PrepareAD /OrganizationName: but I am going to let the ExchangeServer installation do this part

Start the Exchange installation from the DVD. On the initial splash screen that opens, click Step 3: Choose ExchangeLanguage Options, select the appropriate option then click Step 4: Install Microsoft Exchange. The Exchange InstallationWizard will then start.

The first screen you see is the Introduction screen, click Next. Read, agree to and accept the license agreement screen.

Exchange-Setup-01.jpg

This screen allows us to choose the type of installation. As it’s assumed the Exchange 2010 server is a direct replacement forSmall Business Server and all roles will be installed on a single server, we simply select Typical Exchange Server Installationand Click next.

If we were separating our roles out on to different servers we would select Custom Exchange Server Installation and then clicknext.



8 of 31 23/12/2010 12:31 PM



This screen allows us to specify what URL will be used for accessing our Outlook Web App from outside of the network. Whatever you put in here you will need to make sure you have a DNS A record for it in your EXTERNAL DNS server. In thelater steps you will also need to use this name in your SSL Certificate Request. (CSR)

Check the box 'The Client Access role server will be internet-facing' and then specify the URL you will use, do not add https://or anything at the end i.e. /owa. Click next.


This screen is asking us to specify the Exchange 2003 server that the installation will create a routing group connector for. This is essential for mailflow between the servers. Click Browse, the list should be generated automatically and you will beable to select the Small Business Server from the list. Click OK and then next.

Choose on the next screen if you wish to participate in the Customer Improvement program and then click next. At this pointthe readiness checks will be performed to ensure your infrastructure is ready for Exchange 2010.



9 of 31 23/12/2010 12:31 PM


The results of the readiness check should show a warning on the Organisation Prerequisites, this is normal and it’s becausewe didn’t run the setup /PrepareAD /OrganizationName: command earlier on. This can safely be ignored as the setup willperform this task for us.

The other cautionary warning you will see on my screen capture is simply because I haven’t installed the Office Filter Pack soyou will only see this if you didn’t follow the step earlier. Once you click install, the wizard will Install Exchange Server 2010. And we are looking for the screen below. All green.


Now that Exchange is installed, using the Exchange Management Console, navigate to Server Configuration > Hub Transport. Here there will be 2 Receive Connectors listed.

The one we will be dealing with is the one that starts with the word Default and is followed by the name of the Exchange 2010server. Right click on this Receive Connector and select properties. Under the Permission Groups tab, check the box forAnonymous Users. If this box is not checked then servers sending mail to you will not be able to connect. Your e-mails withtherefore be rejected.

One final task before we move on, is to reconfigure any firewall/router rules you may have for ports 25 and 443 to allow theExchange 2010 server to now deal with SMTP traffic and Outlook Web App.

Step 7 - Installing Exchange 2010 SSL Certificate


10 of 31 23/12/2010 12:31 PM

SSL-Cert-01.jpg (59 KB) (File Type Details)


Exchange 2010 installs with a self-signed certificate by default. Whilst this will work, it will cause browser errors in the form ofuntrusted websites, Outlook errors for Autodiscover (which is used for free/busy information & Offline Address Book) and errorswhen using mobile devices and Outlook Anywhere. Whilst for the most part there are ways around these problems, I won’t becovering them in this article because my recommendation, as any other Exchange specialist would recommend, would be touse a 3rd party certificate.

Unlike earlier versions of Exchange, we have a nice easy to use wizard in the Exchange Management Console for certificategeneration. This makes installing commercial certificates in Exchange 2010 much easier and less prone to error.

To start the New Exchange Certificate wizard do the following:Click Start > All Programs > Microsoft Exchange Server 2010Navigate to Microsoft Exchange On-Premises > Server ConfigurationIn the Actions pane click New Exchange Certificate

This will start the New Exchange Certificate Wizard

SSL-Cert-01.jpg

Enter a friendly name for the certificate. This can be whatever you like, but standard practice is to use the company name orsomething that can identify your company. Click NextDO NOT Select to create a wildcard certificate unless you plan on buying a certificate for your entire domain, which is notrequired for Exchange to function. Click Next

SSL-Cert-02.jpg


11 of 31 23/12/2010 12:31 PM


On the following screen pull down the arrows for:Client Access Server (Outlook Web App)Client Access Server (Exchange ActiveSync)Client Access Server (Web Services, Outlook Anywhere, and Autodiscover)

Make sure all the URLs are correct (examples can be found in my screen capture above) and then click Next.

SSL-Cert-03.jpg


12 of 31 23/12/2010 12:31 PM



Confirm the entries on the next page (it’s worth noting on this screen that the address shown in bold is what is known as aCommon Name). This could be important later as Outlook Anywhere requires the common name to be the same as the URLused in the RPC connection. In most of my configurations I use the owa.gkvirtualdomain.co.uk as the common name. To dothis, highlight the URL and click the Set as Common Name option. Click next when finished.

SSL-Cert-04.jpg

You then need to complete your organisation information as shown in the screen above. Then click New on the next screen.And then finish.

You can then open the file you have specified to create the request with, copy and paste the entire contents into the 3rd partyvendors website and follow their instructions for submitting it.

SSL-Cert-05.jpg


13 of 31 23/12/2010 12:31 PM

Exchange-Migration-01.jpg (101 KB) (File Type Details)


Once you receive the signed certificate, right click on the certificate request located as above and select Complete PendingRequest. Follow the instructions to import the certificate you have just received.

Step 8 - Migrate Exchange Data

Now we have Exchange installed, it’s time to migrate the data over. We will start with the easy part as a bit of a break from theprevious 6 steps.

Exchange-Migration-01.jpg

To migrate the user mailboxes, open Exchange Management Console and navigate to Recipient Configuration > Mailbox.Highlight the mailboxes you want to move (the mailboxes that are on the Exchange 2003 server will appear as LegacyMailboxes, as pictured above), right click on them and select New Local Move Request



14 of 31 23/12/2010 12:31 PM


When the New Local Move Request wizard opens, click the browse option to select the Windows 2008/Exchange 2010 servermail store and click OK, then click next.

On the following screen, select what you would like to do when the wizard encounters corrupt messages. You have twooptions: either to skip only the corrupt message or to skip the whole mailbox. Click next and on the following screen click New.


Once the move requests have been verified, we should see the screen above. All the mailboxes you selected should hopefullyshow a green tick. Please note that during the move mailbox process, the user will not have access to their mailbox as it ismoved “offline”.

The next stage is to migrate the Public Folders. To do this complete the following steps on the SBS 2003 Server:Click Start > All Programs > Microsoft Exchange Server > System ManagerNavigate to Administrative Groups > First Administrative Group > Servers > Servername > First Storage GroupRight click on the Public Folder Store and select Move All Replicas. The only option that should appear in the list is yourExchange 2010 server. Click OK.

Now that we have moved the data to the Exchange 2010 server it’s best to leave this for a day or so to a) make sure all thedata is moved before we perform any other Exchange related tasks. b) allow all the outlook clients to update automatically withthe new server settings.

Step 9 - Migrate SharePoint Services


15 of 31 23/12/2010 12:31 PM

Sharepoint-Migration-01.jpg (88 KB) (File Type Details)

Sharepoint-Migration-02.jpg (31 KB) (File Type Details)

If you are using companyweb for an intranet/document storage etc. then you will also need to migrate this. If you are not usingSharePoint then simply skip this step.

First thing you will need to do is to install the Windows SharePoint Services 3.0 which you downloaded as part of thepre-requisites. This is the free version of SharePoint Services. Only the version with Integrated Service Pack 2 will install onWindows 2008 R2.

Once you have downloaded Windows SharePoint Services 3.0, double click to start the installation on the Windows 2008Server. Read, agree to and accept the license agreement and click continue. Select Basic installation. This will install thestandard single site installation.

Once the installation has finished, launch the SharePoint Products and Technologies Configuration Wizard. Click next on thewelcome screen and Yes to confirm you are OK with the services being restarted.NOTE: While IIS restarts, the Outlook Web App will be temporarily unavailable.

On the final screen, check the box to 'Run the SharePoint Products and Technologies Configuration Wizard now' and clickClose.

Click Next on the welcome screen and Yes to confirm you are OK with the services being restarted. The wizard will runthrough again and complete the configuration. Once finished click close.

Make sure you install the 32bit version on the Small Business Server and the 64bit version on the Windows 2008 server.

The next step we need to complete is to run a pre-scan on the current database to allow Windows SharePoint Service 3.0 toupgrade it when we move it to the Windows 2008 server.Perform the following steps to achieve this:

Copy the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin\prescan.exe which can befound on the Windows 2008 server to the Small Business Server. It doesn't matter where you put thisLaunch a command prompt (Start > Run > CMD)From the command prompt run: prescan /V http://companyweb and press enter

Once you have done this still, working on the Small Business server perform the following tasks:Navigate to Start > Administrative Tools > Internet Information Services (IIS)Navigate to servername > Web Sites and right click on companyweb and select stop

We now need to launch the SQL Server Management Studio Express, this can be done by:Click Start > All Programs > Microsoft SQL Server 2005 > SQL Server management Studio ExpressIn the dropdown list on the connection screen, ensure that SERVERNAME\SHAREPOINT is selected and click connect

Before we perform any additional steps, we are going to take a backup of the database used for companyweb. Follow thesesteps to perform a backup:

Expand the Databases folderLocate the database called STS_SBSSERVERNAME_1 right click on the database and select Tasks then Backup

Sharepoint-Migration-01.jpg

On the backup screen, the only section you need to change is the destination. Make sure the "backup to" is set to disk andthen click Add.

Sharepoint-Migration-02.jpg


16 of 31 23/12/2010 12:31 PM

IIS-Configuration-01.jpg (51 KB) (File Type Details)

If you receive the error message above, don’t panic, it’s easily solved by using the following procedure:Click Start > Run > Type regedit > Click OKNavigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\SharePoint\MSSQLServerRight click and create a new String Value called BackupDirectoryDouble click the new value to edit it and give it a value of C:

Close Regedit and try clicking the Add button again on the Backup Screen, specify a location for where you would like to savethe backup and click OK.

We are now going to detach the database from the SBS 2003 server. Still in SQL Server Management Studio Express,right-click on the STS_SBSSERVERNAME_1 select tasks and then Detach.

Locate the Database and Log file, which by default will be located in C:\ Program Files\Microsoft SQLServer\MSSQL$SharePoint\Data on the Small Business Server. You need to copy the STS_SBSSERVERNAME_1.MDF andSTS_SBSSERVERNAME_1_LOG.LDF files to a folder on the destination server, don’t copy them in to the SQL Server datafolder.

Working on the Windows 2008 server perform the following steps:Navigate to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio ExpressOn the connection window enter \\.\pipe\mssql$microsoft##ssee\sql\query in the servername box and click connectRight click on Databases and click attachClick the Add button and select the STS_SBSSERVERNAME_1.MDF you copied from the Small Business Server earlier

We now need to create the website in IIS. To do this, do the following:Navigate to Start > Administrative Tools > Internet Information Services (IIS) ManagerExpand the servernameRight click on Sites and select New Site

IIS-Configuration-01.jpg

On the Add Web Site wizard, enter a site name of companyweb, specify a physical path and host name of companyweb asshown in the image above. You can change these if you wish, but keeping the site name/host name the same will mean theURL your clients use will not change.

Launch DNS manager from Start > Administrative Tools > DNS. Expand the forward lookup zone for your internal domainname and locate the CNAME record called companyweb. This should currently be using the Small Business Server’s servername. Double-click this record to edit it and change it to use the Windows 2008 server instead.

And then finally we need to setup SharePoint Service. To do this perform the following steps:Navigate to Start > Administrative Tools > SharePoint 3.0 Central AdministrationClick Application ManagementSelect Create or Extend Web ApplicationOn the next screen select Create a New Web Application

On the screen that appears, complete the fields as listed below. If nothing is specified, please leave the default settings.In the IIS Web Site Section choose the following:

Use an Existing Website and then select companyweb from the drop down list

In the Security Configuration Section


17 of 31 23/12/2010 12:31 PM

Set Authentication Provider to NTLMSet Allow Anonymous to NoSet Use Secure Socket Layers (SSL) to no

In the Application Pool Section

Use Existing Application pool and Select companyweb from the drop down box

In the Database Name and Authentication Section

Database Server should be set to WINDOWS2008SERVERNAME\Microsoft##SSEE (whereWINDOWS2008SERVERNAME is the name of the Windows 2008 Server)Database Name should be set to STS_SBSSERVERNAME_1Database authentication should be set to Windows Authentication (recommended)

In the Search Server Section

Pull down the drop down list and select the Windows 2008 server from the list

Click OK and your SharePoint Website will be created. Once the wizard has finished, from an Internet Browser type inhttp://companyweb/ and the companyweb website on the Windows 2008 server will be displayed.

Step 10 - Migrate shared user data

Because this step is so generic and it could be different for every server, I am not going to go into specifics, only the moregeneral steps that need to be accomplished.

The shares that are in use on the Small Business Server need to be recreated on the Windows 2008 server. One way we cando this is backup the share definitions from the Small Business Server and restore them to the Windows 2008 server. Thisinvolves working in the registry so please be careful and follow the instructions accurately. The instructions on how to do thiscan be found here: http://support.microsoft.com/kb/125996

The next stage is to restore the actual data to the shares. This is a lot easier if you ensure that the folder structure you haveon the Small Business Server for shares is replicated on the Windows 2008 server. You can simply use Windows Backup tobackup and restore the data. This will keep all permissions and ownership information intact.

You will then need to update any login scripts which will be located in \\LOCALHOST\SYSVOL on the Windows 2008 server toensure that any mapped drives are updated.

You will also need to update any attributes that may be under the Profiles tab in Active Directory Users and Computers for theusers themselves.

Step 11 - 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 recommendyou leave it for a day or two just to allow all client computers to automatically update the Exchange server setting in outlook. Ifyou uninstall Exchange 2003 from the Small Business Server and this hasn’t happened then the clients will have to bechanged manually.

To perform this task we will need Small Business Server 2003 CD 2, which will be asked for during the uninstallation. Beforewe 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 haveRecipient Policies that are used for both e-mail address definition and mailbox management, the settings defined under MailboxManager 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 thisyou will need to use ADSI Edit. This can be done by using the following procedure:

click Start > Run > MMC > Click OKSelect File then Add/Remove Snap-inClick Add and select ADSI Edit and click Add, then close and OKRight click on the ADSI Edit and select 'Connect to'. From the drop down under 'Select a well known Naming Context',select Configuration and click OKExpand Configuration > Services > Microsoft Exchange > Organisation Name > Address List Container > RecipientUpdate ServicesRight click on Recipient Update Service (Enterprise Configuration) and select Delete. There may also be a RecipientUpdate 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 havebeen created as part of the installation. I have highlighted them in the image below. Simply right click on each connector andselect delete.


18 of 31 23/12/2010 12:31 PM

Uninstall-Exchange-01.jpg (78 KB) (File Type Details)

Uninstall-Exchange-02.jpg (70 KB) (File Type Details)

Operations-Masters-01.jpg (41 KB) (File Type Details)

Uninstall-Exchange-01.jpg

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 dropdown next to Exchange Server and select remove, as shown below. Then click next and next again.

Uninstall-Exchange-02.jpg

Step 12 - Transfer all 5 FSMO roles to Windows 2008 Domain Controller

Caution needs to be taken when performing this next step. I would advise that ALL of the previous steps need to becompleted 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:

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

Operations-Masters-01.jpg


19 of 31 23/12/2010 12:31 PM

DCPROMO-01.jpg (63 KB) (File Type Details)

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:Click Start > Administrative Tools > Active Directory Domains and Trusts.Right click where it says Active Directory Domains and Trusts and select Operations Master.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:Click Start > Run and type regsvr32 schmmgmt.dllClick OK to the confirmationClick Start > Run and type MMC and click OKSelect File > Add/Remove Snap-in from the consoleFrom the list select Active Directory Schema, click AddClick Close and OK.Right click on Active Directory Schema and select Change Active Directory Domain ControllerChoose the Windows 2008 Server from the list and click OKClick OK on the warning Dialog box.Right click on Active Directory Schema and select Operations MasterClick the Change button and say yes to the notification dialog

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

Step 13 - 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!

The first thing we need to do is make sure the Small Business Server is not a Global Catalog Server. Click on Start >Administrative Tools > Active Directory Sites and Services. Locate the Small Business Server as shown in the screen shotbelow.

DCPROMO-01.jpg


20 of 31 23/12/2010 12:31 PM

Zone:

Tags:

Category:

Views:

Twitter Facebook Linked In Digg Mixx StumbleUpon

I am an IT Consultant specialising in Microsoft

Products. I have worked with all versions of

exchange from 5.0 to 2010 and Windows NT3.51 to

2008R2. Visit my blog here:

http://demazter.wordpress.com/

Related Articles:Reducing EE Email Clutter using OutlookExchange 2007 / 2010 Backpressure – Quick FixStart / Stop a Windows Service from a non-...How the Windows Deployment Service not sta...ampersand sign in NETBIOS domain name caus...

05/07/10 10:21 AM, ID: 14137

05/17/10 01:34 PM, ID: 14703

05/21/10 08:01 PM, ID: 14936

06/11/10 04:57 AM, ID: 15613

Right click on NTDS settings located under the Small Business Server and select properties. Remove the check from theGlobal 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 OKClick next on the Welcome screenDO NOT check the box that says “This server is the last domain controller in the domain” and Click nextEnter a new administrator password for the local administrator user and click next

The server will then remove Active Directory Services from the Small Business Server and it will no longer be a DomainController.

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 moredetail about some of the processes we have just completed. There is an excellent article from EE Expert tigermatt around thepurpose of the FSMO roles which you will find under the further reading section.

Further Reading

Move/Migrate Sharepoint Services: http://technet.microsoft.com/en-us/library/cc288664.aspxMove last legacy Exchange Server: http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspxDemystifying 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

Exchange Email Server

Exchange 2010 Migration, SBS2003, Small Business Server 2003, migration to Exchange 2010

Tutorial

20879

cliffpritchard:

Looking at this project documentation versus Swing method. Just curious, but step 10 referances a Microsoft KB article thatstates at the bottom that it does not apply to Server 2008 or Server 2008 R2. Would you use the File Server Migration Toolfor this instead?

roneniz:

M8 it was absolute Bliss Reading your well documented Article Bless you for the effort of enriching us 'and i really mean that you are the 1 :-)

Great Article

ace14:

Very good article with detailed process. I have a question.

In step 6, if i have

a. Exchange Server 2007 andb. A seperate box for Server 2007

What steps do i need to perform ? This will be a great help as i am in the process of SBS 2003 migration and needdesperate help as most of the reading i have done suggests that since sbs2003 is 32 bit and since exchange server 2007 is64 bit would not be able to migrate.

In case of migration failure what would be the quickest way to restore to sbs 2003 as the office i am working at cannotafford any downtime.


21 of 31 23/12/2010 12:31 PM

06/11/10 04:58 AM, ID: 15614

06/24/10 03:07 PM, ID: 16109

06/24/10 09:48 PM, ID: 16114

06/24/10 09:59 PM, ID: 16116

06/24/10 10:04 PM, ID: 16118

06/26/10 08:18 PM, ID: 16192

07/01/10 01:43 AM, ID: 16418

Fredzou:

It's a great article but when you move AD from SBS 2003 to STD , the limitations of SBS (like 75 users...) will not betransfered?

Have you got any dfficult any time after?

thx

demazter:

>>but when you move AD from SBS 2003 to STD , the limitations of SBS (like 75 users...) will not be transfered?No the limit is with SBS, this does not effect Windows Standard server.

tmbrodie:

Is it possible to leave the Exchange that is bundled with SBS 2003 running on the old server without the SBS server being theAD controller, yet demote the old server to non-DC status?

demazter:

No unfortunately not. If you demote any exchange server from being a DC it will break Exchange.

Aside from the fact that SBS MUST be a DC or it will shutdown itself routinely.

tmbrodie:

Thanks for that; really great article BTW.

demazter:

Thanks :)Don't forget to vote for it if you found it useful (click yes on the link at the top of the article)

dmessman:

This is a great article and very timely for me as I'm in this process - replacing an SBS 2003 box one for one with a Win 2008R2 box with Exchange 2010. You covered simple things like moving over DHCP, but one thing I'm having trouble configuringon my 2008 box is VPN/RRAS. I've read in some spots that setting up VPN on a DC is not recommended except in SBSwhere there's some stuff inside that makes it ok. What are your thoughts on the topic (since it seems relevant here)?


22 of 31 23/12/2010 12:31 PM

07/01/10 01:49 AM, ID: 16419

07/13/10 09:42 AM, ID: 16946

07/20/10 09:01 PM, ID: 17294

07/21/10 02:32 AM, ID: 17297

08/12/10 02:38 PM, ID: 18135

08/12/10 02:55 PM, ID: 18136

robberbaron:

Great read...query A... at Step 1, the new server gets a DHCP address from SBS.Step 4 transfers DHCP to new server S08 , allowing for the static IP's of the SBS network.But does the new server end up with a Static IP itself ? Does it need one or recommended ? Is this the step to assign such,just before activating the scope ?

query B. if I were to put DC and EX on separate VM's, do I just start over at Step 6 on the EX server , having joined it to thedomain as per step 2 ? Is static IP or reserved Ip desirable for the EX box ?

demazter:

query A... at Step 1, the new server gets a DHCP address from SBS.You need to assign the new server a static address, I wouldn't recommend giving a server a DHCP address.

query B. if I were to put DC and EX on separate VM's, do I just start over at Step 6 on the EX serverYes, just join the second VM to the domain and then continue with the Exchange installation in exactly the same was as if youwere installing on the same server.

The guide is designed for single server migration from SBS2003 but the same processes can be applied if you want tomigrate to a seperate Exchange 2010 server.

Telxon:

Wow! Great instructions. Exactly the process I was working on and had questions about.Thanks!

jtorrrres:

Great article. Any ideas on migrating redirected documents from old srv to new srv. I was thinking of implementing DFS tokeep the same path and copying all of the user folders with xcopy to retain permissions. It always seems like redirectiondoes not play nice even when changing the path in GPO.

Any suggestions would be appreciated. Thx

lowrider925:

Just so you know,

Everything worked ok except the Public folders in my case, none of the public folders moved over. They are still sitting on theold server. i've tried multiple attempts with "move all replicas" and nothing happens or had happened past 5 days.

Advise?

Enformix:

First of all, great article it has been a great help.

I'm running into a issue where I'm trying to transfer the FSMO's. The first three of them, when I'm on my 2k8 box I hit"Change" it says:

The current Domain controller is the operations master. To transfer the operations master role to another computer, youmust first connect to it.

Not quite sure what this means, as I have never seen it before. Any additional info would be greatly appreciated.

Thanks!

Enformix:


23 of 31 23/12/2010 12:31 PM

08/13/10 01:00 AM, ID: 18156

08/13/10 04:54 PM, ID: 18183

08/23/10 10:41 PM, ID: 18691

08/28/10 04:26 PM, ID: 18852

08/28/10 10:37 PM, ID: 18864

08/28/10 11:08 PM, ID: 18865

08/28/10 11:13 PM, ID: 18866

nevermind I see what I did :)

dmessman:

I'm not sure how my migration differed from the instructions, but I found that my send connector on Exchange 2010 wasbroken after I finished this process. The broken send connector (organization configuration -> hub transport -> sendconnectors tab of your server). The send connector was called "SmallBusiness SMTP connector" but there was no value onthe source server tab.

To fix it, I created a whole new send connector with an address space of *

I've got some other oddities that I'm working out that may be the cause of this issue. See question here:http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26400289.html

Mike000001:

This is a great article. I have one question. I used this method recently but made one mistake, I forgot to uninstall exchange2003 before I moved the FSMO roles and demoted the sbs 2003

I do have backups, but is there a simple way to remove the "leftover's" from AD using ADSI edit?

There are no issues -yet and I removed the connectors.

-Thanks

BMussel:

Having problems migrating the Sharepoint site. When creating new web application I receive the following error: "Valuedoes not fall within the expected range".

Any suggestions?

Thanks

Icetoad:

Dont forget to repoint all the outlook clients:

http://davedolan.com/blog/?p=83&cpage=1#comment-121612

demazter:

This step is not required.

As long as both servers are turned on for a period of time Outlook will automatically redirect the servo the new server.

Icetoad:

I disagree, you will have stragglers. Course you could leave the old machine running for a year and hopefully no users willcall in complaining.

Left mine running for two months... still had people call in ocasionally.

Course if your server fails for any reason.. good script to have.


24 of 31 23/12/2010 12:31 PM

08/29/10 12:10 AM, ID: 18867

08/29/10 02:05 AM, ID: 18868

09/09/10 11:25 AM, ID: 19233

09/09/10 12:12 PM, ID: 19234

09/09/10 12:53 PM, ID: 19238

09/09/10 12:55 PM, ID: 19239

09/09/10 01:00 PM, ID: 19240

demazter:

>>I disagree, you will have stragglers. Course you could leave the old machine running for a year and hopefully no userswill call in complaining.

Not sure where you are going with this? There will always be the odd person that is on leave.

I have done hundreds of migrations from one version of exchange to another and have never had to use any type of scriptto update outlook.

Icetoad:

I think i see your disconnect with me on this. You think i meant that you had to use the script to repoint all the outlookclients. I could see how you would get that by my short comment. What i actually mean is that the script will be helpful inavoiding tech support calls by clients that did not use their outlook before the old server was decomissioned.

The end goal of my comment was to avoid end user stress and downtime when a change such as this occurs. I did notcreate the script nor am i looking for points, just being helpful.

jentc001:

OUT-STANDING POST!!! I have never seen such a well documented process for such a complex issue. You will put me outof a job ;)

Thankyou!

TJ

orosie68:

Question....

Can you leave Sharepoint services running on the SBS server after removing Exchange 2003 and demoting the SBSserver? I want to basically remove the Exchange and DC function of the SBS server, and then P2V it and use it as amember server. I want to do this because it is running a few other non-MS apps that I wish to leave on the 2003 platform. Iwould prefer to leave sharepoint on it as well, since I will be bringing in an Expert to role out an entirely new Sharepointenvironment at a later date.

Thanks!

demazter:

Unfortunately not, the SBS server MUST be a domain controller and it must be the FSMO role holder.If it's not then it will randomly reboot.

orosie68:

I see Windows Small Business Server 2003 in the add/remove programs. What happens if you uninstall that?

demazter:

You will be in breach of your license agreement for the product you have installed.

If you want to continue running the server that currently has Small Business Server on it you need to purchase a license forWindows Server Standard and format the machine and re-install the new version.


25 of 31 23/12/2010 12:31 PM

09/09/10 01:01 PM, ID: 19241

09/09/10 01:37 PM, ID: 19245

09/14/10 01:32 PM, ID: 19415

09/14/10 02:08 PM, ID: 19416

09/14/10 04:18 PM, ID: 19420

09/22/10 01:12 PM, ID: 19741

09/22/10 01:18 PM, ID: 19743

09/24/10 07:49 AM, ID: 19832

orosie68:

Just curious because the option is there. It would be much easier to uninstall the SBS role, then go ahead and P2V theserver to a virtual machine...so as not to have to move/re-install the non-MS apps. I would make sure that the server waslicensed.

demazter:

Uninstalling the Small Business Server 2003 does not convert the SBS2003 server to a standard version of Windows.

I would suggest you open a question in the SBS Zone about this

orosie68:

Thanks, demazter. Great write up, btw.

randdv8:

When migrating from SBS 2003 to SBS 2008, there is (up to) a 21 day grace period before the migration must completeand the 2003 SBS shuts down on its own. Does this migration path have the same 7-21 day limitation?

Telxon:

You should consider opening a new question to get more responses.

demazter:

The 21 days is for 2 SBS servers existing in the same domain. Since you are not doing that here it isn't an issue

tallboy755:

I made a mistake when installing the DHCP on the 2008 server in this exact setup.I did not put a default gateway in so it looks like my router is not configured and I cant get onto the internet from the new 08server. I can ping all computers within the network and access just fine but I cannot ping an internet address or access anysites.Can anybody help me fix this?

demazter:

Best thing is to run the connect to the Internet wizard in the SBS Console and then run the Fix my network wizard.

Check in the DHCP admin console to ensure the gateway address is specified in the router option under scope options.

Otherwise to that I would recommend opening a question in the SBS zone.


26 of 31 23/12/2010 12:31 PM

09/29/10 01:58 AM, ID: 20050

09/29/10 01:59 AM, ID: 20051

10/23/10 04:17 PM, ID: 20729

Untitled.png (56 KB) (File Type Details)

10/27/10 08:23 PM, ID: 20915

10/27/10 10:04 PM, ID: 20917

NtegraIT:

@demazter

Could this processed be followed and skip the Exchange installation? We have a customer running SBS 2K3 but we aremigrating them from Exchange to Google Apps for Business. We are replacing the SBS server with a 2K8 server, withGoogle Apps hosting the email services, and would like to migrate their SharePoint site currently hosted on the SBS box tothe new 2K8 Box running WSS v3.

Daeraligh:

Is this the same process as migrating exhange 2003 to 2010. Using a win server 2003 to a new win 2008 server? If not canyou get an articale for it.

This article is most helpful. Thanks

Dae

demazter:

Yes it is the same process, just skip the specific SBS parts.

takwirirar:

I am waiting for the mailboxes to be transferred over however incoming and outgoing mail has stopped even for the mailboxesthat have completed and clients updated. What do I do? Do I need to uninstall Exchange on SBS for normal flow to resumeor did i miss something?

queues

ccoffice:

GREAT ARTICLE demazter!!!I have another twist to add to the mix. If i wanted to keep the SBS 2003 server as my AD server and simply add an Exchange2010 server running on Server 2008 R2 could I use this method and if so where could I stop in the process and Leave theSBS 2003 server running. We plan to decomission SBS 2003 it in a year and add another Server 2008 R2 server to take itsplace, but would like to keep it running in the mean time.


27 of 31 23/12/2010 12:31 PM

11/03/10 01:06 PM, ID: 21079

11/08/10 08:25 AM, ID: 21179

11/08/10 08:44 AM, ID: 21180

11/09/10 01:31 PM, ID: 21196

11/09/10 01:36 PM, ID: 21197

richard2gen:

Hey mate, thanks for the timely article... Saved my hair... :-)

FFChronoS:

have this error instaling ex2010

The following error was generated when "$error.Clear(); set-ExchangeServerRole -Identity $RoleFqdnOrName-IsHubTransportServer:$true -DomainController $RoleDomainController" was run: "Property IsHubTransportServer can't beset on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0(6.5.6500.0).".

Property IsHubTransportServer can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) orlater. The object's current version is 0.0 (6.5.6500.0).

cybera:

hi! thank you so much for such a wonderful article!

1 thing though.. how many users can this configuration support? Say with a Quad Core Xeon and 12-GB of RAM.. SATA3-TB RAID-5, would this be able to hold approx 150-200 users?

Thanks again for such wonderful setup!

cybera:

hi! thank you so much for such a wonderful article!

1 thing though.. how many users can this configuration support? Say with a Quad Core Xeon and 12-GB of RAM.. SATA3-TB RAID-5, would this be able to hold approx 150-200 users?

Thanks again for such wonderful writeup!

alt21:

Hi, this guide has been a great help. I initially installed Windows Server 2008 R2 and Exchange 2010 at a client in thebeginning of the year. Been running SBS 2003 and Exchange 2010 in a coexisted setup since January, mainly because Iwasn't sure about the sharepoint side (companyweb).

I have now been forced to remove the SBS box from the network as after installing Exchange 2010 SP1 I am unable to makeany changes to any of the distribution lists and I assume it’s probably got to do with the legacy objects from SBS messingaround.

Following your instructions I have now transferred companyweb to another server and I'm at the step where I need touninstall Exchange from the SBS box.

During the mailbox move there were a few mailboxes that moved but had an error when deleting the mailboxes off the SBSbox, so I now have 10 odd empty mailboxes left on SBS (see they were pretty much all the Entourage users).

My question now and hopefully someone can answer here is - If I uninstall Exchange from the SBS box, will it cause anyissues with the mailboxes (with the same name) on the Exchange 2010 server?

demazter:

Glad you like my article, don't forget to vote for it :)

With regards to the mailboxes, this is not unusual, a quick way to fix it is to actually move the mailbox again, this will forceExchange to cleanup the old mailboxes.

Alternatively on the Exchange 2003 server run the cleanup agent (navigate to Servers > Servername > Mailboxes right clickand select run cleanup agent. They should all then appear with red crosses on them. If you then right click on them andselect purge this will remove the mailbox from Exchange 2003.

You will not be able to remove Exchange 2003 from the SBS server until the mailboxes have been cleaned up


28 of 31 23/12/2010 12:31 PM

11/09/10 11:15 PM, ID: 21205

11/09/10 11:18 PM, ID: 21206

11/09/10 11:29 PM, ID: 21208

11/09/10 11:49 PM, ID: 21210

11/09/10 11:50 PM, ID: 21211

11/10/10 03:29 PM, ID: 21224

11/10/10 03:43 PM, ID: 21226

11/10/10 10:43 PM, ID: 21234

alt21:

Thank You for the quick reply, I did the clean-up which immediately marked the mailboxes on the SBS 2003 box asdisconnected. Trying to purge gave me an error though

"The operation cannot be performed because this mailbox was already reconnected to an existing user"

I am googling the error now and hopefully will find a quick fix for this, at the same time I will be making a backup of themailboxes on the new server for in case something goes wrong.

alt21:

btw, this piece in your article wasn't clear on what you actually have to install "Make sure you install the 32bit version on theSmall Business Server and the 64bit version on the Windows 2008 server." I assumed it was the "Microsoft SQL ServerManagement Studio Express" though

demazter:

OK, that one should be nice and easy.

On the properties of the database in Exchange System Manager, set the deleted items retention all to 0 then restart theMicrosoft Exchange Information Store service.

alt21:

Would I need to make a backup of the mailboxes on the new server first or would it have no effect on the Exchange 2010side?

demazter:

It has no effect on the existing mailboxes on the 2010 server.

ccoffice:

GREAT ARTICLE demazter!!!I have another twist to add to the mix. If i wanted to keep the SBS 2003 server as my AD server and simply add an Exchange2010 server running on Server 2008 R2 could I use this method and if so where could I stop in the process and Leave theSBS 2003 server running. We plan to decomission SBS 2003 it in a year and add another Server 2008 R2 server to take itsplace, but would like to keep it running in the mean time.

alt21:

I was running my SBS 2003 box and Server 2008 R2 (server not DC) with Exchange 2010 for the last year with very littleissues. I didn't uninstall Exchange 2003 on the SBS box though but no traffic was really passing through it.

I only started having issues after installing SP1 so not sure what changes it made to the setup but I am no longer able tomake changes to distribution lists, keeps giving me "you don't have permission to make changes" or something to that effect.

What would your reason be for keeping the SBS box on the network though?

demazter:


29 of 31 23/12/2010 12:31 PM

11/11/10 09:04 AM, ID: 21249

11/11/10 09:55 AM, ID: 21256

11/15/10 01:41 PM, ID: 21346

11/15/10 01:58 PM, ID: 21349

11/15/10 02:12 PM, ID: 21351

ccoffice, glad you like my guide, don't forget to vote for it :)

There is no problem keeping the SBS2003 server as the AD server. You would just complete up to step 11 and don't do step12 or 13.

ccoffice:

alt21Thanks for the reply and for the comments and after reading demazter's comment I think I will uninstall exchange on the SBS2003 box as he suggests which should eleveate the problem you had.They want to keep the sbs 2003 server around as a AD and File and print server untill they put another server 2008 in nextyear.

dematzter.Thanks again I will go with your process and report back how it goes.You got my Vote. GREAT JOB.

occtechgrp:

Very Nice Post!

dshumsky:

Hi demazter,

Thank you for this Guide, its great. But ive ran into a issue. So I setup 3 test VMs just to test this migration before i do it live.1 SBS 2003 ( A copy of our live server), and 2 2008s for the the DC and the EX server.

So far i followed steps 1 to 11 (skipping 5, because im using router for the DHCP, and skipping 9 because we have neverused sharepoints)

At this point all the mailboxes have moved over to exchange 2010 on the second 2008 server, all users can access thereexchange, internet, login etc.

When i get to step 12 everything breaks. I have no problem transferring all 5 FSMO roles over to the new 2008 DC server asyou explained, but when i go to step 13 and run dcpromo on the 2003 SBS server i get an error that says:

"The box indicating that this domain controller is the last controller for the domain mydomain.com is unchecked.

However, no other Active Directory domain controllers for that domain can be contacted.

Do you with to proceed anyway?

If you click Yes, any Active Directory changes that have been made on this domain controller will be lost.

YES NO "

If i press yes it just fails on the next screen. Also while trying to fix this issue i notices that users can't login anymore andoutlook wont connect to the exchange server anymore. I was able to get everything working again by transferring the 5FSMO roles back to the 2003 SBS server.

I thought maybe it had something to do when the fact i didn't follow your guide for setting up the DHCP, but ive checked andall the client stations and the old SBS server are using the new 2008 DC server as Primary DNS.

Any suggestions?

demazter:

Running the following commands on the SBS2003 server will ensure that DNS is updated appropriately.

DCDIAG /FIXNETDIAG /FIX

If you can post any errors you get from the 2 outputs.

dshumsky:

I had no errors on either of those commands utill i unchecked the Global Catalog check box for the 2003 SBS server, after i


30 of 31 23/12/2010 12:31 PM

11/16/10 06:48 AM, ID: 21375

11/16/10 11:53 PM, ID: 21420

11/24/10 05:58 PM, ID: 21575

didn't that i got the following error after running DCDIAG /FIX

Starting test: FsmoCheck

Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located

- All GC's Are down.

The 2008 DC server is still checked as a Global Catalog

dshumsky:

I ran DCDIAG /fix on the 2008 DC server and i got some additional errors:

Testing server: Default-First-Site-Name\SERVER-DC

Starting test: Advertising

Warning: DsGetDcName returned information for

\\server.acmecomputer.local, when we were trying to reach SERVER-DC.

SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

......................... SERVER-DC failed test Advertising

Starting test: NetLogons

Unable to connect to the NETLOGON share! (\\SERVER-DC\netlogon)

[SERVER-DC] An net use or LsaPolicy operation failed with error 67,

The network name cannot be found..

Starting test: LocatorCheck

Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355

A Global Catalog Server could not be located - All GC's are down.

......................... acmecomputer.local failed test LocatorCheck

The 2008 DC server was a fresh install of server 2008 R2. All i did to it was do all windows updates and then started yourguide here. Any idea why this would be happening?

demazter:

And you made the 2008 R2 server a domain controller and DNS server?

My advice would be to raise a question in the Windows 2008 and Small Business Server zones, this way you can get somemore expert exposure.

dougclingman:

Great article!

We ran into a 'gotcha' in the lab and again during the production migration.

OAB Distribution did not, by default, turn on Web Distribution. Had to go back and set it so the Outlook 2007/2010 clientswould download it.

--

Thank you for the information!

Please Login or Register to post a comment.

| | | | | | | |

Shorten URL Help About Us Contact Us Terms of Use EE Blog Internet Rank Privacy Policy Site Map


31 of 31 23/12/2010 12:31 PM

Documents

Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2 - Exchange 2010 Migration, SBS2003, Small Business Server 2003, migration to Exchange 2010