PENDING Upgrade Operating System TS Step - How to access from DP

[m0lochwalker]

SCCM 1906

I have a successful OS Upgrade Task Sequence which upgrades 1703 to 1803.

There are several instances when the TS will fail, however, due to a hash error when downloaded the Upgrade Package content.

I have troubleshot this a lot, and I would like to know if I can just avoid hashing and downloading this content.

This option IS available in the 'Apply Operating System Image' step options (Access content directly from the distribution point), but it is not available in the 'Upgrade Operating System' step.

My question is: If I use the 'Upgrade Operating System' step and choose 'Source path:' instead of 'Upgrade Package:' - does the TS hash and download the content in any way, or does it just run setup from the share? Is this effectively running setup from a share instead of downloading from the DP? And if so, how would I set the language and architecture which are specified in an Upgrade Package, but not when choosing 'Source path:' in the TS step.

At this point I really just want to avoid hashing the content of this package. I cannot remove security agents or install new RAM in every machine that fails the hash check.

Please advise ASAP.

Thank you!!

 

[Sam Banford]

I'm not sure on disabling hash checks but is there a particular reason you're upgrading your Win 10's this way and not just deploying the 1803 feature update to a collection?

 

[m0lochwalker]

I just want to follow up and close this thread.

In an Upgrade Operating System Task Sequence, on the Upgrade the Operating System step, simply using 'Source Path:' and providing a path to Setup.exe, instead of using 'Upgrade Package:', DOES get around this issue with hash checking. I made that change shortly after posting this initial question to the forum, and have not had a hash error, nor an upgrade failure, since.

Thank you