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

Migrate Small Business Server 2003 to Exchange 2010 and Windows 20...
http://www.experts-exchange.com/Software/Server_Software/Email_Ser...
Start FREE Trial
Contact Us
Member Login
Enter Your Search Terms
Experts Exchange
Software
Server Software
Email Servers
Exchange
Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
demazter Posted on 04/16/10 at 4:03 AM 129 of 130 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 Windows 2008 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 Server Exchange Server 2010 Microsoft Office Filter Pack from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=60c92a37-719c-4077 -b5c6-cac34f4227cc&displaylang=en Windows SharePoint Services 3.0 with integrated Service Pack 2.Only the version with Integrated Service Pack 2 will install on Windows 2008 R2. You can download it from here: http://www.microsoft.com/downloads/details.aspx?familyi d=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en Microsoft 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 the 32bit and 64bit versions
Steps required: 1. Health Checks on Small Business Server 2003 2. Join new Windows 2008 Server to the domain as a member server 3. Prepare Active Directory for Windows 2008 R2 Server 4. Make Windows 2008 R2 Server a Domain Controller of the Existing Small Business Server 2003 Domain 5. Transfer DHCP Service 6. Install Exchange 2010 7. Installing Exchange 2010 SSL Certificate 8. Migrate Exchange Data 9. Migrate SharePoint Services 10. Migrate shared user data 11. Uninstall Exchange 2003 from Small Business Server 2003 12. Transfer all 5 FSMO roles to Windows 2008 Domain Controller 13. DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network Its important that the steps are followed in order as different stages make different changes to the way in which your server operates. 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 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. 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 Windows Small Business Server Service Pack 1 Microsoft 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 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. 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.as px?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 Experts help you?
1. 2. 3. 4. 5. 6. alanhardisty demazter MegaNuk3 Akhater amitkulshr... e_aravind 1,402,587 1,254,590 838,777 497,643 491,738 445,378
ADVERTISEMENT
Hall of Fame
1 of 55
6/28/2011 6:40 PM
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 127.0.0.1 address).
Step 2 - Join new Windows 2008 Server to the domain as a member server
To join a Windows 2008 Server to the Small Business Server domain we need to first ensure that it is receiving a correct IP Address Allow the Windows 2008 Server to receive a DHCP Address from your Small Business Server. Run an IPCONFIG /ALL to check this. The DNS Server entry is probably the most important. This should be configured to use the IP Address of your Small 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 by doing the following: Click Start > Run > type CMD and then click OK type 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 properties From the screen that opens under the section called Computer name, domain, and workgroup settings click Change settings. Then click on Change At this point if you havent already specified the name of your new server you can do so Check the radio button next to where it says Domain and enter the domain name that the Small Business Server 2003 belongs to Click OK At which point you will be prompted for a username and password for a user that has permissions to add the computer to the domain Once you have added your credentials and click OK you will then be informed the server requires restarting. Please restart to resume the migration
8. busbar 9. ronnypot 10. lucid8 11. renazonse 12. Sulimanw 13. viralrathod 14. jjmck 15. sunnyc7 16. cgaliher 17. M-Manak... 18. Chris-Dent 19. shreedhar 20. ckeshav 21. abhijitmdp 22. tigermatt 23. dpreston68 24. BlueDevilF... 25. acbrown... 1. Sembee 2. Mestha 3. alanhardisty 4. demazter 5. Akhater 6. rakeshmig... 7. redseatec... 8. tigermatt 9. gupnit 10. LeeDerby... 11. endital1... 12. busbar 13. MegaNuk3 14. Chris-Dent 15. Exchange... 16. mass2612 17. sunnyc7 18. kieran_b 19. Vahik 20. shauncro... 21. flyguybob 22. Kidego 23. TechSoEasy 24. shreedhar 25. jjmck
290,282 285,778 278,435 207,818 206,482 198,075 174,460 152,994 147,596 143,020 138,206 129,849 119,990 116,679 107,264 102,956 101,871 96,496 19,666,085 6,959,258 5,112,902 5,031,659 3,017,894 2,521,226 2,342,875 2,076,111 1,770,113 1,769,372 1,762,584 1,561,765 1,490,679 1,364,265 1,327,609 1,304,704 1,292,231 1,285,184 1,265,183 1,238,396 1,182,799 1,171,155 1,114,868 1,108,552 1,092,070
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 and forest 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 Computers Right click on the domain name and select Raise Domain Functional Level In the drop down box select Windows Server 2003 and click OK (if this has already been done dont worry) To raise the Forest Functional Level do the following: Click Start > Administrative Tools > Active Directory Domains and Trusts Right 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 Manager Right click on the Organisation name right at the top of the list and select properties In the dialogue box check the Operational Mode, if it says Mixed Mode click the Change Mode button and say yes to the dialogue 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 Active Directory. 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 this version is incompatible by clicking OK Open 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 /domainprep X:\support\adprep\adprep32 /domainprep /gpprep X:\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 type DCPROMO 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 start the Active Directory Domain Services Installation Wizard.
ADDS-Wizard-01.jpg (68 KB) (File Type Details)
ADDS-Wizard-01.jpg
2 of 55
6/28/2011 6:40 PM
On the first screen, there is no need to check the 'Use Advanced mode Installation' check box, just simply click next. On the operating 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 an existing domain. Then Click next.
ADDS-Wizard-03.jpg
3 of 55
6/28/2011 6:40 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 screen above. Click Next. The following screen will give you the results of a domain search and ask you which domain you want to add this domain controller 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 Active Directory Site ensure that you select the correct one if it hasnt 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 are both checked. Click Next. The error message regarding DNS Delegation can safely be ignored. Click Yes on this dialog to continue. If you have separate folders where you want to store your log files, SYSVOL share and the Active Directory database then these can be specified on the next screen. To be honest I keep them all as defaults. Once done, click Next.
4 of 55
6/28/2011 6:40 PM
On the following screen, you are asked to set a password for Directory Services Restore Mode Administrator (DSRM). Please note this is NOT the Domain Administrator password. This password is used to boot the Domain Controller into Directory Services Restore Mode which is used for recovering corrupt/deleted/failed Domain Controllers. Make a note of this password and keep it somewhere safe (in a fire safe for example). Click Next on the following 2 screens. The wizard will then start the promotion of the server to a domain controller (I always check the box on this screen to reboot on completion - This way you can leave it and come back to it knowing that it will be ready to continue). Once rebooted your new server will be a domain controller, DNS server and Global Catalog server in your Small Business Server Domain.
Step 5 - Transfer DHCP Service

By default the Small Business Server will be the DHCP Server (if it isnt and you're using something else for DHCP, then you will simply need to update the DNS configuration this device is giving out so that it points to the 2008 Server instead of the 2003 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 (103 KB) (File Type Details)
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 Next then 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 installing Exchange on this server its not recommended to have a multi-homed server but if you do make sure the LAN card and IP is the only one selected. Click next. NOTE: A multi-homed server is a server that has multiple IP addresses assigned to multiple Network Interface Cards. Normally these types of servers would be used as routers. Whilst Exchange can be made to work in this environment, it's not recommended.
DHCP-Service-02.jpg
5 of 55
6/28/2011 6:40 PM
On the Specify IPv4 DNS Server Settings check the following settings: Check the parent domain name is correct Make sure that the IP Address listed for Preferred DNS server IPv4 Address is the address of the new Windows 2008 Server Remove any entry in the Alternate DNS Server IPv4 Settings as these will not be required Click 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 name the start IP address the 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 dont want it just yet) The subnet mask should have been calculated automatically but if it isnt correct then please change it to ensure it is Enter 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 can assign to fixed addresses. My Small Business Server and Windows 2003 server will have an address below 192.168.10.15 but I might also have printers, photocopiers, and wireless access points that also need fixed IP addresses. I have also left 192.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 confirmation
6 of 55
6/28/2011 6:40 PM
screen. 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 just turn one off and turn the other on this will cause you to have to release and renew the settings on the client machines manually for them to pick up the new DHCP Service. The alternative is to wait the 4 days before your client machines request an IP address 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-in Right click on the Scope listed under your Small Business Server and select properties
DHCP-Service-04.jpg
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 reserved addresses 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 the Address Leases and refresh until you are happy that all the clients now have an IP address. (You might want to leave this overnight 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 > DHCP Expand the Windows 2008 servername and IPv4 then right click on the scope listed Select Activate This will start the DHCP Service on the 2008 server and deactivate the service on the Small Business Server (this will happen automatically 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 Windows 2008 Server. You can now disable the DHCP Server service on the Small Business Server. DO NOT disable the DHCP Client service, as this 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 Small Business Server is also using the Windows 2008 Server for DNS. To do this modify the TCP/IP properties of the network card and change the Primary DNS servers IP address to that of the Windows 2008 Server. Do not enter anything in the Secondary DNS 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 by Microsoft, it is not a recommended configuration. But since we are migrating from Small Business Server the chances are you still 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 be
7 of 55
6/28/2011 6:40 PM
done 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 to add server roles and features via the PowerShell command. Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metab ase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Aut h,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 2008 Server. 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 following command: 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 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 Server Open a command prompt (Start > Run > CMD) Run D:\setup /PrepareLegacyExchangePermissions Run D:\setup /PrepareSchema There is an additional command which is: setup /PrepareAD /OrganizationName: but I am going to let the Exchange Server installation do this part Start the Exchange installation from the DVD. On the initial splash screen that opens, click Step 3: Choose Exchange Language Options, select the appropriate option then click Step 4: Install Microsoft Exchange. The Exchange Installation Wizard 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 (91 KB) (File Type Details)
Exchange-Setup-01.jpg
This screen allows us to choose the type of installation. As its assumed the Exchange 2010 server is a direct replacement for Small Business Server and all roles will be installed on a single server, we simply select Typical Exchange Server Installation and Click next. If we were separating our roles out on to different servers we would select Custom Exchange Server Installation and then click next.
8 of 55
6/28/2011 6:40 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 the later 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 be able 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 point the readiness checks will be performed to ensure your infrastructure is ready for Exchange 2010.
9 of 55
6/28/2011 6:40 PM
The results of the readiness check should show a warning on the Organisation Prerequisites, this is normal and its because we didnt run the setup /PrepareAD /OrganizationName: command earlier on. This can safely be ignored as the setup will perform this task for us. The other cautionary warning you will see on my screen capture is simply because I havent installed the Office Filter Pack so you will only see this if you didnt 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 2010 server. Right click on this Receive Connector and select properties. Under the Permission Groups tab, check the box for
10 of 55
6/28/2011 6:40 PM
Anonymous Users. If this box is not checked then servers sending mail to you will not be able to connect. Your e-mails with therefore 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 the Exchange 2010 server to now deal with SMTP traffic and Outlook Web App.
Step 7 - Installing Exchange 2010 SSL Certificate

Exchange 2010 installs with a self-signed certificate by default. Whilst this will work, it will cause browser errors in the form of untrusted websites, Outlook errors for Autodiscover (which is used for free/busy information & Offline Address Book) and errors when using mobile devices and Outlook Anywhere. Whilst for the most part there are ways around these problems, I wont be covering them in this article because my recommendation, as any other Exchange specialist would recommend, would be to use a 3rd party certificate. Unlike earlier versions of Exchange, we have a nice easy to use wizard in the Exchange Management Console for certificate generation. 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 2010 Navigate to Microsoft Exchange On-Premises > Server Configuration In the Actions pane click New Exchange Certificate This will start the New Exchange Certificate Wizard
SSL-Cert-01.jpg (59 KB) (File Type Details)
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 or something that can identify your company. Click Next DO NOT Select to create a wildcard certificate unless you plan on buying a certificate for your entire domain, which is not required for Exchange to function. Click Next
SSL-Cert-02.jpg
11 of 55
6/28/2011 6:40 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 55
6/28/2011 6:40 PM
Confirm the entries on the next page (its worth noting on this screen that the address shown in bold is what is known as a Common Name). This could be important later as Outlook Anywhere requires the common name to be the same as the URL used in the RPC connection. In most of my configurations I use the owa.gkvirtualdomain.co.uk as the common name. To do this, 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 party vendors website and follow their instructions for submitting it.
SSL-Cert-05.jpg
13 of 55
6/28/2011 6:40 PM
Once you receive the signed certificate, right click on the certificate request located as above and select Complete Pending Request. Follow the instructions to import the certificate you have just received.
Step 8 - Migrate Exchange Data

Now we have Exchange installed, its time to migrate the data over. We will start with the easy part as a bit of a break from the previous 6 steps.
Exchange-Migration-01.jpg (101 KB) (File Type Details)
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 Legacy Mailboxes, as pictured above), right click on them and select New Local Move Request
14 of 55
6/28/2011 6:40 PM
When the New Local Move Request wizard opens, click the browse option to select the Windows 2008/Exchange 2010 server mail 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 two options: 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 hopefully show a green tick. Please note that during the move mailbox process, the user will not have access to their mailbox as it is moved 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 Manager Navigate to Administrative Groups > First Administrative Group > Servers > Servername > First Storage Group 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.
15 of 55
6/28/2011 6:40 PM
Now that we have moved the data to the Exchange 2010 server its best to leave this 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.
Step 9 - Migrate SharePoint Services

If you are using companyweb for an intranet/document storage etc. then you will also need to migrate this. If you are not using SharePoint 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 the pre-requisites. This is the free version of SharePoint Services. Only the version with Integrated Service Pack 2 will install on Windows 2008 R2. Once you have downloaded Windows SharePoint Services 3.0, double click to start the installation on the Windows 2008 Server. Read, agree to and accept the license agreement and click continue. Select Basic installation. This will install the standard single site installation. Once the installation has finished, launch the SharePoint Products and Technologies Configuration Wizard. Click next on the welcome 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 click Close. Click Next on the welcome screen and Yes to confirm you are OK with the services being restarted. The wizard will run through 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 to upgrade 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 be found on the Windows 2008 server to the Small Business Server. It doesn't matter where you put this Launch 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 Express In 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 these steps to perform a backup: Expand the Databases folder Locate the database called STS_SBSSERVERNAME_1 right click on the database and select Tasks then Backup
Sharepoint-Migration-01.jpg (88 KB) (File Type Details)
Sharepoint-Migration-01.jpg
16 of 55
6/28/2011 6:40 PM
On the backup screen, the only section you need to change is the destination. Make sure the "backup to" is set to disk and then click Add.
Sharepoint-Migration-02.jpg (31 KB) (File Type Details)
Sharepoint-Migration-02.jpg
If you receive the error message above, dont panic, its easily solved by using the following procedure: Click Start > Run > Type regedit > Click OK Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\SharePoint\MSSQLServer Right click and create a new String Value called BackupDirectory Double 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 save the 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 SQL Server\MSSQL$SharePoint\Data on the Small Business Server. You need to copy the STS_SBSSERVERNAME_1.MDF and STS_SBSSERVERNAME_1_LOG.LDF files to a folder on the destination server, dont copy them in to the SQL Server data folder. Working on the Windows 2008 server perform the following steps: Navigate to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express On the connection window enter \\.\pipe\mssql$microsoft##ssee\sql\query in the servername box and click connect Right click on Databases and click attach Click 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) Manager Expand the servername Right click on Sites and select New Site
IIS-Configuration-01.jpg (51 KB) (File Type Details)
IIS-Configuration-01.jpg
17 of 55
6/28/2011 6:40 PM
On the Add Web Site wizard, enter a site name of companyweb, specify a physical path and host name of companyweb as shown in the image above. You can change these if you wish, but keeping the site name/host name the same will mean the URL your clients use will not change. Launch DNS manager from Start > Administrative Tools > DNS. Expand the forward lookup zone for your internal domain name and locate the CNAME record called companyweb. This should currently be using the Small Business Servers server name. 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 Administration Click Application Management Select Create or Extend Web Application On 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 Set Authentication Provider to NTLM Set Allow Anonymous to No Set 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 (where WINDOWS2008SERVERNAME is the name of the Windows 2008 Server) Database Name should be set to STS_SBSSERVERNAME_1 Database 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 in http://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 more general 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 can do this is backup the share definitions from the Small Business Server and restore them to the Windows 2008 server. This involves working in the registry so please be careful and follow the instructions accurately. The instructions on how to do this can 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 have on the Small Business Server for shares is replicated on the Windows 2008 server. You can simply use Windows Backup to backup 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 to ensure 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 the
18 of 55
6/28/2011 6:40 PM
users 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 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 hasnt 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: click Start > Run > MMC > Click OK Select File then Add/Remove Snap-in Click Add and select ADSI Edit and click Add, then close and OK 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 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.
Uninstall-Exchange-01.jpg (78 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 drop down next to Exchange Server and select remove, as shown below. Then click next and next again.
Uninstall-Exchange-02.jpg (70 KB) (File Type Details)
Uninstall-Exchange-02.jpg
19 of 55
6/28/2011 6:40 PM
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 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: Click Start > Administrative Tools > Active Directory Users and Computers Right 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 (41 KB) (File Type Details)
Operations-Masters-01.jpg
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.dll Click OK to the confirmation
20 of 55
6/28/2011 6:40 PM
Click Start > Run and type MMC and click OK Select File > Add/Remove Snap-in from the console From the list select Active Directory Schema, click Add Click Close and OK. Right click on Active Directory Schema and select Change Active Directory Domain Controller Choose the Windows 2008 Server from the list and click OK Click OK on the warning Dialog box. Right click on Active Directory Schema and select Operations Master Click the Change button and say yes to the notification dialog Thats all the FSMO roles transferred from the Small Business Server. The next and final step is to demote the server from being 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 shot below.
DCPROMO-01.jpg (63 KB) (File Type Details)
DCPROMO-01.jpg
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 Small Business 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
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/Serve r_Software/File_Servers/Active_Directory/Demystifying-the-Active-Directory-FSMO-Roles.html
Zone: Exchange Email Server Tags: Exchange 2010 Migration, SBS2003, Small Business Server 2003, migration to Exchange 2010 Category: Tutorial Views: 46359
I am an IT Consultant specialising in Microsoft Products. I have worked with all versions of
Share this Article
21 of 55
6/28/2011 6:40 PM
exchange from 5.0 to 2010 and Windows NT3.51 to 2008R2. Visit my blog here: http://demazter.wordpress.com/
Keywords: Migrate Small Business Server 2003 Title 1 Search (While You Type) in a Com... 2 AutoCAD VBA - Adding new dimensi... 3 Part II - Drop Down List with Un... 4 Group Policy Compatibility 5 Does SELECT retrieve rows in the...
05/07/10 10:21 AM, ID: 14137
cliffpritchard: Looking at this project documentation versus Swing method. Just curious, but step 10 referances a Microsoft KB article that states at the bottom that it does not apply to Server 2008 or Server 2008 R2. Would you use the File Server Migration Tool for this instead?
05/17/10 01:34 PM, ID: 14703
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
05/21/10 08:01 PM, ID: 14936
ace14:
Very good article with detailed process. I have a question. In step 6, if i have a. Exchange Server 2007 and b. 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 need desperate help as most of the reading i have done suggests that since sbs2003 is 32 bit and since exchange server 2007 is 64 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 cannot afford any downtime.
06/11/10 04:57 AM, ID: 15613
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 be
22 of 55
6/28/2011 6:40 PM
transfered? Have you got any dfficult any time after? thx
06/11/10 04:58 AM, ID: 15614
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.
06/24/10 03:07 PM, ID: 16109
tmbrodie: Is it possible to leave the Exchange that is bundled with SBS 2003 running on the old server without the SBS server being the AD controller, yet demote the old server to non-DC status?
06/24/10 09:48 PM, ID: 16114
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.
06/24/10 09:59 PM, ID: 16116
tmbrodie: Thanks for that; really great article BTW.
06/24/10 10:04 PM, ID: 16118
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)
06/26/10 08:18 PM, ID: 16192
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 2008 R2 box with Exchange 2010. You covered simple things like moving over DHCP, but one thing I'm having trouble configuring on my 2008 box is VPN/RRAS. I've read in some spots that setting up VPN on a DC is not recommended except in SBS where there's some stuff inside that makes it ok. What are your thoughts on the topic (since it seems relevant here)?
07/01/10 01:43 AM, ID: 16418
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.
23 of 55
6/28/2011 6:40 PM
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 the domain as per step 2 ? Is static IP or reserved Ip desirable for the EX box ?
07/01/10 01:49 AM, ID: 16419
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 server Yes, just join the second VM to the domain and then continue with the Exchange installation in exactly the same was as if you were 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 to migrate to a seperate Exchange 2010 server.
07/13/10 09:42 AM, ID: 16946
Telxon: Wow! Great instructions. Exactly the process I was working on and had questions about. Thanks!
07/20/10 09:01 PM, ID: 17294
jtorrrres: Great article. Any ideas on migrating redirected documents from old srv to new srv. I was thinking of implementing DFS to keep the same path and copying all of the user folders with xcopy to retain permissions. It always seems like redirection does not play nice even when changing the path in GPO. Any suggestions would be appreciated. Thx
07/21/10 02:32 AM, ID: 17297
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 the old server. i've tried multiple attempts with "move all replicas" and nothing happens or had happened past 5 days. Advise?
08/12/10 02:38 PM, ID: 18135
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, you must 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!
08/12/10 02:55 PM, ID: 18136
Enformix:
24 of 55
6/28/2011 6:40 PM
nevermind I see what I did :)
08/13/10 01:00 AM, ID: 18156
dmessman: I'm not sure how my migration differed from the instructions, but I found that my send connector on Exchange 2010 was broken after I finished this process. The broken send connector (organization configuration -> hub transport -> send connectors tab of your server). The send connector was called "SmallBusiness SMTP connector" but there was no value on the 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
08/13/10 04:54 PM, ID: 18183
Mike000001: This is a great article. I have one question. I used this method recently but made one mistake, I forgot to uninstall exchange 2003 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
08/23/10 10:41 PM, ID: 18691
BMussel: Having problems migrating the Sharepoint site. When creating new web application I receive the following error: "Value does not fall within the expected range". Any suggestions? Thanks
08/28/10 04:26 PM, ID: 18852
Icetoad: Dont forget to repoint all the outlook clients: http://davedolan.com/blog/?p=83&cpage=1#comment-121612
08/28/10 10:37 PM, ID: 18864
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.
08/28/10 11:08 PM, ID: 18865
Icetoad: I disagree, you will have stragglers. Course you could leave the old machine running for a year and hopefully no users will call in complaining.
25 of 55
6/28/2011 6:40 PM
Left mine running for two months... still had people call in ocasionally. Course if your server fails for any reason.. good script to have.
08/28/10 11:13 PM, ID: 18866
demazter: >>I disagree, you will have stragglers. Course you could leave the old machine running for a year and hopefully no users will 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 script to update outlook.
08/29/10 12:10 AM, ID: 18867
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 outlook clients. I could see how you would get that by my short comment. What i actually mean is that the script will be helpful in avoiding 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 not create the script nor am i looking for points, just being helpful.
08/29/10 02:05 AM, ID: 18868
jentc001: OUT-STANDING POST!!! I have never seen such a well documented process for such a complex issue. You will put me out of a job ;) Thankyou! TJ
09/09/10 11:25 AM, ID: 19233
orosie68: Question.... Can you leave Sharepoint services running on the SBS server after removing Exchange 2003 and demoting the SBS server? I want to basically remove the Exchange and DC function of the SBS server, and then P2V it and use it as a member 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. I would prefer to leave sharepoint on it as well, since I will be bringing in an Expert to role out an entirely new Sharepoint environment at a later date. Thanks!
09/09/10 12:12 PM, ID: 19234
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.
09/09/10 12:53 PM, ID: 19238
orosie68: I see Windows Small Business Server 2003 in the add/remove programs. What happens if you uninstall that?
26 of 55
6/28/2011 6:40 PM
09/09/10 12:55 PM, ID: 19239
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 for Windows Server Standard and format the machine and re-install the new version.
09/09/10 01:00 PM, ID: 19240
orosie68: Just curious because the option is there. It would be much easier to uninstall the SBS role, then go ahead and P2V the server to a virtual machine...so as not to have to move/re-install the non-MS apps. I would make sure that the server was licensed.
09/09/10 01:01 PM, ID: 19241
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
09/09/10 01:37 PM, ID: 19245
orosie68: Thanks, demazter. Great write up, btw.
09/14/10 01:32 PM, ID: 19415
randdv8: When migrating from SBS 2003 to SBS 2008, there is (up to) a 21 day grace period before the migration must complete and the 2003 SBS shuts down on its own. Does this migration path have the same 7-21 day limitation?
09/14/10 02:08 PM, ID: 19416
Telxon: You should consider opening a new question to get more responses.
09/14/10 04:18 PM, ID: 19420
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
09/22/10 01:12 PM, ID: 19741
27 of 55
6/28/2011 6:40 PM
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 08 server. I can ping all computers within the network and access just fine but I cannot ping an internet address or access any sites. Can anybody help me fix this?
09/22/10 01:18 PM, ID: 19743
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.
09/24/10 07:49 AM, ID: 19832
NtegraIT: @demazter Could this processed be followed and skip the Exchange installation? We have a customer running SBS 2K3 but we are migrating them from Exchange to Google Apps for Business. We are replacing the SBS server with a 2K8 server, with Google Apps hosting the email services, and would like to migrate their SharePoint site currently hosted on the SBS box to the new 2K8 Box running WSS v3.
09/29/10 01:58 AM, ID: 20050
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 can you get an articale for it. This article is most helpful. Thanks Dae
09/29/10 01:59 AM, ID: 20051
demazter: Yes it is the same process, just skip the specific SBS parts.
10/23/10 04:17 PM, ID: 20729
takwirirar: I am waiting for the mailboxes to be transferred over however incoming and outgoing mail has stopped even for the mailboxes that have completed and clients updated. What do I do? Do I need to uninstall Exchange on SBS for normal flow to resume or did i miss something?
Untitled.png (56 KB) (File Type Details)
queues
28 of 55
6/28/2011 6:40 PM
10/27/10 08:23 PM, ID: 20915
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 Exchange 2010 server running on Server 2008 R2 could I use this method and if so where could I stop in the process and Leave the SBS 2003 server running. We plan to decomission SBS 2003 it in a year and add another Server 2008 R2 server to take its place, but would like to keep it running in the mean time.
10/27/10 10:04 PM, ID: 20917
richard2gen: Hey mate, thanks for the timely article... Saved my hair... :-)
11/03/10 01:06 PM, ID: 21079
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 be set 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) or later. The object's current version is 0.0 (6.5.6500.0).
11/08/10 08:25 AM, ID: 21179
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.. SATA 3-TB RAID-5, would this be able to hold approx 150-200 users? Thanks again for such wonderful setup!
11/08/10 08:44 AM, ID: 21180
29 of 55
6/28/2011 6:40 PM
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.. SATA 3-TB RAID-5, would this be able to hold approx 150-200 users? Thanks again for such wonderful writeup!
11/09/10 01:31 PM, ID: 21196
alt21: Hi, this guide has been a great help. I initially installed Windows Server 2008 R2 and Exchange 2010 at a client in the beginning of the year. Been running SBS 2003 and Exchange 2010 in a coexisted setup since January, mainly because I wasn'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 make any changes to any of the distribution lists and I assume its probably got to do with the legacy objects from SBS messing around. Following your instructions I have now transferred companyweb to another server and I'm at the step where I need to uninstall 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 SBS box, 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 any issues with the mailboxes (with the same name) on the Exchange 2010 server?
11/09/10 01:36 PM, ID: 21197
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 force Exchange to cleanup the old mailboxes. Alternatively on the Exchange 2003 server run the cleanup agent (navigate to Servers > Servername > Mailboxes right click and select run cleanup agent. They should all then appear with red crosses on them. If you then right click on them and select 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
11/09/10 11:15 PM, ID: 21205
alt21: Thank You for the quick reply, I did the clean-up which immediately marked the mailboxes on the SBS 2003 box as disconnected. 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 the mailboxes on the new server for in case something goes wrong.
11/09/10 11:18 PM, ID: 21206
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 the Small Business Server and the 64bit version on the Windows 2008 server." I assumed it was the "Microsoft SQL Server Management Studio Express" though
11/09/10 11:29 PM, ID: 21208
demazter: OK, that one should be nice and easy.
30 of 55
6/28/2011 6:40 PM
On the properties of the database in Exchange System Manager, set the deleted items retention all to 0 then restart the Microsoft Exchange Information Store service.
11/09/10 11:49 PM, ID: 21210
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 2010 side?
11/09/10 11:50 PM, ID: 21211
demazter: It has no effect on the existing mailboxes on the 2010 server.
11/10/10 03:29 PM, ID: 21224
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 Exchange 2010 server running on Server 2008 R2 could I use this method and if so where could I stop in the process and Leave the SBS 2003 server running. We plan to decomission SBS 2003 it in a year and add another Server 2008 R2 server to take its place, but would like to keep it running in the mean time.
11/10/10 03:43 PM, ID: 21226
alt21: I was running my SBS 2003 box and Server 2008 R2 (server not DC) with Exchange 2010 for the last year with very little issues. 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 to make 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?
11/10/10 10:43 PM, ID: 21234
demazter: 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 step 12 or 13.
11/11/10 09:04 AM, ID: 21249
ccoffice: alt21 Thanks for the reply and for the comments and after reading demazter's comment I think I will uninstall exchange on the SBS 2003 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 next year. dematzter. Thanks again I will go with your process and report back how it goes. You got my Vote. GREAT JOB.
31 of 55
6/28/2011 6:40 PM
11/11/10 09:55 AM, ID: 21256
occtechgrp: Very Nice Post!
11/15/10 01:41 PM, ID: 21346
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 never used sharepoints) At this point all the mailboxes have moved over to exchange 2010 on the second 2008 server, all users can access there exchange, 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 as you 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 and outlook wont connect to the exchange server anymore. I was able to get everything working again by transferring the 5 FSMO 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 and all the client stations and the old SBS server are using the new 2008 DC server as Primary DNS. Any suggestions?
11/15/10 01:58 PM, ID: 21349
demazter: Running the following commands on the SBS2003 server will ensure that DNS is updated appropriately. DCDIAG /FIX NETDIAG /FIX If you can post any errors you get from the 2 outputs.
11/15/10 02:12 PM, ID: 21351
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 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
11/16/10 06:48 AM, ID: 21375
dshumsky:
32 of 55
6/28/2011 6:40 PM
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 your guide here. Any idea why this would be happening?
11/16/10 11:53 PM, ID: 21420
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 some more expert exposure.
11/24/10 05:58 PM, ID: 21575
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 clients would download it. -Thank you for the information!
01/02/11 10:30 AM, ID: 22614
rajatkondal: I followed the articles for migration . I might have missed something because now i get this error. Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'. I tried most of the resolutions online, can someone help
01/02/11 10:37 AM, ID: 22615
demazter:
33 of 55
6/28/2011 6:40 PM
Are you using the built in administrator account? If so can you try another domain admin user that has Exchange permissions?
01/02/11 01:11 PM, ID: 22617
rajatkondal: I reinstalled CAS server. Now get a new error but related to winRM. the WinRM client sent a request to an Http server and got a response saying the requested HTTP URL was not available. This is usually returned by a http server that does not support WS- management protocol
installing latest updates rightnow. all help is appreciated.
01/17/11 08:30 AM, ID: 22914
Trihimbulus: Once I migrate from SBS 2003 to Server 2008 R2 Standard domain- can my new domain name be company.com instead of company.local??? How, when, and where do I change to .com?
01/17/11 09:06 AM, ID: 22915
dmessman: the short answer to this question is no - and I don't know any scenarios where you'd want your internal domain name to be company.com instead of comany.local anyway.
01/17/11 09:18 AM, ID: 22916
demazter: Domain rename whilst Exchange is installed is I believe not supported. There is no technical reason not to use a .com domain as your internal domain name as long as you own the domain. Check out my article here: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2 008/A_3575-Choosing-the-correct-domain-name.html
01/17/11 09:38 AM, ID: 22917
Trihimbulus: Sorry - let me clarify. We currently have seperate public and internal (private) namespaces. Internally, our domain name is company.local and externally our namespace is booyakasha.com. It is the ".local" that is bothering me and would rather it be ".com" internally for private domain. SBS 2003 makes your domain name ".local" I beleieve (if this is incorrect, besides the point).
01/17/11 09:56 AM, ID: 22918
demazter: SBS can be used for a .com internal if configured that way. However as you are migrating the domain name would be the same. To be honest the .local Donain name is easier (read my article I linked to above) but not essential. The only way to change the domain name is to build a domain then use ADMT to migrate user/computers/groups and perform an inter-org migration instead of joining the new servers to the existing domain and performing a traditional migration.
34 of 55
6/28/2011 6:40 PM
01/17/11 10:02 AM, ID: 22919
Trihimbulus: Thanks for the great info man! I have gone through a migration with the ADMT tool and I think I will just keep it easy and leave it at ".local" lol. It does help clearly keep internal and external distinctivley seperate.
01/17/11 10:21 AM, ID: 22920
demazter: Glad to be of assistance
01/22/11 03:01 PM, ID: 23067
NetFile: Hi demazter, Thanks for this detailed instruction guide. I hope I seen this before I transferred the FSMOs. I transferred the 5 FSMO before uninstalling the Exchange 2003. Add/Remove SBS setup shows " You must be a member if the Domain Admins, Schema Admin and Enterprise Admin Groups. I'm using the built in Administrator ID. Is there other way to uninstall the Exchange 2003 before demoting the SBS 2003?
01/22/11 08:21 PM, ID: 23071
slokula: Exchange been removed using Exchange installer. On Step 13: Demoting SBS 2003. I'm logon as built-in administrator. DCPROMO Error message appears: " Logon Failure: the target account name is incorrect." Any idea why do I get this error message? Do I need to reset any account ID?
01/23/11 03:22 PM, ID: 23078
dmessman: netfile - see this article: http://support.microsoft.com/kb/842694
01/27/11 05:51 PM, ID: 23183
Trihimbulus: Quick question- do I have to follow through with this entire set of steps from start to finish in one fell swoop, or can this be picked away at over the course of let's say 2-4 days while still have all client machines functional including email. Can this be done during normal work hours? Second question- I have remote laptops configured for outlook anywhere (over http/rpc) And in the outlook settings (using outlook 2003, 2007, 2010) I specified the internal name of the exchange 2003 server. Once I migrate over to exchange 2010, will I have to reconfigure those settings or will the outlook clients pickup the new exchange 2010 server name automatically?
01/28/11 12:04 PM, ID: 23206
35 of 55
6/28/2011 6:40 PM
diverseit: Should Step 11 be considered if migrating to hosted exchange environment but still using SBS 2k3 for A/D and filesharing?
02/02/11 01:16 PM, ID: 23426
Trihimbulus: THis sucks! I just realized I can't permanently demote the SBS server and our damn accounting system software is on this server! Does anyone know of any tricks? I was planning on doing the migration this weekend and dont have time to move the accounting system to a new server yet.
02/02/11 01:40 PM, ID: 23427
orosie68: Same boat here. I have a couple of apps that need to be migrated off of the SBS server, since it cant be demoted without rebooting every hour. Almost there.
02/02/11 01:46 PM, ID: 23428
Telxon: Trihimbulus, Just don't move all the FSMO roles (specifically the global catalog) until you're ready to demote the old server. It's a little "kludgy", but I have this exact same situation at a client's site and it's still working until we can remove the last app from the old server.
02/08/11 12:05 PM, ID: 23646
Trihimbulus: Im actually going to have 2 domain controllers coming in to the picture. What role differentiates a backup DC to a PDC Emulator? How do recommend I split the roles up between my 2 new dc's?
02/08/11 12:10 PM, ID: 23647
demazter: In a single domain leave all the FSMO roles on a single server but make sure they are both Global Catalog servers. The comment above isn't stricty acurate. You Should make sure the GC role is applied tonal DC's prior to migration, this has no impact on the migration or the SBS server, unlike transferring the FSMO roles as this will cause SBS to reboot randomly which is not what you want when you are trying to migrate. Remember the GC role is NOT a FSMO role! And if you are installing Exchange Server (any version on a domain controller it must be a GC or exchange will not work)
02/08/11 12:19 PM, ID: 23648
Telxon: Trihimbulus, demazter is correct. I mis-spoke with my last comment regarding GC being a FSMO role. Additionally, like I said, this *is* a kludge; and Exchange did need some tweaking to get it running correctly (specifically the GAL in Exchange) when the new SBS server was not the GC; but is working nonetheless. And, no hourly reboots!
36 of 55
6/28/2011 6:40 PM
Interestingly enough, the last application we needed to be upgraded in order to move to the new SBS box is happening today, so I'll be making the new SBS box the GC later this evening (we'll see how smoothly *that* goes ;-) ).
02/08/11 12:28 PM, ID: 23649
demazter: You seem to be talking about SBS to SBS migration? This is very different from the intended purpose of this guide which is for Migrating from SBS to Full Windows & Exchange.
02/08/11 12:53 PM, ID: 23650
Telxon: Doggone it! Sorry -- was thinking about a different migration. I mis-spoke again. I was using your guide as intended. We're replacing a SBS2003 box with a 2008r2 box with Exchange on it. The last application wasn't x64 certified yet -- which is why we had to leave it on the old SBS box. The new application home will be on the new 2008r2 box. Which is also why it's not rebooting.... the FSMO roles are likely still on the SBS box and new new server is a secondary domain controller -- it's been months since I've worked on this server. :-/ Maybe I should actually re-read my post before hitting submit.
02/09/11 06:32 AM, ID: 23661
Trihimbulus: Ok so to reiterate - I need to bring the 2 new Server 2008 R2 Standard DC's up, make both Global Catalogs before I start transferring FSMO roles. I will transfer ALL FSMO roles to the new PDC Emulator and nothing to the secondary DC. Correct? Another question- on steps 3 and 4- can I do this during a work hours- to say, no reboots will be required on either by SBS 2003 server or workstations?
02/09/11 06:38 AM, ID: 23662
demazter: >>I will transfer ALL FSMO roles to the new PDC Emulator and nothing to the secondary DC. Correct Perfect, but remember, don't do this until you are ready to demote the SBS server, you have as long as you like to do the migration until you transfer these roles. >>Another question- on steps 3 and 4- can I do this during a work hours- to say, no reboots will be required on either by SBS 2003 server or workstations Absolutely, no reboots required for these steps. And would have no impact on the servers whatsoever.
02/10/11 12:20 PM, ID: 23739
Trihimbulus: At Step 6 when I bring the new exchange server online. Can I also do this in a live environment without disrupting any workstations? How bout this, up to what step can I do during work hours lol?
02/10/11 01:38 PM, ID: 23741
demazter: The only steps that will cause user disruption are 8,9 & 10. And even then the disruption is fairly minimal.
37 of 55
6/28/2011 6:40 PM
02/11/11 06:59 PM, ID: 23771
Trihimbulus: Why in the heck is it asking me to install a bunch of hotfixes if my Server 2008 R2 server is fully patched (before install)? I installed all the hotfixes except for one and it asked me for a reboot. Now when I try to install (after language pack) it hangs after copying setup files).
02/11/11 07:00 PM, ID: 23772
Trihimbulus: Do I need to reformat the whole dang server now?
02/11/11 10:43 PM, ID: 23773
demazter: The hotfixes do need to be installed if you are using Exchange install with Service Pack 1 integrated. I've never seem it hang though.
02/12/11 11:15 AM, ID: 23777
Trihimbulus: I'm getting insufficient access rights errors on some mailboxes during the move process. I went in the 2003 Server and added full perms on my account, and went on 2008 DC and added my account as member of Exchange Org group. What else do I need to do???
02/12/11 01:51 PM, ID: 23779
Trihimbulus: Disregard last question- Im in the middle of moving mailboxes and the logfiles are growing pretty large. Should I queue the rest of the moves and enable circular logging to shrink them down?
02/12/11 01:55 PM, ID: 23780
demazter: When I am performing mass mailbox moves I normally enable circular logging. Just make sure you take a backup before and after and make sure when you have finished you disable circular logging again.
02/12/11 02:07 PM, ID: 23781
Trihimbulus: But I'm ok to queue the rest of the moves, enable circular logging, then resume?
02/12/11 06:58 PM, ID: 23783
Trihimbulus:
38 of 55
6/28/2011 6:40 PM
Do I have to uninstall Exchange 2003 before I transfer all FSMO Roles?
02/12/11 11:17 PM, ID: 23788
demazter: Yes, the FSMO role transfer should be the last thing you do before DCPROMO'ing the SBS server.
02/13/11 04:20 AM, ID: 23789
Trihimbulus: If I'm migrating to a standalone Exchange Server (2010 Std) that does not have the DC role installed, are there any additional steps I need to follow?
02/13/11 04:37 AM, ID: 23790
demazter: No, the steps are the same.
02/13/11 06:23 AM, ID: 23795
Trihimbulus: Last question- do I remove the Discovery Search Mailbox (along with not moving it) before I uninstall Exchange 2003?
02/13/11 06:24 AM, ID: 23796
demazter: there shouldn't be a Discovery Search Mailbox in Exchange 2003.
02/13/11 06:44 AM, ID: 23799
Trihimbulus: What about moving the offlien address book before uninstalling Ex2003? In the EMC - it shows Default Offline Address Book generation server = OLD SERVER.
02/13/11 06:44 AM, ID: 23800
demazter: you will need to change that to the new server.
39 of 55
6/28/2011 6:40 PM
02/13/11 07:12 AM, ID: 23801
Trihimbulus: Do I replicate it or move it?
02/13/11 07:50 AM, ID: 23802
Trihimbulus: I am at the end of an Exchange 2003 to 2010 migration and I am guessing I need to convert my recipient policy (only have one, modified the default from Ex2003) from LDAP to OPATH per this article: http://www.simple-talk.com/sysadmin/ exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/ Question is- do I need to do this> Is the default recipient policy using LDAP?? Filter Rules on the Default Recip Policy in Ex2003 MC are (mailnickname=*). Also read in this article that if you happen to do this on Recipient Policies that have (advanced) LDAP queries, all custom filters can be reset to "mailnickname=*" which can result significant email outages. Please advise
02/13/11 09:26 AM, ID: 23803
orosie68: you replicate it, then move it.
02/13/11 09:41 AM, ID: 23804
demazter: You can upgrade the recipient policy. What error are you getting?
02/13/11 10:46 AM, ID: 23805
Trihimbulus: No Error- I just deleted the 2 entries in ADSI edit per the article above. So I am looking at the OAB properties in the PF MC and it says the size is 0KB. Yet, I followed the instructions and moved it over. Any idea?
02/13/11 10:48 AM, ID: 23806
demazter: This is not unusual. I would simply create a new OAB and set it to PF and Web distribution.
02/13/11 10:51 AM, ID: 23807
Trihimbulus: Also getting an error in Outlook when I try to Send/Receive the "Download Address Book"> Error is "Task 'myemailaddress' reported error (ox8004010F): 'The operation failed. An object cannot be found.'
40 of 55
6/28/2011 6:40 PM
02/13/11 10:57 AM, ID: 23808
Trihimbulus: happening on 03, 07, and 10 outlook clients but everything else looks good
02/13/11 11:08 AM, ID: 23809
demazter: Have you assigned the OAB to the mailbox database under the properties of the database?
02/13/11 11:13 AM, ID: 23810
Trihimbulus: Yes I have. Ok so here is where I am now. I am upgrading the OAB, Addresslist and GAL per the instructions in this article: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26687630.html I succesfully ran Set-AddressList All Users IncludedRecipients MailboxUsers, Set-AddressList All Groups IncludedRecipients Mailgroups, Set-AddressList All Contacts IncludedRecipients MailContacts - but when I ran Set-AddressList Public Folders RecipientFilter {RecipientType eq PublicFolder} - I get the following error in the Ex Powershell: " The operation couldn't be performed because object 'Public Folders' couldn't be found on MyDomainController.local + CategoryInfo : NotSpecified: (0:Int32) [Set-AddressList], ManagementObjectNotFoundException + FullyQualifiedErrorId : 2DC1B0B2,Microsoft.Exchange.Management.SystemC onfigurationTasks.SetAddressList". I did the migration to a standalone Exchange 2010 Server and have a seperate standalone DC (MyDomainController.local). Any ideas????
02/13/11 11:14 AM, ID: 23811
Trihimbulus: Why is it referencing my DC and how do I fix this??
02/13/11 11:19 AM, ID: 23812
demazter: Why did you run that command it's not necessary?
02/13/11 11:24 AM, ID: 23813
Trihimbulus: Thought I needed to upgrade the PF for Ex10? So disregard? I don't think it screwd anything up since it obviously didn't complete right? I am very confused as to what is going on with my OAB.
02/13/11 11:26 AM, ID: 23814
Trihimbulus: Also, I am at the point where I uninstall Exchange 2003 but am scared to since it looks like the OAB didn't copy over
41 of 55
6/28/2011 6:40 PM
correctly (nor did Public folders but there wan't much in them anyways).
02/13/11 11:27 AM, ID: 23815
demazter: Did you create a new AOB? And set it to PF and web distribution? Have you specified the PF on the mailbox database properties along with the OAB?
02/13/11 11:30 AM, ID: 23816
demazter: The OAB doesnt matter, you can just create a new one. The PF's export them using outlook before you uninstall Exchange 2003 just to be sure.
02/13/11 11:31 AM, ID: 23817
Trihimbulus: Did you create a new AOB? And set it to PF and web distribution? No - how do I do this? Have you specified the PF on the mailbox database properties along with the OAB? Yes- verified this is set
02/13/11 11:44 AM, ID: 23818
demazter: Using the Exchange Management Console navigate to Organization Configuration > Mailbox. Select New Offline Address book and follow the wizard
02/13/11 11:45 AM, ID: 23819
Trihimbulus: Ok doing it now - thx for your help man
02/13/11 12:01 PM, ID: 23821
Trihimbulus: Something else that is weird. Clients on my network who are configured for for Outlook Anywhere (RPC over HTTPS) are getting a Security Alert because of the Self Signed certificate. It says teh name on the certificate doesnt match the name of the site. Do I need to remove the self signed cert since I installed a GoDaddy UCC Cert?
02/13/11 12:02 PM, ID: 23822
demazter:
42 of 55
6/28/2011 6:40 PM
You need to assign the services to the godaddy certificate by right clicking on it in the Exchange Console.
02/13/11 12:12 PM, ID: 23823
Trihimbulus: I did that, but the self sign cert has the SMTP service assigned to it as well.
02/15/11 07:11 AM, ID: 23875
safenetworksolutions: Thank you for the detailed process given above. We are about to embark on our first SBS2003 to Server2008 / Exchange 2010 migration and i was glad to find such a well-documented article. We will be performing this for a 30 user network. Can those of you who have completed this migration tell me how many hours you had in this? From Prep to Completely migrated. Thanks!
02/15/11 07:12 AM, ID: 23876
demazter: Is there a reason why you are moving to the full products with only 30 users and not moving to SBS2011?
02/15/11 07:16 AM, ID: 23878
safenetworksolutions: Yes. Need for new hardware along with expectation of growth through M&A over the next 12 months.
02/15/11 07:17 AM, ID: 23879
demazter: Growth over and above 75 users/devices? There are no special hardware requirements that would not fit both scenarios.
02/15/11 07:25 AM, ID: 23880
safenetworksolutions: Yes growth above 75 users/devices. Because we are moving to new hardware and will have hours in it for migration either way - we expect to save time by doing the entire thing now instead of going to SBS2011 only to move to Standard in 12 months or less. By moving to standard it gives us a platform to grow from. For instance. (These numbers are not meant to be accurate estimates) If it takes 30 hours to complete the SBS2003 to SBS2011 migration and then takes 60 hours to migrate from SBS2011 to Standard then I used 90 hours to get there. If I can do the full migration from SBS2003 to Standard now and it takes 60 hours total then I just saved 30 man hours. Are you suggesting that moving to SBS2011 first will ease the migration and actually take fewer hours? If that is the case I'm all ears.
43 of 55
6/28/2011 6:40 PM
02/15/11 07:29 AM, ID: 23881
demazter: No, it won't take less time if you know you will move to the Standard edition products in the future then it's best to do it now. In actual hands on hours it would be around 10-12 hours. But this will be spread over 3-5 days depending on circumstances.
02/15/11 09:03 AM, ID: 23884
wfninpa: How do I use this guide if I only want to move EMAIL from my SBS Server to a new Server 2008 R2 with Exchange 2010? If anyone can help me please be specific because I do not have a lot of experience with transitions/migrations. Thanks.
02/17/11 02:47 AM, ID: 23934
takwirirar: Hi demazter, thank you for a brilliant article. A few months on I've just realised that external out of office is not working. I have checked all the settings but cant find anything amiss. I used to have issues with external OOF with SBS 2003 but that was resolved before I migrated
02/19/11 06:15 AM, ID: 23980
svillardi: Demazter, Does this cover 1 to 1 machine migration only or can it be applied to 2 machines? I want to separate a DC from Exchange 2010 on my VMs. Are there any caveats?
02/24/11 03:25 PM, ID: 24100
dpowers3: Great Article...On average, how long will this migrate take? How many hours total across number of days? thanks for your help!
02/24/11 03:28 PM, ID: 24101
demazter: As per above post. It really does depend in amount if data etc. There is no rush, unlike SBS to SBS migrations there is no 21 day limit with this one. In actual hands on hours it would be around 10-12 hours. But this will be spread over 3-5 days depending on circumstances.
02/24/11 03:30 PM, ID: 24102
dpowers3: found the answer on another question from 2/15 In actual hands on hours it would be around 10-12 hours. But this will be spread over 3-5 days depending on circumstances.
44 of 55
6/28/2011 6:40 PM
02/24/11 03:31 PM, ID: 24103
dpowers3: thanks!
02/27/11 11:55 AM, ID: 24142
sphilip951: We are doing a similar project, however our Exchange Server will become a part of another domain forest. Should I complete the steps in the this tutorial first, then use ADMT to migrate the resources to the other domain? Or would there be an opportunity to do so somewhere within these steps?
02/28/11 08:35 AM, ID: 24155
ImagesByMurray: Excellent Article! Thank you. We are planning on moving off of SBS2003 to separate 2008R2 Domain Controller / Exchange Servers (we are at and exceeding 75 users). Would you recommend moving the DC before moving to exchange per this article in this "two box" scenario?
02/28/11 08:36 AM, ID: 24156
demazter: The important thing is that you move the FSMO roles last, the rest can be done in the same order it is in my article.
03/11/11 04:51 PM, ID: 24628
lakorai2: I have tried this solution through the use of virtualbox as a test enviornment. Everything works perfectly except when removing exchange 203 off of the sbs vm. The exchange installer complains that it cannot remove activesync due to an 0x80072030 error. On previous posts on the internet it is suggested that the reason for this is that Exchange is looking for a different version of the msxml3.msi file than what is found in the Exchange program folder. The issue is that I cannot find an sp9 version of this file anywhere on the net. I currently have msxml3 patched to sp9 with the newest security update, which is identical on my production server.
Posted via EE Mobile
03/11/11 04:51 PM, ID: 24629
lakorai2: I have tried this solution through the use of virtualbox as a test enviornment. Everything works perfectly except when removing exchange 203 off of the sbs vm. The exchange installer complains that it cannot remove activesync due to an 0x80072030 error. On previous posts on the internet it is suggested that the reason for this is that Exchange is looking for a different version of the msxml3.msi file than what is found in the Exchange program folder. The issue is that I cannot find an sp9 version of this file anywhere on the net. I currently have msxml3 patched to sp9 with the newest security update, which is identical on my production server.
03/22/11 07:41 AM, ID: 24950
45 of 55
6/28/2011 6:40 PM
LanlinkNetworking: Hi there thanx for the awsome guide, I used it and everything went good until now... when i try to run dcpromo on the sbs server it tells me it can not contact any other DC on the domain... is there anything that i missed ? If i go to AD users and computers it open up by default to the sbs server but if i connect to domain i can select my 2008 server so this should mean that it is actully a DC ? Thank you marthin
03/22/11 07:42 AM, ID: 24951
demazter: >>when i try to run dcpromo on the sbs server it tells me it can not contact any other DC on the domain... is there anything that i missed ? Are both servers configured to only use the new server for DNS? There should be no other entries in the DNS for either server.
03/22/11 07:44 AM, ID: 24952
LanlinkNetworking: yes, both servers is pointing to the new server for dns, should i uninstall dns on the old server ?
03/31/11 12:46 PM, ID: 25333
zilla1126: Maybe I missed this in the article, I was under the impression that an Exchange server should NOT be a DC. Is that no longer the case with Exchange 2010?
03/31/11 12:50 PM, ID: 25334
demazter: It's recommended it shouldn't be, but it is a supported configuration and since the intention of the article is to replace a single server SBS with a single server non SBS, it fits th bill quite well.
03/31/11 01:16 PM, ID: 25338
zilla1126: Okay so what would the caveats of using a single server solution be? Performance? I know there were some permission issues with at least exchange 2003 on a DC, I'm assuming that's no longer the case?
03/31/11 01:18 PM, ID: 25339
demazter: There are no permission issues with any version of Exchange on a domain controller. There will always be performance issues when running multiple services on a single server but the main issue is around redundancy, if Exchange is a Domain Controller it will not use any other domain controller for authentication, but then you
46 of 55
6/28/2011 6:40 PM
would argue that if the DC services on the local server is not working the chances are you have bigger problems anyway.
03/31/11 03:09 PM, ID: 25344
svillardi: I asked this question before and never rec'd a response. Can I use this solution to separate an SBS2003 VM server into 2 VMs? One DC and one Exch 2010? Or is there another recommendation for upgrading and separating the functions?
04/01/11 05:50 AM, ID: 25380
zilla1126: I hate to argue this point, but according to what I've read numerous times, in order to fully administer an exchange server, the delegated user or group assigned to that function must also be a member of the local machine administrator group and on a domain controller local accounts are of course non-existent which is why the potential permission issues on prior versions of Exchange. I first read about this on the "mastering exchange server 2003" book written by Barry Gerber.
04/01/11 06:01 AM, ID: 25381
demazter: There is no permission issue, exchange has been installed in domain controllers in a fully supported environment since SBS2000. Microsoft support Exchange installed on a domain controller. It's not recommended but it is supported. It's not recommended for performance and recovery reasons.
04/01/11 06:29 AM, ID: 25382
svillardi: Dematzer, please reply to my question about separating the sbs2003 box into 2 separate boxes. Should I follow your solution here or is there another method suggested? Thanks!!
04/01/11 06:29 AM, ID: 25383
04/01/11 06:30 AM, ID: 25384
04/01/11 07:06 AM, ID: 25385
47 of 55
6/28/2011 6:40 PM
zilla1126: Thanks for your article, not trying to be a troll, but we are going to have to agree to disagree on this particular point. Thanks. svillardi, why don't you follow this guide to consolidate on one server and once completed bring up an additional DC for the domain, transfer all the roles to the new DC you brought up and demote the DC exchange is installed on and there you go.
04/01/11 07:25 AM, ID: 25386
svillardi: Well that is an interesting suggestion. I wonder, based on your concerns, if this will cause an issue. Since I am doing a migration, I would rather do it using best practices. But this does sound feasible.
04/01/11 07:27 AM, ID: 25387
demazter: You can perform the steps on 2 servers, as already explained in the previous comments above yours. zilla1126, what exactly are you disagreeing with?
04/01/11 08:12 AM, ID: 25388
demazter: Just make one server a domain controller and the other an exchange server. Doing as suggested above will not work because you cannot demote a server with exchange on.
04/01/11 08:33 AM, ID: 25389
zilla1126: svillardi, I don't know how big your Exchange environment is going to be. Having it consolidated one one server on a temporary basis, shouldn't be a problem. demaster, I'm having trouble accepting one person telling me that there have NEVER been permission problems on a consolidated DC/Exchange server, when I have read it numerous times on publications from noted Exchange authorities. That's all. At least in the case of SBS 2003, it wasn't simply server 2003 with exchange 2003. Microsoft had to make some special changes to make both components play nice with each other which is why you had to be careful about which order you installed updates on each component. Which is also why the SBS 2003 Windows Small Business Server must be the root of the Active Directory forest, Windows Small Business Server cannot trust any other domains, It cannot have any child domains and so on and so forth. Did you ever try to change the IP address of an SBS 2003 server by simply changing it in the network adapter properties and not going through the SBS wizard? Point being, SBS is a SPECIAL animal and you do not get SBS server by simply integrating Exchange and Server on the same machine. It also doesn't make sense from a financial point of view cause Windows Server 2008 and Exchange 2010 cost more than a single SBS 2008 or SBS 2011. If you have a need for a single server solution, buy SBS 2008 or SBS 2011. Plus the migration path from SBS 2003 to SBS 2008 is much simpler. If you are going to spend your time and energy to go to full blown Exchange 2010, do it right.
04/01/11 09:36 AM, ID: 25392
demazter: I don't know where you are getting your information from. Perhaps you could provide some links? Yes SBS is a different beast, but it's still a Windows server, and it's still Exchange. And, having worked with Exchange for over 14 years. With a mixture of the full product and SBS. With the full product I have worked with it installed on DC's and not DC's and I have never experienced the issues you are mentioning. I've also answered over 4,000 questions on this site and never cone across this issue. As to why you would use this guide, because you want to move from SBS to the full products removing the 75 user limitation, and you want to continue with a single physical server solution. It's not unheard of. The guide can also be used to migrate to multiple servers from SBS.
48 of 55
6/28/2011 6:40 PM
So, if you don't mind, if you have some questions, please use the Q&A zones. My article is not the place to so that.
04/01/11 09:46 AM, ID: 25393
zilla1126: Also, while running Exchange Server on a domain controller is supported by Microsoft, it is not recommended. Problems with Exchange 2003 Installed on Domain Controllers Note. It is possible to install Exchange Server 2010 on an Active Directory Domain Controller. However, for performance and security reasons it is recommended not to do this, and instead to install Exchange Server 2010 on a member server in a domain.
04/01/11 09:51 AM, ID: 25394
demazter: I have already said that it's not recommended. It is however supported. It mentions nothing about local security groups. There is nothing there to support your statements.
04/01/11 09:59 AM, ID: 25395
zilla1126: How We Solved Problems With Exchange Running on a Domain Controller in EBS
04/01/11 10:17 AM, ID: 25396
demazter: I still cannot see anything there I didn't already know and no mention of security. If you don't have anything of any significance to post, then please stop posting.
04/01/11 10:23 AM, ID: 25397
demazter: Most of what you are posting is concerned with Exchange being installed on the ONLY domain controller, rare conditions, DNS, GC placement etc etc. Which, to be Frank, if it's your only server, it's a problem you will be aware of anyway. And as I said in previous posts, you will have bigger problems.
04/01/11 10:47 AM, ID: 25399
zilla1126: Okay, how's this? http://technet.microsoft.com/en-us/library/bb123643(EXCHG.65).aspx This is from technet, look at the table, row 3. Required permissions or roles to install Exchange server 2003 requires LOCAL MACHINE ADMINISTRATOR. If this wasn't a requirement, why would they post it. I can certainly scan the page from one of my Exchange 2003 books and send it to you if you wish. Please stop arguing a point that you are obviously wrong about. If you have a need to support MORE than 75 users and of course SBS is not designed for that, what makes you think that a pseudo SBS that you cook up by integrating Exchange and Server is going to be able to handle that reliably? If you have a need for more than 75 users, INSTALL EXCHANGE LIKE IT'S SUPPOSED TO BE INSTALLED!
49 of 55
6/28/2011 6:40 PM
04/01/11 10:58 AM, ID: 25400
tigermatt:
The biggest hurdle to overcome here is the fact we are talking about migrating away from an SBS - a Small Business Server. We can therefore assume we are talking about a fairly small company, probably no more than 50 staff (although an SBS can cater for 75 tops, it is not usually recommended to run to that limit on a single box). You are right, there are certain concerns with running Exchange on a Domain Controller, most notably the one demazter already mentioned regarding only using the local Active Directory instance for lookups. In most corporate environments, it would be a no-no, but applying corporate IT methodologies to small businesses doesn't tend to scale. They don't have pots of cash to buy and regularly replace lots of servers and licenses and don't have the employees to warrant such a huge network and the huge costs attached. The TCO of a "corporate" IT system in a small business would just break the bank, particularly when you consider the number of full time staff required to maintain such a system, the energy bill, the cooling bill, the premises to securely house the servers etc. With regards to security, there are issues with allowing Exchange admins to manage an Exchange Server installed on a Domain Controller. zilla1126, I think this might be what you were referring to above. However, for a Small Business, this isn't an issue. If only one or two people are managing the box then there isn't really a case where the management of AD and Exchange would need to be segregated - as with any smaller environment the technician will probably be wearing multiple hats. There is also the argument that running Exchange on a Domain Controller could expose your Active Directory environment to the Internet, and so any exploit in Exchange could be used to access and break AD. BUT - if you take proper consideration for security by enforcing regular password changes, only allowing remote access by HTTPS SSL (I always close port 80 altogether) and patch the box as updates are released, you will be in safe hands. You could perhaps publish through any reverse proxy, such as ISA/Forefront TMG server, if you are that concerned about the stuff sat behind - but then you need another box, more licenses, added complexity for a risk which can be mitigated in other ways. In any event, this is really a strawman argument - even if Exchange were on its own box you could still expose Active Directory via a vulnerability in the code, and you certainly would not want to put an Exchange box in the DMZ to counteract this problem (see http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_1268-Why-you-s houldn%27t-put-an-Exchange-Server-in-the-DMZ.html). Anything you put on the Internet could be broken into given sufficient time, skill and money. Your role is not to become completely immune to attack (as that is impossible) but make it as unattractive as possible for an attacker to attack you. As to "performance" issues, Exchange 2010 is one of the most highly performing versions of Exchange yet. The disk I/O is significantly reduced relative to earlier versions due to significant database re-architecturing. If you're supporting 50 users tops who probably aren't heavy email users and using modern, SERVER GRADE (HP, Dell, IBM etc) hardware with decent processors and enough memory, the server hardware will probably die due to old age before you fill it up or overload it. zilla1126, I am not disagreeing with what you are saying - in a corporate, or even a "larger" environment which warrants an EBS, running Exchange on a DC is not recommended. However, it is a completely supported configuration, and when scaling a solution for a small business, you are unlikely to find many owners willing to pump thousands and thousands of pounds/dollars/elephants/<insert currency here> into multiple boxes and lots of redundancy. Basic RAID and NIC teaming is usually sufficient - and if you lose a box because the motherboard dies, use the 5-year 4*24*7 carepack you bought on it to source a new one. -Matt
04/01/11 11:47 AM, ID: 25404
demazter: >>>If you have a need to support MORE than 75 users and of course SBS is not designed for that, what makes you think that a pseudo SBS that you cook up by integrating Exchange and Server is going to be able to handle that reliably? Have you done it? I have, a number of times, and if the correct measures are taken it can work very well. >>>INSTALL EXCHANGE LIKE IT'S SUPPOSED TO BE INSTALLED! which is how exactly? Exchange is supposed to be installed to meet the needs of the person or people it's being installed for. Who are you to dictate this? There could be a number of valid reasons why this configuration would be required. There may be a need to setup trusts for example, which SBS will not allow, are you suggesting that for say 15 users seperste severs is an absolute must?? Most of my courts would disagree with you, and I would find it hard pushed to convince them otherwise without unecessarily upselling, which I am not in the business of doing.
04/01/11 12:13 PM, ID: 25406
zilla1126:
50 of 55
6/28/2011 6:40 PM
Like I said demazter, we are going to have to agree to disagree. I think we both have valid points and different ways of going about our business. You do whatever works for you and I'll do whatever works for me. Sound fair? Thanks for your time.
04/01/11 12:20 PM, ID: 25407
ImagesByMurray: svillardi: I've done two test runs - migrating from sbs2003 to two boxes - one as a domain controller, the other hosting exchange - it works great if you follow the directions as given. make sure all dns references on all machines (including the sbs2003 box) are pointing to the new dc before commencing the exchange install. i only ran into 2 issues: 1) when migrating public folders, exchange 2003 threw an error, this was resolved by turning off SSL for the exadmin virtual directory on the sbs2003 box. 2) my test included outlook 2003 clients with encrypted communication to the exchange server off by default - simplest solution, turn of encryption as the exchange 2010 server: http://www.howexchangeworks.com/2009/09/cant-connect-outlook-2003-to-exchange.html if you prefer you can enforce outlook 2003 encryption via group policy
04/02/11 09:15 AM, ID: 25423
sphilip951: Demazter, I really appreciate you taking the time to put so much effort into this article. It has made my life so much easier. You've saved me countless hours of research and headaches. Thank you, Thank you, Thank you!!!
04/08/11 10:15 AM, ID: 25610
aZahner: I haven't really seen a mention of this in the article, but I wanted to make certain I'm thinking correctly. If I'm reading correctly We can stop after completing Step 11 and have the SBS server remain as the primary DC and continue to serve as our principal print server CALs Do we need to purchase 2008 CALs for this migration? Last question for this go round... Anyone have some good advice on migrating the print server functionality to another server. It's really the only thing holding up turning the SBS server off at this point. Thanks! Great article, haven't executed it yet, but we're planning to in the coming weeks.
04/08/11 10:24 AM, ID: 25611
demazter: >>We can stop after completing Step 11 and have the SBS server remain as the primary DC and continue to serve as our principal print server Absolutely correct, the SBS server will continue to function correctly until the FSMO roles are transfered. >>CALs Do we need to purchase 2008 CALs for this migration? yes, you will need 2008 server CaLS and Exchange Server CALs. Although, talk to a Microsoft Licensing Specialist. If you get it wrong and get taken to court "I heard it on Experts Exchange" is not a defence. >>Anyone have some good advice on migrating the print server functionality to another server PSMT is probably your best bet: http://technet.microsoft.com/en-us/library/cc773832(v=ws.10).aspx
04/08/11 10:37 AM, ID: 25612
51 of 55
6/28/2011 6:40 PM
aZahner: Thanks for the quick response, I wasn't going to use you as my defense method. :) We've actually migrated to BPOS, so I don't believe the exchange CALS are required for our install. I will look into PSMT.
04/12/11 08:36 AM, ID: 25694
aZahner: I hit another problem when running the adprep32 /rodcprep The previous commands got no errors. I get an error similar to what is described in this EE posting: http://www.experts-exchange.com/Software/Server_Software/File_Servers/Active_Directory/Q_24309905.html?sfQ ueryTermInfo=1+10+30+contact+error+ldap+replica+rodcprep I have a feeling this is related to the path our computer has taken. It is the second SBS 2003 server in our environment (we previously used Swing IT) to migrate from an HP box by the same name to a Dell box of the current name. The intermediary box does show up in Active Directory Sites and Services. I may be missing something but I do not see "DomainDNSZones" or "ForestDNSZones" that the error refers to in ADSI Edit. Using ADSIEdit, I attempted to directly connect to DomainDNSZones and that shows that the FSMOroleowner attribute is not set? Since there is only one domain controller in our environment can I ignore this? If I should open a separate question, let me know. I just want to make sure I go down the right path. Would appreciate any help
04/12/11 08:56 AM, ID: 25697
aZahner: I followed the advice on this webpage and was able to run /rodcprep without errors. The fsmoroleowner attribute was set to the 'deleted' HP SBS server. I believe.
04/12/11 09:09 AM, ID: 25700
aZahner: Forgot the link: http://social.technet.microsoft.com/Forums/en/winserverDS/thread/0b956901-930c-4fe7-80ad-939de1f61b48
04/13/11 05:24 AM, ID: 25730
Mike_Orton: Can anyone please confirm that this will remove ALL restrictions on SBS 2003 including the 75 user limit and no trust relationships allowed between forests?
04/13/11 05:25 AM, ID: 25731
demazter: Once the SBS 2003 server has been removed from the domain ues, all limits and restructions will be removed.
05/28/11 11:51 AM, ID: 27769
mkovac:
52 of 55
6/28/2011 6:40 PM
SBS 2008: Migration: DCPromo fails *** Problem Description *** Migration from SBS The Active Directory Domain Services Installation Wizard was unable to convert the computer account to an Active Directory Domain Controller account. Resolution On SBS 2003 machine: - Domain Controller Security Policy - Local Policies - User Rights Assignment - Enable Computer and user accounts to be trusted for delegation - Add domainnameDomain Admins - Gpupdate /force
05/31/11 04:36 PM, ID: 27870
svillardi: Demazter: Does this process include the routing and VPN access which SBS2003 does?
05/31/11 04:42 PM, ID: 27871
dmessman: this process does not include VPN access. You can set that up yourself in the new Win 2008 box. As far as routing, if you mean firewall/router functionality - that functionality was discontinued after SBS 2003. Now, you need a separate router.
06/01/11 08:23 AM, ID: 27889
RickNCN: I am using this guide to migrate SBS 2003 to Server 2008 but I have a question. I see people are still commenting on this post. I hope it's ok to do the same. Under STEP 1: Health Check, it says: >"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 >Windows Small Business Server Service Pack 1 >Microsoft Exchange 2003 Service Pack 2" My server says: "Microsoft Windows Server 2003 for Small Business Server Service Pack 2" ***FIRST QUESTION*** what do I have? SBS SP2? Does that supercede SBS SP1 referenced above? Do I also have "Windows 2003 Service Pack 2"? How do I know? I have downloaded: SBS2003-KB885918-SP1-X86-ENU.EXE and get an error at the end of the process.
if I Google " small business server 2003 SP2" the first MS result I get is: "WindowsServer2003-KB914961-SP2-x86-ENU.exe" That page says it can be directly installed on: Windows Server 2003 Editions (all 32-bit x86) Windows Server 2003 R2 Editions Windows Storage Server 2003 R2 Editions Windows Small Business Server 2003 (SBS 2003 customers - Please read Knowledge Base Article 932600 before installing SP2) If you read KB 932600 it references not installing SP2 if you're migrating to certain 2003 versions. ***QUESTION 2*** Does this warning apply at all to the migration I'm doing to 2008?
06/01/11 08:24 AM, ID: 27890
derek2323: I need to do a migration on to a Windows Server 2008 Standard, not R2. Is this process the same?
53 of 55
6/28/2011 6:40 PM
06/01/11 08:27 AM, ID: 27891
demazter: There is no SBS SP2, the SP2 refers to Windows and Exchange. The SBS Components can be SP1 or not
The guide can also be used for 2008. The process is almost the same. I have to ask though, why are you using 2008 and not 2008 R2?
06/01/11 08:28 AM, ID: 27892
derek2323: I'm doing IT at a company and that was what was provided to me.
06/01/11 08:48 AM, ID: 27894
derek2323: Would you be able to let me know the differences in the process or point me to somewhere that will? I have been looking for 2 weeks and am unable to find anything. Thanks for the fast reply.
06/01/11 08:56 AM, ID: 27896
RickNCN: UPDATE forgot to mention I ran the Windows SBS 2003 Best Practices tool and it says I don't have SBS 2003 SP1 installed. If I run"winver" I get (The "banner" at the top proclaims: Microsoft WIndows Server 2003 for Small Business Server" then below: "Microsoft R Windows Version 5.2 (Build 3790.srv03_sp2_gdr.101019-0340 : Service Pack 2) You are indeed "demazter". Thanks so much! excellent. Ok - so you're saying that refers to "Windows server" and not the SBS components. Got it.
06/01/11 08:59 AM, ID: 27898
demazter: You still need SBS SP1. It's available in the pre-requisites of my guide.
06/01/11 09:02 AM, ID: 27899
demazter: See here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b6f8a4c0-b707-4161-adeb-44f1b756119f &displaylang=en
06/02/11 05:56 AM, ID: 27930
54 of 55
6/28/2011 6:40 PM
RickNCN: When I run SP1 update, It completes but I get an error "MSDE 2000 Service Pack 4 did not install. " do you think that's a problem I definitely need to solve before continuing the migration?
06/07/11 03:27 PM, ID: 28093
KrisHartman: After reading through this entire guide and comment thread I'm wondering if I missed something. I didn't see anything specifically about moving the DNS server from the SBS2003 to the 2008 standard server. Did I miss something or do the DNS server duties get moved as part of one of the other steps?
06/28/11 04:20 AM, ID: 29237
ZARCINC: I have been upgrading my sbs domain to 2008 R everything to be moving fine until i began the exchange install on it own 2008r server. I am getting an error "Error: The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2010, the forest functional level must be at least Windows Server 2003 native To update the domain functional level, the Active Directory Domain Controllers in the domain must be running the appropriate version of windows. i tried to upgrade my forest funtional level to Windows 2003 but am unable becuae i get an error that a this domain conatains active domain controller tha is not running approprate windows version I check the log file and it is the orgional DC i have been upgrading. Not sure what i missed What do i need to do to raise the domain function? Thank you
06/28/11 11:38 AM, ID: 29269
dj0rbit: I'm trying to do this same migration without Exchange. When I first attempted it before discovering your guide, I ran into issues with licensing and with people accessing the shares. Also the SYSVOL folder did not transfer to the new DC. I then kept on reading information regarding the requirement of the SBS Transition pack(the pack that will essentially convert SBS into Windows Server 2003 Standard).. I did not demote the SBS server and take it off the network. Couple of questions. Will everything just work after I demote the SBS server? Do I really need the Transition pack for this to work? I want to avoid spending an extra cost on the transition pack. Thanks, and I appreciate the help!
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
55 of 55
6/28/2011 6:40 PM

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

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

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

Caricato da

Copyright:

Formati disponibili

Migrate Small Business Server 2003 to Exchange 2010 and Windows 20...

Start FREE Trial

Enter Your Search Terms

Step 1 - Health Checks on Small Business Server 2003

Step 3 - Prepare Active Directory for Windows 2008 R2 Server

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

ADDS-Wizard-02.jpg (46 KB) (File Type Details)

ADDS-Wizard-03.jpg (66 KB) (File Type Details)

ADDS-Wizard-04.jpg (60 KB) (File Type Details)

Step 5 - Transfer DHCP Service

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

DHCP-Service-02.jpg (100 KB) (File Type Details)

DHCP-Service-03.jpg (54 KB) (File Type Details)

DHCP-Service-04.jpg (52 KB) (File Type Details)

Step 6 - Install Exchange 2010

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

Exchange-Setup-02.jpg (79 KB) (File Type Details)

Exchange-Setup-03.jpg (62 KB) (File Type Details)

Exchange-Setup-04.jpg (116 KB) (File Type Details)

Exchange-Setup-05.jpg (102 KB) (File Type Details)

Step 7 - Installing Exchange 2010 SSL Certificate

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

SSL-Cert-02.jpg (173 KB) (File Type Details)

SSL-Cert-03.jpg (65 KB) (File Type Details)

SSL-Cert-04.jpg (91 KB) (File Type Details)

SSL-Cert-05.jpg (75 KB) (File Type Details)

Step 8 - Migrate Exchange Data

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

Exchange-Migration-02.jpg (106 KB) (File Type Details)

Exchange-Migration-03.jpg (108 KB) (File Type Details)

Step 9 - Migrate SharePoint Services

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

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

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

Step 10 - Migrate shared user data

Step 11 - Uninstall Exchange 2003 from Small Business Server 2003

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

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

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

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

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

I am an IT Consultant specialising in Microsoft Products. I have worked with all versions of

Share this Article

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

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

tmbrodie: Thanks for that; really great article BTW.

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

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

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

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

nevermind I see what I did :)