Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 18, 2018 8:10 AM
Hi everyone,
I have a bit of a weird situation happening after we patched up a Windows 2012R2 SCCM server with the latest windows updates. Basically we had a monthly PXE deployment of a task sequence. It worked as you would expect, it boots in PXE starts installing the OS, reboots and installs programs, reboot and done.
However since the updates, the PXE deployment goes in a loop. It boots in PXE, starts installing the OS, reboots, and instead of starting the OS and installing the programs it PXE boots again and installs the OS again, and round and round we go.
Normally in the Device Collection, once a Task sequence starts, if you right click on the machine and click on Clear Required PXE deployments, you could see the deployment and if you do clear it the PXE will start all over again. However, there is no such PXE required deployment on this machine, it never registers. Its like SCCM is not writting in its database that it deployed a Task sequence on PXE. So at reboot it goes in circles because SCCM hasn't registered the previous pxe deployment.
Any ideas where to look? Cause the only other option i have is to restore from backup and i would rather understand the issue and fix it rather than go back.
Thx in advance.
All replies (15)
Wednesday, April 18, 2018 2:50 PM
Have you reviewed smspxe.log?
Jason | https://home.configmgrftw.com | @jasonsandys
Thursday, April 19, 2018 10:31 AM
Hi,
The logs are clean if errors is what you meant. Everything seems to work fine according to the smspxe.log , however in the background, the machine i deployed it to is not advertised as such. So because of this it keeps looping once its restarted.
Thursday, April 19, 2018 2:27 PM
No, logs are about much more than errors.
> "i deployed it to is not advertised as such"
What does this mean?
Jason | https://home.configmgrftw.com | @jasonsandys
Friday, April 20, 2018 9:27 AM
Well comparing them with an identical task sequence on another site i couldn't spot any differences.
It means the Required PXE deployment isn't being recorded. That's why its looping.
Friday, April 20, 2018 1:29 PM
So is this a down-level site that you are comparing against?
The task sequence itself has nothing to do with this behavior though so whether its identical or not is irrelevant.
Have you tested this on multiple PXE booted systems?
And, smspxe.log is still relevant here as well -- as noted, it's not about errors.
Jason | https://home.configmgrftw.com | @jasonsandys
Saturday, April 21, 2018 1:24 PM
I have no idea what you mean. PXE boot on this server doesn't work for any task sequence, it goes in a loop all the time. Like i already said, the smspxe.log says all is fine.
Saturday, April 21, 2018 8:13 PM
> "the smspxe.log says all is fine."
Logs are not just about checking for errors or lines highlighted in red. You need to read them and understand the complete story that they are telling. You need to look for missing things, unexpected things, things that don't fit, etc.
Also, you said: "Well comparing them with an identical task sequence on another site i couldn't spot any differences."
So, I asked, is the other site a down-level site or is it the same version?
When you said "site", did you actually mean "location"? "Site" has a very specific meaning in the context of ConfigMgr so if you don't mean a ConfigMgr site, you shouldn't use the word site as it will confuse everyone.
Jason | https://home.configmgrftw.com | @jasonsandys
Monday, April 23, 2018 6:48 AM
Same version and like i already said about the smspxe log, THERE IS NOTHING THERE! All looks fine.
Monday, April 23, 2018 2:18 PM
So the log is blank?
Sorry, but your statements are vague and ambiguous and you've provided no technical details here (even though I've attempted to nudge you into doing so multiple times) so there's no way to magically give you an answer.
I've not heard of seen anyone else with this issue but if you feel this a bug, then you should open a support case with Microsoft directly.
Jason | https://home.configmgrftw.com | @jasonsandys
Monday, April 23, 2018 11:00 PM
If you share (on OneDrive) the complete SMSPXE and SMSTS log files, I will take a look at it.
Tuesday, April 24, 2018 6:25 AM
If you share (on OneDrive) the complete SMSPXE and SMSTS log files, I will take a look at it.
Hi, here are the log files.
https://1drv.ms/f/s!Ari5HzO9vJeCkY5o_rAfNGzXkcJ3rg
Tuesday, April 24, 2018 8:08 AM
Can you please share the 'complete' SMSTS log file. It has to be the one from the WinPE boot. The one you shared is a few lines in the ending part of some SMSTS log file in the full OS.
Also, the SMSTS and SMSPXE needs to be the matching logs.
Tuesday, April 24, 2018 9:03 AM
I'm afraid i don't follow. Can you specify the location? Cause if you are talking about the smsts on the machine the task sequence is running on then no can do, boot loop remember? At the loop it formats everything.
Still, i will boot it on PXE then remove the network card so it can't loop. Once it's finished installing i can give you the SMSTS log from there i guess.
here you will find what i believe is the matching ones you requested:
https://1drv.ms/f/s!Ari5HzO9vJeCkY5pZRU-ijRbxQOArw
Wednesday, April 25, 2018 11:43 PM
Thanks for the logs.
Can you please do these few things:
1. Check the "Component Status" of SMS_STATE_SYSTEM and make sure that it is healthy.
2. Check the site's State Message inbox and make sure that there is no backlog.
3. On the MP, check the state message outbox (statemsg.box) and make sure that there is no backlog.
Thursday, April 26, 2018 8:03 AM
SMS_STATE_SYSTEM looks healthy to me.
Not sure what you mean about backlogs however. We only have this Primary sccm server and another distribution point on a different location (that one works).