Hi, Im trying to deploy Windows XP SP2 to a virtual machine (VPC 2007) using PXE method. These are the steps I followed Im running Windows 2003 SP2 on SMS server 1.Installed WDS (did not do any configurations in WDS) added PXE service point role 2.Created an OS Image Package and copied it to PXE distribution point 3.Copied both boot images (x64 and x86) to the PXE distribution point 4.Created a computer association and added it to a new collection 5. Created a Task Sequence to run the OS image package 6. Created an advertisement targeting the new collection Then I configured the virtual pc to boot from PXE. This is what I get on the screen Argon PXE Boot Agent v2.00 (BIOS Integrated)(c) Copyright 2004 Argon technology CorporationAll rights reserved. www.ArgonTechnology.com CLIENT MAC ADDR: 00 03 FF 6C CA 2D GUID: 2EA3A1C4-2CBA-5D42-8B8C-B578EC342126CLIENT IP: 10.24.4.157 MASK: 255.255.255.0 DHCP IP: 10.24.4.152GATEWAY IP: 10.24.4.1 Downloaded WDSNBP... Architecture: x86 The details given below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administyrator so that this request can be approved. Pending Request ID: 5 Contacting Server: 10.24.4.246............................................................................................................................................................................................................................................................TFTP Download: smsboot\x86\abortpxe.com PXE Boot aborted. Booting to next device... 10.24.4.246 is the ip address of the SCCM server. It stays for about 1 hour and 30 minutes displaying " Contactig Server..." and finally abort the process. If some one can let me know whats wrong, its much appreciated. Are there any specific logs related to PXE which I can refer to troubleshoot this issue? Thanks Lakmal

You need to look at the SMSPXE.log file to see why the client was not handed the boot program.

The UI you provided indicates that the default BINL provider in WDS got run. This indicates that the ConfigMgr provider, which should run first, either did not run first, or if it did run, it indicated that ConfigMgr was not managing this computer. In the steps you listed, you did not say that you used Import Computer Information to produce a computer record for the virtual machine guest before you PXE booted it. Also, your step #4 says that you created a computer association, which is only used for saving/restoring user state, and doesn't really apply when doing a bare-metal deployment (which is what PXE does).If your step #4 does refer to creating the appropriate computer record, make sure that the MAC address was recorded correctly, as that's what the database lookup is done using (along with the SMBIOS UUID, if present). But if you didn't create the computer record, then that could explain what you saw.

I also got the same error. I checked the smspxe.log file, It said "MAC=00:0C:29:4E:41:01 SMBIOS GUID=31554D56-66FE-EA44-CA0A-D2617B4E4101 > Device has been accepted.smspxe10/29/2007 4:43:09 PM1928 (0x0788)". Nothing else after this line. That's the correct MAC address for my Virtual Machine. Is that any other log file I can check to see why it's not working? I also read it from Microsoft, they said "Q: Is there any WDS configuration required for PXE initiated OS deploys? Ie do I need any boot images on WDS, or are they retrieved right from the PXE service Point (along with everything else advertised)?A: WDS does not need to be configured before installing a PXE service point. After installing WDS and the PXE service point you will need to distribute boot images to the PXE service point distribution point in order for clients to PXE boot. The PXE distribution point should be used only for PXE boot images, and no other packages." http://www.microsoft.com/technet/community/chats/trans/sms/07_0710_tn_sccm.mspx I am not sure how this done. Is it add the boot image under "Operating System Deployement\BootImages" in sccm, or manually copy the boot image to SMSIMAGES$? I did both of them, but still getting the same error. "Pending Request ID: " That will be great if anyone can help me. Thanks in advance.

Hi Keith, I was getting the same "device has been accepted" entry in my log file every 20 seconds while trying to PXE boot a VMwaremachine. I had already tested a PXE boot on a different platform before this. I noticed that the VM was being detected as x64 architecture and once I'd pushed the x64 boot image to the PXE distribution point I was able to boot the VM no worries. regards Simon

Hi Simon,Thanks for the reply. I added x64 boot image, but still no luck, same message. My VMWare is installed on 32bit OS. Is your VMWare installed on 32bit or 64bit OS?Thanks,Keith

Hi Keith, I'm using VMware Virtual Infrastructure Client and I'm not actually sure what's on the other end , however since the PXE boot message says "Architecture: x64" I assume it must be 64bit, whereas my VMware Workstation (on 32bit XP) comes up as x86 as you would expect. Just to test my theory, I removed the x64 boot image from the PXE distribution point and I was able to replicate the situation. Basically, my client machine which just booted into PXE has the following ---- Downloaded WDSNBP... Architecture: x64 The details below .. blah blah Pending Request ID: 263 Contacting Server: 10.1.1.202........... ---- and a . (dot) is addeded every 20 seconds.. which correleates to the smspxe.log as per below ---after the line ProcessDatabaseReply: Found optional advertisement(s): TOP20001 ..every 20 seconds MAC=<blah> SMBIOS GUID=<blah> > Device has been accepted. --- both the MAC and SMSBIOS GUID correleate with the client in the SMS Database. And then the *INSTANT* I added the x64 boot image back to the SMSPXEIMAGES$ distribution point the client changes to "Press F12 for network service boot" and the smspxe.log says "Foud new image SMSPKG\TOP00002" Hope that makes some sense. regards, Simon

Hi Simon, Thanks again. I found something not sure it's relate to this or not. The MAC address on boot screen and smspxe.logare the same, but GUIDare different. The GUID show up in boot screen is GUID=564D5531-FE66-44EA-CA0A-D2617B4E4101 The GUID show up in smspxe.logis GUID=31554D56-66FE-EA44-CA0A-D2617B4E4101 There are not totally different, only change the order. When you boot it up from PXE, are you getting the same GUID or different GUID? Thanks, Keith

Hi Keith, I'm getting the same GUID, you might want to remove the existing computer record from the SMS database and create a new one with the MAC address only. It's funny how the GUID's not totally different, as that's the same thing that Windows Installer does for it's component references. regards, Simon

Hi, I was able to resolve my issue by configuring WDS to respond to known and unknown clients. I didnt see this on technet but it worked or me. Regards, Lakmal

Yes, all is true. Still it is necessary to clean a tick in parameter " For unknown clients, to notify theadministratorand torespond for approval " in Boot, properties of a WDS server Regards, Tirex

I know this has been answered but I had the same issue except I did everything said here and I needed to take one more action that I'd like everyone to know. I had to "Cleat last PXE Advert" and it all started working.

check you smspxe.log in SMS_CCM\logs for errors. potential issues: a) not all flavor images are deployed (x86 & x64) b) errors while extracting files from the boot images into a temporary folder. remove temporary folder if this is the case. c) is the\RemoteInstall\SMSBoot\x86 directory empty ? also there might be status messages on your site server regarding this issue. check this too. if nothing works, send portion of the smspxe.log with errors. Marios

Can you elaborate on your comments? "And then the *INSTANT* I added the x64 boot image back to the SMSPXEIMAGES$ distribution point the client changes to "Press F12 for network service boot" and the smspxe.log says "Foud new image SMSPKG\TOP00002" I have both my x64 and x86 boot images already deployed. I get the same "device has been accepted" messages in the SMSPXE.log, but nothing comes of it. I am also seeing consistent MAC addresses and inconsistent GUID identifiers.

You are having the same problem I am having... "The details given below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administyrator so that this request can be approved." Roger Truss posted the output of what a successful PXE boot looks like. It is always good to knowwhat "right" looks like.Anyway, it triggered an understanding of what is going on with my PXE clients.Specifically, it states "...Please provide these details to your Windows Deployment Services Administrator so that this request can be approved." Duh! I cannot believe I missed this. The install is pending approval. So, it sits there waiting, waiting, waiting...Somehow, I have to approve it. Either real-time or by some form of preset configuration. There is a "Pending" queue in WDS, but so far nothing has shown up even though the clients are actively waiting. So, the question remains: Q1. How dowe "approve" a PXE client requestwithout configuring WDS? Q2. Howcanwe make SCCM "automatically approved" requestswithout configuring WDS? Roger Truss' Post Contacting Server (xxx.xxx.xxx.xxx) Architecture: x64 TFTP download SMSBoot\x64\pxeboot.com Then theWDS server gives me 5 options when I boot an x64 system (The first 4 I created using the WDS console): Image Deploy (x86) ImageCapture (x86) Image Deploy (x64) ImageCapture (x64) Remote Installation Services http://www.myitforum.com/forums/m_173000/mpage_1/key_/tm.htm#173000

I don't actually think you have any problem. You have succesfully PXE booted, and you are prompted to press F12. If you press F12, the process will continue normally. You are prompted for F12 because you have an optional advertisement. If you don't want the F12 prompt, you need to create a mandatory advertisement (add a schedule to the advertisement). Also, if you fail the mandatory advertisement, in order you want to rerun it, you need to "clear PXE advertisment" on the corresponding device / collection. now regarding the comment about the message above about approval: "The details given below show ....so that this request can be approved." you can disregard this message when using PXE with SCCM. This is an aftereffect of using the same binaries for PXE booting as with WDS. When using PXE with SCCM, you don't have to approve anything. hope all this helps Marios

I have tried both mandatory and optional advertisements. In the case of a mandatory "Run As Soon As Possible" advertisement, it simply sits there with the "Contacting Server: 192.168.1.50.............." The SMSPXE.log shows the "Device has been accepted" each time a new period is added. Nothing happens. In fact, the only time I ever got the F12 prompt was when I configured WDS standalone, using the boot and image files that I have been trying to deploy with SCCM\WDS. When I hit F12, it aborted and went to the O/S on the C:\ drive. From a previous post, my questions remain: Q1. How do I "approve" a PXE client requestwithout configuring WDS? I install WDS,assign the PXE role, and deploy the boot imageswithout configuring WDS. Q2. Howcan I make SCCM "automatically approved" requestswithout configuring WDS? I have configured a "Lifecycle" collection and added my new PXE client, by MAC address, to it. The Task Sequence that uses my x86 boot image and installs my reference image is advertised to Lifecycle. The advertisement is set to "Run ASAP"

As a troubleshooting/learning initiative, I did the following: Removed PXE role from site server. Uninstalled WDS and rebooted. Deleted the residual D:\RemoteInstall folder. Installed WDS on the site server. I then decided to try and make WDS work, without any SCCM involvement, in order to confirm that my boot and image files could actually image a machine. Then, if that works, I will add SCCM into the mix and try to do it through SCCM\WDS. So, I configured WDS: Set the server to respond to all clients, but require approval for all unknown clients. Imported my x86 boot image. Imported my x86 reference O/S image. When I boot the PXE client, it proceeds to the "F12"prompt and waits. Then: I check the Pending Devices queue in WDS and the new PXE client is present. I approve the new client. A new AD account is created for the new client w/correct MAC address. The client immediately skips to the O/S on the C:\ drive and boots normally. So, using WDS, I am getting all the way through the approval and machine account creation process, only to skip the actual WinPE boot and image install.

I created a new VM (i.e. new MAC address)and picked upwith the client booting. Then: I check the Pending Devices queue in WDS and the new PXE client is present. I approve the new client. A new AD account is created for the new client w/correct MAC address. The client prompts for an F12 network boot. The WinPE boot image loads on the client The reference image never installs. There was no other prompting for an image, it just booted into the WinPE and sits there. The IPCONFIG shows a good IP address. Everything looks great. It just does nothing. Is there a log file or something to tell if it is failing?

you are not giving us enough info to diagnose your problem. please install PXE again, deploya x86 & x64 boot image to the PXE server, add your device to a collection, advertise a task sequence to this collection and PXE boot your device. check the smspxe.log for errors (even from the start of the file), not just the end. is the remoteInstall\smsboot directory populated with files ? are there any status messages on the site corresponding to your PXE server ? thanks Marios

I have done all the same things in this thread as everyone else. Here is a summary of what I did originally: Installed WDS (did not do any configurations in WDS) added PXE service point role Created an OS Image Package and copied it to PXE distribution point Copied both boot images (x64 and x86) to the PXE distribution point Created a computer association and added it to a new collection Created a Task Sequence to run the OS image package Created an advertisement targeting the new collection To your comments: please install PXE again, I have uninstalled/reinstalled PXE and WDS numerous times during this troubleshooting. deploya x86 & x64 boot image to the PXE server, the boot images are on the "normal" and "SMSPXEIMAGES$" DP. add your device to a collection, I created a collection called Lifecycle and imported the PXE client computer account. advertise a task sequence to this collection I created a task sequence with my proven reference image and advertised it. and PXE boot your device. I got the same boot sequence as others in this thread, hanging at "Contacting Server...." check the smspxe.log for errors (even from the start of the file), not just the end. There are no apparent errors. The is the remoteInstall\smsboot directory populated with files ? The x86 and x64 folders are populated with ~6 files. are there any status messages on the site corresponding to your PXE server ? No. Troubleshooting: The crux seems to be that it sits there at the "Contacting Server...." and waits. It acts like it needs approval, even though the computer is in the Lifecycle collection. So, I thought I would try a simple WDS deployment first. Prove the concept and verify that the image files work. Then, if I got that working, perhaps it would lead to some new information. As a troubleshooting/learning initiative, I did the following: Removed PXE role from site server. Uninstalled WDS and rebooted. Deleted the residual D:\RemoteInstall folder. Installed WDS on the site server. I did NOT install the PXE roll on any site server yet. I will test WDS only and if that works, I will add SCCM into the mix and try to do it through SCCM\WDS. So, I configured WDS: Set the server to respond to all clients, but require approval for all unknown clients. Imported my x86 boot image and the SCCM default x86 boot image. Imported my x86 reference O/S image and a second x86 reference image. When I boot the PXE client, it proceeds to the "F12"prompt and waits. Then: I check the Pending Devices queue in WDS and the new PXE client is present. I approve the new client. A new AD account is created for the new client w/correct MAC address. The client prompts for an F12 network boot and a boot image selection menu appears. The WinPE boot image loads on the client and lauches, but the reference image never installs. The IPCONFIG shows a good IP address. Everything looks great. It just does not install the reference image. Is there a log file or something to tell if it is failing?

Hi PXE Guy, I am also having similar problems. I had an SCCM 2007 setup to experiment with last week, I added 5 clients, at some point I tried hitting F12 on a PC (cant guarantee it was one of the clients) and was pleasantly surprised to see it PXE boot into a Vista screen saying "No OS image found" or something like that. I hadnt, as far as I can recall setup anything for the PXE to work but a colleague of mine had previously used the server to test stuff with so he may well have hadPXE server running somewhere After a week of expreiments and being finally allowed to extend our AD schema I thought I would unistall and reinstall the SCCM system again to start with a clean setup. I have installed (manually) a reference Pc, created a capture CD and made a WIM file. I imported this file into SCCM and copied it to both my main DP and the PXE DP I added a Broadcom network driver to the X86 boot image and sent that to the 2 DPs I created a basic task sequence to install this image. This has the following steps Restart in PE, partition disk, apply OS, apply Windows settings, apply network settings, apply device drivers, setup up OS and config mgr. I got another PC out, imported its MAC address and added it to a collection. Then I created a new advertisment for that collection to run my task sequence. I boot my PC, hit F12 and get this after the PXE startup with the DHCP etc. Downloaded WDSNBP... Architecture: x86 The details given below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID: 25 Contacting Server: 172.17.101.230 TFTP Download: smsboot\x86\pxeboot.com Press F12 for betwork service boot I hit F12 and get PXE-MOF: Exiting HP PXE ROM. Then it drops back into booting from the hard drive. I had previously spent all afternoon before I found out that I needed to import the client via its MAC address into SCCM. I feel I must be very nearly there, can you help. Andy PS Some idiot proof walkthroughs of all these tasks would help. The web casts are great but the speakers do tend to skip over the easy (in their mind) stuff and then talk for ages about additional features which are no use to me yet.

After reading more stuff on these pages I have installed the SMS toolit and used the trace to watch ther smspxe log. When I pxe booted my client again this went up the screen [172.017.010.045:67] Recv From:[000.000.000.000:68] Len:548 21c1834smspxe19/03/2008 17:17:393960 (0x0F78)Executing LookupDevice(9E6BA37A-C9C9-11D7-BBD8-CDB6F36C000B, 00:0B:CD:B6:F3:6C)smspxe19/03/2008 17:17:393984 (0x0F90)CDatabaseProxy :: LookupDevice succeeded: 0 0 683 1smspxe19/03/2008 17:17:393984 (0x0F90)MAC=00:0B:CD:B6:F3:6C SMBIOS GUID=9E6BA37A-C9C9-11D7-BBD8-CDB6F36C000B > Device found in the database. MacCount=1 GuidCount=0smspxe19/03/2008 17:17:393984 (0x0F90)[172.017.010.045:67] Recv From:[000.000.000.000:68] Len:548 79985csmspxe19/03/2008 17:17:473960 (0x0F78)Ignoring req from [000.000.000.000:68] Dest Server:[172.017.010.002]smspxe19/03/2008 17:17:473960 (0x0F78)[172.017.010.045:4011] Recv From:[172.017.102.211:68] Len:548 23c4744smspxe19/03/2008 17:17:473960 (0x0F78)[172.017.010.045:4011] Recv From:[172.017.102.211:68] Len:299 23c57fcsmspxe19/03/2008 17:17:473960 (0x0F78)Executing GetBootAction(683, APP-BRI99)smspxe19/03/2008 17:17:473984 (0x0F90)vLastPXEAdvertisementID is NULLsmspxe19/03/2008 17:17:473984 (0x0F90)vLastPXEAdvertisementTime is NULLsmspxe19/03/2008 17:17:473984 (0x0F90)GetBootAction: MAC:00:0B:CD:B6:F3:6C SMBIOS: SMSID:GUID:6AF4684A-C124-4BAC-8260-50422B564C7C LastAdv:smspxe19/03/2008 17:17:473984 (0x0F90)Advertisement results: OfferId:BRI20000 OfferTime:19/03/2008 16:22:00 PackageID:BRI00005 BootImageID:BRI00001 PackageVer: PackagePath:\\APP-BRI99\SMSPKGC$\BRI00001\ Mandatory:0smspxe19/03/2008 17:17:473984 (0x0F90)Advertisement results: OfferId:BRI20000 OfferTime:19/03/2008 16:22:00 PackageID:BRI00005 BootImageID:BRI00001 PackageVer: PackagePath:\\APP-BRI99\SMSPXEIMAGES$\SMSPKG\BRI00001\ Mandatory:0smspxe19/03/2008 17:17:473984 (0x0F90)ProcessDatabaseReply: Found optional advertisement(s): BRI20000smspxe19/03/2008 17:17:473984 (0x0F90)Mutex was not owned. Now have ownership.smspxe19/03/2008 17:17:473984 (0x0F90)Executing PXE_GetSiteTypeAndDefaultMP(BRI)smspxe19/03/2008 17:17:553984 (0x0F90)GetSiteTypeAndDefaultMP: SiteType=2 DefaultMP=app-bri99.tltinternal.com smspxe19/03/2008 17:17:553984 (0x0F90)Executing PXE_GetSiteTypeAndDefaultMP()smspxe19/03/2008 17:17:553984 (0x0F90)No Default MP found for smspxe19/03/2008 17:17:553984 (0x0F90)Executing PXE_GetMpCertificates(BRI,app-bri99.tltinternal.com)smspxe19/03/2008 17:17:553984 (0x0F90)GetMpCertificates: Certificates:308201DA30820147A0030201020210413146307A9561A64572480537B60466300906052B0E03021D0500302231123010060355040313094150502D4252493939310C300A06035504031303534D533020170D3038303331313132353930325A180F32313038303231363132353930325A302231123010060355040313094150502D4252493939310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100AF0224E35D8C16B1344B2330F4DB7BA7A9C27BD76C8F007641F60B0C44662F5F4AAF58E71D6D2FEE29F6E5BDF71FBCACD4E3EF1DBD94ABC4D9F6019504B95528B41135F6E79B430A0AB9C64B68B218BEF35CF86EDC1E5E66EE736FE14B80F15F9934627CBDC0AE0D776CDEEAC79F4BC8228EB6FDD8973BB6258159AC8DCEBB890203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D0500038181008C52F23361050C00E05EF81A57A20454583C25FCCAFE36F7E92B700912A22618CEF04DF802C426F694A188A8652DD3351795250CBF3130277812DB86CBAE622D2D39BC1B8E6B7835C60446A633D9E28B325E3CDC390F3697EA9B5F9BCD6AC46DB1733517AF7184E32B87199826F6717C4441420BFD2B741350C5BCDBE58F7FF7 smspxe19/03/2008 17:17:553984 (0x0F90)Loaded PXE settings from DB: Default MP: app-bri99.tltinternal.com, Public Certificates: 308201DA30820147A0030201020210413146307A9561A64572480537B60466300906052B0E03021D0500302231123010060355040313094150502D4252493939310C300A06035504031303534D533020170D3038303331313132353930325A180F32313038303231363132353930325A302231123010060355040313094150502D4252493939310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100AF0224E35D8C16B1344B2330F4DB7BA7A9C27BD76C8F007641F60B0C44662F5F4AAF58E71D6D2FEE29F6E5BDF71FBCACD4E3EF1DBD94ABC4D9F6019504B95528B41135F6E79B430A0AB9C64B68B218BEF35CF86EDC1E5E66EE736FE14B80F15F9934627CBDC0AE0D776CDEEAC79F4BC8228EB6FDD8973BB6258159AC8DCEBB890203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D0500038181008C52F23361050C00E05EF81A57A20454583C25FCCAFE36F7E92B700912A22618CEF04DF802C426F694A188A8652DD3351795250CBF3130277812DB86CBAE622D2D39BC1B8E6B7835C60446A633D9E28B325E3CDC390F3697EA9B5F9BCD6AC46DB1733517AF7184E32B87199826F6717C4441420BFD2B741350C5BCDBE58F7FF7smspxe19/03/2008 17:17:553984 (0x0F90)WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode.smspxe19/03/2008 17:17:553984 (0x0F90)WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode.smspxe19/03/2008 17:17:553984 (0x0F90)WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode.smspxe19/03/2008 17:17:553984 (0x0F90)WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode.smspxe19/03/2008 17:17:553984 (0x0F90)Saving Media Variables to "D:\RemoteInstall\SMSTemp\2008.03.19.17.17.55.0002.{7AEA1930-F402-4E88-96B0-EFCAC5115A3E}.boot.var"smspxe19/03/2008 17:17:553984 (0x0F90)[172.017.010.045:4011] Recv From:[172.017.102.211:68] Len:299 23c68b4smspxe19/03/2008 17:18:073960 (0x0F78)MAC=00:0B:CD:B6:F3:6C SMBIOS GUID=9E6BA37A-C9C9-11D7-BBD8-CDB6F36C000B > Device has been accepted.smspxe19/03/2008 17:18:073984 (0x0F90) Apart from the certificate warnings the highlighted line is the only sign that something is wrong. Its strange that the last log wentry say "device has been accepted" Andy

I found the solution, I deleted the advertisment and re created it but set it as mandatory. PXE boot went straight in and started my task sequence. For the MS guys, the PXE documentatiobn is a little fragmented around the technet site,A nice and clear set of docs on this would be really helpful

I am glad this worked for you. thanks for the suggestions. I will forward these to the documentation team. now regarding the issue above, the F12 has to be pressed within 3 secs. If you don't do this, then it aborts to the hard disk. Using a mandatory advertisement, does not have this user interaction, but cannot only be executed once. If you need to execute a mandatory advertisement again, you need to go the device in the corresponding collection, right click, and select "clear advertisement". Marios

you arenot using the SCCM to boot the device but your device is booted using WDS. with SCCM you don't have to go to AD to approove any device. From what you say, you are doing this, so... if you want to use WDS only (without SCCM) and have issues, please refer to the corresponding forums. the log file is smspxe.log in the sms_ccm\logs directory. if you want to use SCCM, please copy the section from the log that shows an error or the device booting. Marios

I am getting to the point where the WinPE launches and then on the reboot, it does not install the image... Per your suggestion, in another thread, I updatedthe PXE certificate expiration date on the PXE role. The next time a PXE client booted, the log showed no errors and four warnings. Prior to that, it had an error followed by the four warnings. SCCM is installed in Mixed Mode, so these warnings do not appear to apply. They suggest failures might occur if running Native mode. The error that did not reappear was: ERROR: PXE Cert not set. This might cause client failures.smspxe4/1/2008 8:49:58 AM2284 (0x08EC) Ideas? Here is the SMSPXE.log extract starting with the GetBootAction for each PXE client... GetBootAction: MAC:00:50:56:02:F9:54 SMBIOS: SMSID:GUID:96F0B6ED-52B2-4FF5-9D7B-1D427CD4A2B5 LastAdv:smspxe4/1/2008 8:49:56 AM2284 (0x08EC) Advertisement results: OfferId:LBI20000 OfferTime:01/01/2008 15:21:00 PackageID:LBI0000A BootImageID:LBI00007 PackageVer: PackagePath:http://LBI-SCCM-01-1-S/SMS_DP_Distribution$/SMSPKG/LBI00007/ Mandatory:1smspxe4/1/2008 8:49:57 AM2284 (0x08EC) Advertisement results: OfferId:LBI20000 OfferTime:01/01/2008 15:21:00 PackageID:LBI0000A BootImageID:LBI00007 PackageVer: PackagePath:\\LBI-SCCM-01-1-S\DISTRIBUTION$\SMSPKG\LBI00007\ Mandatory:1smspxe4/1/2008 8:49:57 AM2284 (0x08EC) Advertisement results: OfferId:LBI20000 OfferTime:01/01/2008 15:21:00 PackageID:LBI0000A BootImageID:LBI00007 PackageVer: PackagePath:\\LBI-SCCM-01-1-S\SMSPXEIMAGES$\SMSPKG\LBI00007\ Mandatory:1smspxe4/1/2008 8:49:57 AM2284 (0x08EC) ProcessDatabaseReply: Using Advertisement found in DB: LBI20000smspxe4/1/2008 8:49:57 AM2284 (0x08EC) Mutex was not owned. Now have ownership.smspxe4/1/2008 8:49:57 AM2284 (0x08EC) Executing PXE_GetSiteTypeAndDefaultMP(LBI)smspxe4/1/2008 8:49:58 AM2284 (0x08EC) GetSiteTypeAndDefaultMP: SiteType=2 DefaultMP=LBI-SCCM-01-1-S.LBI.NET smspxe4/1/2008 8:49:58 AM2284 (0x08EC) Executing PXE_GetSiteTypeAndDefaultMP()smspxe4/1/2008 8:49:58 AM2284 (0x08EC) No Default MP found for smspxe4/1/2008 8:49:58 AM2284 (0x08EC) Executing PXE_GetMpCertificates(LBI,LBI-SCCM-01-1-S.LBI.NET)smspxe4/1/2008 8:49:58 AM2284 (0x08EC) GetMpCertificates: Certificates:308201E630820153A00302010202105C21A0B82AA82F954EFE0AC6D7702321300906052B0E03021D05003028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D533020170D3038303332383135343535365A180F32313038303330343135343535365A3028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100D2C6AA46F4EC1526EC1FFD5D8B0FC2E91413AC771430668DC11968436442E40F2FEF19DF6A5FB2F82D34BF265B0442D638A19E61163F9C57419E3873BCFC641BE9B934A6EF9FD449CF9FA3244DC277350BF6794FF3FCF09BF61E8A4AD8BB2B0FA209F8710D8DA8C37C93C017E7D4973CA100374476EEEAEF5D06502D9957867D0203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D05000381810094DFB48199D7376E70A4619B5928B92792D15D76B7A3D5CEAC2A2BF90CF775F0385816B032CE18C560BF61DE7D39C533D4B3F90C228A5FDC721127FC15705A1449BA2EF371A60FC52A8190BB4438B865F098861470E8068FA255414B7281FF9D4D3E1A175A4EE79E79CCC79C967169FB936B1CEB4FBBA3C34B50FB6A11CFF3AA smspxe4/1/2008 8:49:58 AM2284 (0x08EC) Loaded PXE settings from DB: Default MP: LBI-SCCM-01-1-S.LBI.NET, Public Certificates: 308201E630820153A00302010202105C21A0B82AA82F954EFE0AC6D7702321300906052B0E03021D05003028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D533020170D3038303332383135343535365A180F32313038303330343135343535365A3028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100D2C6AA46F4EC1526EC1FFD5D8B0FC2E91413AC771430668DC11968436442E40F2FEF19DF6A5FB2F82D34BF265B0442D638A19E61163F9C57419E3873BCFC641BE9B934A6EF9FD449CF9FA3244DC277350BF6794FF3FCF09BF61E8A4AD8BB2B0FA209F8710D8DA8C37C93C017E7D4973CA100374476EEEAEF5D06502D9957867D0203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D05000381810094DFB48199D7376E70A4619B5928B92792D15D76B7A3D5CEAC2A2BF90CF775F0385816B032CE18C560BF61DE7D39C533D4B3F90C228A5FDC721127FC15705A1449BA2EF371A60FC52A8190BB4438B865F098861470E8068FA255414B7281FF9D4D3E1A175A4EE79E79CCC79C967169FB936B1CEB4FBBA3C34B50FB6A11CFF3AAsmspxe4/1/2008 8:49:58 AM2284 (0x08EC) ERROR: PXE Cert not set. This might cause client failures.smspxe4/1/2008 8:49:58 AM2284 (0x08EC) WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode.smspxe4/1/2008 8:49:58 AM2284 (0x08EC) WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode.smspxe4/1/2008 8:49:58 AM2284 (0x08EC) WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode.smspxe4/1/2008 8:49:58 AM2284 (0x08EC) WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode.smspxe4/1/2008 8:49:58 AM2284 (0x08EC) GetBootAction: MAC:00:50:56:02:F9:54 SMBIOS:1CE64D56-11C2-D805-42B1-2E8B81C9E315 SMSID:GUID:96F0B6ED-52B2-4FF5-9D7B-1D427CD4A2B5 LastAdv:smspxe4/1/2008 10:54:10 AM3492 (0x0DA4) Advertisement results: OfferId:LBI20000 OfferTime:01/01/2008 15:21:00 PackageID:LBI0000A BootImageID:LBI00007 PackageVer: PackagePath:http://LBI-SCCM-01-1-S/SMS_DP_Distribution$/SMSPKG/LBI00007/ Mandatory:1smspxe4/1/2008 10:54:10 AM3492 (0x0DA4) Advertisement results: OfferId:LBI20000 OfferTime:01/01/2008 15:21:00 PackageID:LBI0000A BootImageID:LBI00007 PackageVer: PackagePath:\\LBI-SCCM-01-1-S\DISTRIBUTION$\SMSPKG\LBI00007\ Mandatory:1smspxe4/1/2008 10:54:10 AM3492 (0x0DA4) Advertisement results: OfferId:LBI20000 OfferTime:01/01/2008 15:21:00 PackageID:LBI0000A BootImageID:LBI00007 PackageVer: PackagePath:\\LBI-SCCM-01-1-S\SMSPXEIMAGES$\SMSPKG\LBI00007\ Mandatory:1smspxe4/1/2008 10:54:10 AM3492 (0x0DA4) ProcessDatabaseReply: Using Advertisement found in DB: LBI20000smspxe4/1/2008 10:54:10 AM3492 (0x0DA4) Mutex was not owned. Now have ownership.smspxe4/1/2008 10:54:10 AM3492 (0x0DA4) Executing PXE_GetSiteTypeAndDefaultMP(LBI)smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) GetSiteTypeAndDefaultMP: SiteType=2 DefaultMP=LBI-SCCM-01-1-S.LBI.NET smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) Executing PXE_GetSiteTypeAndDefaultMP()smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) No Default MP found for smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) Executing PXE_GetMpCertificates(LBI,LBI-SCCM-01-1-S.LBI.NET)smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) GetMpCertificates: Certificates:308201E630820153A00302010202105C21A0B82AA82F954EFE0AC6D7702321300906052B0E03021D05003028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D533020170D3038303332383135343535365A180F32313038303330343135343535365A3028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100D2C6AA46F4EC1526EC1FFD5D8B0FC2E91413AC771430668DC11968436442E40F2FEF19DF6A5FB2F82D34BF265B0442D638A19E61163F9C57419E3873BCFC641BE9B934A6EF9FD449CF9FA3244DC277350BF6794FF3FCF09BF61E8A4AD8BB2B0FA209F8710D8DA8C37C93C017E7D4973CA100374476EEEAEF5D06502D9957867D0203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D05000381810094DFB48199D7376E70A4619B5928B92792D15D76B7A3D5CEAC2A2BF90CF775F0385816B032CE18C560BF61DE7D39C533D4B3F90C228A5FDC721127FC15705A1449BA2EF371A60FC52A8190BB4438B865F098861470E8068FA255414B7281FF9D4D3E1A175A4EE79E79CCC79C967169FB936B1CEB4FBBA3C34B50FB6A11CFF3AA smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) Loaded PXE settings from DB: Default MP: LBI-SCCM-01-1-S.LBI.NET, Public Certificates: 308201E630820153A00302010202105C21A0B82AA82F954EFE0AC6D7702321300906052B0E03021D05003028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D533020170D3038303332383135343535365A180F32313038303330343135343535365A3028311830160603550403130F4C42492D5343434D2D30312D312D53310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100D2C6AA46F4EC1526EC1FFD5D8B0FC2E91413AC771430668DC11968436442E40F2FEF19DF6A5FB2F82D34BF265B0442D638A19E61163F9C57419E3873BCFC641BE9B934A6EF9FD449CF9FA3244DC277350BF6794FF3FCF09BF61E8A4AD8BB2B0FA209F8710D8DA8C37C93C017E7D4973CA100374476EEEAEF5D06502D9957867D0203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D05000381810094DFB48199D7376E70A4619B5928B92792D15D76B7A3D5CEAC2A2BF90CF775F0385816B032CE18C560BF61DE7D39C533D4B3F90C228A5FDC721127FC15705A1449BA2EF371A60FC52A8190BB4438B865F098861470E8068FA255414B7281FF9D4D3E1A175A4EE79E79CCC79C967169FB936B1CEB4FBBA3C34B50FB6A11CFF3AAsmspxe4/1/2008 10:54:11 AM3492 (0x0DA4) WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode.smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode.smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode.smspxe4/1/2008 10:54:11 AM3492 (0x0DA4) WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode.smspxe4/1/2008 10:54:11 AM3492 (0x0DA4)

HI i have same problem.TFTP downloadmsboot\x86\abortpxe.com PXE Boot aborted. one more thing i choose to install X86 Vista image. but it show architecture X64 after DHCP detected. Kesavan

If your architecture is AMD or 64-bit or dual core (?) it gets interpreted as an x64 structure. As a result, you MUST deploy your x64 boot image to both the SMSIMAGE$ and all normal distribution points. The client will boot using that x64 boot image and then run the 32-bit image installation Task Sequence. Other things that I have found cause aborts are listed below: Network Access Account gets cleared somehow http://www.myitforum.com/forums/Network_Access_Account_Not_Set/m_177370/tm.htm Fully Qualified Domain Name not resolvable by the client. http://www.myitforum.com/forums/m_177318/mpage_1/key_/tm.htm#177318 PXE Cert Not Set due to invalid root CA http://www.myitforum.com/forums/m_177312/mpage_1/key_/tm.htm#177312 These have all caused massive headaches and are easily checked on the server side.

this is P4 3 Ghz only. it keep on going on with ................. Butif i boot from Virtual PC, it detect DHCP and then contacts with server then downloading the file. after that it gets restart and then loading windows PE with SCCM background display. after some minutes it gets again restart. now it says insert boot media. i dont know i take mistake. SMSPXE.log file says rocessDatabaseReply: Device has not executed this advertisement: LastAdvDB:K012000F New:K0120010]LOG]!><time="16:30:11.442+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="pxehandler.cpp:539"><![LOG[Mutex was not owned. Now have ownership.]LOG]!><time="16:30:11.442+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="TSBoot.h:671"><![LOG[Executing PXE_GetSiteTypeAndDefaultMP(K01)]LOG]!><time="16:30:12.734+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="database.cpp:871"><![LOG[GetSiteTypeAndDefaultMP: SiteType=2 DefaultMP=sischnscm07.sis.ad ]LOG]!><time="16:30:12.734+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="database.cpp:918"><![LOG[Executing PXE_GetSiteTypeAndDefaultMP()]LOG]!><time="16:30:12.734+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="database.cpp:871"><![LOG[No Default MP found for ]LOG]!><time="16:30:12.734+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="database.cpp:890"><![LOG[Executing PXE_GetMpCertificates(K01,sischnscm07.sis.ad)]LOG]!><time="16:30:12.734+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="database.cpp:973"><![LOG[GetMpCertificates: Certificates:308201DC30820149A0030201020210E811EB2BEEEB69A4489F03CC72EB2923300906052B0E03021D05003023311330110603550403130A54455354424544303031310C300A06035504031303534D533020170D3038303331393131303631395A180F32313038303232343131303631395A3023311330110603550403130A54455354424544303031310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100A9E10733F50FBE155D5573EA76B169CD2D4228F010925B456E71C8F751475F92CCE2B3C7F02C13A5FCAEFE3449A3F8A14E9A91B889D2D923AC50CDD8152035943F100503F2CA8FEFA9A039537032105FFE2FB66807BF375F2994C080D7F89801F437843EC03200D6E58109B6DD58AC720861E5D8998A9AAFD3A5D19C38DCDCB70203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D0500038181006DF559C3838125DE49515A8B700C6B390C37CC01FEC63D17E598BA3F4B26204959F1EC128B96D315ED87E8B739447326DE2EDC0F1E2FB1989DF620E5057FFFE85D5FAA624FA04A8ABEE1F26464A12FD3EC8D79AC76BC06367B8E5AD1B98FB3B2ED462BB76AEED898EFFDA653F0C1F55A8A6546296FA14424B6F0F4D94CADD96B ]LOG]!><time="16:30:12.764+000" date="04-18-2008" component="smspxe" context="" type="0" thread="2612" file="database.cpp:1029"> kindly reply any one give the step by step guide for deploy Windows XP(begining to end.)

Hey i dont know if you have done this, or if its been said before... But for SCCM to approve the pxe booting, you need to set up a Computer Association... Just like any package, do note that everything in sccm is a package technically, the computer must be in a collection and assigned to the site that is going to laucnh his pxe boot. Therefore you need to use the Computer association node in the sccm console to setup a MAC address association with the name of the computer you want it to be. (bare metal installation) Like that when your computer will boot off pxe, it will connect to the pxe reception server (your sccm pxe role site) and the server will check his MAC address in his collection list to make sure this computer is in the Assigned section of this site and see if their is any task sequences assigned to it. **edit** i just re-read carefullyyour first post, you do say youve created this computer association but it seems that you may have misconfigured this step, otherwise you would not need to get an approval. The approval is checked if the computer is in the collection with the correct mac address information (you do not necessarily need to enter biosguid leave it blank) enter the mac address correctly. Also! it may very be a architecture discovery problem, although you may want to install a x86 version for example, if it discovers another it might not run. Their is a command you need to run, i forget exactly what it is, to configure the architecture discovery method for wds (pxe role) check that out. Good luck! Benjamin Niaulin

You have sent to little of your log. Check earlier in the log for "Network Access Account not set" or something like that. This link covers the most likely causes. http://www.myitforum.com/forums/m_177482/mpage_1/key_/tm.htm#177565 Your certificate is good, so my guess is it isthe Network Access Account in the Client Policy. It is probably missing.

After I booted the PXEClient it will get advertisements offered. But after booted the boot image it won't continue with the OSD install package. In the SMSPXE log I receive the following: ProcessDatabaseReply: Device has not executed this advertisement: LastAdvDB: New:GCA20012 The PXEClient which we are trying to install is a member of a collection which has the advertisement. A Computer association isn't neccasary since we have PXEFilter.vbs up and running(and working) ANyone got an idea?

Have you "Cleared the last PXE advertisement" before reattempting?

I did clear the PXE advertisement before retrying.

Hi, Did u use pxelite (from 1E) ? And witch version of sccm have u?

Thanks for all the usefull information in this thread. especially smspxe.log i had some trouble finding it on my server, i am pretty new to all the sccm stuff.on my server 2008 it was on c:\program files\sms_ccm\logshope this can help someonewhat fixed my issue was clearing the advertisment, and starting with a new one.

Figured it out, - WDS needs to be installed, configured and the boot files pointing to thesamefiles but under SMSBOOT folder.- WDS PXE response settings needs to be set to not respond to client requests and the response delay set to 1sec.- In SCCM set the PXE service pointresponse delay time to 0 secs. This should get your PXE clients booting from SCCM- If the PXEclient is rebooting it probably could be the client cant access the share for the image, set administrator permissions or try everyone (read and write) this was the case for me. Remember to update the distribution point after this- Also my wim file to go down was not right in some way, so was getting a invalid boot manager error on startup. Once I used Win XP files and setup the OS as a OS Install Package it worked fine.

We resolved this issue the easiest/ most brutal way. remove packages from pxe dp, remove pxe role, remove wds. reconfigure pxe serverrole and wds. Another error that just came up is that WDS apparently starts bugging after a while. First off, when server starts, WDS is ALWAYS "stopped"... Second.. sometimes our clients didnt recieve pxe and fortunately all we had to do was restart the WDS. Which at first only took 3-5 seconds.... Now after a few weeks, the WDS takes forever to restart and gives an error. something like "the WDS Service was not started IN A TIMELY FASHION" ?? well son of a beesting, i thought. The WDS looked as if it had started up again normally but our clients got yet another strange error. They got to "TFTP Download: SMSBOOT\x64\pxeboot.n12" and retried for 20min b4 exiting pxe. Hmm very strange, since that never happended before. A closer look at the folder.. apparently WDS had EATEN the files required. all that was left in the SMSBOOT\x64 folder was abortpxe! i copied the files needed from the x86 and now it seems to work as befoer... But damn you, WDS never stops causing trouble. couldnt find a suitable thread for this so i hope atleast the first line helps :)

I would look through the logs for a hint on why it is failing. With SCCM 2012, I think its easiest to find these messages in Monitoring > System Status > Status Message Queries > All Status Messages from a Specific System, and then enter in the name of your site server. In my case the failure to boot PXE was because the PXE service point stated that there was no boot image available for the client processor architecture, which was x64. First, I noticed that the boot image was not distributed to the site server I was testing from, or any site servers for that matter. Next, I noticed that on the properties window for the x64 image, the Data Source tab, that the "Deploy this boot image from the PXE service point" option was not checked. I was able to PXE boot following those changes. P.S. I wouldn't recommend modifying the properties of WDS as SCCM is supposed to manage the WDS settings et cetera.