The operation failed with error code '32784' when importing the virtual KACE Systems Management Appliance (4262892)

Consider one of the following causes:

• You are trying to import the KACE VKSMA appliance VM that is exported from a Windows Server 2012 R2 Hyper-V host into a Windows Server 2012 or older Hyper-V host. This action (similar to moving) is not a supported scenario. For more info, see http://support.microsoft.com/kb/2868279
• Features Removed or Deprecated in Windows Server 2012:
  • The WMI root\virtualization namespace is deprecated. The new namespace is root\virtualization\v2.
• Features Removed or Deprecated in Windows Server 2012 R2:
  • WMI root\virtualization namespace v1 (used in Hyper-V)
• This may also occur, if the .exp file is missing from VK1000_9_1_317_HYPERV.zip file.

SOLUTION 1:

1. Open Windows Explorer
2. Browse to the unzipped directory :\VK1000_9_1_317_HYPERV\...
   • where  is the drive letter, of where you want the VK1000_9_1_317_HYPERV.zip file to be unpacked
3. Confirm if the .exp file is present in the :\VK1000_9_1_317_HYPERV\Virtual Machines\ sub-directory
   • If the .exp file does not exist, continue with SOLUTION 2
   • If the .exp file is present, continue with step 4
4. Delete the .xml file (the original .xml file can still be found in the VK1000_9_1_317_HYPERV.zip file)
5. Open Hyper-V Manager
6. In Hyper-V Manager, in the Actions pane, click Import Virtual Machine. The Import Virtual Machine dialog box appears.
7. In the Import Virtual Machine dialog box, click Copy the virtual machine (create a new unique ID).
8. Click Browse, browse to the folder where you exported the base virtual machine, and then click Select Folder.
9. To import the base virtual machine as a new virtual machine, click Import.

SOLUTION 2:

1. Open the Hyper-V Manager
2. In Hyper-V Manager, in the Actions pane, click New | Virtual Machine
3. In the Specify Name and Location dialog, specify a new name (e.g. vK1000) and click Next
4. In the Assign Memory dialog, provide the appropriate amount of memory and click Next
5. In the Configure Networking dialog, select the virtual switch and click Next
6. In the Connect Virtual Hard Disk dialog, select either:
   • Use an existing virtual hard disk, select the VK1000_9_1_317_HYPERV.vhdx file and click Next or
   • Attach a virtual hard disk later and click Next
7. In the Installation Options, select Next to accept the default setting and click Next
8. Verify the Summary and select Finish

Alternatively, you can create the virtual machine using the Windows Powershell:

WINDOWS POWERSHELL METHODS

Note: You can change the values, described in cursive, to match your production environment.

Method 1:

This method creates a new virtual machine named vK1000 that has 4GB of memory, connects to an existing virtual hard disk and an existing virtual switch named KACENet.

• New-VM –Name "vK1000" –MemoryStartupBytes 4GB -SwitchName "KACENet" –VHDPath VK1000_9_1_317_HYPERV.vhdx
• Start-VM –Name "vK1000"

Method 2:

This method creates a new virtual machine named vK1000 that has 4GB of memory, connects to an existing virtual hard disk. After creating a new virtual machine, it will connect to a new virtual switch named KACENet. In this method, the Switch Type "Private" is used for isolated internal communications. You can use Switch Type "Internal", if communications from the VMs to the Hyper-V host must be established.

• New-VM –Name "vK1000" –MemoryStartupBytes 4GB –VHDPath VK1000_9_1_317_HYPERV.vhdx
• New-VMSwitch -Name "KACENet" -SwitchType Private
• Get-VMNetworkAdapter –VMName "vK1000" | Connect-VMNetworkAdapter -SwitchName "KACENet"
• Start-VM –Name "vK1000"