Complete your post-migration tasks. Follow the instructions on pages 75 through 78 in the Microsoft migration document.
  Manage natively joined computer objects in Windows SBS Console

This setting is only if you manually joined ‘stuff’ and thus it didn’t end up in the MybusinessOU/SBSComputers bucket.

Drag and drop the computer objects from their current location to the SBSComputers container, and then click Yes in the warning dialog box.

If you were a good SBSer, you won’t have to do a thing here.

  Remove Source Server entries from DNS  

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.   Click Continue in the User Account Control dialog box.

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.

(basically expand all the trees and look for the old server name and the old server IP and remove them)

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.

You’ll see several LDAP records for the old server and remove these.

  Configure POP3 Connectors

Some folks use pop connectors for legacy programs.. I don’t use them at all.  If you need to, it’s in the Network tab under connectivity.  It’s pretty self explanatory what to do.

  Update mailbox quotas

Yeah like we don’t set any quotas in small business, other than tell people “I told you so” when their Outlook runs slow.  I already took all the quotas off and we’ll be leaving them off.

  Share line-of-business and other application data folders

We already did that via David Overton’s handy dandy script.  You do need to poke holes in the server firewall as you need them for databases.  More on this in another blog post as well.

  Install 32-bit printer drivers on the server running SBS 2008. See the blog post  for more information

This one is going to get it’s own blog post.  Stay tuned.

  Fix client computer issues after migrating from SBS 2003

“When migrating to Windows SBS 2008 from Windows SBS 2003 Premium Edition with Microsoft Internet Security and Acceleration (ISA) Server installed, client computers on the network still have the Microsoft Firewall Client and Internet Explorer configured to use a proxy server. This causes connectivity issues on the client computers, because the proxy server no longer exists. If there is a different proxy server configured, the client computers continue to use the server running Windows SBS 2003 for the proxy server. To fix this issue, you must remove the Firewall Client on the client computers, and then reconfigure Internet Explorer either to not use a proxy server or to use the new proxy server.”

Dude, if I just ripped out the SBS 2003 premium with ISA, I should have done this (which I did) as a preliminary step when I installed the brand new firewall.  This needs to be done as a pre-step, not a post step.  Now here is where you do want to reset someone’s password, log in ON THEIR PROFILE and make sure everything works.  Like … oh.. the BOSS THAT PAYS YOUR BILLS would be a good one to log into and check. 


4 Responses to Migration Step Thirty Two: We see the finish line in view

  1. Bill V says:

    Hi Susan,

    Just wondering… What documentation are you following for the migration? Might have missed this at the beginning of your journey. Swing Kit or Karl Palachuk’s migration book.

    Bill V

  2. bradley says:


    Microsoft migration method.

    I’ll discuss all three in the end.

  3. Bill V says:

    Looking forward to it. Perhaps a post with a PDF of all the steps. That would be GREAT!

  4. Jake says:

    When finding printer drivers I’ve found dumping out the built-in Microsoft drivers from a x86 2008 Server saves a lot of hassle.

    On a x86 2008 server goto %systemroot%\system32\DriverStore\FileRepository and copy out all the folders that start with prn* and also copy out the ntprint directory. Then you can just use the 2 letters after prn to locate the manufacturer.
    prnhp001.inf_ba023fd3 = HP
    prnlx001.inf_54ff49cf = Lexmark
    prnky001.inf_9592bf8d = Kyocera Mita

    If your not sure just open the INF file and look under the [Manufacturer] section and it will tell you.