{"id":9278,"date":"2008-11-18T15:55:00","date_gmt":"1999-11-29T20:00:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=9278"},"modified":"2008-11-18T15:55:00","modified_gmt":"1999-11-29T20:00:00","slug":"vmm-2008-p2v-to-hyper-v-of-dl360g5","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=9278","title":{"rendered":"VMM 2008 P2V To Hyper-V Of DL360G5"},"content":{"rendered":"

I’ve used a "security server" running DL360’s with WSUS and AV in several jobs now.\u00a0 They’re great candidates for virtualisation so the security server at work was my first target to convert to a virtual machine, thus freeing up some h\/w for profit making.<\/p>\n

The P2V process of VMM 2008 is pretty easy.\u00a0 I found no fault with it.\u00a0 However, I did have some problems that were non-VMM 2008 related.<\/p>\n

The VM would hang on boot up.\u00a0 I got it into safe mode and disabled the HP services.\u00a0 They were trying to access hardware that didn’t exist.\u00a0 Ideally you would uninstall this stuff before P2V but I needed to keep the physical machine online until the virtual was ready.<\/p>\n

Once the VM was ready I installed the integration components in VMM 2008.\u00a0 I fired up the VM and tried to log in … uh oh!\u00a0 It needed to be reactivated.\u00a0 Luckily I’d put the machine on a test network with Internet access so that was done.\u00a0 Then I had a service failure pop-up.\u00a0 The event log showed that was OK, the server was looking for the domain and not finding it … it’s still on the test network while the physical machine is still providing services.<\/p>\n

Now the killer.\u00a0 I got a pop up about WMIPRVSE failing.\u00a0 That repeated 9 times when I closed it.\u00a0 I also had dozens of WINMGMT errors in the application log.\u00a0 To troubleshoot I made a checkpoint and started googling and trying things out.\u00a0 In the end here’s what it came down to:<\/p>\n