I am not certain where the problem is so I am listing the actions in segments:
1. BOOT PC & select Network Boot
2. PC gets an IP address and starts the PXE Boot process.
3. Boot.sdi flys by loading (usually you cannot see it, but on a slow link you can)
4. Boot.wim / Boot_x64.wim starts loading (on a 1gb link to the PXE Server on the same subnet this takes us about 12 - 18 seconds)
5. PE Load screen begins to spin (blue window and rotating marbles)
6. PE loads and OS Provisioning starts
I am guessing your issue is with step 4.
We had problems with this being slow and even timing out before the PC could load the PE (Boot.wim). Not any longer. We placed the PXE server on the same subnet as the devices being imaged. added 1GB connectivity. Problem solved. Also
- I discovered that the PXE Rep Deployment script from 9.5 SP2 does not work in 9.6 (Duh - Right? We didnt't realize we were using that.
- Make certain that the VB Script for the PXE deployment (now found in SD - under all packages) points to OSDREP.vbs in Program Files\LANDesk\ManagementSuite\landesk\files
- We did not have the PXE Reps loaded quite right - I had to actually remove the reps using the 9.6 SP2 script for removal and then re-push the PXE Reps on some units
- We have PXE Reps at remote sites also