Client Management Suite

I'm looking for a way to accomplish some advanced software installations in our environment.    We just recently upgraded from 6.x to 7.1 SP2.  Right now, in 6.x, we have a software product that is contained in a single package that has 5 different programs you can choose from.  We then have 5 seperate tasks configured, each pointing to their own seperate collection.  So when we get a new PC that we need to roll out the application to we have to add the PC to all 5 collections.  From my understanding, 7.1 SP2 can simplify this considerably (maybe I'm wrong).  Here is the final goal I have in mind.

I want to have 1 software resource called "This Software".  I currently have it set up to run from a UNC location though I'm open to other ideas or recommendations.  The UNC path contains the installation file as well as the updates/fixes that we have come up with over the years.  I would like to create a Managed Software Delivery that will check the target computer to see if "This Software" is installed.  If it is not installed then it will install it.  Then it should check to see if a specific registry key exists, if it does, it moves to the next step, if it doesn't it applies a .reg file.  After this it should check to see if a specific file exists on the target computer, if it does, it moves to the next step, if it doesn't it copies the files from the UNC location to a specific folder on the target computer.

I have been able to create the one software resource and then create a number of different command lines that can be used in the MSD.  The problem with this is that since they are all one software resource I can only apply one rule (as far as I know anyway).  This means it checks to see if the program is installed, if it is, it does nothing, if it isn't it then runs through the entire MSD, installing the application, applying the registry key and copying the files.  But to be honest right now I'm not even sure it does all of those properly.  Any help that anyone can give would be much appreciated, I have several of these scenarios that I would like to set up similarly.

As you've discovered, each Software Resource can only have one Detection (and one Applicability) rule.

But some of your Software Resources might have a Type of "Update" or "Service Pack" with appropriate Dependencies. Then, when you put your primary Software Release ("This Software") into a policy the Updates and Service Packs are automatically available. I've not experimented too much on how the dependencies affects the ordering except that I know that if "This Software" has a dependency, that will install first and if it has and Update or Service Pack that gets installed afterwards.

I would avoid using UNC paths. For any of the 5 tasks that require software, create a Package as part of the deliverable Software Resource (Software Release, Update or Service Pack). I use the Software Library, I thing if you use UNC as a package source you'll need to create a separate folder for each Software Resource; for the Software library you can just specify which files you wish to select for any given package.

I try and include into detection rules a check for newer versions - you don't want "This Software" trying to install if someone's got a newer version installed.

You will need a software resource for each, which you'll then bundle up into a single MSD.  For how to properly relate all those item together, check out the section on Associations here:

https://www-secure.symantec.com/connect/articles/symantec-software-management-71-best-practices-part-2

And if you haven't read that entire Best Practices guide, do it now.  It's well worth the time.

If this is one program with 4-5 customizations or fixes, then you should contain the program in a .vbs wrapper that takes care of each requirement: the install itself, the reg fixes, the file copies, etc.  Your detection rule can check using AND statements that files and registries are present, or you can handle this in the .vbs wrapper.