abortpxe.com becaus of drivers?

[ADB]

Just after the the boot file has been loaded, the customized backgroung image and the TS appears saying "Windows is starting up". After that i can recognize very quickly, that it tries to Set Up Network and then the PXE is aborted.

 

What is the problem?

 

I have added NIC drivers from Intel as suggested on this site and allready postet a question on Anywebs explanation to NIC drivers here

 

Finally my client sais again "Contacting Server <IP> (Gateway 0.0.0.0)" which is not true, it is set to 192.168.200.1 and "Pending Request ID: 30" as well as further down: "TFTP Download: smsboot\x86\abortpxe.com"

 

I receive an IP from the DHCP which is running on another server than the SCCM and WDS. the BootFile is also downloaded. All the needed Folders are Shares. I have added an AutoAplyDrivers AND an ApplyDrivers in the TS which are set to "Install all compatible drivers" as well as "Do unattended installation..."

 

Is it the boot image generated from SCCM? (it is finalized and contains the needed drivers. Not done with DISM but by updating the DP). In the boot imagePackage sequence i also added both, the SMSPXE and the <SERVERName>-Distribution Points.

 

Is it the TS?

 

(PS: I have also CLeared the last PXE Advertisements)

 

Any Ideas? (the smsts.log can't be read cause I'm BUILD-AND-CAPTURING from a BareMetal)

 

cheers A.

[anyweb]

can you try this please http://www.windows-noob.com/forums/index.php?showtopic=669

 

cheers

niall

[ADB]

Hi Niall

 

I deleted my vm and right now I am building a Reference Machine so I can capture it. Due to lack of virtual disk-space on our esx-server, I had to delete it to go ahead.

 

But I allready had gone through these steps of clearing last PXE-Adds and re-creating a new client...

 

Hope it will work for the capture.

 

Is it true that windows 7 machines aren't sysprepped?

 

 

cheers Anna

[anyweb]

windows 7 machine can be sysprepped of course, as sysprep is built into the os now (since vista)

[ADB]

windows 7 machine can be sysprepped of course, as sysprep is built into the os now (since vista)

 

 

so just to get it right: I configure my reference, run the sysprep in shut-down mode and then boot the reference from Network to start the capture Task-Sequence created in SCCM?

[abhi1411]

Hi,

 

Which models are having this issue. in my case it was HP 8300 and 6460b which were giving this error message.