Citrix: Import NetScaler (10.1 Build 120.13) on Hyper-V Server 2012R2 / 8.1

Written by Ingmar Verheij on November 5th, 2013. Posted in Netscaler

Hyper-V did not find virtual machines to import from locationI tried importing a Citrix NetScaler Virtual Appliance on a Windows 8.1 machine and received the error “Hyper-V did not find virtual machines to import from location”. Importing the same appliance on Windows Server 2012 did work.

The cause of this error is that the virtual machine is exported from a Windows Server 2008R2 server (running Hyper-V 2) and Microsoft deprecated the WMI root\virtualization namespace v1 in Windows Server 2012 (Hyper-V 3) and removed it Windows Server 2012 R2 (see TechNet).  There’s no support for the old WMI format.


When a virtual machine is exported using Hyper-V 2008 R2 three folders are created:

  • Snapshots
  • Virtual Hard Disks
  • Virtual Machines

SJCDHYPERV01rootvirtualizationMsvm_ResourceAllocationSettingDataIn the Virtual Machines folder a file with the name {GUID].exp exists that contains the specification of the virtual machine, including all hardware devices. The hardware is addressed using WMI using the deprecated WMI format (root\virtualization).

Starting Windows Server 2012 (Hyper-V 3) the configuration is not stored in a .exp file but in a .xml file, specifying the hardware using the WMI format root\virtualization\v2.  For more details see Microsoft TechNet.



The workaround that’s available is to import the Citrix NetScaler Virtual Appliance in a Windows Server 2012 Hyper-V (no R2) machine and export it using the new WMI format (root\virtualization\v2),. This of course requires you to have a Hyper-V 2012 machine available. In case you don’t have it available, I provided the XM, you can find it at the bottom of this article.



Option 1) Import and export


  • Open Hyper-V Manager
  • Click on Import Virtual Machine
  • Specify the location of the (extracted) Citrix NetScaler Virtual Appliance
  • Select the virtual machine to import
  • Choose the import type: Copy the virtual machine (create a new unique ID)
  • Choose the destination and storage folders

Import 1Import 2Import 3Import 4Import 5Import 6Import 7Import 8



  • In Hyper-V Manager select the imported virtual appliance
  • Click Export
  • Specify the export location



You can now import the exported virtual machine in Windows Server 2012 R2 (or Windows 8.1)


Option 2) Use my XML file

  • Extract the Citrix NetScaler Virtual Appliance
  • Remove the existing .exp file
  • Place the 55A0A2A9-2571-4F7F-88B3-763E3BC0169E.XML file (for link see below) in the Virtual Machines folder


Virtual Machines

You can now import the exported virtual machine in Windows Server 2012 R2 (or Windows 8.1)




You can use the virtual machine configuration file here:





At the moment of writing Citrix NetScaler (10.1) does not support Windows Server 2012 (R2), hence why the import doesn’t work. The solution provided is only for testing purposes.




Ingmar Verheij

At the time Ingmar wrote this article he worked for PepperByte as a Senior Consultant (up to May 2014). His work consisted of designing, migrating and troubleshooting Microsoft and Citrix infrastructures. He was working with technologies like Microsoft RDS, user environment management and (performance) monitoring. Ingmar is User Group leader of the Dutch Citrix User Group (DuCUG). RES Software named Ingmar RES Software Valued Professional in 2014.

More Posts - Website

Follow Me:
TwitterLinkedInGoogle Plus

Tags: , , , ,

Trackback from your site.

Comments (7)

  • Erik Bakker
    5 November 2013 at 16:25 |

    Option 3: create a new VM with the correct specifications (2 vcpu and 2gb ram) with no harddisk en copy/paste the netscaler vhd to the newly created VM folder, then modify the vm to use that vhd.

  • 15 November 2013 at 05:53 |

    Hey Ingmar,
    Excellent article.Thanks a lot for sharing the downloading links here.

  • Sigmar Hund
    14 March 2014 at 12:18 |

    Thank you for providing your XML-file! Worked like a charm.

  • 24 March 2014 at 17:52 |

    Works like a charm. Thanks mate

  • bry
    31 March 2014 at 15:49 |

    Thanks for this, man! I was stuck in a rut, looking thru the .xml and .exp files trying to find what they pointed to, and what I could to import this damned appliance… Option 2 did the trick as I did not want to spin up a 2012 vm, and my experience w/ Hyper-V is limited to 2012 R2. Anyway, thanks again!

Leave a comment



%d bloggers like this: