ConfigMgr Task sequence fails due to multiple restart updates.

Update*  issue was fixed with SP2/R2 SP1.

A few weeks back I started to build a new build and capture task sequence for a customer and stumbled over this this problem…again. I had a script to look for those nasty updates from Alex Verboon which works fine if you have just a few Software Update Groups but is rather uncomfortable if you have many. There also was a script from the Deployment Guys which works for MDT deployments.

My problem was that I wasted a whole day (TS took 6 hrs to get to the point of failing) figuring out that Microsoft added new updates in its March Patch release and I did not look for those. So I started to write a little Powershell script which looks at the KB article from Microsoft, gets the KB Numbers, pipes them into ConfigMgr and creates (or updates) a Software Update Group so you can easily manage the membership of the updates in other groups.

The Script is pretty simple, feel free to use it and update it as you wish. Just copy it and run it.  .\Create-TSFailUpdatesGroup.ps1 -SiteCode PS1 -SUGName TSFAilUpdates

If you have any remarks, put them in the comments.





Microsoft fixed this issue with the 2012 SP2/R2 SP1 release. You now get the option to retry the Updates in the Install Updates Task Sequence step.


2 thoughts on “ConfigMgr Task sequence fails due to multiple restart updates.

  1. I tried the the “retry this step……” option, but still my TS fails
    When I run the script I get the following 2 errors:

    Method invocation failed because [System.Object[]] does not contain a method named ‘Trim’.
    At D:\PS Script\Create-TSFailUpdatesGroup.ps1:40 char:1
    + $TSFailUpdates = $TSFailUpdates.Trim()
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound

    Update KB numbers
    New-CMSoftwareUpdateGroup : Cannot validate argument on parameter ‘UpdateId’. The argument is null or empty. Provide
    an argument that is not null or empty, and then try the command again.
    At D:\PS Script\Create-TSFailUpdatesGroup.ps1:83 char:56
    + New-CMSoftwareUpdateGroup -Name $SUGName -UpdateId $kbs
    + ~~~~
    + CategoryInfo : InvalidData: (:) [New-CMSoftwareUpdateGroup], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.


Leave a Reply

Your email address will not be published. Required fields are marked *