Hi everyone I'm trying to run a OSD at test environment and I seem to be battling. My SCCM Primary servre is an x86 bit.SP2 with R2 and my test machine is also a x86bit this are the Steps i have taken Created a use domain account and configured computer client agent for Network acccess acount installed WDS and not configered installed and configured PXE service point Created Package defination for ConfigMgr Clients Distributed both SCCM Default Boot images(x86 and x64) to PXE Distr point Distributed the OS image to Distr point Created a collection with no membership Created a Computer Assorciation using the Blank Computer Mac address added the Machine to the created Collection Created A tast sequence added the x86 boot image Advertised the Task sequence to the Colcetion Booting the the Bank Computer from the Network it bootup get an IP Address but showing Achitecture bieng x64 Starts windows loading files.... Then it show the SCCM Wall paper after few min the Machine reboots then it givev an abortpxe error. Please help.

usually that indicates that you need to add network drivers to your boot.wim image for the client hardware, however without seeing what your SMSTS.log file says and checking ipconfig it's hard to tell, can you please enable command prompt support in your boot.wim images and check these things ? Troubleshooting PXE and PE problems Troubleshooting with the help of SMSTS.LOG and F8 My step by step SCCM Guides I'm on Twitter > ncbrady

Hi Brady, Am also getting the same error, my client is hosted in ESXi 4.0. What are the network drivers needs to be added for my boot image. Note : I am having this environment in my Lab. Let me know any info is required....? Regards, Ramesh

for vmware try adding VMware Accelerated AMD PCNet Adapter VMware PXI Ethernet Adapter My step by step SCCM Guides I'm on Twitter > ncbrady

Use E1000 network adapter in ESXi´s guests, it emulates Intel Pro 1000 network cards, which are supported in WinPE (boot image). Also, abortpxe usually means that there is no task sequence advertisement for that MAC adress (computer). If you would upgrade your SCCM site to R3, you will get unknown computer support and your life will become much easier :)

Use F8, check if you receive IP adres, open notepad and check if you can see your HD (or use diskpart). If you don't receive IP address try loading network drivers with drvload.exe. For ESX, if the host comes with the VMXNET3 Nic only the driver comes in 2 variations, vmxnetndis5.inf and vmxnetndis6.inf. Probably only one will actually work so test it and only import the right one. Use drvload.exe. For WinPE drivers in general, you can import the one from Dell which contain lots of common WinPE drivers: http://ftp.dell.com/sysman/Dell-WinPE-Drivers-A05.CAB

Use F8, check if you receive IP adres, open notepad and check if you can see your HD (or use diskpart). If you don't receive IP address try loading network drivers with drvload.exe to test. For ESX, if the host comes with the VMXNET3 Nic only the driver comes in 2 variations, vmxnetndis5.inf and vmxnetndis6.inf. Probably only one will actually work so test it and only import the right one. Use drvload.exe to test it first. For WinPE drivers in general, you can import the one from Dell which contain lots of common WinPE drivers: http://ftp.dell.com/sysman/Dell-WinPE-Drivers-A05.CAB