If you’ve been paying attention

On July 12, 2011, in sbsblog, by

If you’ve been paying attention there’s been three recent blog posts about the Microsoft migration method and things to keep in mind while performing it.

One thing I’ll still like to recommend STRONGLY is that you practice.  Preferably not on a paying customer on their deployed SBS 2003 box.  You want to physical to virtual  a SBS 2003 (the crustier the better) and then practice the migration on THAT.

First Part: SBS 2011 Standard Migrations – Keys to Success <http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx>

Second Part: SBS 2011 Standard Migrations – Keys to Success – Part 2: The Setup Phase <http://blogs.technet.com/b/sbs/archive/2011/07/08/sbs-2011-standard-migrations-keys-to-success-part-2-the-setup-phase.aspx>

SBS 2011 Standard Migration – Keys to Success – Part 3: Post Setup and Common Failures – The Official SBS Blog – Site Home – TechNet Blogs:


20 Responses to If you’ve been paying attention

  1. Scott says:

    Being an SBS newbie back then, I purchased an OEM SBS2003 and, of course, didn’t know about the 90 days to purchase software assurance. So technically, licensing prevented me from being able to P2V my SBS2003 install. But I crossed my fingers and dialed up the activation hotline and was presently surprised when I was able to get to the desktop in a Hyper-V. I practiced the migration twice using MS and DIVA resources and our migration went along without a hitch.

    My only issue with SBS2011 is trying to remember how many critical errors I’m supposed to ignore… grrrrrr

  2. Dean says:

    “Preferably not on a paying customer on their deployed SBS 2003 box”

    LOL !

  3. Dean says:

    Shouldn’t you P2V the customers server though and do AT LEAST one trial run ? That way you know the problems with THAT server.

    Does anyone know what the BEST P2V program that will make Microsoft compatible VHD’s is ? Doesn’t have to be free.

  4. bradley says:

    Sysinternals Disk2vhd works like a champ.

  5. Dean says:

    “Sysinternals Disk2vhd works like a champ.”

    Yeah but the problem with those Sysinternals tools is that they are not supported. If you run into a problem you are on your own. Disk2vhd hasn’t been updated since October of last year. When working on live stuff I always prefer supported tools if possible.

  6. bradley says:

    You asked for the Best. Given that SBS 2003 is not supported unless it’s in virtual server, you won’t get much support period.

  7. Dean says:

    Well, the best overall. I’m not interested in only SBS.

  8. bradley says:

    If you want to go to a MS virtualization platform, it is the best. Anytime there is Exchange in the mix you have to tap dance around support of Exchange on virtualization throughout the years.

  9. Dean says:

    “Anytime there is Exchange in the mix you have to tap dance around support of Exchange on virtualization throughout the years.”

    What does that have to do with disk2vhd ? Or P2V for that matter ?

  10. bradley says:

    Support. Exchange 2003 is supported on Virtual Server 2005 only. Exchange 2007 and later on HyperV.

    If you are in the process of PtoVing something and you tell the support person “I’m doing this to move to HyperV” Exchange will dictate if they support you or not.

  11. Dean says:

    Your getting things mixed up. I’m talking about the tool to use to make a virtual machine NOT what’s in the virtual machine. The tool used could care less ( at least a proper one should ) about what is in the OS. In other words the tool should only be making a faithful copy of what is on the hard drive.

    I asked what tool does that the best and that can make Microsoft compatible VHD’s hopefully with support from the company that made it. Maybe Disk2vhd is the best but I wanted multiple opinions.

  12. bradley says:

    Support boundaries are driven by the platform. Exchange 2003 for example isn’t supported in Vmware. If you want to have support all the way throughout the virtualization process, it’s the parts that drive the support.

    ISA 2004, for example, isn’t supported at all in virtualization.

  13. Dean says:

    All of that still has nothing to do with the tool you use to make the VHD. And if it’s the parts that drive support that would be the very first part which is why I would prefer that it be supported.

    You could of course make a fresh VHD and install the OS into it fresh.

  14. Dean says:

    “Because this software is “as is,” we may not provide support services for it.”

    “The software is licensed “as-is.” You bear the risk of using it. Sysinternals gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this agreement cannot change. To the extent permitted under your local laws, sysinternals excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.”


  15. Dean says:

    It’s not your fault. It’s that California air.

  16. Dean says:

    “Do not use the Disk2VHD Windows Sysinternals utility on Domain Controllers”


    I would add don’t use it at all on servers, especially ones running ANY kind of database which is what Active Directory is hence the above warning.

  17. bradley says:

    There are things we do in SBS that the big guys never do. For one they don’t care about dc, they build a new one and replicate. We, however do whatever it takes to restore it exactly as it was. Of course ours is also the mail server and kitchen sink.
    For the needs of the intent – to do a dry run of migration it works perfectly.

  18. SeanPT says:

    The whole point of taking your SBS2003 box, making a VHD and running the migration through a virtual session to see if there are any hiccups. If you can get it working right with virtual tools then who cares if it isn’t supported?