1. All systems start with the same basic system image, deployed via PXE boot.
2. All systems get initial activation, registrations, and system updates via Ansible.
3. All systems get customized via Ansible playbooks and Chocolatey.
4. When it becomes useful, we roll our own Chocolatey packages and either submit them to the public repository, or set up our own repository.

1. Boot from the network (on the lab machines, press F8). The computer will boot into Windows PE.
2. In the command prompt, type ipconfig /renew, then Enter. This will refresh the DNS and NetBIOS leases.
3. Connect to the network drive by typing net use \\truenas01\installers
4. Begin the install process as follows:

   For an unattended install:

   \\truenas01\installers\Win10\setup.exe /unattend:\\truenas01\installers\Win10\Autounattend.xml

   For normal install:

   \\truenas01\installers\Win10\setup.exe

5. Let the Windows install complete, then log in as BMS Administrator (creds in BitWarden).
6. In Windows Explorer, connect to \\truenas01\installers, then copy ConfigureRemotingForAnsible.ps1 to the target machine.
7. Open a Powershell session using 'Run as Administrator.' Change the execution policy by typing Set-ExecutionPolicy -Scope Process Unrestricted, then run ConfigureRemotingForAnsible.ps1.
8. Once the script completes, get the machine's IP address by typing ipconfig.

Once you have the machine's IP address, you can configure the ansible inventory and run the rest of the configuration playbook against the target.

If you run into:

System Error 67 has occurred.
The network name cannot be found.

It's potentially because you included a trailing slash, and NetBIOS doesn't like that.