NavigationUser login |
Pitfalls to avoid with SCVMM 2008 P2V (error 2916)Recently I’ve had to set up two Hyper-V hosts. As we are currently running a hodgepodge of VMWare products (mainly VMWare Server in various incarnations, including the disgusting version 2), we are looking for alternatives that are easier to manage. VMWare might be leading from a technical standpoint, but if you are used to proper service and operations management it’s easy to come away disappointed. Hence my foray into Microsoft’s virtualization territory. Read on for a few pointers into the various pitfalls I managed to fall into (and clamber out again). First of all, every single problem I had had to do with the fact that all communication is SSL encrypted. Not once have I encountered a problem with a specific application or system to convert, nor with the conversion components themselves. So here goes, in order of discovery and severity:
Other than that, it has been smooth sailing so far. SCVMM is a great piece of software, and while a little unpolished when it comes to integrating ESX it’s a lot better than what VMWare offers when integrated with the rest of System Center (an I'm fortunate enough to have most of them). By mirko at 30.03.2009 - 20:19 | mirko's blog | login to post comments
|