Installing Virtual CD Software in a Virtual Machine

Installing Virtual CD Software in a Virtual Machine

  • Comments 8

Like many Hyper-V users, I have created ISO images of most of my CDs / DVDs (and in the case of my MSDN software – have downloaded in ISO format to begin with).  I then have these images stored on a file server.

It is possible to connect a CD ISO image on a file server to a Hyper-V virtual machine, as long as you are working in a domain environment and you are running the Hyper-V management user interface directly on the Hyper-V server.

If you run the Hyper-V management user interface on a remote computer, you will need to enable constrained delegation in order to use ISO images on a network share.  If you are running in a workgroup environment your only option is to enable anonymous access to the file share that holds your ISO images (obviously not a good idea from a security point of view).

Aside: The reason for these conditions is that Hyper-V requires the use of both your personal user credentials and the Hyper-V servers workstation credentials when connecting an ISO image to the virtual machine. 

Your user credentials are used to verify that you personally have permission to use the ISO image in question.  The use of your user credentials is why constrained delegation needs to be enable for remote management to work.

The Hyper-V server workstation credentials are used to ensure that we can start the virtual machine, and connect the ISO image to the virtual machine, even when you are not logged into the server (for example, if the server needs to be rebooted).  Unfortunately workstation credentials only work in domain environments – so workgroup environments need to enable anonymous access.

As I am using Windows Home Server for my file server – which does not support being joined to a domain – setting up a share with anonymous access was the only option for me.  But I found this idea so abhorrent that I would make local copies of ISO files as I needed them instead. 

Needless to say I was far from happy with this arrangement.

Furthermore, as I often use Remote Desktop to connect directly to the guest operating system in my virtual machines, I have found it irritating to need to switch back to the Hyper-V management user interface solely for the purpose of connecting a new ISO image.

Luckily I have found a simple and elegant solution to both of these problems.

What I have done is to install Virtual CD software inside each of my virtual machines.  This allows me to use ISO images that are stored on my Windows Home Server, and I can connect CD ISO images even when I am connected using Remote desktop.  For my virtual machines I am using Alcohol 52%, but other programs to look at for this include Virtual CloneDrive and DAEMON Tools.

This solution will not work for installing operating systems (but I these days I tend to use Windows Deployment Services for that – so that is not an issue for me) but it works for everything you could think of once the operating system is up and running.


Leave a Comment
  • Please add 7 and 6 and type the answer here:
  • Post
  • I think the best ISO tool for use inside VMs is MagicISO's free MagicDisk. It even lets you compress your ISO files down and run from the compressed image. They have versions that work in Windows XP, Server 2000 on up to Windows 7/Server 2008R2 in both 32 and 64 bit.

  • Since there was a problem with windows 7 and daemon tools when I first got my hands on win7, I went out and looked for an alternative.

    Pismo File Mount Audit package is free and works great.

    Right click the .iso and mount it, it will then act like a folder.

  • +1 on MagicDisk I have used it all VMs of all Windows flavors and it has worked great and has been very fast.

  • Magicdisc is really great, doesn't even need a reboot and supports all current operating systems.

  • I will have to go and check these options out!



  • I have been using Pismo File Mount Audit package and find it be have the best interface, but recently changed to Virtual Clone Drive as PFMAP was missing the capability to do launch the "autorun" program on a disk image. (I genererally don't do this, but explicitly needed to test that it works)

  • +1 for Pismo. With the command line options for pismo you can install it unattended which means that for our server build scripts we can kick them off against a vanilla Windows Server and then be able install pismo through script as well as mount and install any other software that uses ISOs all through script without any user interaction.

  • install 7zip and just extract the iso?

Page 1 of 1 (8 items)