GJHorn,
- vBoot provisioning is performed against a machine that has a functioning OS and a running agent. You cannot boot a machine to the NIC and start a vBoot provisioning process. That is not its purpose. If you boot to NIC you must have a PXE Server running on that subnet or have your DHCP Scope options (or IP Helpers) set for a single PXE.
- Your preferred server does not issue IP Addresses.
- The very first action in a vBoot Provisioning process should be to copy WinPE to that target machine and then issue a reboot command so that it will boot into WinPE. From there, the rest of your provisioning actions will execute in order.
- If you want vBoot as an option in your provisioning solution, your preferred server may serve the WinPE file. If it's not present on the preferred server, then it will pull it from the core or other network resource.
- I'm on a 9.5 box at this moment but here's a screenshot of a vBoot action. You can only issue this command to a machine with a functioning agent and OS. It downloads the WinPE boot file and then reboots the machine into WinPE.
