Windows 7 to 10 upgrade SCCM task sequence has started failing on all upgrades after over 600 successful deployments.

I've been pushing the upgrade from Windows 7 to Windows 10 1607 for a couple of months.  Have done 600+ machines succesfully.
All of a sudden, starting a few weeks ago ALL upgrades are failing and rolling back to Windows 7 with one of the following errors:

The task sequence execution engine failed execution of the task sequence.
The task sequence manager could not successfully complete the execution of the task sequence.

I suspect it's failing at the Intel HD video driver that's incompatible because I have to accept the removal when manually updating.  Before, it would just delete and add the Microsoft generic, and I'd have to load the Win10 Intel Driver later in the task sequence. ...but that's just a guess.

Where should I look and what do I look for?  Why all of a sudden would this stop working?
sy wittnetwork engineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam LeinssServer SpecialistCommented:
Search the C: drive on a failed client for SMSTS.LOG and post it here and we can take a look.
1
McKnifeCommented:
Is this 1607 LTSB? If not, it's time to update your image anyway since 1607 falls out of support (is within the grace period altready), soon.
1
sy wittnetwork engineerAuthor Commented:
Thanks.  The error code is for an incompatible application.  The PC's I'm deploying to are the same as the 600 I've succesfully done.
I've noticed on some of the manual upgrades, I'm getting the Intel driver and now some SCCM endpoint incompatibility issues.

Could one of the SCCM endpoint updates break this?

Thanks for looking.
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Adam LeinssServer SpecialistCommented:
So first off you probably want to edit the LOG file as it has your Windows 10 MAK key...you should really be using KMS and not MAK anyways, but that's not what you asked.

Looking at the log it appears not to be a SCCM issue, but a Windows 10 upgrade blocking issue:

Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online.      

Which if you Google that leads to incompatible software installed.

I would try running setupdiag from https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag and then see if that will pinpoint the program it doesn't like.

Failing that, you can look at the logs manually in C:\$Windows.~BT\Sources\panther.   I believe it will be one of the XML files that should provide the compatibility blocks.
1
sy wittnetwork engineerAuthor Commented:
The log above is for 1709 I did this weekend.

Here's a 1607 log.  They look the same.
0
sy wittnetwork engineerAuthor Commented:
Thanks Adam-

This from the panther folder - It looks like MS endpoint is the issue.

What!!  I've got SCCM endpoint on all of my machines.  Here's the relevant bit:

</DriverPackages><Programs><Program Name="Microsoft Endpoint Protection" Id="" IconId="msmpeng.exe|a54cab5e3b135c46"><CompatibilityInfo BlockingType="Hard" StatusDetail="WarnUpgrade" Message="This app isn’t compatible with Windows 10 and won’t be available after upgrading. For more info or to get an updated version, contact your antivirus provider. After you’ve upgraded your PC, we’ll turn on Windows Defender or a previously installed compatible product to help protect your PC. Select Confirm if you would like to proceed with the Windows 10 upgrade."/><Action Name="Dismiss" Link="wsc:wica:_msmpeng.exe|a54cab5e3b135c46" DisplayStyle="Link" ResolveState="NotRun"/></Program></Programs></CompatReport>
0
Adam LeinssServer SpecialistCommented:
CompatibilityInfo BlockingType="Hard"

Hard block = no go.

You'll need to either remove it or upgrade it during your task sequence.  I have to ask...I see you are uninstalling Total Defense which is another security product.  Is that something you used in the past?  Then I see something called Etrust that is uninstalling?  Your log files aren't getting to the server either as you have a bad username or password:

Unsuccessful in connecting to \\OurSCCMServer\SMS_CC1\TSresults. Invalid username or password.      ConnectNetworkFolder      6/8/2017 10:37:54 AM      5584 (0x15D0)

My recommendation: Remove SCEP in your upgrade TS before the Upgrade Operating System step, under Post-Processing in the upgrade TS: re-install SCEP.  That seems to be the easiest solution.  Of course you should verify that SCEP will work with whatever build of Windows 10 you are deploying.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sy wittnetwork engineerAuthor Commented:
Adam,
Thanks for the bit of housekeeping.  I had an old uninstaller for our old Endpoint solutions.  I just disabled it.

Seems odd that Microsoft Endpoint (SCCM endpoint?) would be incompatible all of a sudden. - once again, I did 600+ until about a month ago, when it started bombing out.
0
Adam LeinssServer SpecialistCommented:
Do the 600+ have SCEP installed?  

Do they all have the same version of SCEP installed?
0
sy wittnetwork engineerAuthor Commented:
They do now, but we get daily updates from Microsoft.  I'm wondering if one of the SCEP updates blew this up, but it seems odd that no one else seems to be having the issue.
0
sy wittnetwork engineerAuthor Commented:
It was a combination of the 1607 version not installing and checking "ignore any dissmissable compatibility messages" with 1709

Thanks Adam and McKnife, you sent me in the right direction
0
sy wittnetwork engineerAuthor Commented:
Thanks Adam and McKnife, you sent me in the right direction.  See last post for details
0
Adam LeinssServer SpecialistCommented:
That's very interesting.  Setup compatibility usually falls into a Warning or a Hard Block.  I would not think that a hard block could be dismissed.
0
sy wittnetwork engineerAuthor Commented:
It would seem not, but when doing a manual install I saw that I could 'OK' the message and continue.

Or.. maybe it was the burnt feather offering I made to the SCCM gods. :)

Thanks again!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.