So what I end up doing was this:
1. Set my DHCP Server as "THE" PXE Representative (Removed all other Reps)
2. Ran these 2 commands in the DHCP server
After each commend you should see a "command completed successfully" message or something similar.
netsh dhcp server add optiondef 60 PXEClient String 0 comment=PXE support
netsh dhcp server set optionvalue 60 STRING PXEClient
Then rebottled the bare metal server in PXE (in my server by pressing F12)and voala! it worked.
Answering the 2 questions above:
1. Is this the expected behavior? I thought the concept of using PXE Net Boot was to NOT use the USB (provisioning Boot Media) and that it would get the task from the network.
Yes. When the USB is used, it connects to the Core and runs the scheduled task. The PXE Net Boot (When configured correctly) bypasses the need for the USB, in essence, the PXE is a piece of software needed to initialize the OS or an application, in this case the LANDESK Provisioning Application, which in turn connects to the Core. Since there was a scheduled task, it doesn't needs the credentials, it just runs the task. If there wasn't a task scheduled, the normal logging prompt and selection of template would appear.
2. If the above is not as expected, what do I suppose to see once the system boots from PXE Net Boot? Is a DOS screen so I imagine it will be some kind of task detailing the progress of the capture?
The normal LANDESK Provisioning Windows will appear, just as when using the USB.