Comments on: Windows 10 Servicing Plans and In-Place Upgrades In Microsoft SCCM

By: majid

majid — Wed, 22 Apr 2020 15:01:21 +0000

I set up a 1809 feature update from sccm windows 10 service plan.

All of our machines are 1709 x64. Machine have received the update and apply it but they still are showing in Monitoring -> Deployment -> Deployment Status -> Unknow

Client check passed /Active
Client check passed /inActive
Client check failed /Active

How do I fix this or why are these machine still showing states as unknown.

I can see that sccm had a message back from machine to say that its 1809 now but till the deployment status is showing these machine are not updated.

By: PUNITH G S

PUNITH G S — Thu, 23 Jan 2020 19:24:12 +0000

In reply to ricky.

Hi
Deployed Windows 10 1809 feature update through sccm. But setupact log ends with error

Execute(400):Result = 0x800704C7

Tried disabling antivirus but of no use…

By: Justin Chalfant

Justin Chalfant — Thu, 28 Nov 2019 19:32:19 +0000

In reply to Mohamed Reda. There's really not enough details here to provide any constructive feedback on what's going on here.

By: Mohamed Reda

Mohamed Reda — Wed, 23 Oct 2019 22:11:36 +0000

I have currently setup an 1809 Feature Update From SCCM Windows 10 Servicing

All machines are on Windows 10 1607. However, some of the machines are appearing as in progress and non-compliant.

The feature update is x64 and all OS x64.

Thanks

By: Justin Chalfant

Justin Chalfant — Wed, 17 Jul 2019 10:07:04 +0000

In reply to ricky.

Not a great way I’m aware of. The windows 10 setup will migrate what’s compatible. I know a lot of people say good things about https://www.scconfigmgr.com/modern-driver-management/

By: ricky

ricky — Thu, 11 Jul 2019 20:32:40 +0000

Great Video, How do we manage drivers of different vendors during Upgrade from Win 7 to Win10? I.e I have multiple dell, lenovo, Hp win7 machines and I am planning to upgrade them to Win 10. they all have a diffrent set of drivers, how do I deploy each manufacturer’s drivers with Single task sequence?

By: Benedikt Gunzelmann

Benedikt Gunzelmann — Wed, 20 Mar 2019 21:08:47 +0000

Hello David,

the suspension of Bitlocker during the in-place upgrade does not depend on the task sequence or SCCM functionality but on the actual Windows setup. Therefore it doesn’t matter if you upgrade via Servicing Plan or Task Sequence because both will only call the Windows setup.

For this reason, the behavior should be as you want it to be. 😉

I hope this short answer is enough to answer your question to your satisfaction. 🙂

By: David Zemdegs

David Zemdegs — Mon, 04 Mar 2019 22:54:36 +0000

According to https://docs.microsoft.com/en-us/sccm/osd/deploy-use/create-a-task-sequence-to-upgrade-an-operating-system it says:
“If you’re using BitLocker Disk Encryption, then by default Windows Setup automatically suspends it during upgrade.”
We plan on using the standard upgrade task sequence to upgrade from 1607 and 1703 to 1709. Will this automatically handle bitlocker as stated in the article?

By: Justin Chalfant

Justin Chalfant — Sat, 02 Feb 2019 16:31:50 +0000

In reply to Richa Nema. What's the error in setupact.log?

By: Richa Nema

Richa Nema — Sat, 02 Feb 2019 13:42:43 +0000

Outstanding explanation! Thank you so much for your wonderful information to share with us.

Here, I need your help!
In my environment, I am upgrading windows 10 device version from 1607 to 1709 using SCCM Servicing plan.
We have deployed 12 days before but still, the compliance status is just 18% and most of machines are failing or moving in error state under deployment status.
Kindly suggest resolution.

Thank you!

By: Justin Chalfant

Justin Chalfant — Tue, 31 Jul 2018 13:49:52 +0000

In reply to Nico. Good point, I will add that to the resources. Thanks!

By: Nico

Nico — Tue, 31 Jul 2018 09:22:41 +0000

Hi Justin,

great videos, keep up the good work! 🙂

FYI, you should maybe add SetupDiag. Great little tool to troubleshoot failed Upgrades.
https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

By: Justin Chalfant

Justin Chalfant — Mon, 30 Jul 2018 23:31:20 +0000

In reply to Dean Buen. Good question, it's only supported to use the install.wim from the media. It may technically work if you replace the install.wim in the sources with a custom WIM, but this wouldn't be supported an may not work as intended.

By: Dean Buen

Dean Buen — Mon, 30 Jul 2018 21:06:54 +0000

Great video blog on this. One quick question on using the task sequence upgrade. Can I still use a custom .wim file using the upgrade Windows 10 task sequence or do I have to default .wim file that comes with the v1803 release?

Thanks
Dean