Category Archives: Sbs 2011 Migration Steps

Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server 2003 [Susan adds]


 


Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server 2003 [Susan adds]


Susanism by Susan Bradley


So here’s what I did.. I took all of the blog posts I did for migration from SBS 2003 to SBS 2011 and put them in this document that you can download from the Skydrive.


I then cross referenced to the pages in this document:  http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ea184914-6445-4d7a-a432-927e6880dcd0

Holler if you have questions!

So when you read that migration document you can match it up with the blog posts and screen shots I did along the way.


 

Step 35 – deleting the DNS entries in the source server



Delete DNS entries of the Source Server for Windows SBS 2011 Standard migration

After you decommission the Source Server, the DNS server still contains entries that point to the Source Server. Delete these DNS entries.
 To delete DNS entries that point to the Source Server
1.    On the Destination Server, click Start, click Administrative Tools, and then click DNS.
2.    In the User Account Control dialog box, click Continue.
3.    In the DNS Manager console, expand the server name, and then expand Forward Lookup Zones.
4.    Right-click the first zone, click Properties, and then click the Name Servers tab.
5.    Click an entry in the Name servers text box that points to the Source Server, click Remove, and then click OK.
6.    Repeat step 5 until all pointers to the Source Server are removed.
7.    Click OK to close the Properties window.
8.    In the DNS Manager console, expand Reverse Lookup Zones.
9.    Repeat steps 4 through 7 to remove all Reverse Lookup Zones that point to the Source Server.


Step 34 – giving the Adminstrators group the rights they need

Next up is clean up time… first up we need to give the built in admin the right to log on as a batch job.


Give the built-in Administrator group the right to log on as a batch job for migration
 Note
After you migrate, you should give the Administrator group the right to log on as a batch job.
After you migrate an existing Windows SBS 2003 domain to Windows SBS 2011, verify that the built-in Administrator group still has the right to log on as a batch job to the Destination Server. Administrators need this right in order to run an alert on the Destination Server without logging on.
 To give the built-in Administrator group the right to log on as a batch job
1.    On the Destination Server, click Start, click All Programs, and then click Administrative Tools.
2.    In the Administrative Tools menu, select Group Policy Management.
3.    In the Group Policy Management console tree, click Forest: <ServerName>, and then click Domains.
4.    Click the name of your server, expand Domain Controllers, right-click Default Domain Controllers Policy, and then click Edit.



5.    In the Group Policy Management Editor, click Default Domain Controllers Policy <ServerName> Policy, expand Computer Configuration, and then click Policies.
6.    In the Policies tree, expand Windows Setting, and then click Security Settings.
7.    In the Security Settings tree, expand Local Policies, and then click User Rights Assignment.



8.    In the results pane, scroll to and then click Log on as a batch job.
9.    In the Log on as a batch job Properties dialog box, click Add User or Group.




10.    In the Add User or Group dialog box, click Browse.
11.    In the Select Users, Computers, or Groups dialog box, type Administrators.
12.    Click Check Names to verify that the Administrators group appears, and then click OK three times.


Step 33 – dcpromo-ing down the SBS 2003

In my real migration at the office, at this point in the migration I turned off the SBS 2003 rather than immediately dcpromo-ing it to ensure that I hadn’t forgotten anything still hooked to the SBS 2003.  Remember you will be removing this server and having to reinstall it.  You cannot dcpromo down the SBS 2003 and leave it as a member server. 


To demote the Source Server


1.   On the Source Server, click Start, click Run, type dcpromo, and then click OK.

2.   Click Next twice.

Note

Do not select This server is the last domain controller in the domain.

3.   In the Summary dialog box, you are informed that AD DS will be removed from the computer and that the server will become a member of the domain. Click Next.

You’ll be prompted to put in a password..

4.   Click Finish. The Source Server restarts.

5.   After the Source Server restarts, add the Source Server as a member of a workgroup before you disconnect it from the network.

Step 32 start thinking about printers

Physically disconnect printers that are directly connected to the Source Server
Before you demote the Source Server, physically disconnect any printers that are directly connected to the Source Server and are shared through the Source Server. Ensure that no Active Directory objects remain for the printers that were directly connected to the Source Server. The printers can then be directly connected to the Destination Server and shared from Windows SBS 2011 Standard.


Moving from a 32bit printer world to a 64 bit printer world is a bit painful… I’ll do a series of blog posts on how to do this exactly… stay tuned for more.


For now just move the printers around and plan ahead for 64bit drivers and possibly 32bit workarounds.

Manually removing Exchange 2003 from the migration process

<FOR ANYONE READING THIS AFTER THE FACT — PLEASE READ THIS CAVEAT FIRST:>


Please note, I got here because I got stuck.  This isn’t how you should normally uninstall or remove Exchange.  Normally you just go into add/remove and do it from there. Remember I got stuck here.  I also had previously moved the recepient update services ahead of time.  I also had a safety net.  I had a full backup of the entire server.  I had a system state backup of the server.  I knew that I could dig myself out of a hole and call in support if I needed to.    Do not start ripping out Exchange without knowing that you have a backup, a system state backup and a safety net.  This should be your absolute last resort should you get stuck.  Got it?


It’s party time on a Friday night and I’m manually ripping out Exchange…wooo hooo!  (yeah yeah I need a life, what can I say)


http://support.microsoft.com/kb/833396


This article describes the steps to automatically or manually remove Microsoft Exchange Server 2003 from your computer.

Before you can remove Exchange Server 2003, you must disconnect all mailbox-enabled users from the mailboxes on the Exchange server. After all mailbox-enabled users have been disconnected, you can use the Exchange 2003 Setup program to remove Exchange Server 2003.

However, you may be unable to use the Exchange 2003 Setup program to remove Exchange 2003. In this scenario, you can manually remove Exchange 2003. To do this, you must first stop and disable all Exchange services. You can then use Registry Editor to remove registry keys that are part of the Exchange installation. After you have removed the registry keys, you must remove and then reinstall Internet Information Services (IIS). Then, you must reinstall any service packs or security updates that are installed on the server
.

Actually I don’t need to reinstall IIS as I’m going to dcpromo down this server.


If you must remove Microsoft Exchange Server 2003 from your computer, you must first disconnect all mailbox-enabled users from the mailboxes on the Exchange server. You can then run the Exchange Server 2003 Installation Wizard. In the wizard, click the Remove option for the installed components on the Component Selection screen.

However, if you cannot use the Exchange Server 2003 Installation Wizard to remove Exchange Server 2003, you can use Registry Editor to manually remove the registry settings for Exchange Server 2003.


I know that all the mailboxes have moved so we don’t need to nuke users..


Use the Active Directory User and Computers snap-in to disconnect all mailbox-enabled users


You cannot remove the Exchange Server 2003 components if the Exchange server still has mailboxes for mailbox-enabled users. To use the Active Directory User and Computers snap-in to disconnect all mailbox-enabled users, follow these steps:


Ignore these steps all of my mailboxes don’t say “legacy” in the SBS 2011 so I know they have moved.


Run the Exchange Server 2003 Setup program to remove the installed components


You can remove the Exchange components by running the Exchange Server 2003 Setup program from Programs and Features in Control Panel on the computer that is running Exchange Server 2003. To do this, follow these steps.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.


  1. Click Start, click Control Panel, and then click Add or Remove Programs.
  2. In the Currently installed programs list, right-click Microsoft Exchange, and then click Change/Remove.
  3. In Microsoft Exchange Installation Wizard, click Next.
  4. In the Action list on the Component Selection page, click the down arrow next to each component that has been installed, and then click Remove.

    Note Installed components have a check mark in the Action list. When you click Remove, the check mark is replaced by the word Remove.
  5. Click Next two times.
  6. Click Finish.

In the case of SBS you are supposed to remove Exchange by going into Windows Small Business Server 2003 (just the 2003 not the 2003 r2 section of add/remove) click on it, and when the integrated components of the server pop up and you see Exchange pull the arrow key down to remove.


If we scroll up to where Exchange is separately listed.. we can’t remove it from there



So now we need to stop the services…


Manually remove Exchange Server 2003


If you cannot remove Exchange Server 2003 by using Add or Remove Programs, you can use Registry Editor to remove the Exchange entries from the registry. Before you edit the registry, you must stop and disable all Exchange 2003 services on the computer.


Stop and disable the Exchange Server 2003 services


The following table lists the core Exchange Server 2003 services.


Collapse this tableExpand this table
NameDescription
Distributed Transaction Coordinator Coordinates transactions that are distributed across multiple databases, message queues, and file systems.
Internet Information Services (IIS) Admin Service Allows you to administer the Exchange HTTP virtual server in the IIS snap-in.
Microsoft Exchange Event Monitors folders and generates events for Exchange Server 5.5 applications.
Microsoft Exchange Internet Message Access Protocol (IMAP4) Provides Exchange IMAP4 services.
Microsoft Exchange Information Store Manages Exchange information storage.
Microsoft Exchange Management Service Hosts Exchange WMI providers
Microsoft Exchange Message Transfer Agent (MTA) Stacks Provides Exchange X.400 services.
Microsoft Exchange Post Office Protocol version 3 (POP3) Provides Exchange POP3 services.
Microsoft Exchange Routing Engine Processes Exchange message routing and link state information.
Microsoft Exchange Site Replication Service Replicates Exchange information in the organization.
Microsoft Exchange System Attendant Monitors Exchange and provides necessary services.
Network News Transfer Protocol (NNTP) Transports newsgroup messages across the network.
Simple Mail Transfer Protocol (SMTP) Transports e-mail across the network.
World Wide Web Publishing Service Provides HTTP services for Exchange and IIS.

To stop and disable the Exchange Server 2003 services, follow these steps:


  1. Click Start, point to Programs, point to Administrative Tools, and then click Services.
  2. In the Name list, right-click an Exchange service, and then click Stop.
  3. After the service stops, right-click the Exchange service again, and then click Properties.
  4. In the Startup Type list, click Disabled, and then click OK.
  5. Repeat steps 1 through 4 for every Exchange service.

I’ve disabled the services that are left



Now we have to remove the registry keys


Use Registry Editor to remove the Exchange registry keys


Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:


322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows


Translation – if you screw up you blow up Cleveland.  Since the point of this exercise is to totally remove this server from the network anyway, screwing up the registry is okay.  Remember that you cannot have a SBS 2003 on the same network as SBS 2008 or SBS 2011.  Bofh of them will check for another SBS DC in the network and will shut down every hour on the hour.


  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange
  3. Right-click Exchange, and then click Delete. Click Yes in the Confirm Key Delete dialog box.

 


  1. Repeat steps 2 and 3 for the following registry keys.

Collapse this tableExpand this table
Registry KeyDefinition
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DAVEX WebDAV
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EXIFS Microsoft Exchange Installable File System
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ExIPC Epoxy
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EXOLEDB Exchange OLE DB
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IMAP4Svc Microsoft Exchange IMAP4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeActiveSynchNotify Microsoft Exchange ActiveSynch Notifications
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeADDXA Microsoft Exchange Active Directory Connection Agreements
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeAL Microsoft Exchange Address Lists
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess Microsoft Exchange access to Active Directory
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeES Microsoft Exchange Event
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeFBPublish Microsoft Exchange Publish Free/Busy
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS Microsoft Exchange Information Store
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMGMT Microsoft Exchange Management
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA Microsoft Exchange Message Transfer Agent Stacks
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU Microsoft Exchange Directory Service to Metabase
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOMA Microsoft Exchange Outlook Mobile Access
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA Microsoft Exchange System Attendant
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSRS Microsoft Exchange Site Replication Service
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeTransport Microsoft Exchange Message Routing
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB Microsoft Exchange Outlook Web Access
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\POP3Svc Microsoft Exchange POP3
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc Microsoft Exchange Routing Engine

Did that…. but now when they ask me to use the Exchange system manager to remove Exchange stuff from AD I can’t.


Remove the Exchange Server 2003 server from Active Directory


To remove the Exchange Server 2003 server from Active Directory, follow these steps.

Note This procedure removes all references to the server in Active Directory. It also removes the mailbox-enabling attributes from all Active Directory users who have mailboxes on the server that you removed.


  1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
  2. Expand Administrative Groups/Your_Administrative _Group_Name/Servers.

    Note In this step, replace Your_Administrative _Group_Name with the name of your administrative group.
  3. Right-click the name of the Exchange Server 2003 server that you want to remove, click All Tasks, and then click Remove Server.

Not to fear, we have adsiedit to the rescue.


If you cannot install or run Exchange System Manager, you can use the Active Directory Service Interfaces (ADSI) Edit snap-in to manually remove enough of the server attributes so that you can try a successful reinstallation. This method does not perform cleanups of references to the server object outside the server’s own container. We do not recommend that you use this method unless you intend to immediately reinstall the server in the same administrative group. This is because you may have to manually remove or edit many attributes on objects throughout Active Directory.

The ADSI Edit snap-in is available in Windows Support Tools. For more information about how to install Windows 2000 Support Tools, click the following article number to view the article in the Microsoft Knowledge Base:


301423  (http://support.microsoft.com/kb/301423/ ) How to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require that you reinstall Microsoft Windows 2000 Server, Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
To use the ADSI Edit snap-in to remove an Exchange Server 2003 server from an Exchange Server 2003 administrative group, follow these steps:


  1. Click Start, point to Programs, point to Windows 2000 Support Tools, point to Tools, and then click ADSI Edit.
  2. Expand the following items:
    Configuration Container
    CN=Configuration, DC=Domain_Name,DC=com
    CN=Services
    CN=Microsoft Exchange
    CN=Your_Organization_Name
    CN=Administrative Groups
    CN=Your_Administrative_Group_Name_Or_Exchange5.5_Site_Name
    CN=Servers
    Note In this procedure, Domain_Name represents the name of your domain, Your_Organization_Name represents the name of your organization, and Your_Administrative_Group_Name_Or_Exchange5.5_Site_Name represents for the name of your administrative group or Exchange Server 5.5 site.
  3. Right-click the Exchange Server 2003 server object, and then click Delete.
  4. Click Yes in every adsiedit dialog box that prompts you to confirm the deletion

I can’t remember if I installed this on here or not.. but all I had to do was type in adsiedit.msc and it launched the interface.  Now on this one be careful as you can blow up Cleveland in here.



See where we are at?


Configuration Container [domain.lan]
     CN=Configuration, DC=Domain_Name,DC=com
          CN=Services
               CN=Microsoft Exchange
                    CN=Your_Organization_Name
                         CN=Administrative Groups
                              CN=Your_Administrative_Group_Name_Or_Exchange5.5_Site_Name <in SBS this is first administrative group>
                                   CN=Servers

 Under Servers it will list your old SBS 2003.



See where you are at? 


  1. Right-click the Exchange Server 2003 server object, and then click Delete.
  2. Click Yes in every adsiedit dialog box that prompts you to confirm the deletion.

Go look again at what you are deleting and where you are.  You are under the CN=first administrative group and are deleting out the OLD SBS 2003 box.



Are you really sure?



Delete the container?



So right about now you are probably wondering why I didn’t just nuke the “CN=first administrative group” right?


Microsoft recommends that you do not remove the original Administrative groups from an organization.


My nicely migrated SBS production 2008 box to this day lists both the Exchange Administrative Group from Exchange 2007 and the first administrative group of SBS 2003



So if you have manually gone in and just nuked that first administrative group thinking that that will not cause issues, guess again, public folders and other such things want that folder there.


So to review, you want to delete the SERVER name out of that adsiedit.msc, you do NOT want to delete that CN=first administrative group that you see there.  Regardless that that’s the name of the Exchange group in Exchange 2003, you keep it on the server even after you just have Exchange 2010 in the network.

How to manually remove Exchange Server 2003 from your computer

So if you get something stuck in removing your Exchange 2003




Never fear you can manually pick out Exchange 2003 if you really and truly get stuck.


How to remove Exchange Server 2003 from your computer:
http://support.microsoft.com/kb/833396


Hitting cancel thought keeps the uninstall process going…


Hang on I may have googled up something else that refers back to something I wrote eons ago.. (how funny)


So for some other KBs that you might stumble on if you have issues….


Error message when you try to remove Exchange Server 2003 or Exchange 2000 Server: “0x80072030 (8240): There is no such object on the server”:
http://support.microsoft.com/kb/283089


Error: “Setup failed while installing sub-component Exchange ActiveSync with error code 0xC0070643 (please consult the installation logs for a detailed description). You may cancel the installation or try the failed setup again.” while installing Exchange 2003 SP2:
http://camie.dyndns.org/technical/ex2003-sp2-msxml3/



Actually I’m kinda glad this old image of a SBS 2003 didn’t cleanly uninstall like my real one did.  Stay tuned to a Friday night fest of manually removing an Exchange 2003 box.


Do I know how to party or what?

Step 32 – saying goodbye to the old SBS 2003

    You must uninstall Exchange Server 2003 from the Source Server before you demote it. This removes all references in AD DS to Exchange Server on the Source Server. You must have your Windows SBS 2003 media to remove Exchange Server 2003.


    Important


    To remove Exchange Server 2003 from the Source Server, click Windows® Small Business Server 2003 in Add or Remove Programs, and then click Remove. Follow the instructions to finish the procedure.



    At this step you need ANY SBS 2003 media not necessarily YOUR SBS 2003 media.  I downloaded media and then attached the ISO as a DVD to the SBS 2003.


    You’ll need just disk 2 of SBS 2003



    Now go into add/remove programs.





    click next on this one





    Oh but wait ..what’s this error?



    I removed the connectors earlier….


    Delete the routing group connectors that connect the Exchange 2003 or Exchange 2000 routing groups and the Exchange 2007 routing group. You can do this from Exchange 2003 or Exchange 2000 System Manager, or you can use the Remove-RoutingGroupConnector cmdlet in the Exchange Management Shell. For more information, see Remove-RoutingGroupConnector.

    Why am I getting this error?  OH silly me, I deleted it from the SBS section (first administrative group) — the SBS one, but I didn’t delete the connector that goes between the two boxes. 




    Click to remove it


    Confirm the removal


    And there it goes



    When you are done, go into services and make sure that all the Exchange services have been removed.

    Step 31 – getting ready for removing Exchange

    For detailed instructions about how to complete these steps, see the section “To remove the last Exchange 2003 or Exchange 2000 server from an Exchange 2007 organization” in the article “How to Remove the Last Legacy Exchange Server from an Organization” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=141927).


    1.   Move all mailboxes.


    2.   Move all contents from the public folders.


    3.   Move the Offline Address Book Generation Process.


    4.   Remove the public folder mailbox and stores.


    5.   Verify that you can send and receive email to and from the Internet.


    6.   Delete the routing group connectors.


    7.   Delete or reconfigure the Mailbox Manager policies.


    8.   Move the public folder hierarchy.


    9.   Delete the domain Recipient Update Services.


    10.  Delete the Enterprise Recipient Update Service.


    You read this one and go… uh.. we just did most of this.


    9.   Delete the domain Recipient Update Services.


    10.  Delete the Enterprise Recipient Update Service


    We need to do those two.


    1. Perform the following steps to delete the domain Recipient Update Services:

      1. In Exchange 2003 or Exchange 2000 System Manager, expand Recipients, and then select Recipient Update Services.
      2. Right-click each domain Recipient Update Service, and then select Delete.
      3. Click Yes.
    2. You will not be able to delete the Recipient Update Service (Enterprise Configuration) by using Exchange 2003 or Exchange 2000 System Manager. Perform the following steps to delete the Recipient Update Service (Enterprise Configuration) by using ADSI Edit (AdsiEdit.msc):

      1. Open ADSI Edit, expand Configuration, expand CN=Configuration,CN=<domain>, expand CN=Services, expand CN=Microsoft Exchange, expand CN=<Exchange organization name>, expand CN=Address Lists Container, and then select CN=Recipient Update Services.
      2. In the result pane, right-click Recipient Update Service (Enterprise Configuration), click Delete, and then click Yes to confirm the deletion

    This is one that in my SBS 2008 migration I punted and moved the exchange server to the new server.


    It worked fine.



    Step 30 odds and ends

    Got folder redirection — http://technet.microsoft.com/en-us/library/gg563795.aspx


    Got a terminal server? http://technet.microsoft.com/en-us/library/gg563793.aspx


    Now mind you we’re at the “finish the migration step” http://technet.microsoft.com/en-us/library/gg563804.aspx but we haven’t moved over the printers to the new servers … so we’re not quite done… nor have we removed Exchange 2003 yet.


    But the finish line is in sight for sure.