Sun, Nov 14 2010 23:50
bradley
Decisions to make
During this time right now you may have clients that you want to migrate but you don't want to be out of the shoot first thing. What to do?
First off a caveat. This does put your client in an unsupported state. This is one of those "it works" but "it's not supported". You can consider moving the SBS 2003 to hyperV while you wait for SBS 2011 to RTM and you wait until you've had time to practice migration.
Exchange sets the tone of what gets supported and it doesn't get supported on HyperV. Virtual server 2005 yes, HyperV no. Does it work? Yes. Is it supported? Again, no.
So why am I blogging that you may want to think about this? Because the reality is you may want to think about this route. If their existing hardware is soo wheezy you can't bandaid it, you could think about getting a new server and HyperVing it just to hold them over.
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")