> I managed to get SBS 2008 running on a Hyper-V Server. I am amazed
> that Microsoft could put out such a crippled product as Hyper-V Server. I am
> seriously questioning whether this is a viable production configuration. Not
> to have a GUI is one thing, but essentially Hyper-V Server has no local
> interface whatsoever for managing the virtual servers. Getting the MMC to
> work remotely was a nightmare and may not even have been possible without
> the HVREMOTE script that I found on a blog. Yes, it's working, but I fear
> that if something goes wrong it will be extremely difficult to fix without a
> functioning local management interface. I know I could install a full
> Windows Server 2008 (SBS Premium) and have a GUI and MMC as the hypervisor,
> but that may be a tough sell in the SMB segment. Also, while one could run
> other services and roles on that parent server, that would defeat the
> purpose of having a simple machine *just* to be the hypervisor. It seems as
> though Hyper-V Server is more Hype than Server.
>
> That said, has anyone developed some best practice guidelines for
> this previously uncharted territory? How does one intelligently set up and
> manage an SBS 2008 in a virtual machine? Or is it better just to stick with
> installing SBS 2008 on a real machine and leave virtualization to those who
> have graduated from the SMB space? Finally, can an SBS 2008 be virtualized
> after the fact through some sort of conversion process?
>