rjarrett
Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline
|
I have seen many posts in TechNet and here about PXE imaging. One of the symptoms that seems to be inexplicable is that the client will boot into PXE, get its DHCP settings, contact the PXE server, pull the WinPE boot, boot into the SCCM splash screen and then reboot after ~3 minutes. No explanation given.
This may be arising from a whole host of reasons. As an example:
- Ethernet driver is not included in the WinPE boot image.
- Network Access account is not set in the Client Policy.
- DHCP, DNS, or WDS is not configured properly.
- There is no Mandatory advertisement.
- PXE client is not set in the correct boundaries.
- The boot images are not populated on distribution points and SMSIMAGE$.
- etc. etc. etc.
A lot of these problems occur when the client cannot get its network thoughts together. In general, you can enable F8 support on the WinPE boot image and check out IPCONFIG /All and get the details. It is worth checking the X:\Windows\Temp\SMSTSLogs\SMSTS.log for a message like unknown host (gethostbyname failed). This could indicate that it cannot resolve the URL path specified in the Site Systems properties.
If you open the Site Systems properties for your PXE server, you will see a checkbox that is enabled by default. It is the Specifiy a Fully Qualified Domain Name... If the path specified here is not resolvable in your PXE client's F8 command window, then you are dead.
When I deselected this checkbox and booted a fresh PXE client, voila! It worked.
_____________________________
Let me know if this helped...
Rob Jarrett
SMS\VB Development
|
Printable Version
PXE Client Reboots After Booting In WinPE - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread