Yeah, saw that article thanks, but in it it says "If an incorrect HAL is forced during Setup or by using a System Preparation Image (Sysprep), you can see the correct list of HALs only if you perform a new installation of Windows XP or Windows Server 2003. You cannot change to a HAL other than what is listed in Device Manager. Device Manager does not permit the change from a Non-ACPI HAL to an ACPI HAL. You must use a new install of Windows XP or Windows Server 2003 for this kind of change. Change from an ACPI HAL to a Non-ACPI HAL only for troubleshooting purposes."
And the instructions are for moving from just about any HAL *other* than Standard PC (non-acpi). :( -----Original Message----- From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: 08 December 2008 16:52 To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types http://support.microsoft.com/kb/309283/ It actually is trivial, though unsupported. I have done this a few times w/o issue. jlc -----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 6:52 AM To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types There is no trivial way to update a HAL that I know of. I just use the products that MSFT has made available to me... I'm not a virtualization MVP, sorry. :-( Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 8:46 AM To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types Is there a way to do it at the OS level without using something quite as....large as SCVMM? I'm keen to not have to learn anything new today in case my head explodes. -----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: 08 December 2008 13:42 To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types So...download the 120 day eval and use it to do your imports. And, in regards to performance: my tests indicate them being pretty much neck-and-neck. Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 8:39 AM To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types Michael, Alas no. We did the import using VMX2vhd on the internet. We don't run SCVMM here. Olly -----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: 08 December 2008 13:32 To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types Are you using SCVMMs V2V and/or import capabilities? Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 8:29 AM To: NT System Admin Issues Subject: VMWARE to Hyper-V and HAL types Hi chaps, I'm looking at moving our VMWare based VMs to our new Hyper-V based servers. New VMs are working a treat, and certainly Hyper-V seems far more responsive than our VMWare based setup. However existing VMWare based VMs are proving an issue. While the VM's have been imported to Hyper-V without any problems it would appear that the HAL of the VMWare VMs have all been set to 'Standard PC' at some point during the installation of the guest OS (all Windows 2003). In order to install the Hyper-V tools we need to be running a ACPI based HAL. My question is this; is there a way in Windows 2003 to move from a Standard PC based HAL to an ACPI based HAL ? I know that MS don't support it (at least from what i can see on the web), but is there a way to hack a solution to it ? The only option we have at the moment is to re-install the guest OS's but that would mean a lot of work and possibly re-config of the apps running on them. Olly ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
