Hello,

I am currently working with SCCM 2012 R2 (CU3).
So far, the windows updates were not applied to the workstations or servers.
I am trying to bring workstations and servers up to date.
I created multiple update software groups (less than 1000 updates per group) and I am trying to keep it simple :
- 2 ADR (1 for computers, 1 for servers)
- 1 package per year, multi-OS

I deployed the updates to my phase 1 (pilot) and I get a lot of "Failed" status during the installation.
I can't find much information in the logs and I was wondering if there are some known issues about that.
I get the 0x87D00668 (Software update still detected as actionable after being applied) and a lot of 0x80070308.

Since some workstations/servers are way behind in term of updates, should I patch them manually first or SCCM should be able to manage this type of case ?
I was also wondering in which order the updates are applied and if that could cause the issue.

Thanks for reading and for your help.

SCCM should be able to manage fine.

How big is your deployment package? If you have almost 1000 updates in a package, that could be enormous.

For the servers I have 6 update groups :

- 2003 to 2009 
- 2010  
- 2011   
- 2012   
- 2013   
- 2014   
- January 2015 
- February 2015

Each update group contains less than 500 updates.
I deployed all the software update groups to my "phase 1" at the same time.
Should I deploy 2003/2009, then once the deployment finished, apply 2010...In that case, it would take forever to bring the server up to date.

Thanks for your help.

 

You shouldnt have to stagger it like that, but I still am concerned about the size of those deployment packages. What size do they show in the console? If you dont have the 'Size (KB)' column you can right click and add it. The reason I ask is because I had similar issues in my lab at home because I had added all Win7, Office, Server, etc updates into respective packages. I found out some of my packages were 22GB because I didnt filter properly. I ended up adding Required >=1 in my ADR.

This may be caused by the fact the max runtime has been reached for an update. Some updates like Service packs will take longer than others.

See here to increase the run time and see how that goes.

https://technet.microsoft.com/en-us/library/gg712304.aspx#BKMK_SetMaxRunTime

• Proposed as answer by Naked Nuts 21 hours 34 minutes ago

Good point but it impacts random updates...

It might take a long time to identify the updates with the problem and to modify their max run time :(

Thanks.

For the "Computer updates", I don't include Office in the same package and software update group.  I created a specific one for Office.

For my "server updates" packages, they are configured like that :

Thanks.

This may be caused by the fact the max runtime has been reached for an update. Some updates like Service packs will take longer than others.

See here to increase the run time and see how that goes.

https://technet.microsoft.com/en-us/library/gg712304.aspx#BKMK_SetMaxRunTime

• Proposed as answer by Naked Nuts Friday, February 20, 2015 2:40 PM