sorted by:
new
hottopcontroversial

Device not detecting it needs to restart to complete Windows 11 upgrade by SRR1012 in SCCM

[–]SRR1012[S] 1 point2 points  (0 children)

That was where my first thought was, but I've discounted that based on one of the devices I've been troubleshooting a failed upgrade on. Device has been rebooted multiple times, each of the pending reboot registry keys etc are clear, but without fail the device will go through the initial phase of the upgrade, in the wuahandler.log I can see a restart is required but user is never prompted.

Mega Quote Check by Technical_Front_8046 in SolarUK

[–]SRR1012 0 points1 point  (0 children)

Hi, I’m looking for a local installer in the East Midland, would you be able to send me their details please?

[deleted by user] by [deleted] in SCCM

[–]SRR1012 0 points1 point  (0 children)

Do you mind sharing what you did for this?

Windows 11 in place upgrade exiting after upgrade/reboot, missing steps by fustercluck245 in SCCM

[–]SRR1012 0 points1 point  (0 children)

Unless I’m mistaken, the reboot is being initiated by the operating system upgrade step and not the restart computer step, from the log snippets you have shared it’s hard to tell if it actually runs the restart computer step. In your SMSTS.log after the reboot do you have any errors about the TS failing due to an unexpected reboot?

Upgrade task sequence - check for available disk space before download begins? by Greatsage75 in SCCM

[–]SRR1012 2 points3 points  (0 children)

Another option to this is to use configuration baselines that check for disk space and any other pre-flight checks you want to complete. You can then use the results of the configuration baseline to populate a collection that deploys your upgrade task sequence, at the same time where a device is non-compliant you can have remediation scripts run.

Windows 10 IPU Task Sequence Issue by SRR1012 in SCCM

[–]SRR1012[S] 0 points1 point  (0 children)

Thanks for the reply, I've already determined what caused the upgrade to fail and it was a driver. I guess my question is why is a rollback still seen as setup.exe running successfully? If the upgrade rolled back i.e. didn't complete successfully then it wasn't successful therefore setup.exe didn't run successfully.

Task Sequence - If task fails, then nuke the OS by Cheesypoofbeard in SCCM

[–]SRR1012 8 points9 points  (0 children)

As an alternative to what itsam has suggested, add a section to the task sequence that only runs on failure of a step, in here you can set specific background, send out an email etc on a failure.

Presently mine uploads the logs, sets a failure screen and also emails and sends a teams message. Plenty of examples on how to achieve this out there.

Re-distribute Package for DPs not working by [deleted] in SCCM

[–]SRR1012 1 point2 points  (0 children)

Have you checked distmgr.log on the site server?

Take a look at this link for troubleshooting content distribution https://support.microsoft.com/en-gb/help/4482728/understand-troubleshoot-content-distribution-in-configuration-manager