sccm task sequence without OS and USB drivers W10

[ADMaster]

Hi all

I have two separate SCCM issues at the moment. I am running the latest 1702 and deploying W10 1703.

 

The first issue, I have an upgrade task sequence that upgrades W8 or an older version of W10 to 1703. After the OS is applied I remove the metro apps and redo the branding.

I had one machine fail the upgrade, it applied the OS but did not run any of the customizations.

I created a task sequence with a reboot step and the customization steps. When the task runs it reboots but does not run the other steps until I log on. The task fails because these scripts need to run with the same privileges they would if it was an OS deployment.

Yes I can simply reimage the machine but I'd like to have a one click fix for when I ask users to upgrade their own machines.

How can I get the TS steps to run after a reboot but before logging in?

 

The second issue is USB drivers this was an issue last year with 1511 and/or 1607 too. Deploying a full OS not upgrade to a laptop works fine, but to a desktop/AIO sometimes the mouse and keyboard to not work. I have found if I remote into the machine and update the usb driver to use the one from Microsoft and not Intel it works.

I disabled the Intel USB drivers in SCCM but this is still happening on 1703. I'd like to find a solution before I image all the labs this summer.

The two machines I tested my image on today were a custom local brand, but if I recall last summer this was an issue on my Lenovo's and HP's. I'll do more testing on Monday.

 

Thank you

[Annabelle]

How do you deploy your drivers?

Do you use the auto apply drivers or do you create driver package for specific computer model and then apply the driver package base on the computer model?

[ADMaster]

I let it auto apply

I imported updated Drivers Friday and one of them was the 1c26 driver so I'll try a reimage Monday without disabling that updated one.

 

I also think I found part of the problem with my TS. One of my steps disables PC reset, since that part did run it erred out. I need to figure out how to check for that and continue.

[Annabelle]

Could there be more than one USB driver and SCCM auto apply driver applies the wrong one?

Have you tried specifying the specific driver package with the correct USB driver?

[ADMaster]

I downloaded an updated driver pack from HP and it worked on the one PC I tested today. I'll have to try it on the other models.

 

I cannot test the rerun task anymore. I found that it was running in the background but failing on various steps. I'm not sure how to recreate the failure that caused the issue in the first place. Also some of my tests were misleading me. I had already logged on and got a new profile while it was in a failed sate. I logged on with a new user and the desktop is as it should be.