05-14-2008 09:27 AM
05-14-2008 11:42 AM
05-22-2008 10:08 AM
06-03-2008 10:48 AM
06-09-2008 01:07 PM
06-12-2008 10:35 AM
07-10-2008 09:11 AM
Well I tried your suggestion Cliff. I got as far as running the Recovery Disk Wizard. It failed to discover the HyperV drivers. It did find the virtual NIC drivers. I also got a warning from the wizard indicating that 64-bit drivers were not supported but they can be added manually (or words to that effect). I suspect we are dealing with a "half-way" build; 8.0.2 has partial 64-bit driver support but doesn't actually work. Then I thought to myself, how hard would it be for Symantec to provide a custom SRD image that would work in this scenario (recovering to a running 64-bit VM).
Symantec: Question -- How long do we have to wait for a solution? HyperV is now released. I signed up for the beta test of 8.5 but have heard nothing. I am testing a version of System Center VMM 2008 that does work as far as converting a running 64-bit server to a VM. Is Symantec actually working on a solution? It would be polite to let customers know what is going on...
Cheers, Tony
07-10-2008 09:17 AM
Hi Tony,
I found a workaround. What I ended up doing was simply using the BESR console to convert the images I needed to .VHD files. When you boot up on them in Hyper-V and run the Integration Services setup it first has to replace the HAL and reboot. After it does that it goes ahead and installed the Hyper-V drivers and voila! I was up and running. Of course, that was for a 32 bit version of Windows. What happens if you try to convert the image to a .VHD file?
Cliff
10-18-2008 11:31 AM
10-20-2008 10:36 AM