adamxp12 · December 10, 2016 15:08
diff --git a/Copy ISO to Hyper-V Core server using powershell b/Copy ISO to Hyper-V Core server using powershell
 Copy-Item -Path "\\arnoldv2\iso\Windows disks\en_windows_10_enterprise_x64_dvd_6851151.iso" -Destination c:\en_windows_10_enterprise_x64_dvd_6851151.iso;

 This powershell command is used to copy from a server in this case arnoldv2 to the local C: drive on a Hyper-V core
 run this on the Hyper-V server using powershell

 You might argue saying that you should just use the UNC path directly in Hyper-V manager but even after following every blog post on google I couldnt get it past the "Permision to open attachment" error and this method results in a faster install time as its not streaming ISO over network
	Copy-Item -Path "\\arnoldv2\iso\Windows disks\en_windows_10_enterprise_x64_dvd_6851151.iso" -Destination c:\en_windows_10_enterprise_x64_dvd_6851151.iso;

	This powershell command is used to copy from a server in this case arnoldv2 to the local C: drive on a Hyper-V core
	run this on the Hyper-V server using powershell

	You might argue saying that you should just use the UNC path directly in Hyper-V manager but even after following every blog post on google I couldnt get it past the "Permision to open attachment" error and this method results in a faster install time as its not streaming ISO over network