Solved

SCCM 2012 - Package install timeout, rerun?

Posted on 2014-12-10
3
723 Views
Last Modified: 2015-05-29
Hello

I have a deployment to install SP2 for Office 2010.  The deployment has gone out to all our systems.

I initially set a timeout on the deployment to be 60 minutes.  Approx 180 computers have shown as error'd because of this.  How can I force SCCM to install to these computers again?

It doesn't seem to be trying to rerun the package

Thanks
0
Comment
Question by:Wolf
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 23

Expert Comment

by:Nagendra Pratap Singh
ID: 40493107
If it is a package/program mode then this will run it only once. I guess this is the one you have used.

You ay create another deployment and send it out with a larger time frame. Incidentally, SCCM sets 2 hours for each deployment and Service packs can sometimes take more time.

You may be able to make a new collection which is a subtraction of the collection you have pushed to - Machines with have Office SP2 and re deploy.

Or you can use right click tools and rerun the deployment on the collection created.
0
 
LVL 22

Accepted Solution

by:
Adam Leinss earned 500 total points
ID: 40494267
I've found with SCCM that if you set the behavior to "Never re-run" and then change it later, it is never honored by the clients.  You have start over with a whole new package with a new package ID.  The clients track the success or failure of the deployment in their registry at: HKLM\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\.  I guess you could create a package, target the 180 that failed and remove the specific package ID that failed and that should trigger a restart of the package on said clients.
0
 
LVL 22

Expert Comment

by:Adam Leinss
ID: 40802812
I should amend this answer with another possibility that works on SCCM 2012R2.  The above statement is all true, but you can also load something called Micro Right Click Tools (free) for the SCCM console and if you right-click on a Deployment, you can actually re-run just the failed ones using Micro's built-in Powershell scripts.

Download: http://www.nowmicro.com/recast/right-click-tools/
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question