localzuk Posted July 5, 2013 Posted July 5, 2013 (edited) I am currently setting up/learning SCCM 2012, and I have gone through the various tutorials at Windows-Noob.com. I have an odd issue here - a PC that is in the database, and has a C&B task sequence deployed to it (via a collection which contains only this computer). PXE *was* working recently, but now in the SMSPXE.log file, I am getting the following: D8:D3:85:91:5D:A4, 8C836100-8107-11E1-AE58-D8D385915DA4: device is in the database. SMSPXE 05/07/2013 14:26:32 7816 (0x1E88) Client boot action reply: GUID:5FC33DBC-D989-4D0D-B7B8-145A57A2C65A SMSPXE 05/07/2013 14:26:32 7816 (0x1E88) D8:D3:85:91:5D:A4, 8C836100-8107-11E1-AE58-D8D385915DA4: found optional advertisement 4962000F SMSPXE 05/07/2013 14:26:32 7816 (0x1E88) Client boot action reply: GUID:5FC33DBC-D989-4D0D-B7B8-145A57A2C65A SMSPXE 05/07/2013 14:26:44 7816 (0x1E88) D8:D3:85:91:5D:A4, 8C836100-8107-11E1-AE58-D8D385915DA4: found optional advertisement 4962000F SMSPXE 05/07/2013 14:26:44 7816 (0x1E88) Client boot action reply: GUID:5FC33DBC-D989-4D0D-B7B8-145A57A2C65A SMSPXE 05/07/2013 14:26:56 7816 (0x1E88) D8:D3:85:91:5D:A4, 8C836100-8107-11E1-AE58-D8D385915DA4: found optional advertisement 4962000F SMSPXE 05/07/2013 14:26:56 7816 (0x1E88) Client boot action reply: GUID:5FC33DBC-D989-4D0D-B7B8-145A57A2C65A SMSPXE 05/07/2013 14:27:08 7816 (0x1E88) D8:D3:85:91:5D:A4, 8C836100-8107-11E1-AE58-D8D385915DA4: found optional advertisement 4962000F SMSPXE 05/07/2013 14:27:08 7816 (0x1E88) Basically, after identifying the machine in the database, it then repeatedly says that an optional advertisment is available and the machine doesn't boot. It sits at the PXE boot stage, with the DHCP.... getting longer and longer. It never gives an error. A little background: SCCM was working with PXE but then I had to disable the PXE bit for one reason or another. Re-enabling it didn't work and it took me some effort to get it back working again (ie. WDS wouldn't re-install but it is now installed and running). Edited July 5, 2013 by localzuk 1
localzuk Posted July 8, 2013 Author Posted July 8, 2013 Monday morning bump... Still doing it and I'm at a loss.
FN-GM Posted July 8, 2013 Posted July 8, 2013 Does the machine have a duplicate BIOS GUID or Mac address than another in SCCM? This will help to find a duplicate MAC address - http://www.edugeek.net/forums/o-s-deployment/114622-osd-machine-previously-use.html#post981110
Gatt Posted July 8, 2013 Posted July 8, 2013 Can you PXE boot any machines? are you getting a PXE timeout or other error? If noone can get a PXE address then it could be more PXE/WDS problems If nothing is getting a PXE prompt then PXE/WDS may still be broken - especially if you had issues with WDS.
localzuk Posted July 8, 2013 Author Posted July 8, 2013 It appears not, no device can PXE boot. I also don't get any PXE errors - it just sits saying ...... forever, and the SMSPXE.log says the above constantly.
Gatt Posted July 8, 2013 Posted July 8, 2013 I take it you have the correct options set in DHCP for the Boot Server Host Name and Bootfile Name? In WDS, is the server showing as configured, and set to respond to all clients? I know SCM 2012 should do this, but you may need to give it a slight nudge if it hasnt
localzuk Posted July 8, 2013 Author Posted July 8, 2013 (edited) Yup. It was working previously. Both the DHCP options are where they should be. (I wouldn't get anything in SMSPXE.log if this bit wasn't working I think?) Just had a look in WDS and its set to respond to all... I've now let a machine run at PXE stage, trying to boot for 25 minutes. I have loads of repeats of the above cycle of messages, and a line of dots that now wraps round onto a second line on the PC after DHCP. No error. Just ........ Edited July 8, 2013 by localzuk
localzuk Posted July 8, 2013 Author Posted July 8, 2013 I've now deleted all Boot images, all task sequences, all OS images and installers and am starting the entire lot from scratch. I've removed PXE/WDS rebooted, deleted the RemoteInstall folder and re-enabled PXE. So, we'll see what happens now...
Harshad Posted July 8, 2013 Posted July 8, 2013 I sometimes get an error with my SCCM server where the client does not receive any PXE advertisement. All I do is restart the WDS service and it starts working !!
localzuk Posted July 8, 2013 Author Posted July 8, 2013 It isn't that. I'm a bit beyond a simple reboot.
localzuk Posted July 8, 2013 Author Posted July 8, 2013 Well... now it hasn't populated the SMSBoot folder - all the folders inside are empty, and the distribution of the boot images are stuck 'In Progress'... I think I may just uninstall SCCM completely and start afresh - I've only been using it for WSUS so far!!
Gatt Posted July 8, 2013 Posted July 8, 2013 Urgh I had this - I removed all OS Images from the DPs, removed the DP and PXE role completely, removed WDS and deleted the RemoteInstall Folder - there is also something like an SMSBoot in the %WINDIR%\Temp folder IIRC.. (follow the logs to ensure everythign is deleted & uninstalled) Reboot, reinstall WDS, the DP and the PXE - keeping an eye on logs, etc I did get it to go in eventually without rebuilding SCCM
localzuk Posted July 8, 2013 Author Posted July 8, 2013 I've tried that twice now. No errors in the logs. Nothing in the temp directory related either...
pritchardavid Posted July 9, 2013 Posted July 9, 2013 I cant even get pass that, when I try PXE boot it just to the next device quickly. I do see SMS is looking for policy or something and I do see and request number. Have no idea what to do.
Harshad Posted July 9, 2013 Posted July 9, 2013 (edited) In SCCM database have you tried to right click on the same machine that is not PXE booting and selected "Clear last PXE advertisement"? Edited July 9, 2013 by Harshad
localzuk Posted July 10, 2013 Author Posted July 10, 2013 Well... after all that. Still doesn't work. GAH!!! Same thing happening.
Gatt Posted July 10, 2013 Posted July 10, 2013 Could there be something on your switches blocking PXE?
localzuk Posted July 10, 2013 Author Posted July 10, 2013 (edited) Nope. We don't have any rules on the core - and the client is on the same VLAN as the SCCM server. PXE has to be working - otherwise there'd be nothing appearing in the SMSPXE.log file. I have one last thing I'm going to try - completely redo the VM. I just re-installed SCCM this time, so the next step is wipe the entire thing and start afresh... Edited July 10, 2013 by localzuk
localzuk Posted July 10, 2013 Author Posted July 10, 2013 Wooooooo!!!! Got it working. The change I made - unticked 'Enabled command support', applied, processed, reticked, applied, processed and voila. What a stupid thing. 1
Gatt Posted July 10, 2013 Posted July 10, 2013 Yeah that is a bit odd - F8 support should have nowt to do with PXE booting Guessing that whatever it needs to load wasn't loading properly...
localzuk Posted July 10, 2013 Author Posted July 10, 2013 SCCM - you are a weird beast, placed here to torment us poor techies into madness.
TechMonkey Posted July 10, 2013 Posted July 10, 2013 Glad others are having the same issues. I am finding images or installers are stuck processing and PXE doesn't start from machines. Someone else set it up so I may have to go over the install as I don't appear to have a SMSBOOT folder!
Protocol0 Posted July 2, 2016 Posted July 2, 2016 Localzuk!! THANK YOU!!! I was having the exact issue you were having 3 years ago! reading the thread was really depressing as I thought I too was going to have to reload sccm from scratch... then you posted your fix! and BOOM... Unticking that F8 must do something else with the distro point... i know i updated the boot image a few times before trying your fix. Thank you for posting your solution. All to often folks abandon their threads once they find the fix on their own. ....yes i joined edugeek.net specifically to say thanks! =]
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now