I have been tasked with deploying Windows 10 on Hyper-V on Windows 10 Enterprise for a small group of testers to use to test Office 365 environments. I ma fairly new at this.
My predecessor had created a USB drive which contained the following:
1. Windows 7 Base Image (sysprepped)
2. An unattend.xml file
3. An Executable that basically starts Batch Script which in turn starts a PowerShell script.
4. A folder containing a PowerShell and Batch script
The PowerShell script is pretty great:
It does a bunch of checks (usb drive name, proper cred's, windows 10 installed, verifies naming scheme with company policies) before checking for hyper-v and turning that on if missing. It then creates a modified version of the pc name based on computer script is run on and adds VM. Then is copies the template hard drive (#1 above) and the unattend.xml. It then adds the user credentials provided by user to the unattend. Next it mounts the hard drive and copies the modified unattend, and then dismounts drive. A virtual switch is created, the hard drive is renamed according to naming standards, and the vm is created and started. It works really, really well for the Windows 7 image.
I am trying to convert this to do the exact same thing for Windows 10 and having issues.
I have a VM that is set up like I want and I sysprep it. I need to copy a VHDX file, but it seems to me that a avhdx file is created.
Where is the basic directions for doing this located?
Matt Dillon