Jump to content

Recommended Posts

Posted

Good morning forum,

 

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!

Posted

Aye, as above, or on the similar lines if you have any custom drivers in your boot you may need to re-add them if it regenerated the image rather than updating it (As in when confmgr auto pulls the ADK over the old ones)

 

Steve

Posted

Sorry to play the dull card.

Not all my devices had a network drivers in SCCM before. By that then I presume I was lucky they were even booting? However at least one of the devices I use does. Are you suggesting I removed the drivers from the boot image and then re-add them. Or do I need to do something else with my boot image? I've already run Update Distribution Point. That was the point in which it stopped working. Also taking into account that these don't have specific Windows 10 drivers I can download.

Posted

Do you mean drivers within your OS build? or for the Boot image?

 

The drivers for the Boot image are just for the PE environment, which as you said often isn't needed, but depends on the hardware. However, sometimes during the updating the Boot image gets deleted/re-made so it'll lose those drivers.

 

If you check your boot image (drivers tab) does it have any drivers currently attached? If so which ones? (Again just the boot image, not the OS)

 

Steve

Posted

There are some network drivers in there. I have since managed to pull the logs. Done it on two devices and they're the error. Attached.

 

2019_06_24 11_46 Office Lens.jpg

Posted
Doesn't get as far as the task sequence. Basically it was running SCCM 1810 with no problems. I updated to 1902 and now I cannot get to my password screen to even pick a task sequence. I set up a VM yesterday afternoon and booted to that. Exact same problem but without the red error entries. And as you say, it looks like it's no longer seeing an HDD...
Posted
I've cleaned out all the drivers from the Boot Image (x64) image and updated the Distribution Point again. Seems to have done the trick. At the very least I can image, although whether they error out is yet to be seen. Step in the right direction at least.
Posted

Have you enabled F8, and checked out the smsts.log in X:\Windows\Temp\SMSTS\SMSTS.log

 

I had to do it yesterday - turned out the machine had a bad bios battery and had wrong time/date info.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...