Problem with SCCM Deployment after Computer boots into WIN PE via PXE-Boot

ACECORP
ACECORP used Ask the Experts™
on
I am having a problem with SCCMs PXE OS Deployment Feature and am hoping someone has seen this problem and can advise me how to go about resolving it.

I am able to PXE-Boot to Windows PE without incident as can be seen below.
<See Uploaded PDF File for Complete Description with Images>

However, about 30 seconds after the preparing network connections message flashes across the WIN PE window, the server reboots and
goes right back to the PXE-Boot screen where the process begins, and starts all over again.

So, I am unable to actually deploy an operating system to this new bare bones server.

This problem happens regardless of whether or not I use a Windows 2003 Server or Windows XP Custom Made Capture Image (image.wim file) , or a Windows 2008 Server, 2008 Server R2, or Windows 7 image.wim file taken directly from the CD (and placed on a file share of course).

The x64 boot image I created has the Network Card and all relevant drivers on it as placed by clicking Add Drivers to Boot Images shown below.
<See Uploaded PDF File for Complete Description with Images>

and then adding those drivers to the PXE-Boot image and then updating the distribution point as shown below.
<See Uploaded PDF File for Complete Description with Images>

The details of the task sequence I created and applied to the Deploy OS collection can be seen below.
<See Uploaded PDF File for Complete Description with Images>

Honestly, everything looks kosher in the task sequence, so I am at a complete loss as to what could be causing the problem.

I am hoping someone has seen this problem and can advise me how to go about resolving it.

OS-DeploymentIssue.pdf
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
Hello,

Here I think we don't have enough information fo find the cause of the issue.
So we need to gather more info in order to debug.

What you can do is:
- In SCCM, when preparing the Boot image package, you can enable "command line support"
- When done, update the Boot image again so the change is reflected
- Once done, when using this boot package, you can now open a command prompt during the initialization by pressing F8
- Then you can have a look in the SMSTS.log located during WinPE boot in X:\Windows\Temp\smstslog\

Here you should find the necessary information about what as failed... Can be the boundaries not defined correctly, advertisement not seen, missing package(s), computer object not present in SCCM database, etc...

Author

Commented:
I took a look at the log file as per your recommendation and found that everything seems to stop once logging is switched from X:\Windows\Temp\SMSTSLOG\smsts.log to X:\SMSTSLOG\smsts.log

There are a few errors in the origional log file (before it switches them to the other path) as shown below, if that is any help.

![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="15:57:18.203+000" date="10-28-2009" component="TSPxe" context="" type="0" thread="576" file="tspxe.cpp:185">
<![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="15:57:18.203+000" date="10-28-2009" component="TSPxe" context="" type="3" thread="576" file="tspxe.cpp:185">
<![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="15:57:18.203+000" date="10-28-2009" component="TSPxe" context="" type="3" thread="576" file="tsmbootstraputil.cpp:1419">
<![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="15:57:18.203+000" date="10-28-2009" component="TSPxe" context="" type="0" thread="576" file="tsmbootstraputil.cpp:1420">
<
Specifically it looks like the main error is "Failed to download pxe variable file".

When I tried to view the new log file (x:\smstslog\smsts.log) that the appears in the last line of the origional log file (x:\windows\temp\smstslog\smsts.log), I keep getting a message that says "the process cannot access the file because it is being used by another process."

Any additional suggestions would be greatly appreciated.


smsts.log

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial