Hi i am trying to pxe boot several different maschines with ConfigMgr. some work each time and some others don't i receive log entries in smspxe.log MAC=00:0C:29:BE:6A2 SMBIOS GUID=803D4D56-1FDE-9BF0-E8F6-10A22DBE6AD2 > Device has been accepted. or MAC=00:0C:29:BE:6A2 SMBIOS GUID=803D4D56-1FDE-9BF0-E8F6-10A22DBE6AD2 > Device has been rejected. several times and it just won't boot. those devices which do not boot now did boot once before... even when they won't boot the record thepxe advertisment in the computer account in ConfigMgr how can i troubleshoot this? thanks in advance

I would create a boot CD, with F8 enabled. Boot the machines that are not working on that and se what errors come up.. If it is no advertisement available, maybe the machines you try to install are obsolete (happens once they have been installed). Then add the machine to your collection by creating a query that will find the non obsolete version and add it to your collection (here I guide I wrote- http://kongkuba1.spaces.live.com/blog/cns!EEFF1607E296E5AB!185.entry ). Looking at your log files my guess is your problem is acutely this... Could also be that you get an error indicating your pc does not exist, properly do to wrong MAC or you need to clear the PXE advertisement.. In any case you can test this on the fly. Just make the change in SCCM and run X:\sms\bin\i386\TSbootshell.exe from the prompt you open with F8 and the Enter password dialog will open again. Michael Petersen

The fact that it is reporting that the client has been rejected it sounds to me like the PXE Service Point is not accepting the connection. Are you running in Mixed or Native mode? Also, check the PXE Service Point role and make sure the PXE SP is set to respond to ALL network interfaces. Good luck

Hi Michael, i created a boot CD and booted the machines which do not pxe boot. they installed just fine. i also checked for obsolete records which were not the cause. i am lost here since some pc's do pxe boot fine also if i install them again and again, others just won't sometimes they say 'Device has been rejected' sometimes they say 'Device has been accepted' but still they hang at 'contacting the server .....' also the some of the virtual vmware machines booted once and then never again. any hints?

Hi MoFF25, i run in mixed mode. the PXE SP is set to answer on ALL interfaces. it is not that it doesn't work at all, just some machines are not booting, the only repead in the smspxe.log that they are MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted. MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted. MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted. any hints?

Hi there.. i got the troublesome machines to boot via pxe now. but only for once. what i did was to remove the pxefilter and the pxe service point. reinstalled both and booted the machines once via pxe which worked as it should. after they finished their installation i - checked for obsolete entries - cleared the last pxe advertisment and tried to boot them via pxe again... and they wont start but they keep tellling me that the device has been accepted [010.049.000.003:4011] Recv From:[010.049.005.031:68] Len:299 246a434smspxe9/11/2008 2:37:43 PM2856 (0x0B28)MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted.smspxe9/11/2008 2:37:43 PM4164 (0x1044)[010.049.000.003:4011] Recv From:[010.049.005.031:68] Len:299 246b4ecsmspxe9/11/2008 2:38:02 PM2856 (0x0B28)MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted.smspxe9/11/2008 2:38:02 PM4164 (0x1044)[010.049.000.003:4011] Recv From:[010.049.005.031:68] Len:299 246c5a4smspxe9/11/2008 2:38:22 PM2856 (0x0B28)MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted.smspxe9/11/2008 2:38:22 PM4164 (0x1044)[010.049.000.003:4011] Recv From:[010.049.005.031:68] Len:299 246d65csmspxe9/11/2008 2:38:42 PM2856 (0x0B28)MAC=00:0C:29:BC:3A:01 SMBIOS GUID=3BC44D56-DA63-C508-A242-D78F0BBC3A01 > Device has been accepted.smspxe9/11/2008 2:38:42 PM4164 (0x1044) other machines which worked repeatedly before still work on pxe boots... i am lost here... how else can i find out the reason for this strange behaviour??? thnaks in advance

I am having the same problem. I have SCCM 2007 R2 setup and thought I had everything working with OSD. I can deploy onmost workstations, but from my HP Servers (Or the 1 I have tried so far) I cannot SMSPXE.log says "The device was rejected." And yes I have it PXE enabled on all interfaces and set to respond to requests as it works for other workstations perfectly fine and they are 64 bit like the server and I have both x64 and 32 bit boot images on DPs.The weird thing I found is if I shutdown the SCCM server while it is waiting to PXE boot, for a split second it starts to load the boot image, but then fails of course once the server finishes shutting down. Any resolution to this yet?

Ok now it is accepted. but still not pxe booting. SMSlogbelow I find the MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF weird and I don't knwo what the SMBIOS GUID of 46746E...... belongs too. The Server I am trying to PXE boot is MAC=00:1A:4B:334:7A SMBIOS GUID=33383134-3431-5532-5837-313130335632 <![LOG[[192.168.149.244:4011] Recv From:[192.168.149.244:9000] Len:274 21c22c8]LOG]!><time="18:29:42.435+420" date="10-21-2008" component="smspxe" context="" type="0" thread="3360" file="smspxe.cpp:663"><![LOG[Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF)]LOG]!><time="18:29:42.435+420" date="10-21-2008" component="smspxe" context="" type="0" thread="3796" file="database.cpp:394"><![LOG[CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0]LOG]!><time="18:29:42.435+420" date="10-21-2008" component="smspxe" context="" type="0" thread="3796" file="database.cpp:444"><![LOG[MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database.]LOG]!><time="18:29:42.435+420" date="10-21-2008" component="smspxe" context="" type="0" thread="3796" file="pxehandler.cpp:349"><![LOG[[192.168.149.244:4011] Recv From:[192.168.149.149:68] Len:299 21c33d8]LOG]!><time="18:29:52.483+420" date="10-21-2008" component="smspxe" context="" type="0" thread="3360" file="smspxe.cpp:663"><![LOG[MAC=00:1A:4B:334:7A SMBIOS GUID=33383134-3431-5532-5837-313130335632 > Device has been accepted.]LOG]!><time="18:29:52.483+420" date="10-21-2008" component="smspxe" context="" type="0" thread="3796" file="pxehandler.cpp:1904">

If you look at rest of the logs, you will find an entry that says why the device was rejected. Normally, it is because there is no advertisement associated with that device, or the advertisement has run before on that device.

following up, was this issue resolved?

Hi . try to restart the WDS service . I found this to be helpful when the computer is being recognized but the pxe image doesn't boot . thanks

Hi. it has not been resolved for me. i still have the problems when pxe-booting VMware ESX or VMWare workstation computers. it works once after reinstalling the pxe-point. after that if i try to reinstall the machine it eiter says in the log that it does accept the device but nothing happensit just hangs on 'contacting server.......' or it rejects the device.... bye

Hi: I've had various issues with a similiar issue. Are you trying to make the pxe boot mandatory? If you are it will create a record in the cache of the WDS server that stores the client's MAC for up to 60 minutes before it clears it. This causes major issues for when you try to boot back to back. Example: You boot Computer "A" withouta pxe advertisement. You try to pxe boot it but if doesn't find an advertisement and continues normally. You advertise a Task Sequence to this computer and try to boot it back up again, the computer is already stored in the cache and WDS will look there, see a record and just say again you don't have an advertisement when you actually do. Another scenario would be in your case you have a mandatory assignment. You boot up the first time it creates a record in the cache as well as a pxe certificate record. You want to give it a new advertisement so you advertise a new Task Sequence or you want to rerun the same one. To do this you must clear both the pxe certificate which you can easily do by right clicking on the computer in SCCM console and say clear pxe advertisement, but you must also clear the WDS cache. The easiest way I found is create a batch file that just stops and starts the services to refresh it. net stop wdsservernet stop ccmexecnet start wdsservernet start ccmexec That is all my batch file has, stops the wds server, stops the ccmexec, starts them both back up. It has worked flawlessly for me. If this doesn't work the only other thing I can think is that you have the task sequence to only rerun on error. If the Task sequence runs fine, it won't run again if you have this set. You would need to set the property to Always Rerun. Let me know if this helps! Good luck!

As a last resort, try deleting the computer object and re-importing it.

Hi, If it is R2 try to run the task sequence against "All Unknow Computers" collections. Leave the MAC and the Guid as it is. Also make the task sequnce compulsary advertisment.

When the problem occurs have we cleared the last PXE advertisement on computer record? That needs to be done to allow the madatory advertisement to rerun. Just right-click on the machine in ConfigMgr and select CLear last PXE advertisement.John | Program Manager | System Center Configuration Manager

I'm having the same issue and have spoken to Microsoft about it but they are unsure of the cause.All signs point to WDS not talking to SCCM properly. A restart of WDS fixes it for me but this is hardly a permanent resolution!

I had a similar issue now and found out that PXE image share was missing required access permissions. Fixing permissions did the job, so I got past "Contacting server..." part

@ cko42 : Regarding your VM machines , if you are using Trend micro AV , continue reading my blog post on http://scug.be/blogs/sccm/archive/2009/06/30/sccm-2007-pxe-boot-with-vmware-workstation-and-trend-micro-av-not-working.aspxThe Trend micro firewall driver could cause some issues over here !KennyHope it helps , Kenny Buntinx www.scug.be/blogs/sccm/

here's my take on the same issue Contacting Server (xxx.xxx.xxx.xxx) ..... the dots go on for ever and your SMSPXE.log will say things like Device has been accepted but nothing else to give you a clue as to what is actually wrong, the solution in my case was to reset the PASSWORD in AD users and computers for the user i specified in the MDT VBS filter (SMSinstall)My SCCM Guides http://www.windows-noob.com/forums/index.php?showforum=44

Late but hopefully helpfulI faced the same issue, but an inspection of the SMS_PXE_SERVICE_POINT component log revealed the following: The SMS PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device. I had mistakenly deleted all my x64 boot images, so adding a new one resolved the issue.-Sindre

I have to agree. I have the exact same problem with the exact same solution. Restarting WDS fixes it every time. I also agree restarting the WDS service every time you want to image a PC isn't a permanent resolution. Why Microsoft insists on having two duplicate services is beyond me. SCCM shouldn't need to depend on WDS to work. Just bundle the WDS service in with SCCM. I know this hurts the marketing ploy of offering something that partially works for free (WDS) so you'll buy SCCM which is supposed to do it all, but sometimes you (Microsoft) just needs to design something that WORKS!

Late but hopefully helpful I faced the same issue, but an inspection of the SMS_PXE_SERVICE_POINT component log revealed the following: The SMS PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device. I had mistakenly deleted all my x64 boot images, so adding a new one resolved the issue. -Sindre Hi, I had the exact same issue. A fresh install of SCCM 2007 R2 and a VMWare workstation that was not willing to boot. The smspxe.log kept saying device accepted but didn't start to download the boot image. I also reviewed the logs for the SMS PXE Service Point component and saw the same message as Sindres posted here above. I had only deployed the 32bit boot image to my pxe distr. point as I'm going to deploy Win 7 32bit. Apparently it also needs the 64 bit bootimage. Once I deployed it as well, it immediately kicked of the download for the boot image. Many thanks Sindres! Kind regards, Filip