Should you really virtualize MultiPoint with itself?

In Multipoint 2011 you were allowed to install Multipoint, rip out its guts and then install it as a child.  It kinda sorta made some sense when you were in the 2008R2 era as it saved the price tag of a GUI server OS to control a virtualized Multipoint.  But in the 2012 era it’s more of a ehhhhh do you really want to do that? and a ehhhhh should you do that?  Remember in the 2012 era you get a 1+2 virtualization right, not the 1+1 you had in 2008 r2.  So you already get a spare in the parent GUI 2012.


Also there’s more hoops to jump through to get RemoteFX working on server 2012. 


So while one CAN still install Multipoint 2012, rip out the guts and make it a base operating system for virtualization… the better question is… why not plop down a Server 2012 as your virtualization base?  It’s a better decision to do virtualization the right way.

One Thought on “Should you really virtualize MultiPoint with itself?

  1. Even with Server 2008 R2 this didn’t really make sense. Hyper-V Server was freely available, so it would have been easier to just install a Hyper-V Server, then install MultiPoint as a guest (unless you really REALLY need a GUI for your host).

    The same is true with the 2012 version. The only difference is that you’re now getting 1+2 virtualization rights instead of 1+1, though the “1+” part has always been available for free anyway.

Post Navigation