April 17, 2014
Jan 03, 2018 Alas, yes my dear administrators not all task sequence steps were created equal. There are some steps that just love to watch the world burn and Install Software Updates is their king. Don’t just take my word for it either, the users have spoken: Fix the Software Update Task Sequence. It is not by chance that this is currently the second. Alas, yes my dear administrators not all task sequence steps were created equal. There are some steps that just love to watch the world burn and Install Software Updates is their king. Don’t just take my word for it either, the users have spoken: Fix the Software Update Task Sequence. It is not by chance that this is currently the second.
This topic is not new but it has been asked a lot lately on the forums so a post is in order.
Sccm 2012 Install Software Updates Task Sequence Fails
![Sccm task sequence Sccm task sequence](https://i1.wp.com/www.petervanderwoude.nl/wordpress/wp-content/uploads/TS_RunTaskSequence.jpg?ssl=1)
To use the “Install Software updates” step in a Task Sequence to install Software updates requires that the computer that is being deployed/reimaged is a member of one or more collections with the updates that should be installed deployed to it.
There are two options for the “Install Software Updates Step”:
Mandatory Software Updates = This naming is perhaps not really clear as in Configuration Manager 2012 Software Updates are deployed as “Required”. This option will install all updates deployed to the computer as required.
All Software Updates = this option will install all Software Updates that are deployed to the computer as “Available”
What if I am using Unknown Computer support to install my clients? In that scenario you have two options:
- Deploy all the “Software Update Groups” to the “Unknown Computers” collection. This option will require you to deploy all updates multiple times which is not fun.
- Include the two “Unknown Computer”(one for x86 and one for x64) objects in your normal Collection that you use to deploy Software Updates.
This is a much better option which doesn’t require multiple deployments of all Software Update Groups
Also check out this KB article, http://support.microsoft.com/kb/2894518 for an issue with deploying Software Updates during a Task Sequence that requires multiple reboots.
Posted by1 year ago
Archived
I am currently experimenting with installing Windows Updates during OSD with our Task Sequence Media. I have added a script that puts the computer in a collection 'OSDUpdates' which works as intended. I have deployed a bunch of updates to that collection that are definitely applicable to the computer I am deploying.
![Software Software](https://msdnshared.blob.core.windows.net/media/2017/03/030617_2027_BuildingWin9.png)
Finally I have added the step 'Install Software Updates' in the Task Sequence, but nothing happens. Here is what I see in the smsts.log file:
There are two things that stand out to me:
Microsoft graphics app free. 2 minutes to read.In this articleWindows provides APIs and components that support graphics, gaming, and imaging.
Install Task Manager
Error opening registry key HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdate, software update is not properly configured on this client machine
No updates need to be installed on this machine. InstallSWUpdate 29/03/2018 9:54:29 5340 (0x14DC)
I guess this kind of makes sense because when I go look in the OSDUpdates collection I see the computer, but it also says the computer has no SCCM Client installed. So I guess it doesn't know what groups it belongs to, thus doesn't know that there are updates deployed to it?
Here are the steps that I put at the end of my Task Sequence:
- Scan for Updates (Run Command Line: WMIC /namespace:rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000113}” /NOINTERACTIVE)
- Wait for scan to finish (powershell sleep for 30 seconds)
- Install Software Updates (All software updates available for installation) Photoshop cs5 free download tumblr.
- Restart Computer
I repeat these steps three times before the final reboot, but every time the smsts log says the same thing. So what am I missing here? How do you make this work?
21 comments