Okay, not really an issue, but a thank you and a slight issue.

[SBPDevelopment]

Here is a list of things I did to get the process to flow... The issue I'm having is that it is not fully unattended, I get prompted to run through the task sequence even though I don't have to change anything. If you have suggestions on how to make this fully automated, please let me know.

Summary: I end up with the wim files as expected, but have to click through the TS and shutdown the machines after they are captured. Thank you, this is pretty amazing.

#1. Download the files #2. Unblock all the ps1 files #3. Create the c:\setup folder #4. Copy the files to C:\Setup\ImageFactoryV3ForHyper-V #5. Copy the ini setup to C:\Setup\PSini #6. Install latest adk #7. Install latest mdt #8. Create a REF Folder in Task Sequences #9. Create a Deploy/Capture TS for Server 2012 R2 Standard (and every other os and version above that) #10. Update Deployment Share #11. Update the ini and xml files (server name, vswitch, SkipCapture=No, DoCapture=Yes) #12. Run these two scripts to enable hyper-v and Powershell Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All Add-WindowsFeature RSAT-Hyper-V-Tools -IncludeAllSubFeature

[DeploymentBunny]

Ok, so, if you check the customsettings.ini file you should see that it adds the computer BIOS serial number, if not you are missing the PSINI PowerShell module

[it-leksand]

so, i got one issue here (moved from V1 to V3 just today) and that is the script exits abruptly while the installation is still going...

`Name PercentComplete Warnings Errors DeploymentStatus StartTime LastTime

---

W10X64-SWE 53 0 0 Active/Running 2021-02-01 10:07:22.977 2021-02-01 10:09:13.267

LIF, Cleanup VMs, 02/01/2021 11:11:09 Deleting 'W10X64-SWE' failed. The operation cannot be performed while the object is in its current state. + CategoryInfo : InvalidOperation: (:) [Remove-VM], VirtualizationException + FullyQualifiedErrorId : InvalidState,Microsoft.HyperV.PowerShell.Commands.RemoveVM + PSComputerName : DESKTOP-153K4D0`

the installation is still going and i expect it to finish without issues.. is there any obvious reason why the script would exit all of a sudden?