Client Management Suite

 View Only

Deploying Software with Software Management Solution 7.5 - Basic 

Sep 09, 2014 02:39 PM

I had to make instructions for a co-worker to deploy software to our managed computers.  This is just a basic set of instructions for uploading and deploying software.  I didn't get in to a lot of the advanced features.  If you need help at anytime, a lot of the frames have little blue question marks.  If you click on them they will take you to context based help / descriptions of the options available. 

 

How to Deploy Software Packages

Table of Contents

Prepartion

Uploading Software Package

Software Portal Option

Create Inventory Policy

Create Installed Filter

Create Managed Software Deliver Policy

 

Preparation

Before you begin, collect the following information depending on the package:

Software Name

Software Version

Software Company

Software executable file version

MSI install GUID (if deploying an MSI)

Targets needing software installed

 

Uploading Software Package top

In the Symantec Management Console Select Manage > Software Catalog

1.png

When the Software Catalog opens select Add and select from the list.  In this case we will be adding a software update.

2.png

When the Software package window opens, give it a name, input the correct version number and type in the the company name .  Select the name as it appears.  If the company isn’t listed, select New and add it.

3.png

*As you can see there are required fields that will be validated when you select OK.

4.png

After filling in the Properties tab, move to the Package tab.  Select Add package.

5.png

The Add or Edit Package frame displays.  Name the package, set the package source and click add to browse for the package.  If the install is executed by any other item in the package other than the auto selected executable, highlight it and click Set Installation File. Check the box for Automatically genereate command line when package is created. Select Ok.

6.png

Upon returning to the Package tab, the package and command line will now be populated.

7.png

Move to the Rules tab. Create a Detection Rule by selecting New.

8.png

Name the Detection rule and build it with the appropriate detection options.  In this case we are doing a simple file version detection looking for an equal match to the file version of swinit.exe. When done building select OK.

9.png

Move to the File Inventory tab.  Select Add.

10.png

 

From Add select Local File.  Browse to the location that this software is installed on a resource computer and select the files you wanted associated with this software.

11.png

After the files have been selected they will be added to the File Inventory tab.  Once completed select OK.  This will save & close the software update frame. 

12.png

Software Portal Option top

 

If the software needs to be added to the Software Portal reopen the software package and move to the Software Publishing tab. Check the Publish check box and select Add User.

13.png

Set your search scope options and sselect Find. Highlight the result you want to pick.  Only one can be added at a time.

14.png

Set wether that user is Approved  or Requires Approval.  Add any other users or groups if neccesary.  Select Ok to save & close.

15.png

Create Targeted Software Inventory top

Right click on the Software Update and move your mouse to  Actions  and then Create Targeted Software Inventory.

16.png

The Software Inventory Policy frame will open.  Name the policy accordingly.  Take note that by default all new policies are created in an off state.

17.png

Set the inventory policy schedule.

18.png

Verify your targeted systems for this policy.

19.png

Turn the policy on and Save changes.

20.png

 

Create Installed Software Filter top

Right click on the Software Update and move your mouse to  Actions  and then Create Targeted Software Filter.

21.png

 

The Create Installed Software Filter frame displays. Change the name if desired. Select OK to save & close.22.png

Create a Managed Software Delivery Policy top

In the Symantec Management Console select Manage > Policies.

23.png

 

Find the Managed Software Delivery folder. Right click on the folder you want to create the policy under and select New > Managed Software Delivery.

24.png

 

In the right hand frame a New Managed Software Delivery policy will be created.  Give it a Name. This name will be displayed in the client agents. Select Add > Software.

25.png

Search for the software you wanted to add to the policy. Select OK.26.png

 

Verify the Compliance & Remediation settings and then open the Advanced options. Set your Download options.27.png

Move to the Run tab and set the desired options.

28.png

If desired, set Results-based actions. Select OK.

29.png

Move to the Applied to section.  Select Apply to > Computers.

30.png

 

In this policy we want to to target all computers in our Active Directory Production OU.  Select <Exclude computers not in > <Group> <browse to the proper container>.

31sy.png

Select Add rule and add an option to exclude computers that already have this software installed.  Select <exclude computers in> <Filter> <Computers with Adobe Shockwave Player 12.1.3.153 Installed>.

32.png

 

In the Schedule section set an appropriate time or window to deliver & install. Turn the policy on at the top of the window and select Save changes at the bottom.  If this is an update to a previously deployed policy and the old policy is no longer being used make sure you check to make sure it is turned off.

33.png

 

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Oct 16, 2014 09:13 AM

Hi, very good article to get started.

However I have found that if I install application manually on test computer and let software inventory pick it up, it will be recognised correctly when you add it to software catalog, saves having duplicate entries.

Also, I have noticed that creating filter with installed software is more reliable from add_remove table.

When running installation, you can point to .bat file with a bit more logic in it if you cannot do it in the actual task/ job.

Andrey Shipov

Related Entries and Links

No Related Resource entered.