Hyper-V 2019 will NOT mount ISO from a network share.

Like most IT guys. They have a repository of their ISO images saved on a network share so that they can mount the ISO if needed on multiple machines. I recently switched to Hyper-V and have been having an issue with creating VMs and using my ISO from my network share to do so.
Hyper-V Manager available through RSAT doesn’t have an option to mount an ISO or capture a drive from a machine on which is running. Instead it gives you drives of the Hyper-V host, and that would of course require you to have an ISO or the disc itself present on the host. I didn’t want to do that. I would rather have my repository share available for that purpose to allow for all the drive space to be available on the Hyper-V host.

So, I would map a network drive with my ISOs. The mapping would succeed, but mapped drive (letter) will not be visible in Hyper-V manager when trying to mount an ISO. Okay, so next I tried mounting from UNC share directly, but that would also fail, with the message:
“‘VM’ failed to add device ‘Virtual CD/DVD Disk’” “User account does not have permission required to open attachment”.

hyperv1
Access Denied Error when trying to mount the ISO

It goes back to the constrained delegation requirement for the Hyper-V host accounts to be used to perform functions such as this. This has been a pain to say in the least, as I have also had issues with live migration with my machines not being clustered due to different hardware.

So, in researching, I found this blog post. It has helped me through this issue with mapping the shared folder with the ISOs.

The cause of the problem is that the Hyper-V is intended to run with VMM Library Server and to mount files from it, not any random share. To re-mediate this:

  • You need to assign full NTFS and share permissions to computer account of Hyper-V on a shared folder with ISO’s you want to mount.
  • In AD on the computer account of Hyper-V machine delegate specific service ‘cifs’ to the machine you want your ISO’s mounted from. Microsoft calls this constrained delegation.

Here is step by step procedure for the constrained delegation:

  1. Go to Active Directory Users and Computers
  2. Find the Hyper-V server computer account and open up its properties.
  3. Go to Delegation tab.
  4. Select Trust this computer for delegation to the specified services only radio button.
  5. Click the Add button.
  6. Click the Users or Computers… button.
  7. In the Add Services window, click Users or Computers and enter the computer account that will  act as a library server and click OK.
  8. Select the cifs Service Type and click OK.

The resulting setup should look something like this:

Constrained delegation
What the configuration should look like for constrained delegation

I added both the server that contained the ISO images and the server that I run my RSAT tools from just to be safe. I next rebooted the Hyper-V host (that is a requirement).
When the host rebooted, I was able to successfully create the VM.

Hopefully, this will also solve my issue with live migration between my hosts. I will have to test that again and will inform everyone here if that succeeds as well!

PLEASE COMMENT!
THANKS FOR READING!

References:
Hyper-V Server 2012 won’t mount ISO from a network share
Hyper-V authentication in Windows Server 2016 for managing remote Hyper-V servers through RSAT
Constrained Delegation

VCSServiceManager.msi

LDLNET LLC - Life In Action! Your Source for Professional IT Services!

Let me just say that file is possibly: THE WORST FILE THAT EVER EXISTED ON THE FACE OF THIS EARTH! 

I have had the absolute worst experience trying to install VMWare vCenter Server 6.x onto my Windows Server at the house. I didn’t really have any issues with installing vSphere 6.7 on my HPE Proliant DL360 g6 server so that I could update my environment. I was going to put vCenter on as well so that I could keep my servers updated and such.

The main issue with the install is that it fails when installing the VCSServiceManager.msi component with a 1603 error. Needless to say, this has been a major issue that started with version 6.0. I have looked through all of the following articles in my search to remediate this issue:

I’ve looked through more than that honestly and was NOT able to get past that part of the install, now I did install the msi separately, and the main install acted like it finished successfully, but none of the services installed on the server and the vCenter Component was basically non existent when trying to access it. I even went through setting up an Microsoft SQL Server Express back end thinking it might be an issue with the Python SQL component that comes with vCenter. I even formatted my Server OS and started from scratch. No luck what so ever on the installation. I bet I spent 30 man hours over the course of a week or two trying install after install.

Seeing that it is the evaluation version, I cannot seek direct help from VMWare as their support is paid support, but being an IT guy myself, and seeing all the problems with that part of the install, leads me to believe that I wasn’t the problem when I was installing the software. I followed all the processes to get the installation to go smoothly and correctly, but did not succeed.

I used to be a real advocate for VMWare as a great Hypervisor, but, I will be migrating to Hyper-V now. I’m running all 2019 servers anyway, I should have Hyper-V on my host.

Question: Has anyone had issues with Hyper-V or Server 2019 Datacenter on an HPE Proliant DL360 g6 server? I haven’t seen too much issue from my research. So if the blog is down this weekend, you’ll have knowledge why as I convert my VMs to VHDX disks and get Hyper-V setup.

Happy Reading! Please leave some feedback!