Video Screencast Help

Making SoftPaq deployment useful

Created: 13 Nov 2009 • Updated: 08 Jul 2010 | 4 comments

Is there some best practice method for SoftPaq deployment I'm missing here? I select a SoftPaq, I select a bunch of computers (and this in itself is poor, it should be a filter group, computers needing SoftPaq X) and then I choose a schedule... except I can't think of a non-rubbish schedule. Either I deploy now, and half the computers don't get the SoftPaq, or I deploy on a schedule and all the computers download it even when they've already got it installed. To top it off, once they have installed the SoftPaq they still appear on the deployment list for that SoftPaq, meaning it's impossible to see if new machines have appeared which need it.

The entire SoftPaq deployment mechanism seems useless for anything other than a small shop. Am I missing something?

Comments 4 CommentsJump to latest comment

jahnemar's picture

Is the softpack registered in add/remove programs?

If it does then you can use "Conditions".

Set the default condition to do nothing.
Create a condition with "Application name" does not contain "your application" that installs the softpack.
If you want to upgrade an application then you can add "Application Version" to the condition.
Archangel's picture

Quitch - Were you able to get this resolved?

Quitch's picture

jahnemar's response sounds helpful, though off the top of my head I can't reconcile it with how to implement it. Still, I'll need to have a poke around.

Unfortunately I haven't been able to try yet because we found that only machines after time X were appearing in the list of computer to deploy packages to and the ones prior to this point never appeared. We were reinstalling to resolve but the product is generating errors on install that we haven't been able to fix yet.

Archangel's picture

Quitch - I have a meeting with a sales engineer today.  I'll post the results.