garytown VS Download-WindowsESD

I recorded how I was able to get those fwlink urls out of the MCT https://github.com/gwblok/garytown/blob/master/Feature-Updates/ProductXML.md

Typically, you'd set that variable via a pre-definded structure. Example, I run this script in my TS to set the name based on the Model Name, this works great in my lab, because I only have one of each Model, but it's an example of how you can automatically set the computer name. https://github.com/gwblok/garytown/blob/master/OSD/CloudOSD/CreateOSDComputerName.ps1

I've done this in the past: https://github.com/gwblok/garytown/edit/master/CreateManufacturerCollections.ps1

https://github.com/gwblok/garytown/tree/master/OSD/CloudOSD There is an OSDCloud based TS you can import from a zip file in that repo

I've never done this before, nor am I that proficient with PS, but try this (shamelessly taken from garytown's github)

You can check out this script for a sample: https://github.com/gwblok/garytown/blob/master/hardware/HP/ConfigItems/HPManagementBaseline/HPBiosUpdateComplianceRemediation.ps1

Given that ARM64 OSD support entered preview last week, I took a bit of time to cobble together a tool based on the idea put forth in a blog post by Mike Niehaus and automated it. It's got limited error handling and language support, because I built this for my purposes in about 30 minutes cobbled together from snips of things I've done in the past, but feel free to fork or fix if you desire.