If you’re running SBS 2003 on Hyper-V then you should be aware that this is not a supported configuration as detailed in one of my previous posts.

I asked Chris Almida of Microsoft who owns the Migration Feature and this was his reply

SBS 2003 contains a version of Exchange and Sharepoint that are specifically NOT supported under Hyper-v.  Since these are integrated into SBS 2003  it too becomes unsupported on Hyper-v.  This doesn’t mean that it won’t run it simply means if you call MS for support of any issue with SBS 2003 and are running on Hyper-v you won’t be able to get any support.

I also asked him whether Microsoft would support an installation of SBS 2003 which had been part way or through all the steps of a Swing Migration and his reply was

The short answer is yes,  however support of Jeff’s method comes from Jeff himself MS won’t support issues related to it.

 

 

So, if you ring Microsoft PSS and SBS 2003 is running on Hyper-V then you won’t get support for it. Interestingly I asked a few Partners whether they would use this scenario and they have said they would or they are already doing this. One Partner told me on Facebook that they had a published Microsoft case study with this type of set-up.

Why would you want to do this? Why not go straight to SBS 2008 on Hyper-V if you’re doing a hardware refresh?

I think this can be a stepping stone for a customer going from SBS 2003 to SBS 2008 but who needs new hardware. You can sell them a new server, virtualise SBS 2003, they have new hardware with no impact on their current setup/configuration. They are happy with you and maybe more likely to buy SBS 2008 at a later date especially in the current economic climate. Obviously they have to have the appropriate license to be able to virtualise SBS 2003.

What do you think? Is this something you are doing or looking to do?