ACECORP
asked on
Problem with SCCM Deployment after Computer boots into WIN PE via PXE-Boot
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
<![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><ti
<![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="15
<![LOG[HRESULT_FROM_WIN32(
<
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\
Any additional suggestions would be greatly appreciated.
smsts.log