Moving from GPO software installs to SCCM

[Kevin79]

We currently use Group Policy to install software and are moving to SCCM 2007. I've done a little testing with packages and SCCM will reinstall the software if it was installed by group policy. Is there a way to have it so that if the software is already installed, SCCM won't reinstall it?

[Trevor Sullivan]

Yes, you have a couple of options:

 

1. Write a wrapper script around the deployment that checks for existence of the software first.

 

2. Put the deployment inside a task sequence, and deploy the task sequence instead. You can set a conditional (such as a WMI query) on each task sequence item, so if the condition is met, then the software will not install.

 

Hope this helps.

 

Cheers,

Trevor Sullivan

http://trevorsullivan.net

http://twitter.com/pcgeek86

[Kevin79]

Yes, you have a couple of options:

 

1. Write a wrapper script around the deployment that checks for existence of the software first.

 

2. Put the deployment inside a task sequence, and deploy the task sequence instead. You can set a conditional (such as a WMI query) on each task sequence item, so if the condition is met, then the software will not install.

 

Hope this helps.

 

Cheers,

Trevor Sullivan

http://trevorsullivan.net

http://twitter.com/pcgeek86

 

Wouldn't the task sequence be used for an OSD?

 

How would I do a wrapper script?

[Lucid]

It also depends about WHEN you're talking about. Deploying an application to an existing client machine versus during OS deployment are different methods. If to existing machines, you can use a membership query on your collection to only populate it with machines that need the application - so ones that already have the right version won't show up. Here's some queries to help illustrate: http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx

 

And a "script wrapper" is using whatever scripting language you like to first check it the application is installed, and if it isn't, to go ahead and install it. So instead of deploying the .EXE or .MSI file, you deploy the .CMD, .BAT, .VBS, or whatever file (make sure it's part of your package of course). This script then makes the choice to install or not.

 

And lastly.. You can use Task Sequences to deploy things other than OS images. There are some guides on this site, and I'm sure your favorite search engine can help you find other useful examples...

[Kevin79]

It also depends about WHEN you're talking about. Deploying an application to an existing client machine versus during OS deployment are different methods. If to existing machines, you can use a membership query on your collection to only populate it with machines that need the application - so ones that already have the right version won't show up. Here's some queries to help illustrate: http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx

 

And a "script wrapper" is using whatever scripting language you like to first check it the application is installed, and if it isn't, to go ahead and install it. So instead of deploying the .EXE or .MSI file, you deploy the .CMD, .BAT, .VBS, or whatever file (make sure it's part of your package of course). This script then makes the choice to install or not.

 

And lastly.. You can use Task Sequences to deploy things other than OS images. There are some guides on this site, and I'm sure your favorite search engine can help you find other useful examples...

 

Thanks. I'll look at those queries. With the wrapper, would it still give go information as to the status of the install? I.E. if it failed, why it failed.

[Kevin79]

How would I create a collection that will check for certain software in the add/remove programs and it if exists, EXCLUDE it from the collection? I see ways of including computers in collection that have certain software installed, but not exclude them.

[Lucid]

With a script wrapper you can return a basic Success/Failure code. For example, in VBScript, this returns success "Wscript.Quit" and this returns failure "Wscript.Quit(1)".

 

As for your collection query question, take a look at the Office 2007 query here: http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx , keeping in mind that you'd have to check two different spots if you've got a mix of 32-bit and 64-bit operating systems...