When booting into WinPE automation it is found that the automation agent is not gathering primary lookup key data. (MAC address, UUID, SN, Asset Tag) This causes managed machines to not perform the work that has been scheduled for it. It will also cause new machines to not appear in the console at all. The automation agent will look like it is connected but it won't be found in the console.
Currently this is seen on all versions of GSS 3.x
You won't see an error message during the boot process. The client machine will not do the work that has been scheduled for it or it won't appear in the console (if it is a new machine).
There are currently two possible causes for this.
The boot option was built from a remote console. When building a thumb drive or a DVD .iso file from a remote GSS console you're also calling Boot Disk Creator remotely. When gathering inventory the automation agent makes WMI calls. To make these WMI calls there needs to be specific .cab files added to the boot.wim file when creating your boot option. When creating this boot option from a remote console Boot Disk Creator is unable to locate the needed .cab files to add them to the boot.wim file.
Currently, the BDC will cache certain files to assist with building the boot option quicker. These files are stored under a folder called cache in both the x86 and x64 folders.