Jump to content


Sign in to follow this  
T_Lister

Client reboots before the task sequence password

Recommended Posts

First apologies if there is already a thread for this, I have been unable to find one.

I have just upgraded my SCCM to 1902, I have installed the latest ADK, I've installed the latest PE and then I updated my boot image.  What I cannot understand is that when I PXE boot a new client, it almost makes it to the Enter Password and then the client reboots.  I've tried three different models of machine and I get the exact same problem.

Any advise would be most welcome.

Thanks in advance!

Share this post


Link to post
Share on other sites


enable diagnostic support in your boot wim, then press f8 at the pxe password screen, in the cmd prompt use cmtrace x:\windows\temp\smstslog\smsts.log

 

and review the failures in red to see why it's having issues, if you can attach the smsts.log file here that would help or if you cannot, then attach screenshots of the errors highlighted in SMSTS.log

Share this post


Link to post
Share on other sites

it's not enough to go on, please copy the smsts.log file from x to your usb drive and attach it here.

Share this post


Link to post
Share on other sites

it seems like you have PXE booted and SCCM detects three USB drives and no local drive, is that correct, can you tell me a bit more about how you are testing here ? why are you not trying to test this with virtual machines ?

also, if you are indeed testing on real hardware that is not detecting the hdd, then have you added any storage drivers for the chipset to your boot wim ?

cheers

niall

Share this post


Link to post
Share on other sites

Hi Niall,

Haven't used a VM since I set everything up over a year ago to be honest as I've always been able to tweak the image slightly every time I've needed to add something to the task sequence.  These are machines that have always worked, so I just went to run the task sequence again.  I can't even deploy the existing task sequences that I've been using since last year. 

Other than installing 1902, the latest ADK, PE and running Update Distribution Points on the Boot 64 image I haven't changed a thing.  Ulitmately what I'm trying to do is push out Windows 10 1903.  Up until this update I was installing 1803 without issue.  I'll put a VM together now to test it out though.

Share this post


Link to post
Share on other sites

try updating your boot wim(s) to the distribution points again, to make sure they get injected with all the new binaries from the SCCM 1902 upgrade.

Share this post


Link to post
Share on other sites

Once I cleared out all the drivers from Boot Image (x64) it allowed me to boot into SCCM again.  Now I'm back to errors on the task sequence, but at least the devices will image again.  New problem for a new day, but as far as this specific fault goes, it is resolved thank you.

Share this post


Link to post
Share on other sites

ok well you can always post your smsts.log here and we'll advise :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...