Symantec™ Software Management Solution 7.5 powered by Altiris

Symantec™ Software Management Solution 7.5 powered by Altiris
Symantec™ Software
Management Solution 7.5
powered by Altiris™ User
Guide
Altiris™ Software Management Solution 7.5 from
Symantec™ User Guide
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Legal Notice
Copyright © 2013 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and the Checkmark Logo, Altiris, and any Altiris or Symantec
trademarks used in the product are trademarks or registered trademarks of Symantec
Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks
of their respective owners.
This Symantec product may contain third party software for which Symantec is required to
provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs
are available under open source or free software licenses. The License Agreement
accompanying the Licensed Software does not alter any rights or obligations you may have
under those open source or free software licenses. For more information on the Third Party
Programs, please see the Third Party Notice document for this Symantec product that may
be available at http://www.symantec.com/about/profile/policies/eulas/, the Third Party Legal
Notice Appendix that may be included with this Documentation and/or Third Party Legal Notice
ReadMe File that may accompany this Symantec product.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Support’s
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base.
The Technical Support group works collaboratively with the other functional areas
within Symantec to answer your questions in a timely fashion. For example, the
Technical Support group works with Product Engineering and Symantec Security
Response to provide alerting services and virus definition updates.
Symantec’s support offerings include the following:
■
A range of support options that give you the flexibility to select the right amount
of service for any size organization
■
Telephone and/or Web-based support that provides rapid response and
up-to-the-minute information
■
Upgrade assurance that delivers software upgrades
■
Global support purchased on a regional business hours or 24 hours a day, 7
days a week basis
■
Premium service offerings that include Account Management Services
For information about Symantec’s support offerings, you can visit our website at
the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Contacting Technical Support
Customers with a current support agreement may access Technical Support
information at the following URL:
www.symantec.com/business/support/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at
the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■
Product release level
■
Hardware information
■
Available memory, disk space, and NIC information
■
Operating system
■
Version and patch level
■
Network topology
■
Router, gateway, and IP address information
■
Problem description:
■
Error messages and log files
■
Troubleshooting that was performed before contacting Symantec
■
Recent software configuration changes and network changes
Licensing and registration
If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/business/support/
Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
■
Questions regarding product licensing or serialization
■
Product registration updates, such as address or name changes
■
General product information (features, language availability, local dealers)
■
Latest information about product updates and upgrades
■
Information about upgrade assurance and support contracts
■
Information about the Symantec Buying Programs
■
Advice about Symantec's technical support options
■
Nontechnical presales questions
■
Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources
If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan
[email protected]
Europe, Middle-East, and Africa
[email protected]
North America and Latin America
[email protected]
Contents
Technical Support ............................................................................................... 4
Chapter 1
Introducing Software Management ................................ 12
About Software Management ..........................................................
About Software Management Framework ....................................
About Software Management Solution ........................................
How Software Management Solution integrates with Software
Management Framework ...................................................
Components of Software Management Framework .............................
Components of Software Management Solution ..................................
Web parts for Software Management Framework ................................
Web parts for Software Management Solution ....................................
What you can do with Software Management Framework .....................
What you can do with Software Management Solution .........................
Where to get more information ........................................................
12
13
14
16
18
18
19
20
22
23
25
Section 1
Getting Started with Software
Management ............................................................ 28
Chapter 2
Implementing Software Management
Framework ...................................................................... 29
Introducing Software Management Framework ...................................
About the Software Catalog ......................................................
Benefits of the Software Catalog ................................................
About the separation of software-related user roles .......................
About the Software Library .......................................................
Benefits of the Software Library .................................................
Implementing Software Management Framework ................................
Setting up the Software Library .......................................................
Configuring the Software Library ......................................................
Scheduling a Clean up File Resources task .......................................
Running a Clean up File Resources task ...........................................
Adding descriptions to installation error codes ....................................
Defining known-as wildcards ...........................................................
29
30
31
32
33
35
36
38
39
41
42
42
43
Contents
Editing or deleting a known-as association .........................................
Populating the Software Catalog ......................................................
Introducing software resources ..................................................
Importing a package to create a software resource ........................
Discovering software on managed computers ..............................
Configuring the Software Discovery policy ...................................
Assigning a type to a software resource ......................................
Resolving duplicate software resources ......................................
Creating a filter for installed software ..........................................
Chapter 3
45
46
49
51
54
57
59
60
61
Implementing Software Management Solution ............ 63
Implementing Software Management Solution ....................................
Installing or upgrading the Software Management Solution
plug-in .................................................................................
Installing the Software Portal plug-in .................................................
Configuring security privileges for Software Management
Solution ................................................................................
Configuring the default settings for Managed Software Delivery .............
63
65
68
69
71
Section 2
Managing software and applications on
client computers .................................................... 74
Chapter 4
Working with software resources .................................... 75
Chapter 5
Adding or editing a software resource ...............................................
Deleting a software resource ..........................................................
Associating a package with a software resource .................................
Adding an existing package to the Software Library .............................
Creating a command line for a software resource ................................
Creating or editing inventory rules ....................................................
Adding associations to a software resource .......................................
Adding file resources to a software resource manually .........................
Exporting a software resource and its details ......................................
75
77
78
80
81
83
88
89
90
Using the Enhanced Console View for Software
Management ..................................................................
92
Introducing the Software view and the Software Catalog window ............
Accessing the Software Catalog window ...........................................
Finding software in the Software view and in the Software
Catalog ................................................................................
Saving a software search ...............................................................
92
96
97
99
8
Contents
Managing a saved software search ................................................ 100
Installing software by drag and drop ............................................... 101
Chapter 6
Importing data from a data provider ............................. 103
Introducing data providers ............................................................
Adding a data provider .................................................................
Importing data from a data provider ................................................
Configuring the precedence settings for a data provider ......................
Importing data from a data provider with a schedule ...........................
Importing data from a data provider manually ...................................
Chapter 7
Managing Windows Installer applications ................... 114
Introducing Windows Installer applications .......................................
Updating the source paths of Windows Installer applications ................
Configuring a Source Path Update policy .........................................
Repairing Windows Installer applications .........................................
Configuring a Windows Installer Repair policy ...................................
Creating customized Windows Installer policies and tasks ...................
Chapter 8
103
106
107
109
110
112
114
115
117
119
120
122
Managing virtual applications ........................................ 124
Introducing software virtualization and virtual applications ...................
About software virtualization ...................................................
About managing virtual applications ..........................................
About VSA and XPF virtual package files ...................................
About the applications that you can virtualize ..............................
About data layers, exclude entries, and preventing the loss of
virtual application data .....................................................
Methods for virtualizing software ..............................................
Methods for installing and managing virtual software ....................
Actions that you can perform on a virtual software layer ................
Installing the Symantec Workspace Virtualization Agent .....................
Managing virtual applications ........................................................
Virtualizing software during installation ............................................
Installing and managing a virtual software layer with a Software
Virtualization task .................................................................
Installing and managing a virtual software layer with a Quick Delivery
or Package Delivery task ........................................................
Installing and managing a virtual software layer with a Managed
Software Delivery policy .........................................................
124
125
126
127
127
128
130
131
133
134
135
136
138
140
141
9
Contents
Section 3
Delivering software ................................................... 143
Chapter 9
Performing a quick delivery of a single software
resource ......................................................................... 144
Introducing software delivery .........................................................
About software delivery ..........................................................
Methods for delivering software ...............................................
Methods for uninstalling software .............................................
Performing a quick delivery of a single software resource ....................
Creating a Quick Delivery task with the Quick Delivery wizard ..............
Creating a task in Software Management Solution .............................
Editing a task in Software Management Solution ...............................
Scheduling a task and selecting computers in Software
Management Solution ......................................................
Running a Software Management Solution report ..............................
Chapter 10
156
157
Delivering Packages .......................................................... 160
Delivering a package without defining a software resource ..................
Delivering software packages with the same configurations as 6.x
Software Delivery tasks ..........................................................
Accessing a Legacy Software Delivery policy ...................................
Assigning an Altiris 6.x software package to a software resource ..........
Assigning multiple Altiris 6.x software packages to software
resources ............................................................................
Adding 6.x software packages to a package assignment task ..............
Editing 6.x software packages .......................................................
Chapter 11
144
145
145
148
149
152
153
155
160
162
163
164
166
170
171
Performing an advanced software delivery ................. 172
Introducing advanced software deliveries ........................................
About advanced software deliveries ..........................................
About the execution of Managed Software Delivery policies ...........
About policy applicability, compliance, and remediation ................
About software delivery deferral options for the user ....................
About deferring the execution of software remediation ..................
About installing software that replaces other software ...................
About the status of Managed Software Delivery policies ...............
Viewing all Managed Software Delivery policies ................................
Creating a Managed Software Delivery policy with the Managed
Software Delivery wizard ........................................................
Creating a Managed Software Delivery policy ...................................
172
173
174
176
178
180
181
182
182
183
184
10
Contents
Editing a Managed Software Delivery policy .....................................
Selecting the delivery destinations for a Managed Software Delivery
policy .................................................................................
Performing an advanced software delivery .......................................
Delivering multiple software resources and tasks sequentially ..............
Performing an emergency policy update ..........................................
Viewing emergency policy update reports ........................................
Chapter 12
186
188
189
190
192
194
Delivering software from user requests using the
Software Portal ............................................................ 196
Introducing software requests and the Software Portal .......................
About the Software Portal .......................................................
What you can do with the Software Portal ..................................
About the software in the Software Portal ..................................
Methods for adding software to the Software Portal .....................
Statuses of software requests in the Software Portal ....................
Software request workflow ......................................................
Methods for delivering software from approved software
requests .......................................................................
Setting up the Software Portal .......................................................
Implementing the Software Portal .............................................
Adding a software resource to the Software Portal .......................
Adding a Managed Software Delivery policy to the Software
Portal ...........................................................................
Configuring the Software Portal settings ....................................
Configuring security privileges for the Software Portal ........................
Reviewing and approving software requests .....................................
Finding and filtering software requests ......................................
Processing a software request on the Administrator Portal
page ............................................................................
Using the Software Portal on the client computer ...............................
Opening the Software Portal ...................................................
Setting up the Software Portal with your user profile .....................
Finding and filtering software requests on the Manager Portal
page ............................................................................
Requesting software in the Software Portal ................................
Reviewing or adding comments to a software request ..................
Canceling a software request ..................................................
Processing a software request .................................................
Installing approved software ....................................................
196
197
198
198
199
200
202
204
205
205
207
209
209
211
214
214
214
217
217
218
219
220
221
223
224
225
Index ................................................................................................................... 227
11
Chapter
1
Introducing Software
Management
This chapter includes the following topics:
■
About Software Management
■
Components of Software Management Framework
■
Components of Software Management Solution
■
Web parts for Software Management Framework
■
Web parts for Software Management Solution
■
What you can do with Software Management Framework
■
What you can do with Software Management Solution
■
Where to get more information
About Software Management
Software Management consists of the management of software. The use of software
resources helps you gain efficiencies in the performance of your daily software
management tasks. With the Software Management Framework you can automate
those tasks so you can spend more time on other issues.
See “About Software Management Framework” on page 13.
Software Management Solution provides intelligent and bandwidth-sensitive
distribution and management of software. Software Management Solution integrates
with the Software Management Framework to focus on software delivery.
See “About Software Management Solution” on page 14.
Introducing Software Management
About Software Management
About Software Management Framework
Software Management Framework is part of the Symantec Management Platform.
It provides the Definitive Software Library and configuration management capabilities
of a Configuration Management Database (CMDB).
Software Management Framework facilitates integration between the solutions in
Symantec Management Platform by providing a common way to store, identify, and
detect software. It provides the structure in which to define the software and it
provides the tools with which to manage the software definitions.
Software Management Framework introduces a change in the way that software
is identified. All software is defined in a single location and in a consistent manner.
The software definitions are referred to as software resources. The software-related
functions in Symantec Management Platform can use these software resources,
which ensures that they all identify the same software in the same way.
The use of software resources helps you gain efficiencies in the performance of
your daily software management tasks. You no longer need to perform many of
your software tasks manually. Instead, you do some of the work initially by defining
the information that helps to automate those tasks. Then you can let Software
Management Framework and the solutions help manage your software so that you
can spend more time on other issues.
Examples of how the software resource data can help you perform software tasks
are as follows:
■
You can define any other software that a specific software resource depends
on. When you deliver that software resource, the dependency software is
automatically included in the delivery. You do not have to remember to deliver
the dependency software separately.
■
The software resource’s unique identifier provides a consistent way to detect
the software on the client computers. Before the software delivery process
downloads the software to a computer, it can determine whether that software
is already installed. The delivery process can also check the computer
periodically to verify that the software is still installed and to reinstall the software
if necessary. This automated verification and remediation can substantially
reduce your need to respond to help desk calls for missing or broken software.
(Windows only) You can define a detection rule that contains additional
information about the software and makes the detection process even more
accurate.
■
You can specify the critical executable files that are associated with a software
resource. Then inventory scans can accurately determine whether that software
is installed on a computer. For example, you specify four critical files and add
them to the detection rule for a software resource. When the detection rule
13
Introducing Software Management
About Software Management
evaluates a client computer, it considers the software to be installed only if it
finds all four files on that computer.
Software Management Framework promotes smart software management so that
you know all about your software as follows:
■
You know what software you have, where it is installed, and where the physical
software packages are.
■
You know that the software you install is the software that you intended to install.
■
You know that the software remains in the correct state on the client computers.
■
You know that when a software inventory scan finds an application on a
computer, the application is identified as the same one that you installed.
■
You know that patches are applied to the correct software.
Your solutions can provide this knowledge because they use the software resource
information that you define in Software Management Framework.
Software Management Framework supports packages for the Windows, UNIX Linux,
and Mac operating systems. With few exceptions, all the functions in Software
Management Framework work the same for all platforms. For example, you use
the same method to create a software resource for a Windows, UNIX, Linux, or
Mac OS package.
See “Components of Software Management Framework” on page 18.
See “About the Software Catalog” on page 30.
See “Benefits of the Software Catalog” on page 31.
See “About the Software Library” on page 33.
See “Benefits of the Software Library” on page 35.
About Software Management Solution
Software Management Solution provides intelligent and bandwidth-sensitive
distribution and management of software from a central Web console. It significantly
reduces desktop visits and lets you easily support your mobile work force.
See “What you can do with Software Management Solution” on page 23.
See “Implementing Software Management Solution” on page 63.
See “Components of Software Management Solution” on page 18.
Software Management Solution also lets users directly download and install
approved software or request other software.
14
Introducing Software Management
About Software Management
Software Management Solution integrates with the Software Catalog and the
Software Library that are part of the Symantec Management Platform. By leveraging
this information, Software Management Solution ensures that the correct software
gets installed, remains installed, and runs without interference from other software.
This integration lets your administrators focus on delivering the correct software
instead of redefining the packages, command lines, and so on for each delivery.
See “How Software Management Solution integrates with Software Management
Framework” on page 16.
See “About Software Management Framework” on page 13.
See “About the Software Catalog” on page 30.
See “About the Software Library” on page 33.
Software Management Solution combines the functionality of earlier versions of
Software Delivery Solution and Application Management Solution. It also supports
the software virtualization technology that was available in Altiris Software
Virtualization Solution.
Software Management Solution data is stored in the Configuration Management
Database on the Notification Server computer. The data is grouped in resource
data classes. A resource data class defines one or more fields, and the properties
of the fields, that a resource of that class may have.
Settings in the Symantec Management Platform determine how long the data is
retained in the database before it is purged. You can specify the retention period
for specific data classes. These settings are on the Purging Maintenance page,
Resource Event Data Purge Settings tab, that appears in the Symantec
Management Console.
For more information, see the topics on resource data classes and purging the
Configuration Management Database in the Altiris™ IT Management Suite 7.5
Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
The data classes that represent Software Management Solution data are as follows:
■
Computer Events:
AeX SWD Execution
AeX SWD Package
AeX SWD Status
SoftwareManagementSolution MSI Repair
■
Events:
SoftwareManagementSolution App State Failures
SoftwareManagementSolutionAppRepair
15
Introducing Software Management
About Software Management
■
Policy Compliance Remediation
■
Virtual Software Events:
Software Virtualization Events
Software Management Solution supports hierarchy and replication. These features
let you create tasks and policies at the top-level Notification Server computer and
replicate them to child-level Notification Server computers.
Hierarchy defines the information flows across multiple Notification Server computers
in an enterprise. Hierarchy uses replication to copy and synchronize shared objects
and data between multiple Notification Server computers within the same hierarchical
structure.
Software Management Solution supports full and differential replication. Differential
replication replicates only those items that changed since the last replication.
Hierarchy replicates each object or piece of data in one direction only.
Software Management Solution supports hierarchy editable properties (HEP). This
feature lets you configure which of the policies' properties can the administrators
down the hierarchy. By default, all of the hierarchy editable properties (Schedule,
Resource targets, and Enabled) are turned off and cannot be modified down the
hierarchy. One exception is the Resource targets property in the managed software
delivery policies, which is turned on by default. This exception is required for the
managed software delivery policies to be published correctly to the Software Portal
down the hierarchy.
Software Management Solution supports packages for the Windows, UNIX, Linux,
and Mac operating systems. With few exceptions, all the functions in Software
Management Solution work the same for all platforms. For example, you use the
same method to create a delivery task for a Windows, UNIX, Linux, or Mac OS
package.
For a complete list of the platforms that Software Management Solution supports,
see the Client Management Suite Release Notes.
How Software Management Solution integrates with Software
Management Framework
In Software Management Solution, Quick Delivery and Managed Software Delivery
leverage the software resource information that is in the Software Management
Framework. Software Management Framework consists of the Software Catalog
and the Software Library, as well as tools to create and manage the software
resources. When you create a task or policy, you select a software resource to
deliver. Any information about the software that the task or the policy needs is
available from the software resource.
16
Introducing Software Management
About Software Management
Software Management Framework, together with the Software Catalog and the
Software Library are part of the Symantec Management Platform.
See “About Software Management Framework” on page 13.
See “Components of Software Management Framework” on page 18.
See “About the Software Catalog” on page 30.
See “About the Software Library” on page 33.
Table 1-1
How features in Software Management Solution use software
resource information
Feature
Usage of software resource information
Quick Delivery
The Quick Delivery wizard limits the selections that you need to make to deliver software.
You select the software resource to deliver, the command line to use, and the destinations
to target. The software resource provides any other information that is required for the
delivery. This simplified delivery method lets you entrust certain deliveries to
non-administrators such as help desk personnel.
Managed Software
Delivery
The software resource information is essential for the complex deliveries that Managed
Software Delivery performs.
Managed Software Delivery uses the software resource’s rules to intelligently perform
applicability and compliance checks and to remediate the software that is out of compliance.
These checks conserve bandwidth by ensuring that the software is not downloaded to
computers on which it is already installed.
The Managed Software Delivery wizard can use the software resource’s associations to
alert you to the following situations:
■
When the selected software depends on other software resources
■
When an update to the selected software is available
■
When other software supersedes the selected software
■
(Windows only) When the selected software resource conflicts with another software
resource
See “About advanced software deliveries” on page 173.
Software Portal
(Windows and Mac OS only) In each software resource, you can configure settings for
making that software available to the Software Portal. The settings determine which users
are allowed to request that software and whether their requests require approval.
See “About the Software Portal” on page 197.
17
Introducing Software Management
Components of Software Management Framework
Components of Software Management Framework
The components of Software Management Framework let you define and manage
your software resources.
See “About Software Management Framework” on page 13.
Table 1-2
Components of Software Management Framework
Component
Description
Software Catalog
A centralized model of the software that is known in your
organization. The Software Catalog contains the meta data
that describes your software resources.
In ITIL terms, the Software Catalog represents a portion of
a Configuration Management Database (CMDB).
See “About the Software Catalog” on page 30.
Software Library
A secure directory that is the centralized repository of the
definitive, authorized versions of the software that your
organization manages. It is the physical source for your
managed packages.
In ITIL terms, the Software Library is equivalent to a Definitive
Software Library (DSL).
See “About the Software Library” on page 33.
Tools to populate the
Software Catalog and the
Software Library and to
manage their contents.
These tools let you create the software resources that you
need to manage.
Components of Software Management Solution
The components of Software Management Solution let you deliver and manage
software on client computers.
See “What you can do with Software Management Solution” on page 23.
18
Introducing Software Management
Web parts for Software Management Framework
Table 1-3
Components of Software Management Solution
Component
Description
Software delivery tasks You can use any of several methods to deliver software to client
and policies
computers. The method that you use to create the task or policy
depends on your delivery requirements.
See “Methods for delivering software” on page 145.
Software Portal
The Software Portal is a Web-based interface that is installed on
the client computers. With the Software Portal, users can request
and install software with little or no administrator involvement.
See “About the Software Portal” on page 197.
Tasks and policies for
managing Windows
Installer applications
You can manage Windows Installer applications as follows:
Tasks for managing
virtual applications
You can use software virtualization to facilitate the management
of most Windows-based software on managed computers.
Software virtualization lets you avoid conflicts between
applications. It also lets you quickly restore a broken application
to its original installed state.
■
Repair broken Windows Installer applications.
■
Update the source paths for Windows Installer applications.
See “Managing virtual applications” on page 135.
Reports
Predefined reports let you easily view and analyze your software
management data. You can also create your own custom reports.
See “Running a Software Management Solution report”
on page 157.
Web parts for Software Management Framework
Web parts are the building blocks for portal pages in the Symantec Management
Console. Web parts are predefined for the products that you have installed. You
can edit the predefined Web parts, and you can create new Web parts. Your user
privileges determine which of the Web parts you can use and whether you can edit
and add Web parts.
19
Introducing Software Management
Web parts for Software Management Solution
Table 1-4
Web parts for Software Management Framework
Web part
Description
Data Providers
Lets you view a list of registered data providers. For each provider,
the list displays the number of available software resources and
when an import or gather was last run. A software resource is
available if it has data that is ready to be imported.
On this Web part, you can add or delete a data provider. You can
also open a data providers page to edit its setting.
From the right-click menu of a data provider, you can schedule an
import or a gather. When you schedule an import, you can import
the data provider’s meta data. You can also import the software
packages that are associated with the meta data if the data
provider supports this functionality.
See “Importing data from a data provider with a schedule”
on page 110.
After the gather runs, the Available data column of the Data
Provider Web part is updated. A gather also gathers a list of the
available software resources and adds them to the Data Provider
Summary page. From the right-click menu of a data provider, you
can click View Data Provider Summary to access the Data
Provider Summary page. On this page, you can select specific
software resources to import.
See “Importing data from a data provider manually” on page 112.
To use the functionality of the Data Provider Web part, you must
be assigned the Symantec Software Librarian security role.
Software Finder
Lets you perform a quick search of the software resources that
are in the Software Catalog. You can edit, delete, and perform
other actions on the software resources that are found.
See “Finding software in the Software view and in the Software
Catalog” on page 97.
Web parts for Software Management Solution
Web parts are the building blocks for portal pages in the Symantec Management
Console. Web parts are predefined for the products that you have installed. You
can edit the predefined Web parts, and you can create new Web parts. Your user
privileges determine which of the Web parts you can use and whether you can edit
and add Web parts.
See “About Software Management Solution” on page 14.
20
Introducing Software Management
Web parts for Software Management Solution
For more information, see the topics about portal pages and Web parts in the the
Altiris™ IT Management Suite 7.5 Administration Guide from Symantec™at the
following URL:
http://www.symantec.com/docs/DOC5330
Table 1-5
Web parts for Software Management Solution
Web part
Description
Data Providers
Lists each of the available data providers for the software
management products.
Open Software
Request Status
Displays a pie chart that summarizes all the open requests that
are in the Software Portal and groups them by status. It also shows
the number of requests that are in each status group.
Recent Software
Delivery Status
Lists all software deliveries and displays a green bar next to those
that succeeded and a red bar next to those that failed. It includes
the following delivery types: Managed Software Delivery, Quick
Delivery, Package Delivery, and Legacy Software Delivery.
Software Compliance
Summary
Displays a pie chart that shows how many software installations
are compliant and not compliant among those that were installed
with Managed Software Delivery. This data is based on the most
recent compliance checks that the currently-active Managed
Software Delivery policies performed.
A software installation is considered compliant when it is in the
correct state on the client computers. For example, if the software
is installed and it should be installed, it is compliant. If the software
is installed but it should not be installed, it is not compliant.
Software Delivery
History
Displays a graph that shows the number of deliveries that
succeeded and failed among the deliveries that were attempted
within the specified time period. It includes the following delivery
types: Managed Software Delivery, Quick Delivery, Package
Delivery, and Legacy Software Delivery.
Software Delivery
Status
Displays a pie chart that shows the number of deliveries that
succeeded and failed among all deliveries that were attempted. It
includes the following delivery types: Managed Software Delivery,
Quick Delivery, Package Delivery, and Legacy Software Delivery.
Software Finder
Lets you quickly find a software in the catalog.
Software Portal
Request Summary
Displays a pie chart that summarizes all the software requests
that were placed through the Software Portal and groups them by
status. It also shows the number of requests that are in each status
group.
21
Introducing Software Management
What you can do with Software Management Framework
What you can do with Software Management
Framework
Software Management Framework uses the Software Catalog and the Software
Library to provide a structure for identifying and managing software. The tasks that
you can perform in Software Management Framework help you to define and
manage the software that is used in your organization.
See “Implementing Software Management Framework” on page 36.
Table 1-6
Key tasks in Software Management Framework
Task
Description
Set up the Software Library
You can set up a Software Library directory and associate it with a Symantec
Management Platform installation.
See “Setting up the Software Library” on page 38.
Configure settings
The Software Management Framework settings can help you manage the Software
Catalog and its resources.
Schedule the Clean up File Resources task to periodically delete any files that might
be left in the database after file resources are deleted. This task is scheduled by default.
Edit it only if you want to change the schedule or disable it.
The Known-as mappings create known-as associations to associate the unique
identifiers of two software resources so that they are identified as being the same
software. The known-as associations help the software-related operations to identify
software resources accurately. Create any necessary known-as associations before
you begin to populate the Software Catalog or as soon as you find duplications. New
known-as associations do not affect existing software resources.
The Installation Error Code Descriptions list eliminates the need to look up a
numerical error code when you run a report, associate informative descriptions with
the error codes. Some error code descriptions are predefined. Create additional
descriptions if the predefined descriptions do not meet your needs.
View the software
You can perform a search in the Software view and in the Software Catalog window
to find specific software. You can also use advanced search criteria to further narrow
the software that is displayed.
See “Finding software in the Software view and in the Software Catalog” on page 97.
Populate the Software
Catalog
You populate the Software Catalog by adding software resources. You can use any
of several methods to add software resources to the Software Catalog.
22
Introducing Software Management
What you can do with Software Management Solution
Table 1-6
Key tasks in Software Management Framework (continued)
Task
Description
Add and edit software
resources
Regardless of how a software resource is created, you can add and edit additional
information as follows:
■
Create associations between software resources.
You can define associations between software resources in the Software Catalog.
These associations add logic to software-related tasks.
■
Associate a package with a software resource.
You can define the installation package that installs a software resource.
See “Associating a package with a software resource” on page 78.
Associate files with a software resource.
A software resource can contain references to the important files that it installs.
These files typically are DLL and EXE files. However, you can add references to
any files that can help to identify a specific software resource.
See “Adding file resources to a software resource manually” on page 89.
Configure the package server settings for a package.
You can assign a package to the package servers that it can be copied to and
delivered from.
■
■
Populate the Software Library The Software Library is a secure directory that is the centralized repository of the
definitive, authorized versions of the software that your organization manages. Place
packages in the Software Library to ensure that external users cannot change the
packages after they have been approved for rollout in your environment.
Create command lines for
software resources
You can create a command line that runs a package or that runs without a specific
package.
See “Creating a command line for a software resource” on page 81.
The Command Line Builder helps you create command lines without an extensive
knowledge of the command-line options or syntax. You select the appropriate options
and the Command Line Builder creates an error-free command line for an optimal
installation, update, or other action.
Create inventory rules
(Windows only) Inventory rules perform the checks that are related to the software that
is installed on a client computer and to the computer’s environment. You can create
and edit the inventory rules that you associate with specific software resources.
See “Creating or editing inventory rules” on page 83.
What you can do with Software Management Solution
Software Management Solution lets you distribute and manage the software that
is used in your organization.
23
Introducing Software Management
What you can do with Software Management Solution
See “About Software Management Solution” on page 14.
Table 1-7
Task
What you can do with Software Management Solution
Description
Configure the default settings Configuration settings control the behavior of Managed Software Delivery policies.
for Managed Software
Rather than configuring these settings individually for each policy, you can configure
Delivery policies.
the default settings that apply to all new Managed Software Delivery policies. Then
you can change the settings for a specific policy only when needed.
See “Configuring the default settings for Managed Software Delivery” on page 71.
Perform an advanced
software delivery.
Managed Software Delivery simplifies your advanced software deliveries by letting you
deliver software as a unit, which can include multiple software resources and their
dependencies. For example, you can create a single Managed Software Delivery policy
that installs an application and its associated patches and service packs. Managed
Software Delivery can also run any task at any stage of the delivery.
See “About advanced software deliveries” on page 173.
See “Performing an advanced software delivery” on page 189.
Perform a quick delivery of a You can perform a quick delivery of a single software resource that runs with minimum
single software resource.
configuration. You can use the task-based Quick Delivery method to specify the software
to deliver, the action to perform, and the computers to deliver to. Because the software
resources and the delivery settings are predefined, Quick Delivery makes it easy for
administrators and non-administrators to deliver software.
See “Performing a quick delivery of a single software resource” on page 149.
Deliver a package without
Package Delivery lets you quickly push out any package regardless of whether it is
defining a software resource. associated with a software resource.
See “Delivering a package without defining a software resource” on page 160.
Deliver the tasks and
packages that were created
in Altiris Software Delivery
Solution 6.x.
When you upgrade from Notification Server 6.x to Symantec Management Platform
7.x, you can migrate your software-related tasks and packages.
For more information about 6.x data migration, see the Altiris™ IT Management Suite
from Symantec™ Migration Guide version 6.x to 7.5 at the following URL:
http://www.symantec.com/docs/DOC5668
Deliver software to fulfill user By using the Software Portal, users can request and install software through a
requests.
Web-based interface with little or no administrator involvement.
See “About the Software Portal” on page 197.
24
Introducing Software Management
Where to get more information
Table 1-7
What you can do with Software Management Solution (continued)
Task
Description
Manage Windows Installer
installations on client
computers.
You can create policies and tasks to manage Windows Installer applications on
managed computers as follows:
■
■
Manage virtual applications.
Repair Windows Installer applications.
You can proactively identify and repair broken applications on selected computers.
If an application needs repair, a repair command is sent to the Windows Installer
service to initiate self-repair.
See “Repairing Windows Installer applications” on page 119.
Update the source paths for Windows Installer applications.
You can update the source paths of Windows Installer applications with resilient
source paths. The updated source paths point to the package servers that you
designate. If an application needs modification or repair, Windows Installer can
access the needed installation file from one of these servers.
See “Updating the source paths of Windows Installer applications” on page 115.
You can use software virtualization to facilitate the management of most Windows-based
software on managed computers. Software virtualization lets you avoid conflicts between
applications and quickly restore a broken application to its original installed state.
Software Management Solution lets you perform the following virtualization actions:
■
Virtualize applications during a Managed Software Delivery installation.
■
Deliver and install virtual layers with any Software Management Solution delivery
policy or task.
Manage the existing virtual layers on the client computers.
■
See “Managing virtual applications” on page 135.
Where to get more information
Use the following documentation resources to learn about and use this product.
Table 1-8
Documentation resources
Document
Description
Location
Release Notes
Information about new
features and important
issues.
The Supported Products A-Z page, which is available at the following
URL:
http://www.symantec.com/business/support/index?page=products
Open your product's support page, and then under Common Topics,
click Release Notes.
25
Introducing Software Management
Where to get more information
Table 1-8
Documentation resources (continued)
Document
Description
Location
User Guide
Information about how to ■
use this product,
including detailed
■
technical information and
instructions for
performing common
tasks.
The Documentation Library, which is available in the Symantec
Management Console on the Help menu.
The Supported Products A-Z page, which is available at the
following URL:
http://www.symantec.com/business/support/index?page=products
Open your product's support page, and then under Common Topics,
click Documentation.
Help
Information about how to
use this product,
including detailed
technical information and
instructions for
performing common
tasks.
The Documentation Library, which is available in the Symantec
Management Console on the Help menu.
■
Click the page and then press the F1 key.
Help is available at the
solution level and at the
suite level.
■
Use the Context command, which is available in the Symantec
Management Console on the Help menu.
Context-sensitive help is available for most screens in the Symantec
Management Console.
You can open context-sensitive help in the following ways:
This information is
available in HTML help
format.
In addition to the product documentation, you can use the following resources to
learn about Symantec products.
Table 1-9
Resource
Description
SymWISE
Articles, incidents, and
Support
issues about Symantec
Knowledgebase products.
Symantec product information resources
Location
http://www.symantec.com/business/theme.jsp?themeid=support-knowledgebase
26
Introducing Software Management
Where to get more information
Table 1-9
Symantec product information resources (continued)
Resource
Description
Location
Symantec
Connect
An online resource that
contains forums, articles,
blogs, downloads,
events, videos, groups,
and ideas for users of
Symantec products.
http://www.symantec.com/connect/endpoint-management/forums/
endpoint-management-documentation
Here is the list of links to various groups on Connect:
■
■
■
■
■
■
■
■
■
■
■
Deployment and Imaging
http://www.symantec.com/connect/groups/deployment-and-imaging
Discovery and Inventory
http://www.symantec.com/connect/groups/discovery-and-inventory
ITMS Administrator
http://www.symantec.com/connect/groups/itms-administrator
Mac Management
http://www.symantec.com/connect/groups/mac-management
Monitor Solution and Server Health
http://www.symantec.com/connect/groups/monitor-solution-and-server-health
Patch Management
http://www.symantec.com/connect/groups/patch-management
Reporting
http://www.symantec.com/connect/groups/reporting
ServiceDesk and Workflow
http://www.symantec.com/connect/workflow-servicedesk
Software Management
http://www.symantec.com/connect/groups/software-management
Server Management
http://www.symantec.com/connect/groups/server-management
Workspace Virtualization and Streaming
http://www.symantec.com/connect/groups/
workspace-virtualization-and-streaming
27
Section
1
Getting Started with
Software Management
■
Chapter 2. Implementing Software Management Framework
■
Chapter 3. Implementing Software Management Solution
Chapter
2
Implementing Software
Management Framework
This chapter includes the following topics:
■
Introducing Software Management Framework
■
Implementing Software Management Framework
■
Setting up the Software Library
■
Configuring the Software Library
■
Scheduling a Clean up File Resources task
■
Running a Clean up File Resources task
■
Adding descriptions to installation error codes
■
Defining known-as wildcards
■
Editing or deleting a known-as association
■
Populating the Software Catalog
Introducing Software Management Framework
Before you implement Software Management Framework, it is a good idea to better
understand its components, benefits, and other useful information.
To help you get more familiar with Software Management Framework you can refer
to the following:
■
The Software Catalog component of Software Management Framework
See “About the Software Catalog” on page 30.
Implementing Software Management Framework
Introducing Software Management Framework
■
The benefits of the Software Catalog to software management
See “Benefits of the Software Catalog” on page 31.
■
Simplifying software-related actions with user roles
See “About the separation of software-related user roles” on page 32.
■
The Software Library component of Software Management Framework
See “About the Software Library” on page 33.
■
The benefits of the Software Library to software management
See “Benefits of the Software Library” on page 35.
About the Software Catalog
The Software Catalog is a component of Software Management Framework, which
is part of the Symantec Management Platform.
See “About Software Management Framework” on page 13.
See “Components of Software Management Framework” on page 18.
The Software Catalog is a centralized model of the software that is known in your
organization, regardless of where the software is installed. The Software Catalog
does not contain any software. Instead, it contains the data that describes the
software. If a package is associated with the software, the Software Catalog also
points to the source of the package file.
The Software Catalog provides a common way to describe software so that all
software-related actions can identify it accurately.
In ITIL terms, the Software Catalog represents a portion of a Configuration
Management Database (CMDB). A software resource that is defined in the Software
Catalog is equivalent to a configuration item (CI).
We recommend that you define in the Software Catalog all the software that you
need to manage. Typically, you need to manage the software that is approved for
installation in your organization. You manage approved software to ensure that is
installed properly and it remains in the correct state.
You might also decide to manage the software that is not approved for installation
in your organization. You might not think that unsupported software needs to be
managed. However, you might want to do so to ensure that it is never installed. For
example, you can define game software or certain peer-to-peer applications in the
Software Catalog. Then you can check the client computers for that software and
uninstall it when it is found.
The Software Catalog eliminates the need to perform software-related tasks manually
and lets you define the software resources and rules that can automate those tasks.
See “Benefits of the Software Catalog” on page 31.
30
Implementing Software Management Framework
Introducing Software Management Framework
Benefits of the Software Catalog
The initial time that you take to define your software in the Software Catalog results
in both immediate and long-term benefits. We recommend that you define in the
Software Catalog all the software that you need to manage.
See “About the Software Catalog” on page 30.
Table 2-1
Benefits of the Software Catalog
Benefit
Description
Ensures consistency
and accuracy
The Software Catalog reduces the risk of user errors because all the information about a
software resource is predefined.
Examples of how the software resource information can be used are as follows:
■
■
■
Users do not need to define the package and the command line every time they deliver
software. When users select a software resource instead of its packages or command
lines, they are less likely to act on the wrong software.
Users are less likely to miss dependencies and other associations between software
resources because the associations are defined in the Software Catalog.
The software resource’s unique identifier provides a consistent way to detect the software
on the client computers. Therefore, Inventory Solution can determine which managed
computers have specific software installed.
(Windows only) You can define a detection rule that contains additional information about
the software and makes the detection process even more accurate.
Promotes efficiency
You can define a software resource one time and use it many times. Even non-administrators
can perform the routine tasks that are associated with managing the software on the client
computers. Then the administrators can focus on the software tasks that have more advanced
requirements
Simplifies software
-related actions
The Software Catalog separates the software-related information from the actions that are
taken on the software. The software experts can define the software resources and make
decisions about their packages, command lines, dependencies, and other properties. The
users who perform the software tasks only need to know which software resource to select
and what action to perform. This separation of roles means that a non-administrator, such
as a technical support person, can easily deliver a patch or update when needed.
See “About the separation of software-related user roles” on page 32.
31
Implementing Software Management Framework
Introducing Software Management Framework
Table 2-1
Benefits of the Software Catalog (continued)
Benefit
Description
Facilitates automation
Because the Software Catalog simplifies software-related actions, it becomes easy to
automate them.
Examples of some of the software-related actions that you can automate are as follows:
■
■
Delivering for compliance and remediation
With Software Management Solution, you can create a policy that delivers software and
verifies that it remains in the correct state after installation. The policy uses the information
in the Software Catalog to check the software on the client computer and to reinstall the
software when necessary.
See “Performing an advanced software delivery” on page 189.
Delivering software through the Software Portal
With Software Management Solution, end users can request software through a
Web-based portal and install it on their computers with little or no outside intervention.
The administrator decides what software each user or group of users is allowed to install
and specifies which software requires approval. That information is defined in the Software
Catalog. If the software is pre-approved, it is installed when the user creates the request.
See “About the Software Portal” on page 197.
About the separation of software-related user roles
Software Management Framework lets you separate the software-related roles in
your organization. In a small organization, the same person or persons might assume
both roles. However, in a larger enterprise, you can let your most knowledgeable
administrators perform the more advanced tasks.
See “About the Software Catalog” on page 30.
See “About the Software Library” on page 33.
32
Implementing Software Management Framework
Introducing Software Management Framework
Table 2-2
Software-related user roles
Role
Description
Administrators who manage
the information in the
Software Catalog
These administrators act as the software librarians. A software librarian is an expert
on the software that your organization uses. The software librarian typically spends
more time on critical software issues and little or no time on day-to-day software tasks.
The primary responsibilities of the software librarian are as follows:
■
Add software resources to the Software Catalog.
■
Add package files to the Software Library.
■
■
Monitor and edit the software resources that internal and external processes add
to the Software Catalog. For example, from Software Discovery scans.
Ensure that each software resource contains the information and logic that is
required to install successfully. For example, package resources, command lines,
associations, detection rules, and file resources.
Distribute package files to package servers.
■
In Software Management Solution, make software available to the Software Portal.
■
Administrators and
non-administrators who
perform software-oriented
tasks such as software
delivery, software inventory,
or patch installation
These administrators do not need to know all the details about the software. They only
need to know which software resource to act upon and what action to take.
For example, help desk employees can quickly deliver an update by selecting the
correct software resource from the Software Catalog. They do not need to find the
correct package file and determine the command line to run it. As a result, you free
your software administrators to focus on more complex delivery tasks.
About the Software Library
The Software Library is a component of Software Management Framework, which
is part of the Symantec Management Platform.
See “About Software Management Framework” on page 13.
See “Components of Software Management Framework” on page 18.
In ITIL terms, the Software Library is equivalent to a Definitive Software Library
(DSL).
The Software Library is a secure directory that is the centralized repository of the
definitive, authorized versions of the software that your organization manages. It
is the physical source for your managed packages. A package that is sourced from
the Software Library is referred to as a managed package. Each package that is in
the Software Library has a unique signature that helps to maintain the integrity of
the data in the library. You place packages in the Software Library to ensure that
external users cannot change the packages after they have been approved for
rollout in your environment.
33
Implementing Software Management Framework
Introducing Software Management Framework
See “Benefits of the Software Library” on page 35.
Each package is associated with a software resource. A software resource whose
packages are sourced from the Software Library is referred to as managed. A
software resource whose packages are not sourced from the Software Library is
referred to as unmanaged. For example, the packages of an unmanaged software
resource might be on an unsecured network share or a local hard drive.Before you
can place a package in the Software Library, you must create a software resource
and associate the package with it.
Symantec recommend that you source all your packages from the Software Library.
The only packages that are not associated with software resources are as follows:
■
Packages that are added when you create a Package Delivery task in Software
Management Solution and source the package from the Software Library.
■
Packages that are added as a result of a migration from Software Delivery
Solution 6.x to Software Management Solution 7.5.
The only correct ways to add package files to the library are through Software
Management Framework as follows:
Automatically
Package files can be added to the Software Library automatically when
you import a package file to create a software resource.
See “Importing a package to create a software resource” on page 51.
If you have a data provider that lets you import software resources and
their associated software packages, you can create a schedule for the
import. When the import runs, it can import any available software
resources and the software packages that are associated with those
software resources. The software packages are imported into the
Software Library.
See “Importing data from a data provider” on page 107.
Manually
When you manually associate a package with a software resource, you
can choose to add the package file to the Software Library.
See “Associating a package with a software resource” on page 78.
If you have a data provider that lets you import software resources and
their associated software packages, you can manually import specific
software packages. You gather a list of software resources that are
available for import. You then select from this list the specific software
resources that you want to import from this data provider. When you
import a software resource, you can also import its associated software
package into the Software Library.
See “Importing data from a data provider” on page 107.
34
Implementing Software Management Framework
Introducing Software Management Framework
Do not add package files directly to the Software Library directory on the file system.
To do so prevents the proper associations from being made and compromises the
integrity of the Software Library. You need to secure the Software Library directory
so that only the application identity of Notification Server has access. The application
identity of Notification Server is the account that is used to access Notification
Server. Do not give directory access to any other users.
Each Software Library is associated with a single Symantec Management Platform
installation.
See “Setting up the Software Library” on page 38.
Benefits of the Software Library
The Software Library is a secure directory that is the centralized repository of the
definitive, authorized versions of the software that your organization manages. A
package that is sourced from the Software Library is referred to as a managed
package.
The Software Library puts you in control of your software packages. You no longer
have to keep track of which folders contain which packages, or which package is
the correct version. You no longer have to worry that someone might accidentally
or deliberately tamper with a package. Instead, you can let the Software Library
manage your packages so that you can spend your time more productively.
We recommend that you source all your packages from the Software Library.
See “About the Software Library” on page 33.
Table 2-3
Benefit
Benefits of the Software Library
Description
Secures your software assets You can secure the Software Library so that only Symantec Management Platform
operations can access it, and only authorized administrators can perform those
operations. Unauthorized users are prevented from making any changes to the managed
packages.
Centralizes your software
assets
When you store all your packages in the Software Library, you always know where
your physical packages are. You no longer have to keep track of which folders contain
which packages, or which package is the correct version.
Ensures that package servers When you distribute a managed package to package servers, the signature of the
contain the correct versions package on the servers is periodically compared to the original package’s signature.
of packages
If the signatures do not match, the package on the package server is replaced with the
approved version.
35
Implementing Software Management Framework
Implementing Software Management Framework
Table 2-3
Benefits of the Software Library (continued)
Benefit
Description
Ensures that the correct
versions of packages are
delivered
When a package is delivered, a snapshot of the package is created on the client
computer and compared to the snapshot on the package server. If the snapshots do
not match, it is possible that some kind of interception has occurred and corrupted the
package. In that case, the package is re-downloaded.
If the package is already on the client computer because of a recurring delivery or a
delivery re-attempt, its existing snapshot is used for comparison. If a mismatch occurs,
the package is re-downloaded.
The ability to deliver software is available if Software Management Solution is installed.
Implementing Software Management Framework
Because Software Management Framework is part of the Symantec Management
Platform, you do not need to perform a separate installation or configuration.
However, before you use Software Management Framework, you must set it up
and prepare it for use.
Before you implement Software Management Framework, you should become
familiar with its components, benefits, and other useful information.
See “Introducing Software Management Framework” on page 29.
36
Implementing Software Management Framework
Implementing Software Management Framework
Table 2-4
Process for implementing Software Management Framework
Step
Action
Description
Step 1
Install the Symantec Management
Agent to manage client computers
and install the Software
Management Framework Agent.
A managed computer is the one on which the Symantec
Management Agent is installed. The Symantec Management Agent
is the software that establishes communication between the
Notification Server computer and the computers in your network.
The Software Management Framework agent is installed on the
client computers along with the Symantec Management Agent.
Therefore, separate installation and configuration are unnecessary.
The Symantec Management Console does not contain a user
interface for viewing, installing, or configuring the agent.
The Software Management Framework agent runs on the client
computers to perform the following functions:
■
■
■
■
Manage the agent and plug-in rollout technology for the
Symantec Management Platform.
Perform the Software Discovery scan in Software Management
Framework.
Software Discovery scans managed computers and collects
information about the Windows software that they contain.
See “Discovering software on managed computers”
on page 54.
Create and update a client-side software cache that keeps
track of the software that is installed and discovered on the
client computer.
Manage all the software delivery functions in Software
Management Solution.
Software deliveries are closely integrated with the software
resources in the Software Catalog. The Software Management
Framework agent manages the package downloads and other
aspects of software delivery.
You may have performed this step when you installed Notification
Server or when you added new computers to the network.
Step 2
Configure security roles for
Administrators need the appropriate privileges to manage the
Software Management Framework. packages in the Software Library and the software resources in
the Software Catalog.
Step 3
Set up the Software Library.
The Software Library is the physical source for your managed
packages. Set up a library directory for each server installation.
See “Setting up the Software Library” on page 38.
37
Implementing Software Management Framework
Setting up the Software Library
Table 2-4
Process for implementing Software Management Framework
(continued)
Step
Action
Description
Step 4
(Optional) Configure settings for
managing the Software Catalog
and its contents.
You can configure the following settings for Software Management
Framework:
Step 5
■
Clean up File Resources
Periodically delete any files that might be left in the database
after file resources are deleted.
■
Known-As
Use known-as associations to associate the unique identifiers
of two software resources so that they are identified as being
the same software
■
Installation Error Code Descriptions
Associate informative descriptions with the installation error
codes that appear on reports.
Populate the Software Catalog with The software resources that you plan to manage must be defined
software resources.
in the Software Catalog.
A software resource provides a common way to describe the
software so that all software-related actions can identify it
accurately. The software resource data is stored in the Software
Catalog.
See “Populating the Software Catalog” on page 46.
Setting up the Software Library
The Software Library is a secure directory that is the centralized repository of the
definitive, authorized versions of the software that your organization manages. Each
Software Library is associated with a single server installation.
Warning: After you begin to populate the Software Library, do not move the directory
or the packages that it contains. If you move the packages, you break all the
references to those packages in existing policies. The only safe way to relocate the
Software Library is through the Symantec Management Console.
38
Implementing Software Management Framework
Configuring the Software Library
Table 2-5
Process for setting up the Software Library
Step
Action
Description
Step 1
Calculate the disk space
requirement.
The size and the number of the packages in your organization determine
the amount of free disk space that the Software Library requires. To
determine your disk space requirement, multiply the average size of
your packages by the number of packages that you plan to manage.
Step 2
Create the Software Library
directory.
Locate the directory on a shared drive that has sufficient disk space
and that is accessible from the current Symantec Management Platform
installation.
Step 3
Configure the directory’s
security settings.
In Windows Explorer, in the directory’s Properties dialog box, edit the
sharing settings and security settings as follows:
Step 4
Configure the Software
Library.
■
Share the directory.
■
Set the security levels on the directory.
Give full control to the application identity of Notification Server. The
application identity of Notification Server is the account that is used
to access Notification Server. You specify the appropriate user name
and password when you install Notification Server.
To prevent unauthorized changes to the packages in the Software
Library, do not give directory access to any other users.
To let the Symantec Management Platform products access the
Software Library, point to the location of the library from Software
Management Framework. You can also configure the number of seconds
to wait before a server timeout occurs. You can increase the timeout
value if you encounter problems when you manage a package that
contains large files.
See “Configuring the Software Library” on page 39.
See “About the Software Library” on page 33.
Configuring the Software Library
The Software Library is a secure directory that is the centralized repository of the
definitive, authorized versions of the software that your organization manages. A
package that is sourced from the Software Library is referred to as a managed
package. To let the Symantec Management Platform products access the Software
Library, configure its location by using Software Management Framework.
This task is part of the process for setting up the Software Library.
See “Setting up the Software Library” on page 38.
39
Implementing Software Management Framework
Configuring the Software Library
Warning: After you begin to populate the Software Library, do not move the directory
or the packages that it contains. If you move the packages, you break all the
references to those packages in existing policies. The only safe way to relocate the
Software Library is through the Symantec Management Console.
To configure the Software Library
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Software Library Configuration.
3
On the Software Library Configuration page, type the full UNC path to the
shared directory that represents the Software Library.
For example, \\computer_name\swlibrary
Note: Ensure that you configure the directory’s security settings to give full
control to the application identity of Notification Server.
4
Click Validate to verify that the path is valid.
5
(Optional) Change the timeout value.
The timeout value is the number of seconds to wait before a server timeout
occurs when you manage a package in the Software Library. If you encounter
problems when you manage a package that contains large files, increase this
value.
6
To save the configuration settings, click Save changes.
40
Implementing Software Management Framework
Scheduling a Clean up File Resources task
7
8
If a Software Library that contains packages already exists in a different location,
in the Managed packages exist dialog box, click one of the following options,
and then click OK:
Migrate existing
packages
Moves the existing packages from the old Software Library
folder to the new one. The migration also changes the
packages’ source paths in any existing policies or tasks that
refer to those packages.
Convert existing
packages
Leaves the packages in the old Software Library folder and
marks them as UNC-sourced. The conversion also changes
the packages’ source paths in any existing policies or tasks
that refer to those packages. The new source path is the
UNC path of the old Software Library.
Change existing
packages
Points packages already existing in the library to a new
Software Library path. This option implies that all packages
from the previous location were manually copied or already
exist in the new Software Library path.
Close the Software Library Configuration page.
See “About the Software Library” on page 33.
Scheduling a Clean up File Resources task
The Clean up File Resources task lets you delete the files that remain after an
internal or third-party product deletes software from the Software Catalog. By default,
the Clean up File Resources task is scheduled to run every week. You cannot
change the default task, but you can create a new instance of the task that contains
a different schedule. Each time you define a new schedule, a new instance of the
task appears.
The Clean up File Resources task runs on the Notification Server computer but not
on the client computers.
To schedule a Clean up File Resources task
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Clean up File Resources.
3
On the Clean up File Resources page, in the Task Status section, select a
task and click New Schedule.
4
In the New Schedule dialog box, define the schedule and click Schedule.
41
Implementing Software Management Framework
Running a Clean up File Resources task
5
Close the Clean up File Resources page.
Running a Clean up File Resources task
The Clean up File Resources task lets you delete the files that remain after an
internal or third-party product deletes software from the Software Catalog. By default,
the Clean up File Resources task is scheduled to run every week. If you edited the
task schedule, additional instances of the task might exist. You can run the default
task or any of the other tasks immediately.
See “Scheduling a Clean up File Resources task” on page 41.
You can run any Clean up File Resource tasks immediately, including those that
have run and those that are scheduled to run in the future. For example, the default
task is scheduled to run weekly but you decide to run it two days before its scheduled
start date.
You can also re-run any task that is completed.
When you run any task, a new instance of that task appears on the Clean up File
Resources page. When the task finishes, a check mark appears to the left of the
task name.
To run a Clean up File Resources task
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Clean up File Resources.
3
On the Clean up File Resources page, right-click a task and click Start Now.
Adding descriptions to installation error codes
You can add or edit descriptions of the numeric error codes that are returned when
a software installation on a managed computer produces an error.
Some error code descriptions are predefined. Create additional descriptions if the
predefined descriptions do not meet your needs.
When a software installation on a managed computer produces an error, the resulting
reports typically display a numeric error code. To eliminate the need to look up the
error code when you run a report, you can associate an informative description with
the error code. Thereafter, the reports display the description instead of the numeric
code.
Examples of how you can use the installation error code descriptions are as follows:
42
Implementing Software Management Framework
Defining known-as wildcards
■
A task that runs a Windows Installer installation fails and returns a numeric error
code. The error number is not a standard Windows Installer error. Upon
investigation, you learn that the error originates from a custom action in the MSI
file. You can add that error number and its description so that future reports
display the description.
■
A proprietary type of installation EXE returns its own set of error codes. If you
know the meaning of the numeric codes, you can add their descriptions.
Error code descriptions are predefined for Windows Installer installations. Other
installation types might also have predefined error code descriptions. If a description
is not defined for a particular error code, the numeric code appears on the reports.
Errors that appear to the end user always appear as numeric codes even if you
define their descriptions.
To add descriptions to installation error codes
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Installation Error Code Descriptions.
3
On the Installation Error Code Descriptions page, click Add or Edit.
4
In the Add or Edit Installation Error Code dialog box, add or edit the error
code information.
Because the error codes are saved as integers, the leading zeroes are dropped.
For example, if you enter 0050 the error code is saved as 50.
For more information about the options, click the page and then press F1
5
Click OK.
6
Close the Installation Error Code Descriptions page.
Defining known-as wildcards
Known-as associations let you associate the software resources that are similar
but have variations in their company names or software names. When you set up
the known-as associations, you define a wildcard for a specific known-as name.
When a new software resource is added to the Software Catalog, it is compared
to the known-as wildcards. If a wildcard match is found, the company name or the
software resource name is changed to the known-as name for that wildcard.
Create any necessary known-as associations before you begin to populate the
Software Catalog or as soon as you find duplications. New known-as associations
do not affect existing software resources.
43
Implementing Software Management Framework
Defining known-as wildcards
When software resources originate from multiple sources, their company names
and software names can be inconsistent. Normally, if two software resources are
identical but their identifying information is different, they are considered to represent
different software. You can create known-as associations and wildcards to associate
two software resources so that they are identified as being the same software. The
known-as associations help you to identify software resources accurately.
You can create known-as associations for a company or a software resource as
follows:
Company
During the import of a package, its company name is compared
to the company wildcards. If a wildcard match is found, the
company name in the new software resource is changed to the
known-as company name for that wildcard.
For example, you associate the wildcard expression Symantec*
with Symantec Corporation. When you import any software
resource whose company name is Symantec, Symantec Corp.,
or any other variation, its company name is changed to Symantec
Corporation.
Software
During the import of a package, its name is compared to the
software known-as wildcards. If a wildcard match is found, the
name of the new software resource is changed to the software
resource name for that wildcard.
For example, you might create a wildcard to replace MS Office
with Microsoft Office.
Warning: Be sure to make the wildcard restrictive enough.
Otherwise, you might associate multiple software resources that
have the same name but do not represent the same software. For
example, the wildcard MS Office* changes MS Office Standard,
MS Office Professional, and Microsoft Office Enterprise to the
same name. Such associations can cause problems with the
software identification.
The unique identifiers of the associated software resources are not changed even
when their company names or software names change.
The wildcard checks and associations occur when software resources are added
to the Software Catalog from the Import wizard or from the Software Discovery
scan. When you create a new known-as wildcard, existing software resources are
not affected even if they match the wildcard.
When you resolve duplicate software resources, the association that is created
appears in the Known As Mappings list.
See “Resolving duplicate software resources” on page 60.
44
Implementing Software Management Framework
Editing or deleting a known-as association
You cannot create a known-as association between software resources or company
names except through the wildcard matching. However, you can edit and delete
existing known-as associations.
See “Editing or deleting a known-as association” on page 45.
To define known-as wildcards
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Known-As.
3
On the Known-As page, in the Resource Type drop-down list, select the type
of item to define a known-as association or wildcard for.
4
Under the Wildcards section, click Add.
5
In the Add or Edit Known-As Wildcard dialog box, enter the name to associate
the software resource with and the wildcard, and then click OK.
The wildcard must follow regular expression syntax.
For more information about the options, click the page and then press F1
6
Close the Known-As page.
Editing or deleting a known-as association
Known-as associations let you associate the software resources that are similar
but have variations in their company names or software names. You can edit or
delete existing known-as associations to correct association errors. For example,
if a wildcard is too broadly defined, the known-as associations for certain software
resources can be incorrect.
To edit or delete a known-as association
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Known-As.
3
On the Known-As page, in the Resource Type list, select the type of
association to edit or delete.
4
In the Known As Mapping section, select an association and click Change
Mapping.
45
Implementing Software Management Framework
Populating the Software Catalog
5
In the Select Company dialog box or the Select Software dialog box, select
a new name to associate the software resource with and click OK.
6
Close the Known-As page.
Populating the Software Catalog
The software resources that you plan to manage must be defined in the Software
Catalog.
See “About the Software Catalog” on page 30.
You can use any of several methods to add software resources to the Software
Catalog. You do not have to use all the population methods, and you do not have
to use them in any particular order.
By default, the Software Catalog contains predefined software resources for some
of the agents and plug-ins. The products that you have installed determine which
agents and plug-ins appear in the Software Catalog. You can use these software
resources to roll out the agents.
Table 2-6
Methods for populating the Software Catalog
Method
Description
When to use
Inventory policy
Software inventory tasks or policies scan the
target computers for the available applications
and report the collected information to the
Software Catalog.
Symantec recommends that when you have
Inventory Solution installed, that using an
Inventory policy is the preferred method. This
method also lets you identify what software
is installed on client computers.
You must have Inventory Solution installed
to use the Inventory policies.
If you have administrator rights and want to
deliver discovered software on additional
computers you can use the current
discovered software resources. You can add
an installation package and a command line
to the discovered software resource to make
it deliverable. You can then deliver the
package with Managed Delivery or Quick
Delivery or publish it to the Software Portal.
46
Implementing Software Management Framework
Populating the Software Catalog
Table 2-6
Methods for populating the Software Catalog (continued)
Method
Description
When to use
Import from installation
file or package
Imports information from a package file to
When you want to quickly create a software
create a new software resource or add to an resource for a package. This method is most
existing software resource.
effective when you import a supported file
type because it creates the software
The Import Software wizard simplifies the
resource’s command lines.
software resource creation and the package
definition.
Also use this method when you want to add
a package resource or command lines to an
See “Importing a package to create a
existing software resource that does not have
software resource” on page 51.
them.
You can then deliver the package with
Managed Delivery or Quick Delivery or
publish it to the Software Portal.
Add a software resource Adds the software resource and its
manually.
information manually.
When the software resource contains a
command line but not a package. For
example, a command line that uninstalls a
See “Adding or editing a software resource”
package that is already on the client
on page 75.
computer.
Also use this method when you need to
deliver a package and you want to take
advantage of the benefits of Managed
Delivery. You can quickly create a software
resource for the package with a minimum of
details as follows: the identifying information,
the reference to the package resource, and
an installation command line. You can take
the time to add more information to the
software resource after you deliver it.
Managed Delivery is available if Software
Management Solution is installed.
Symantec recommends that if you do not
have much experience with command lines
it is better to use an automated import method
instead. If you add a software resource
manually, you should test the command lines
carefully. By testing, you can avoid rolling out
badly configured command lines.
47
Implementing Software Management Framework
Populating the Software Catalog
Table 2-6
Methods for populating the Software Catalog (continued)
Method
Description
When to use
Perform a Software
Discovery scan.
Collects the information about the software
resources that are installed on managed
computers and the files that are associated
with the software. The software resource
information is added to the Software view
and appears in the Newly Discovered
Software list.
When Inventory Solution is not installed you
may use the Software Discovery to gather
information about the software that is installed
on client computers.
See “Discovering software on managed
computers” on page 54.
By default, the Software Discovery policy is
scheduled to run two times per week on all
the computers that contain the Software
Management Framework agent. However,
you can run the Software Discovery policy at
any time, on any managed computers that
contain the Software Management
Framework agent.
The scan can create the software resources
with the minimum metadata : the company
(vendor) name, software name, and version.
Then you can add the package resources
along with the other software resource
information as needed.
Software Discovery gathers only a part of the
data from Software Inventory task or policy.
For this reason, Symantec recommends that
you gather software inventory using an
Inventory policy instead.
Note: If you have Inventory Solution installed
the Software Discovery scan is disabled.
If you have administrator rights and want to
deliver discovered software on additional
computers you can use the current
discovered software resources. You can add
an installation package and a command line
to the discovered software resource to make
it deliverable. You can then deliver the
package with Managed Delivery or Quick
Delivery or publish it to the Software Portal.
48
Implementing Software Management Framework
Populating the Software Catalog
Table 2-6
Methods for populating the Software Catalog (continued)
Method
Description
When to use
Assign migrated
Software Delivery
Solution 6.x software
packages to software
resources (if Software
Management Solution is
installed).
Assigns migrated 6.x software packages to After you migrate the 6.x software package.
software resources to make them compatible
You can then deliver the package with
with the delivery methods of Software
Managed Delivery or Quick Delivery or
Management Solution.
publish it to the Software Portal.
When you assign a 6.x package to a software
resource, you can assign it to an existing
software resource or create a new software
resource. If you assign a software package
to an existing software resource, the data of
the software package is added to the software
resource.
Import from a data
provider.
Imports data from a data provider to create
or update software resources in the Software
Catalog. The amount of information that the
resulting software resources contain depends
on what the data provider includes. To import
data from a data provider, you must install
the product that lets you connect to the data
provider.
When you have a data provider that lets you
import software resources. Those responsible
for distributing software can then easily
deliver and manage these software
resources.
Precedence settings determine if a data
provider can update the data that is in the
Software Catalog.
Introducing software resources
A software resource consists of the metadata that describes a specific instance of
a software application. For example, Norton Internet Security 2008 - English.
A software resource represents a common way to describe the software so that all
software-related actions can identify it accurately. The software resource data
resides in the Software Catalog. You create and manage the software resources
in Software Management Framework.
In ITIL terms, the Software Catalog represents a portion of a Configuration
Management Database (CMDB). A software resource that is defined in the Software
Catalog is equivalent to a configuration item (CI).
See “About the Software Catalog” on page 30.
49
Implementing Software Management Framework
Populating the Software Catalog
Table 2-7
Metadata that describes a software resource
Metadata
Description
Properties
The properties that identify a software resource. The minimum amount of data that is required
to create a software resource is its company (vendor) name, software name, and version.
Type
The software resource types are as follows:
■
Software release
■
Service pack
■
Software update
Package resources
A package resource is an association with the physical package or packages that install the
software. A package consists of the files that Software Management Solution uses to install
the software on the client computers.
Command lines
The command lines that are associated with a software resource determine what occurs
after the software resource is delivered to the client computer. For example, a command
line can install or uninstall the software.
Detection and
applicability rules
Detection rules and applicability rules help the software-related operations to identify software
accurately. A detection rule determines whether a specific instance of a software application
is installed on a client computer. An applicability rule determines whether a client computer
has the correct environment for an installation of the software.
Warning: UNIX, Linux, and Mac OS operating systems do not support detection and
applicability rules; therefore, do not add them to non-Windows software resources. When
you add rules to non-Windows software resources, the rules are always evaluated as false,
which can cause errors in your software-related operations.
Associations
The associations between software resources define relationships such as dependency and
supersedence.
File resources
(Windows only) File resources are associations with the important physical files that the
software resource installs. File resources typically represent EXE or DLL files. The detection
rules can use the file resources to determine whether the software is installed on a client
computer.
Unique identifier
The package resource’s unique identifier provides consistency in the way that Notification
Server identifies specific software.
A deliverable software resource is one that can be delivered to and installed on
client computers. To be deliverable, the software resource’s type must be software
release, service pack, or software update. Also, the software resource must be
associated with a package, a command line, or both.
50
Implementing Software Management Framework
Populating the Software Catalog
You need to make software resources deliverable only if you plan to use Software
Management Solution to deliver the software.
See “Assigning a type to a software resource” on page 59.
See “Associating a package with a software resource” on page 78.
See “Creating a command line for a software resource” on page 81.
Examples of deliverable software resources are as follows:
■
A package and several command lines to run the package.
■
A Word template that is placed in a directory on the client computer but does
not require installation.
■
A command line that uninstalls a package that is already on the client computer.
Importing a package to create a software resource
You can import information from a package to create a new software resource or
add a package association to an existing software resource.
Use the Import Software wizard when you want to quickly create a software resource
for a package. This method is most effective when you import a supported file type,
because it creates the software resource’s command lines. Also use this method
when you want to add a package resource or command lines to an existing software
resource that does not have them.
You can create a software resource for any type of installation file. By default,
Software Management supports several installation types, which means that it can
collect more information from installation files of those types.
For example, when you import an installation file, the software resource is created
in the Software Catalog. Its company (vendor) name, software name, and version
are defined and its package is added to the Software Library. When you import a
supported installation file type, the default command lines are created also.
Table 2-8 lists the installation file types that are supported for Windows operating
systems.
Table 2-9 lists the installation file types that are supported for the UNIX, Linux, and
Mac operating systems.
Table 2-8
Installation file types for Windows
Installation file
type
Description
BAT, CMD
A Windows batch installation file.
51
Implementing Software Management Framework
Populating the Software Catalog
Table 2-8
Installation file types for Windows (continued)
Installation file
type
Description
JS, VBS
A Windows script installation file.
EXE
An executable file. In this context, the EXE must be an installation file
such as Setup.exe.
MSI
A distributable installation database that Microsoft Windows Installer
runs on the destination computer.
VSA, XPF
A portable virtual software layer, which installs one or more
Windows-base applications or sets of data.
See “About VSA and XPF virtual package files” on page 127.
Table 2-9
Installation file types for UNIX, Linux, and Mac OS
Installation file
type
Description
BZ2
A compressed archive file that installs UNIX, Linux, or Mac OS software.
DEPOT
A software depot for HP-UX.
GZ
A compressed archive file that installs UNIX, Linux, or Mac OS software.
PKG
A package of compressed installation files for Mac OS X. It must be
archived. For example, with TAR.GZ.
RPM
A package file that contains the software that Red Hat Package Manager
(RPM) can install. RPM is a command line driven package management
system that installs uninstalls, verifies, queries, and updates Linux
software packages.
RTE
A native software installation package for AIX.
SUN PKG
A native software installation package for Sun OS.
TAR, TAR.BZ2,
TAR.GZ, TAR.Z
A TAR file is an archive file that consists of one or more files and installs
UNIX, Linux, or Mac OS software. A TAR.BZ2, TAR.GZ, or TAR.Z file
is a compression of a TAR file.
Z
A UNIX compressed file.
ZIP
A compressed archive file that installs UNIX, Linux, or Mac OS software.
During the import, the ID of the new software resource is compared to the IDs of
the existing software resources. If the new software resource matches an existing
52
Implementing Software Management Framework
Populating the Software Catalog
software resource, you can associate the new package and any related information
with the existing software resource. For example, the Software Catalog can contain
a software resource that is not yet associated with a package. Later, you can import
the package and add it to the existing software resource.
A software resource might not be associated with a package for one of the following
reasons:
■
A Software Discovery scan created the software resource with the software
information that it found on a client computer.
■
A data provider supplied the software resource without an associated software
package.
The software resource’s unique identifier provides consistency in the way that
Notification Server identifies specific software. Software delivery, discovery, and
usage actions are based on the software identifier. As a result, you are assured
that their data is associated with the correct software resources.
Typically, the main components of the unique identifier are the software resource’s
company (vendor) name, software name, and version. The unique identifier can
also contain additional information. For example, if the software is language-specific,
the language code is included. If the software is targeted for a specific architecture
such as x86, the architecture type is included.
To import a package to create a software resource
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, on the Installed Software subpane, right-click Installed
Software and select Import Software.
3
On the Import Software: Specify Software page, select the package to import.
For more information about the options, click the page and then press F1
4
Click Import.
5
On the Import Software: Software Details page, review the information that
was obtained from the package that you imported and make changes if
necessary.
For more information about the options, click the page and then press F1
6
Click OK.
53
Implementing Software Management Framework
Populating the Software Catalog
Note: When importing software packages using Import Software wizard, package
files can be read by an unauthorized party during data transfer from package store
to the Notification Server server. If package files contain sensitive information, such
as passwords inside scripts, in unencrypted form, then such software import can
be a subject to information disclosure threat.
Discovering software on managed computers
Software Discovery scans managed computers and collects information about the
software and the related files that they contain. By default, the Software Discovery
policy is scheduled to run two times per week on all the computers that contain the
Software Management Framework agent. However, you can run the Software
Discovery policy at any time, on any managed computers that contain the Software
Management Framework agent.
Any client computer that has the Symantec Management Agent also has the
Software Management Framework agent because they are installed together.
Software Discovery performs a basic software discovery on targeted computers.
To perform a more detailed software inventory, you can run the Collect Full
Inventory policy that is provided with Inventory Solution.
For more information, see topics about software inventory in the Altiris Inventory
Solution™ from Symantec™ User Guide.
Note: If you have Inventory Solution installed, the Software Discovery policy is
switch off by default, because the Collect Full Inventory policy is available instead.
Perform Software Discovery scans for the following reasons:
■
To determine what software is installed on the managed computers that are in
your organization.
You can use this information to track software licenses and assets.
■
To add new software resources or update existing software resources for the
installed software.
■
To obtain information about the critical files that are installed with the software
and associate that file information with the appropriate software resource.
Use this file information in the software resource’s detection rule, which
determines whether that specific software is installed on a computer. For
example, in Software Management Solution, a Managed Delivery policy installs
software only if its detection check determines that the software is not already
installed.
54
Implementing Software Management Framework
Populating the Software Catalog
Table 2-10
Where Software Discovery finds information on the client computer
Source
Description
Registered MSI files
Software Discovery reads information in the registered MSI files for installed software.
An MSI file provides the information to create a software resource and its file associations.
Typically, the MSI files provide information about the majority of Windows software that is
installed in your organization.
Add/Remove Programs Software Discovery reads the entries in Add/Remove Programs for the software’s company
entries
(vendor) name, software name, and version. The Add/Remove Programs entries provide
information about MSI software and non-MSI software.
Inventory cache entries When Managed Delivery and Quick Delivery install software, they record information about
from Managed Delivery the installed files in a cache on the client computer. This information is primarily useful for
and Quick Delivery
non-MSI installations.
This information is available only if Software Management Solution is installed.
Detection rules that are
on the client computer
for specific software
resources
Software Discovery evaluates the detection rules that it finds on the client computer to
determine if the software that the rules define is installed. A detection rule ensures that
Software Discovery can detect an installed software resource that is EXE-based and add it
to the Newly Discovered Software list.
The detection rules are placed on the client computer during the following processes:
■
■
When Managed Delivery installs a software resource.
Managed Delivery stores information about the software in a cache on the client computer.
Software Discovery collects the information from the cache.
This information is available only if Software Management Solution is installed.
When a Targeted Software Inventory policy runs for a specific software resource.
This information is available only if Inventory Solution is installed.
Table 2-11
Process for discovering software resources on managed computers
Step
Action
Description
Step 1
Configure the Software
Discovery policy.
The Software Discovery policy runs the scan on the client computers.
You cannot create multiple instances of the policy with different
schedules and destinations. Instead, you reconfigure the schedule and
destinations when you run the policy.
See “Configuring the Software Discovery policy” on page 57.
55
Implementing Software Management Framework
Populating the Software Catalog
Table 2-11
Process for discovering software resources on managed computers
(continued)
Step
Action
Description
Step 2
Review the inventory data
that is returned.
The options for reviewing the inventory data are as follows:
■
■
Step 3
Update the software
resources to facilitate future
inventory scans.
View the contents of the Newly Discovered Software list in the
Software view.
This folder displays the software resources that are marked as
installed, including those from previous Software Discovery scans.
If Inventory Solution is installed, run the Installed Software report.
This report lists the software resources that are marked as installed.
It also lists the computers on which the software is installed and the
installation dates. You can access the Installed Software report from
the Reports menu or from the right-click menu in the Software
Catalog.
The data that Software Discovery provides can make future inventory
scans more accurate.
Update the software resources in the following ways:
■
■
Resolve duplicate software resources.
Duplicate software resources can occur when Software Discovery
creates a new software resource for the software that is already
defined in the Software Catalog. Perhaps the company name in
each resource is slightly different.
See “Resolving duplicate software resources” on page 60.
Add the file resources to the software resource’s detection rule.
Software Discovery can add the file resources to a software resource
but it does not add those files to a detection rule. You can use those
file resources to create a detection rule or to update an existing
detection rule.
See “Adding file resources to a software resource manually”
on page 89.
56
Implementing Software Management Framework
Populating the Software Catalog
Table 2-11
Process for discovering software resources on managed computers
(continued)
Step
Action
Description
Step 4
Update the software
resources to make them
deliverable.
To be deliverable, a software resource must be assigned a type and it
must be associated with a package, a command line, or both.
This step applies only if you
plan to use Software
Management Solution to
deliver the software.
Make the software resources deliverable in the following ways:
■
■
■
Assign a type of software release, service pack, or software update
to the software resource.
See “Assigning a type to a software resource” on page 59.
Associate a package with a new software resource.
Software Discovery does not associate packages with the software
resources. If you have the package file, you can associate it with
the new software resource.
See “Associating a package with a software resource” on page 78.
Add a command line to the software resource.
See “Creating a command line for a software resource” on page 81.
Configuring the Software Discovery policy
The Software Discovery policy scans managed computers and collects information
about the software and the related files that they contain. The Software Discovery
scan is a step in the process for discovering software resources on managed
computers.
See “Discovering software on managed computers” on page 54.
The Software Discovery scan performs several tasks to collect information about
the software that is installed on client computers.
Table 2-12
Tasks that Software Discovery performs
Task
Description
Scans the client
computer.
Software Discovery evaluates several sources of inventory information on the client computer.
57
Implementing Software Management Framework
Populating the Software Catalog
Table 2-12
Tasks that Software Discovery performs (continued)
Task
Description
Collects the software
data.
For each instance of software that it finds, Software Discovery collects the following data:
■
■
■
■
■
The software’s unique identifier, which consists of the company (vendor) name, software
name, and version.
The MSI product code, for Windows Installer-based applications only.
The unique identifiers of the critical files that are installed with the software. Only EXE
files, DLL files, and OCX files are considered to be critical.
The unique identifier consists of the file’s name, hash value, and size. The file information
is collected only for MSI-based software and any software that was originally installed
with a Managed Delivery policy.
The GUID that identifies the computer resource in Notification Server.
The GUID that identifies the user resource in Notification Server, if the software was
installed per user.
Records the collected
data in a cache on the
client computer.
Software Discovery updates a cache on the client computer with the data that it collects.
Sends the data to the
server.
You can configure Software Discovery to send all software resources or only software
resources that changed since the last time the software inventory was collected. These
configuration options are in the Settings section of the Software Discovery policy.
Inventory Solution reads the cache when an inventory task scans a client computer. The
Software Discovery data makes future inventory scans more accurate because it provides
a way to positively identify a specific instance of software.
Updates the Software
For each instance of software that it finds, Software Discovery updates the Software Catalog
Catalog with the
as follows:
software resources and
■ Creates a new software resource or updates an existing one, depending on whether the
their associated file
found software’s identifier matches that of an existing software resource. Only the
resources.
metadata is created. Packages are not defined.
■ Associates the collected file resources with the software resource.
You can configure this policy to send all software resources or only software
resources that changed since the last time the software inventory was collected.
By default, the Software Discovery policy is scheduled to run two times per week
on all the computers that contain the Software Management Framework agent.
However, you can run the Software Discovery policy at any time, on any managed
computers that contain the Software Management Framework agent.
We recommend that you schedule the Software Discovery policy to run during a
maintenance window because the policy is processor intensive.
58
Implementing Software Management Framework
Populating the Software Catalog
To configure the Software Discovery policy
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Software Catalog and
Software Library Settings > Software Discovery.
3
On the Software Discovery page, in the Settings section, select whether to
send only the software resources that have changed or all software resources.
The option to send only the software resources that changed is selected by
default. Select the option to send all the software resources if some of the data
that was previously sent to the server has been lost. For example, sometimes
when the management of a client computer moves from one Notification Server
to another, the new server does not have this data.
4
In the Applied to section, select the destination resources to which to apply
the policy.
5
In the Schedule section, set the schedule.
6
At the upper right of the page, click the colored circle, and then click On.
7
Click Save changes.
Assigning a type to a software resource
An unassigned software resource is one that is not categorized as a software
release, an update, or a service pack.
An unassigned software resource is one that is not categorized as a software
release, an update, or a service pack. Most of the unassigned software resources
originate from the Software Discovery scans. The unassigned software resources
can also originate from other internal products or third-party products that add
software resources without specifying their types.
Warning: After you set the software resource type you cannot change it.
To assign a type to a software resource
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, in the Installed Software subpane, click Newly Discovered
Software.
59
Implementing Software Management Framework
Populating the Software Catalog
3
In the center pane, right-click a software resource and on the context menu,
click Actions > Assign Type.
Software that is managed or unmanaged does not appear in this list.
4
In the Assign Software Type dialog box, select the type to assign and click
OK.
The software resource types are as follows:
■
Software release
A full version of the software. Installation of a software release results in a
complete, operational instance of the software.
■
Service Pack
A collection or roll up of the updates and fixes that bring a software release
to a known state. A service pack does not represent a complete instance
of the software. It must be installed on a computer that already contains
the software release.
■
Software Update
A small number of changes that improve or fix a software release. A software
update does not represent a complete instance of the software. It must be
installed on a computer that already contains the software release.
Resolving duplicate software resources
Duplicate software resources occur when two software resources represent the
same software but have different identifiers. When you resolve duplicate software
resources, both of their unique identifiers are associated with one software resource
and the other software resource is deleted. If the duplicate software resource
contains any information that is not in the original one, you can merge the data
before the duplicate is deleted.
Each software resource in the Software Catalog has a unique identifier. Two software
resources can represent the same software but have different identifiers. Such
duplicate software resources can occur when the same software is added to the
Software Catalog by different methods. For example, you import a package to create
a software resource for Adobe Reader 9 from Adobe. Then a Software Discovery
finds an incidence of Adobe Reader 9 from Adobe Systems on a client computer.
You know that the two software resources are the same but because they have
different company names, they have different identifiers.
Review the Software Catalog periodically to look for duplicate software resources.
Look for the software resources that have identical or similar names or company
names. For example, Microsoft Office 2008 professional and Office 2008
Professional. When you find duplicates, you can resolve the duplication.
60
Implementing Software Management Framework
Populating the Software Catalog
To resolve duplicate software resources
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, in the Newly discovered/undefined
software list, right-click the software resource that is a duplicate of another
one and click Actions > Resolve Duplicate Software Resources.
3
In the Resolve Duplicate Software Resources dialog box, specify how to
resolve the duplication, select the software resources to merge or associate,
and click OK.
For more information about the options, click the page and then press F1
4
If you selected the option to merge the software resources, complete the series
of Merge Software Resources pages that appear. Click Next to advance to
each page.
These pages let you define the information that is copied from the duplicate
software resource to the original one.
For more information about the options, click the page and then press F1
5
When you complete the Merge Software Resources pages, click Merge
Software.
You can complete the merge process at any point as you step through the
pages. For example, if you want to merge the packages only, you can complete
the merge process after you complete the Packages to include page.
Creating a filter for installed software
You can create a filter that finds managed computers by the software that is installed
on them. For example, you can create a filter for all the computers that contain
Norton AntiVirus 2011.
A resource filter is a set of resources that are grouped according to some specific
criteria. In Notification Server, you can create a filter for any type of resource so
that you can isolate certain resources into narrow groups. You can use the filters
to select the resources to act upon throughout Notification Server.
A filter can include any software that supersedes the main software resource or
that the main software resource supersedes. For example, Norton AntiVirus 2008
supersedes both Norton AntiVirus 2006 and Norton AntiVirus 2007. You can create
a filter that finds all the computers that have any one of the three versions.
61
Implementing Software Management Framework
Populating the Software Catalog
You can view the installed software filters in the Software Filters folder, which is
under the Filters view in the Symantec Management Console. You can access
the Filters view from the Manage menu.
When you create a filter in Notification Server, you specify the filter definition with
a SQL query. When you create a filter for installed software from the Software
view, the SQL query is created for you. We recommend that you do not edit the
SQL in the installed software filters. If you need to change an installed software
filter, it is best to delete it and then recreate it from the Software Catalog.
You can view the installed software filters in the Software Filters folder, which is
under the Filters view in the Symantec Management Console. You can access
the Filters view from the Manage menu.
To create a filter for installed software
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the Installed Software subpane, click Newly Discovered Software.
3
In the center pane, select the software, and on the right-click menu, click
Actions > Create Installed Software Filter.
4
On the Create Installed Software Filter dialog box, define the filter, select
any superseding or superseded software, and add software resources if
necessary.
The Name field identifies this filter. When you create a filter from a software
resource in the Software Catalog, the software resource’s name is inserted
into a default filter name. Make the name descriptive enough for others to easily
identify this filter. Change this name if it does not follow your organization’s
standards for naming filters.
The Description field lets you type a description to further identify this filter
and make it more recognizable. Do not include critical information in the
description because it is not intended to appear in all the lists that contain the
name.
Click Add to add software resources to the filter. For example, three different
FTP clients are installed throughout your organization and you want to
standardize on one specific FTP client. You can create a filter that finds any
of the three existing FTP client applications.
The software list shows the selected software resource and any software
resources with which it has a supersedence association. You can choose to
include any superseding software or superseded software in the filter.
5
Click OK.
62
Chapter
3
Implementing Software
Management Solution
This chapter includes the following topics:
■
Implementing Software Management Solution
■
Installing or upgrading the Software Management Solution plug-in
■
Installing the Software Portal plug-in
■
Configuring security privileges for Software Management Solution
■
Configuring the default settings for Managed Software Delivery
Implementing Software Management Solution
Before you use Software Management Solution, you must set it up and prepare it
for use.
See “About Software Management Solution” on page 14.
The prerequisites for implementing Software Management Solution are as follows:
■
Symantec Management Platform and Software Management Solution must be
installed on the Notification Server computer.
For details, see the Symantec™ IT Management Suite 7.5 powered by Altiris™
technology Planning for Implementation Guide at
http://www.symantec.com/docs/DOC5670.
Software Management Solution is installed from Symantec Installation Manager.
The Symantec Installation Manager (SIM) handles the installation and initial
configuration of the Symantec Management Platform. This easy-to-use
installation wizard verifies installation readiness and steps you through the
product installation and configuration.
Implementing Software Management Solution
Implementing Software Management Solution
If you need to install or uninstall Software Management Solution after the initial
platform installation, Symantec Installation Manager is available in the Symantec
Management Console.
For details, see the Symantec™ IT Management Suite 7.5 powered by Altiris™
technology Planning for Implementation Guide at
http://www.symantec.com/docs/DOC5670.
You upgrade this product by using the Symantec Installation Manager.
For details, see the IT Management Suite Migration Guide version 7.0 to 7.5 at
the following URL:
http://www.symantec.com/docs/DOC5669.
■
The Symantec Management Agent must be installed or upgraded on the
computers that you plan to manage.
Software Management Solution requires that target computers be managed. A
managed computer is one on which the Symantec Management Agent is
installed.
The Symantec Management Agent for UNIX, Linux, and Mac must be installed
or upgraded on the non-Windows computers that you plan to manage.
For more information, see the topics about installing or upgrading the Symantec
Management Agent in the Altiris™ IT Management Suite 7.5 Administration
Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
Table 3-1
Process for implementing Software Management Solution
Step
Action
Description
Step 1
Install or upgrade the Software
Management Solution plug-in on
managed computers.
The Software Management Solution plug-in is required for you to
deliver and manage software on client computers.
Perform this step every time that you need to install or upgrade
the Software Management Solution plug-in on the client computers
that do not have it.
The unified Software Management Solution Plug-in Install policy
lets you install the solution plug-in on all supported operating
systems.
See “Installing or upgrading the Software Management Solution
plug-in” on page 65.
You may have performed this step when you installed the
Symantec Management Platform or when you added new
computers to the network.
64
Implementing Software Management Solution
Installing or upgrading the Software Management Solution plug-in
Table 3-1
Process for implementing Software Management Solution
(continued)
Step
Action
Description
Step 2
Configure security privileges for
Software Management Solution.
Administrators need the appropriate privileges to deliver and
manage the software in your organization.
You or another administrator may have already performed this
step when you configured security for the Symantec Management
Platform.
For more information, see the topics about setting up security in
the Altiris™ IT Management Suite 7.5 Administration Guide from
Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
Step 3
Configure default settings for
Managed Software Delivery.
You can configure the settings that control the behavior of
Managed Software Delivery policies. Rather than configuring these
settings individually for each policy, you can configure the default
settings that apply to all new Managed Software Delivery policies.
See “Configuring the default settings for Managed Software
Delivery” on page 71.
Step 4
(Optional) Implement the Software The Software Portal is installed on the Notification Server computer
Portal.
when Software Management Solution is installed. If you plan to
use the Software Portal, you must perform additional
implementation steps.
See “Implementing the Software Portal” on page 205.
Step 5
(Optional) Install the Symantec
Workspace Virtualization Agent.
If you plan to use software virtualization to manage Windows-based
software on client computers, install the Symantec Workspace
Virtualization Agent on those computers.
See “Installing the Symantec Workspace Virtualization Agent ”
on page 134.
Installing or upgrading the Software Management
Solution plug-in
Before you can deliver or manage software on client computers with Software
Management Solution, you must install the Software Management Solution plug-in
on those computers.
65
Implementing Software Management Solution
Installing or upgrading the Software Management Solution plug-in
If you upgraded from a 7.x version of Software Management Solution, you must
upgrade the Software Management Solution plug-in that is installed on the managed
computers.
Upgrade from a 6.x version of Software Management Solution plug-in is not
supported. You must upgrade Symantec Management Agent first, and then use
the Software Management Solution Plug-in Install policy to install the plug-in.
For more information about upgrade and data migration, see the IT Management
Suite 7.5 Installation Guide at the following URL:
http://www.symantec.com/docs/DOC5697
You install the Software Management Solution plug-in to Windows and non-Windows
computers using the Software Management Solution Plug-in Install policy.
This task is a step in the process for implementing Software Management Solution.
See “Implementing Software Management Solution” on page 63.
To install or upgrade the Software Management Solution plug-in
1
In the Symantec Management Console, on the Settings menu, click
Agents/Plug-ins > All Agents/Plug-ins.
2
In the left pane, under Agetns/Plug-ins, expand Software > Software
Management, and then click one of the following policies:
3
■
Software Management Solution Plug-in Install
Click if it is a new installation or if you upgraded from the 6.x version of the
product.
■
Software Management Solution Plug-in Upgrade
Click if you upgraded from the 7.x version of the product.
In the right pane, check or uncheck Enable Verbose Reporting of Status
Events according to your needs.
This option records the detailed events that are related to the installation and
posts them to the Notification Server computer.
4
Under Applied to, on the toolbar, click Apply to, and then choose where to
install the agent.
For more information, see the topics about specifying the targets of a policy or
task in the Altiris™ IT Management Suite 7.5 Administration Guide from
Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
66
Implementing Software Management Solution
Installing or upgrading the Software Management Solution plug-in
5
Under Schedule, on the toolbar, click Schedule, and then configurethe
schedule for the policy.
Note that if you turn off and then turn on the policy, it cannot run on the same
computer again. To run a policy on the same computer again, you must
configure it to run on a schedule.
http://www.symantec.com/docs/DOC5330
6
(Optional) Under Extra schedule options, configure following options:
Run once ASAP Lets you run the policy as soon as possible, and only once.
Note that if you turn off and then turn on the policy, it cannot run on
the same computer again. To run a policy on the same computer
again, you must configure it to run on a schedule.
User can run
Allows the user on the client computer to run the policy manually.
Notify user
when the task
is available
Displays a message to notify the user that new software is available.
When the user clicks the message, the New Software is Available
dialog box opens. The user can start, dismiss, or defer the policy. If
you do not choose to prompt the user, the New Software is
Available dialog box does not appear.
The New Software is Available dialog box appears only if Show
popup notifications is checked.
This option does not apply to UNIX, Linux, or Mac OS.
Warn before
running
Displays the Starting Task dialog box to notifiy the user before the
policy runs.
Unless you let the user defer the policy, the policy starts 60 seconds
after the Starting Task dialog box appears. A progress bar shows
the amount of time that remains. The user can dismiss the Starting
Task dialog box but cannot cancel the policy unless you checked
User can run.
The Starting Task dialog box appears only if the Show popup
notifications is checked in the client computer’s Symantec
Management Agent settings.
This option does not apply to UNIX, Linux, or Mac OS.
7
Turn on the policy.
At the upper right of the page, click the colored circle and then click On.
8
Click Save changes.
67
Implementing Software Management Solution
Installing the Software Portal plug-in
Installing the Software Portal plug-in
(Windows only)
The Software Portal plug-in provides access to the Software Portal Web application
from the client computers. It configures the URL that the users use to access the
Software Portal. The plug-in also installs shortcuts to the Software Portal interface
on the client computers.
This task is a step in the process for implementing the Software Portal. Perform
this task every time that you need to install the Software Portal on the client
computers that do not have it.
You can skip this step for Mac client computers. The Software Management Solution
plug-in for UNIX, Linux, or Mac supports the Software Portal on the Mac operating
system.
See “Implementing the Software Portal” on page 205.
The Software Portal plug-in requires that the Software Management Solution plug-in
is installed on the client computers.
See “Installing or upgrading the Software Management Solution plug-in” on page 65.
Note: If the Symantec Management Agent window is open on the client computer
when this plug-in is installed, the Software Portal link does not appear. To prevent
this issue, restart the Symantec Management Agent on the client computer after
the plug-in is installed. After the Symantec Management Agent restarts, the Software
Portal link becomes available to the user.
To install the Software Portal plug-in
1
In the Symantec Management Console, on the Actions menu, click
Agents/Plug-ins > Rollout Agents/Plug-ins.
2
In the left pane, expand Software > Software Management, and then click
Software Portal Plug-in Policy.
3
On the Software Portal Plug-in Policy page, specify where to place the
shortcut for the Software Portal on the client computers.
Click one or more of the following options:
■
Show link for Software Portal on Desktop
■
Show link for Software Portal in Start Menu
■
Show link for Software Portal in Symantec Management Agent’s
context menu
68
Implementing Software Management Solution
Configuring security privileges for Software Management Solution
This option places the Symantec Management Agent icon in the notification
area on the client computer. The user can right-click the Symantec
Management Agent icon to display the context menu and access the
Software Portal.
4
Under Applied to, select the computers or users on which to install the plug-in.
For more information, see the topics about specifying the targets of a policy or
task in the Altiris™ IT Management Suite 7.5 Administration Guide from
Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
5
Click Save changes.
Configuring security privileges for Software
Management Solution
As part of the Software Management Solution implementation, you configure security
privileges for the users who need to deliver and manage software on client
computers.
See “Implementing Software Management Solution” on page 63.
We provide security recommendations for two levels of software administrators and
one level of non-administrators. You can adapt these recommendations to the size
of your software management team.
69
Implementing Software Management Solution
Configuring security privileges for Software Management Solution
Table 3-2
Recommended security privileges for Software Management Solution
Type of user
Recommended privileges
Senior software
administrators
Senior administrators are responsible for the more critical software management tasks, such
as performing complex deliveries. They might also manage the Software Catalog and the
Software Library, which means that they can create and manage your organization’s software
resources and packages.
Senior software administrators need the Right Click Menu - Actions privileges that are
specific to Software Management Solution as follows:
■
Configure Managed Delivery Options
■
Managed Software Delivery
■
Quick Delivery Task
■
Source Path Update
Senior administrators might need to create and edit software resources, even if they are not
responsible for managing the Software Catalog or the Software Library. Therefore, they
need some of the Software Management Framework-related Right Click Menu - Actions
privileges. Examples are as follows:
■
Edit Command Line
■
Edit Software Resource
■
Edit Package
■
Import Package
For more information, see the topics about right-click menu privileges in the Altiris™ IT
Management Suite 7.5 Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
Senior software administrators need the Software Portal Privileges.
Software administrators Software administrators perform the majority of the software delivery tasks in your
organization.
Software administrators need the Right Click Menu - Actions privileges that are specific
to Software Management Solution as follows:
■
(Optional) Configure Managed Delivery Options
You might provide this privilege depending on the administrator’s level.
Managed Software Delivery
■
Quick Delivery Task
■
Source Path Update
■
Software administrators need some of the Software Portal Privileges.
70
Implementing Software Management Solution
Configuring the default settings for Managed Software Delivery
Table 3-2
Type of user
Recommended security privileges for Software Management Solution
(continued)
Recommended privileges
Non-administrators who You might let non-administrators perform single, routine software deliveries so you can free
can deliver software
your software administrators to focus on more complex delivery tasks. For example, help
desk employees can deliver a software update without escalating the requirement to the
administrators.
The Right Click Menu - Actions privileges for non-administrators are as follows:
■
■
Managed Software Delivery
Typically, these employees do not need to create Managed Software Delivery policies,
but you might decide to let them run the policies to deliver software.
Quick Delivery Task
To configure security privileges for Software Management Solution
1
In the Symantec Management Console, on the Settings menu, click Security
> Account Management.
2
In the left pane, click Account Management > Roles.
3
On the Roles page, in the left pane, click the security role that you want to
configure.
4
In the right pane, on the Privileges tab, select the privileges that you want to
assign the role.
To select a privilege, check the corresponding check box.
Most users require other privileges in addition to the Software
Management-related privileges. For example, to run a Quick Delivery task, a
user must have right-click menu privileges for Quick Delivery and for scheduling
a task.
For more information, see the topics on setting up security, security roles, and
security role privilege settings in the Altiris™ IT Management Suite 7.5
Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
Configuring the default settings for Managed
Software Delivery
Configuration settings control the behavior of new Managed Software Delivery
policies. Rather than configuring these settings individually for each policy, you can
71
Implementing Software Management Solution
Configuring the default settings for Managed Software Delivery
configure the default settings that apply to all new Managed Software Delivery
policies. Then you can change the settings for a specific policy only when needed.
The default settings speed up the creation of Managed Software Delivery policies
and promote consistency among them.
You can override the default settings for Managed Software Delivery as follows:
■
When you create a Managed Software Delivery policy manually
■
When you edit an existing Managed Software Delivery policy
Changing the default settings does not change the settings in the Managed Software
Delivery policies that were created earlier.
Software Management Solution settings control the behavior of the software-related
policies and tasks. The default settings let administrators create policies and tasks
without having to enter the details that they are not familiar with. Instead, a more
experienced administrator can configure the default settings that apply to all the
new policies and tasks that are created. When necessary, the administrator who
runs the specific policies and tasks can change the settings.
Table 3-3
Sources of default settings for Software Management policies and
tasks
Policy or task
Source of default settings
Managed Software Delivery
All new managed software delivery policies inherit the default
settings that are defined on the Managed Delivery Settings
page. You can override the default settings for specific
Managed Software Delivery policies.
Changing the default managed software delivery settings
does not affect the execution of the managed software
delivery policies that were created earlier.
See “Configuring the default settings for Managed Software
Delivery” on page 71.
Package Delivery
Quick Delivery
Source Path Update
Software Virtualization
Windows Installer Repair
Some of the task settings are predefined. Other settings for
these tasks are obtained from the Task Management settings
or the Symantec Management Agent settings. You can
override the settings for specific tasks.
72
Implementing Software Management Solution
Configuring the default settings for Managed Software Delivery
To configure default settings for Managed Software Delivery
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand Software, and then click Managed Delivery Settings.
3
On the Managed Delivery Settings page, configure the settings on the
following tabs:
4
Schedule
Lets you define the schedule on which a Managed Software
Delivery policy runs.
Download
Lets you define how a Managed Software Delivery policy’s
downloads are handled.
Run
Lets you define how a Managed Software Delivery policy
runs on the client computer.
Click Save changes.
73
Section
2
Managing software and
applications on client
computers
■
Chapter 4. Working with software resources
■
Chapter 5. Using the Enhanced Console View for Software Management
■
Chapter 6. Importing data from a data provider
■
Chapter 7. Managing Windows Installer applications
■
Chapter 8. Managing virtual applications
Chapter
4
Working with software
resources
This chapter includes the following topics:
■
Adding or editing a software resource
■
Deleting a software resource
■
Associating a package with a software resource
■
Adding an existing package to the Software Library
■
Creating a command line for a software resource
■
Creating or editing inventory rules
■
Adding associations to a software resource
■
Adding file resources to a software resource manually
■
Exporting a software resource and its details
Adding or editing a software resource
You can add a software resource to the Software Catalog manually or you can edit
an existing software resource.
You are most likely to add a software resource manually when you need to act on
the software resource quickly. For example, to deliver software immediately.
Warning: When you change an existing software resource, the change affects all
the policies and tasks that use that software resource.
Working with software resources
Adding or editing a software resource
In the following procedure, you access a software resource to edit it from the
Software Catalog. You can also access an existing software resource from the
Software view. If you double-click a software resource in the center pane, its
software resource page opens.
To add or edit a software resource
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
To add a software resource, in the Software Catalog window, in the Newly
discovered/undefined software list, click Add and on the Add menu, select
one of the following types:
■
Software Release
■
Service Pack
■
Software Update
Warning: After you set the software resource type you cannot change it.
3
4
To edit a software resource, do one of the following:
■
To edit an existing software resource that is undefined, in the Newly
discovered/undefined software list, select it and then click the Edit symbol.
When the list contains more than 20,000 software resources click Show
all software at the bottom of the list to display all software resources that
are undefined.
■
To edit an existing software resource that is defined, locate the software
product that the software resource is associated with in the Managed
software products or Unmanaged software list. Then click the software
product and in the Software Product dialog box open the required software
resource from the list on the Identify inventory tab.
On the software resource page, complete the tabs or edit the metadata on the
tabs.
The information on the Properties tab and the Package tab is required. The
information on the remaining tabs is optional.
For more information about the options, click the page and then press F1
5
Click OK.
76
Working with software resources
Deleting a software resource
Deleting a software resource
You can only delete a software resource from the Software Catalog if it does not
have a reference. A reference is an association between the software resource and
another item in the Symantec Management Platform. For example, references are
created for the policies and tasks that contain the software resource.
See “Adding or editing a software resource” on page 75.
When you try to delete a software resource that has references, a message appears
that lets you view the Item References page. This page lists all the references to
the software resource. Before you can delete a software resource, you must delete
all its references.
You can delete a software resource’s references in the following ways:
■
Delete the referenced item.
For example, if the software resource references a Quick Delivery task, then
delete that task.
■
Delete the reference from the Item References page.
The following procedure describes how to delete a software resource from the
Software Catalog window. You can also delete software resources from the
Software view.
To delete a software resource
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, in the Newly discovered/undefined
software list, right-click a software resource, and then click Delete.
3
In the Delete dialog box, click OK.
If another item does not reference the software resource, it is deleted.
4
If one or more items reference the software resource, in the Delete Item dialog
box, click Click here to display a reference dependency report for the
selected item.
77
Working with software resources
Associating a package with a software resource
5
On the Item References page, select the referenced items, and on the
right-click menu, click Delete.
The [Used By] Name column shows the items that are referenced.
Warning: A referenced item is deleted even if it is referenced by other software
resources. For example, if a referenced item is a Managed Software Delivery
policy that includes other software resources, the policy is deleted. If you do
not want to delete the policy, delete the software resource from the policy.
6
In the Delete Item dialog box, click OK.
The selected items are deleted from the console. The items remain on the Item
References page until you click Refresh.
7
Close the Item References page and in the Delete Item dialog box, click Retry
delete.
Associating a package with a software resource
You can associate a package with a software resource manually in the following
situations:
■
When you create the software resource manually
■
When the software resource was added as a result of a Software Discovery
scan
The Software Discovery scan cannot associate a package with a software
resource.
■
When the software resource has multiple packages
For example, you create a software resource that is associated with the package
for Microsoft Office. You also have a repackaged version of the Microsoft Office
package. Associate the repackaged version with the same software resource
as the original version.
With this exception and few other exceptions, it is best to associate only one
package with a software resource. Otherwise, it is more difficult to manage the
software that each package installs.
■
When the software resource was imported from a data provider without an
associated software package.
A software package is a folder that contains one or more files that you deliver to a
managed computer.
A package can be any of the following items:
78
Working with software resources
Associating a package with a software resource
■
An installation executable, such as an MSI or EXE.
■
A utility script or other program.
■
A non-executable file, such as a Microsoft Word template.
■
Any additional files that should be installed with the package file. For example,
a package can consist of a Microsoft Word installation file along with
corporate-standard template files.
Packages are associated with software resources. When a software resource is
delivered to a client computer, its package is downloaded to the client computer. If
the package contains an executable file, the command line that is associated with
the software resource determines how the package is executed.
Generally, it is best to associate only one package with a software resource.
Otherwise, it is more difficult to manage the software that each package installs.
For example, you might be tempted to create a single software resource and add
two packages for two different versions of an application. However, then you cannot
install, associate, upgrade, or inventory each version separately.
When you associate a package with a software resource, you define the package’s
source. Notification Server manages the package from this source. For example,
the package is distributed to package servers from the source that you define.
If you select the Software Library as the source, the package files are placed in a
new folder within the Software Library. By sourcing the package from the Software
Library, you secure the package and ensure that the correct version is always used.
If you do not source the package from the Software Library, the package is
considered to be unmanaged.
See “About the Software Library” on page 33.
When you define a package, you also can configure if and how the package is
made available to the package servers in your environment. Package servers reduce
the load on Notification Server and the network by distributing packages to multiple
locations for download.
When you associate a package with a software resource, you can also create
command lines for that package.
See “Creating a command line for a software resource” on page 81.
To associate a package with a software resource
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, in the middle pane, double-click the software
resource.
3
On the software resource page, click the Package tab.
79
Working with software resources
Adding an existing package to the Software Library
4
On the Package tab, click Add package.
5
In the Add or Edit Package dialog box, enter the package details and assign
the package to package servers.
For more information about the options, click the page and then press F1
6
On the software resource page, click Save changes.
7
Close the software resource page.
Adding an existing package to the Software Library
You can change a package’s source to the Software Library from a different source.
By sourcing the package from the Software Library, you secure the package and
ensure that the correct version is always used. After you change the source to the
Software Library, you cannot change it again.
This action copies the package file to the Software Library folder. Thereafter, any
policies or tasks that act on that package obtain it from the Software Library.
See “About the Software Library” on page 33.
To add an existing package to the Software Library
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the Software view, in the Deliverable Software pane, select the software
list that contains the software resource that the package is associated with.
3
In the middle pane, double-click the software resource.
4
On the software resource page, click the Package tab.
5
On the Package tab, in the Packages section, right-click a package and click
Actions > Import package.
Note: Ensure that you have the Software Library as the selected package
source.
6
In the Import Package dialog box, click OK to confirm the action.
Warning: The package’s source is changed as soon as you perform this step,
even if you do not save the changes for the software resource.
80
Working with software resources
Creating a command line for a software resource
7
On the software resource page, click Save changes.
8
Close the software resource page.
Creating a command line for a software resource
A command line determines how software is installed or uninstalled on the client
computer. A command line that is associated with a software resource can run a
package or run without a specific package. For example, a command line that is
not associated with a package might run a batch file or repair an application.
The types of actions that a command line can perform depend on the type of
installation that the package represents. They also depend on the platform that the
package is installed on. For example, a command line for an MSI package can
advertise the delivered software but a command line for an RPM package cannot.
The most common command-line actions are installation and uninstallation.
A software resource can contain multiple command lines to perform different actions.
For example, a software resource that has an MSI package might have multiple
command lines that perform the following actions:
■
Install the package silently.
■
Uninstall the package.
■
Apply a transform to the package.
■
Repair the package.
■
Install the package silently except for a progress bar.
By predefining the command lines for a software resource, you automate the
software management actions and reduce the risk of user errors. For example, a
user who needs to quickly deliver a software resource can select the software
resource and the action to perform. For example, an installation or a repair. The
user does not need to create a command line or even know the command-line
syntax for the software package.
In a software delivery environment, you typically limit or hide the installation user
interface.
For best results when you use command lines for software management, build the
command lines according to the following guidelines:
■
A command line should never run in a way that requires user interaction.
For example, it should not prompt for installation configuration or display any
messages that require the user to click any option or other control.
81
Working with software resources
Creating a command line for a software resource
■
A command line should contain sufficient input data so that it can run without
input from the end user.
■
Consider whether the command line requires the software package and set the
package option on the command line accordingly.
For example, Windows Installer applications can be uninstalled or repaired
without requiring the package. Instead, you can use the product code GUID
value in the command line. By not needlessly delivering the software package
you save network bandwidth during the software delivery.
You can create a command line that runs a package or that runs without a specific
package.
When you import a supported installation file type into the Software Catalog, default
command lines are created automatically. When you import a non-supported
installation file, or when you add a software resource in any other way, you must
create the command lines.
Creating
To create a command line for a software resource
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, do one of the following:
■
For an undefined software resouce, in the Newly discovered/undefined
software pane, select it and then click the Edit symbol.
■
For a defined software resource, locate the software product that the
software resource is associated with in the Managed software products
or Unmanaged software pane. Then click the software product and in the
Software Product dialog box open the required software resource from
the list in the Identify inventroy tab.
3
On the software resource page, click the Package tab.
4
On the Package tab, add or edit the command line as follows:
5
■
To add a command line to the software resource, click Add command.
■
To edit an existing command line, select it in the Command Lines list and
click Edit.
In the Add or Edit Command Line dialog box, define the command line and
click OK.
For more information about the options, click the page and then press F1
For example, you use the Application Management agent command-line options
to create the command line that runs the agent according to your specifications.
82
Working with software resources
Creating or editing inventory rules
6
Close the software resource page.
Creating or editing inventory rules
(Windows only)
Inventory rules evaluate the software that is installed on a client computer and the
client computer’s environment.
You can use inventory rules as follows:
■
To determine whether specific software is installed on a client computer.
These rules are called detection rules.
■
To determine whether a client computer has the correct environment for an
installation of the software.
These rules are called applicability rules.
Rules are associated with software resources. A rule is not used in any way if it is
not associated with a software resource. However, if you delete a software resource,
any rules that you created and associated with that software resource are not
deleted. The rules remain in the database. All rules are listed in the drop-down list
on the software resource Rules tab so that you can associate them with another
software resource.
If a rule is associated with a software resource, it appears on the Rules tab for that
software resource.
Inventory rules can be created or added in the following ways:
■
When you associate rules with a software resource, you can create or edit the
rules.
■
When you import an MSI to create a software resource, the import process
creates a detection rule that checks for the MSI file’s product code.
■
Other internal products or third-party products can be programmed to create
and use rules.
Warning: UNIX, Linux, and Mac OS operating systems do not support detection
and applicability rules; therefore, do not add them to non-Windows software
resources. When you add rules to non-Windows software resources, the rules are
always evaluated as false, which can cause errors in your software-related
operations.
Inventory rules are made up of expressions, which define the items that the rule
should evaluate. Inventory rules can contain one or more expressions.
83
Working with software resources
Creating or editing inventory rules
You can create the following types of rules:
Smart rules
Many smart rules update dynamically based on what is selected
in the expressions that make up the rule. Smart rules can contain
smart or standard expressions.
For more information about the options, click the page and then
press F1
Standard rules
Standard rules are static. Standard rules can contain only
standard expressions.
For more information about the options, click the page and then
press F1
The Inventory Rule Management agent runs the inventory rules on client computers.
The Inventory Rule Management agent is installed on the client computer and runs
as a Web service on the Notification Server computer.
You can create new inventory rules for a software resource or edit its existing rules.
A software resource can be associated with a detection rule and an applicability
rule.
Inventory rules evaluate the software that is installed on a client computer and the
client computer’s environment. You can associate a software resource with the
following types of inventory rules:
Detection rules
Determine if specific software is installed on a client computer. A
detection rule ensures that Software Discovery can detect an
installed software resource that is EXE based and add it to the
Newly Discovered Software list. A detection rule must also be
associated with an EXE based software resource for a compliance
check in a Managed Software Delivery to report success.
A detection rule can look for information such as the file
associations, MSI product code, shortcuts, and registry entries.
For example, when you define a software resource, you can
associate it with one or more files that represent it. A detection
rule looks for the presence of those files on the client computer.
If it finds those files, then it assumes that the software resource
is installed.
84
Working with software resources
Creating or editing inventory rules
Applicability rules
Determine whether a client computer has the correct environment
for an installation of the software.
An applicability rule can look for information such as the operating
system, processor type, Windows language, and registry entries.
For example, if the software requires a specific operating system,
the applicability rule checks the client computer for the presence
of that operating system.
The detection rules and the applicability rules help the software-related operations
to identify software resources accurately.
Examples are as follows:
■
In Software Management Solution, a Managed Delivery policy uses an
applicability rule to determine whether the software can be installed on the client
computer. If the client computer has the correct environment, the Managed
Delivery policy uses a detection rule to determine whether the software is already
installed. If the software is not installed, then the policy installs it. The use of the
detection rule prevents you from reinstalling the software on the computers that
already have that software.
■
In Inventory Solution, the Targeted Software Inventory policy uses a detection
rule to determine whether a specific software resource is installed on client
computers. The policy then reports the computers that contain the software.
Some rules, such as those that Software Management Solution uses, can be
predefined. Otherwise, you create the rules that you need for each software
resource. Other internal products or third-party products can be programmed to
create and use detection and applicability rules.
Best practices for creating rules are as follows:
■
In general, detection rules should be specific enough to identify a given version
of a software resource from other versions. However, the rules should not be
so specific that the detection fails. For example, when you create file expressions,
do not use a specific file version. Instead, specify a range of versions.
■
Try to set up rules so that they find file paths by extracting them from the registry
instead of by looking in a static path. You can set up rules this way by using the
Registry Key/File Path to File Version expression type. That expression type
reads the file path from the registry and compares it against a version range.
85
Working with software resources
Creating or editing inventory rules
Warning: UNIX, Linux, and Mac OS operating systems do not support detection
and applicability rules; therefore, do not add them to non-Windows software
resources. When you add rules to non-Windows software resources, the rules are
always evaluated as false, which can cause errors in your software-related
operations.
To create or edit an inventory rule
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, do one of the following:
■
For an underfined software resource, in the Newly discovered/undefined
software pane, select it and then click the Edit symbol.
■
For a defined software resource, locate the software product that the
software resource is associated with in the Managed software products
or Unmanaged software pane. Then click the software product and in the
Software Product dialog box open the required software resource from
the list in the Identify inventroy tab.
3
On the software resource page, click the Rules tab.
4
To access the dialog box where you can edit existing rules or add a new rule,
perform one of the following actions:
5
■
To edit an existing rule, next to the detection or applicability drop-down list,
click the Edit detection rule symbol or the Edit applicability rule symbol.
■
To add a new rule, next to the detection or applicability drop-down list, click
the Add a new detection rule symbol or the Add a new applicability rule
symbol.
In the Create rule dialog box or Edit rule dialog box, in the Name box, type a
name to describe the rule.
Skip this step when you edit an existing rule.
86
Working with software resources
Creating or editing inventory rules
6
To edit an existing rule expression, select the rule expression in the left pane
and edit it in the right pane.
Note: The And, Not, Or operators apply to the rules, which reside under the
corresponding operator in the expression tree in the left pane. The rule does
not work, if the operator and the rules, to which it must apply, are on the same
level in the expression tree. Please see the example of correct usage of the
Or operator below:
7
To add an operator, on the toolbar, click the Add a new rule expression
symbol, click Operators, and then select an operator.
The Add a new rule expression symbol is only enabled if an operator is
selected in the left pane.
8
9
To create a new rule expression, on the toolbar, click the Add a new rule
expression symbol, click one of the following options, and then select the
expression:
■
Standard Rule
Standard rules are static and can only contain standard rule expressions.
You can add standard rule expressions to smart rules, but you cannot create
new standard rules.
■
Smart Rule
Some smart rules are dynamic and all smart rules can contain smart and
standard rule expressions.
Complete the fields that are necessary to add the expression.
For more information about the options, click the page and then press F1
10 Click OK.
11 Continue to add expressions until the rule is complete.
87
Working with software resources
Adding associations to a software resource
12 On the software resource page, click Save Changes.
13 Close the software resource.
Adding associations to a software resource
You can define associations between software resources in the Software Catalog.
These associations add logic to software-related tasks. For example, in Software
Management Solution, you can create a policy that delivers a software resource
and all the software that it depends on.
When new software resources are created, review them for possible associations
with existing software resources. For example, when you introduce a new version
of antivirus software, create a supersedence association with the earlier version of
that software.
To add associations to a software resource
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, do one of the following:
■
To add a new software resource, in the Newly discovered/undefined
software list, click Add.
■
To edit an existing software resource that is undefined, in the Newly
discovered/undefined software list, select it and then click the Edit symbol.
■
To edit an existing software resource that is defined, locate the software
product that the software resource is associated. You can make the edit in
the Managed software products or Unmanaged software list. Then click
the software product and in the Software Product dialog box open the
required software resource from the list in the Identify inventroy tab.
3
On the software resource page, click the Associations tab.
4
On the Associations tab, in Association Type, select the type of association
to create.
For example, you can simplify software management in a heterogeneous
environment by categorizing software by operating system.
88
Working with software resources
Adding file resources to a software resource manually
5
In the sections that appear on this tab, click Add to associate software
resources with the current one.
The sections that appear on this tab depend on the type of association that
you selected.
6
In the Select Software dialog box, specify the software resources to add to
this association and click OK.
Adding file resources to a software resource manually
You can associate a file resource with a software resource. A file resource is a
representation of an important file that the specific software installs. Each software
resource can contain multiple file resources.
A file resource is a representation of an important file that a specific instance of
software installs. These files typically are DLL and EXE files. However, you can
add references to any files that can help to identify the software on a client computer.
(Windows only) When you associate the file resources with a software resource,
you can add the file resources to the software resource’s detection rule. Then, the
rule can look for those files on the client computer to determine whether that software
is installed.
See “Creating or editing inventory rules” on page 83.
File resources can be added to a software resource in the following ways:
Manually
Regardless of how the software resource is created, you usually
need to add the file resources manually.
The procedure that follows show you how to add file resources to
a software resource manually.
From a Software
Discovery scan
Software Discovery scans managed computers and collects
information about the critical files that are installed with each
software application. Then Software Discovery associates the file
information with the appropriate software resources.
See “Discovering software on managed computers” on page 54.
(Windows only) After you associate file resources with a software resource, add
the file resources to the software resource’s detection rule.
See “Creating or editing inventory rules” on page 83.
89
Working with software resources
Exporting a software resource and its details
To add file resources to a software resource manually
1
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
2
In the Software Catalog window, do one of the following:
■
To add a new software resource, in the Newly discovered/undefined
software list, click Add.
■
To edit an existing software resource that is undefined, in the Newly
discovered/undefined software list, select it and then click the Edit symbol.
■
To edit an existing software resource that is defined, locate the software
product that the software resource is associated with in the Managed
software products or Unmanaged software list. Then click the software
product and in the Software Product dialog box open the required software
resource from the list in the Identify inventroy tab.
3
On the software resource page, click the File Inventory tab.
4
On the File Inventory tab, click Add.
5
In the Files to Add dialog box, click Add and select either of the following:
■
Local file
Local files can be selected on a local computer, even through a console
has it opened remotely.
■
Server file
Server files are those files add by an administrator to another software
resource by using the Local file method.
6
If you selected Local file, in the Open dialog box, select one or more files and
click Open.
7
If you selected Server file, in the Select File dialog box, select one or more
files and click OK.
8
When you finish adding files, in the Files to Add dialog box, click OK.
9
On the software resource page, click OK.
Exporting a software resource and its details
You can export a software resource and any of its metadata to a detailed XML file.
You might use the XML file as a backup. You also can replicate the software
resource on another Notification Server computer by importing the XML file to that
computer.
90
Working with software resources
Exporting a software resource and its details
Note: You cannot execute a Managed Software Delivery policy if you import XML
after an export when the package source is the Software Library. If you import XML
to another Notification Server computer you must manually copy the MSI file to the
same location on the first Notification Server computer. If you delete a software
resource that has been imported from the Software Library, the package for this
software resource is also deleted. As a consequence you must manually re-create
this package to download this package after a software resource is re-imported.
The detailed export is different from the Symantec Management Platform default
export, which exports only the data about the software resource itself. In addition
to exporting the metadata, the detailed export can strip out the security information
that can make the XML file difficult to re-import. To export the same information
with the default export function, you would have to export every piece of metadata
individually.
To export a software resource and its details
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, click Newly Discovered Software or one of the lists in the
Deliverable Software pane.
3
In the center pane, right-click a software resource and click Actions > Detailed
Export.
4
In the Exporting dialog box, select the information to export with the software
resource.
For more information about the options, click the page and then press F1
5
Click OK.
6
In the File Download dialog box, do either of the following:
7
■
Click Open to open and view the file. You can save the file from the Internet
Explorer toolbar.
■
Click Save to save the file and in the Save As dialog box, specify a name
and location and click OK.
If the Download complete dialog box appears, click Close.
91
Chapter
5
Using the Enhanced
Console View for Software
Management
This chapter includes the following topics:
■
Introducing the Software view and the Software Catalog window
■
Accessing the Software Catalog window
■
Finding software in the Software view and in the Software Catalog
■
Saving a software search
■
Managing a saved software search
■
Installing software by drag and drop
Introducing the Software view and the Software
Catalog window
The Software view lets you find and manage software efficiently. You can also
perform many other actions on your software from this view. To access the Software
view, on the Manage menu, click Software.
See “Finding software in the Software view and in the Software Catalog” on page 97.
You can also allow specific user roles to perform the specific key tasks that relate
to software management from the Software view. To enable the user role to perform
these key tasks, you must assign the user role-specific Software Management
privileges.
Using the Enhanced Console View for Software Management
Introducing the Software view and the Software Catalog window
The Software Catalog window is an extension of the Software view. The Software
Catalog window contains lists of all the software that is known in your organization.
In this window, you can perform many of the same actions that you can perform in
the Software view. In addition you can review all installed software and move
undefined software to the Managed software products list or to the Unmanaged
software list. Undefined software is the software that is neither managed nor
unmanaged. From the Software Catalog window, you can also import a package
to create a software resource, add a software resource manually, and edit or delete
an existing software resource.
See “Accessing the Software Catalog window” on page 96.
See “About the Software Catalog” on page 30.
The Software Catalog window has the following three panes that list all of the
known software in your organization:
■
Newly discovered/undefined software
This list contains all of the installed software that has been discovered in your
environment and that is still undefined. The list also contains the deliverable
software resources which are not associated with managed or unmanaged
software products. When you run a software inventory, it discovers all the
installed software in your environment that was not previously discovered. You
can move installed software from this list to the other two lists.
Note: If you associate a software to a software product, it is then removed from
this list.
■
Managed software products
This list displays the installed software that you have chosen to manage or that
matches predefined product filters. If installed software matches a predefined
filter it is automatically added to the list of managed software products. We
currently have predefined filters for many products including Adobe and Microsoft
products. You can track usage and licenses of managed software products. You
must have Asset Management Solution installed to track software licenses.
■
Unmanaged software
This list includes the software that you either do not need to manage or choose
not to manage. You move software to this list if the software is not licensed or
if you do not want to track or deliver it.
The Software Catalog window is unique in that it is the one location from which
you can perform the following software management tasks:
■
Add a software resource to the software catalog manually.
93
Using the Enhanced Console View for Software Management
Introducing the Software view and the Software Catalog window
The software is added to the list of undefined software resources that you can
choose to manage.
See “Adding or editing a software resource” on page 75.
■
Add a software product directly to the Managed software products list.
■
Delete a software product.
When you delete a software product, any software resources that are associated
with the product appear again in the Newly discovered/undefined software
list.
In the Software view and the Software Catalog, you perform many actions on
software resources and software products. You can perform most of these actions
in the Software view and in the Software Catalog, while you can only perform some
actions in the Software Catalog.
Note: The products that you have installed determine the actions that are available
in the Software view and the Software Catalog. For example, if Software
Management Solution is installed, you can deliver software. If Inventory Solution
is installed, you can find software on client computers or blacklist an application.
Other internal products or third-party products can be programmed to introduce
additional actions that are not listed here. For information on the other tasks that
you can perform, see the Help for the products that you have installed.
Table 5-1
Actions you can perform in the Software view and in the Software
Catalog
Your goal
Description
(Software Catalog only) Add
a software product directly.
In the Software Catalog, you can add a software product directly to the Manage
software products list.
(Software Catalog only) Add
a software resource.
In the Software Catalog, you have the following options for adding a software resource:
■
■
Import an application package to create a software resource for that application.
See “Importing a package to create a software resource” on page 51.
Add a software resource manually.
See “Adding or editing a software resource” on page 75.
Additional options for adding software resources are available in other areas of the
Symantec Management Console.
Add the software resource to An organizational group is a hierarchical organization of resources for management
an organizational group.
and security purposes. You can add a software resource to any organizational group.
94
Using the Enhanced Console View for Software Management
Introducing the Software view and the Software Catalog window
Table 5-1
Your goal
Actions you can perform in the Software view and in the Software
Catalog (continued)
Description
Assign a type to a software
An unassigned software resource is one that is not categorized as a software release,
resource that is unassigned. an update, or a service pack.
See “Assigning a type to a software resource” on page 59.
Create a filter that is based
on installed software.
You can filter managed computers by the software that they contain. You can select
software from the Software Catalog to include in the filter criteria.
See “Creating a filter for installed software” on page 61.
Delete a software resource.
You can delete a software resource only if no other items in the Symantec Management
Console reference it. For example, if no policies or tasks contain that software resource.
When you try to delete a software resource that is referenced, you can display a report
of the items that reference the software.
Edit a software resource.
You can edit an existing software resource.
See “Adding or editing a software resource” on page 75.
(Software Catalog only)
Delete a software product.
In the Software Catalog, you can delete a software product. When you delete a software
product, the software resources are listed again in the Newly discovered/undefined
software list.
Export the software resource You can export a software resource to an XML file. An additional option lets you export
to an XML file.
the software resource and its details to an XML file.
See “Exporting a software resource and its details” on page 90.
Find software.
You can use a search to narrow the search results so that the list pane contains only
the objects that you want to work with. In addition, in the Software view, you can also
use advanced search criteria to further narrow the information that is displayed in the
results list. You can save software searches if you are likely to search for the same
software more than once. In the Software view, you can also modify, hide, or delete
a saved search.
See “Finding software in the Software view and in the Software Catalog” on page 97.
See “Managing a saved software search” on page 100.
Manage software as a
product.
You can manage software as a product rather than as a software resource. When you
manage software as a product, you can track software usage and licenses. You can
make any software in the newly discovered software list a managed software product.
Move a software resource to You can move a software resource from the newly discovered list to the Software
the list of unmanaged
Catalog’s unmanaged software list. You move software to this list if the software is not
software.
licensed or if you do not want to track or deliver it.
95
Using the Enhanced Console View for Software Management
Accessing the Software Catalog window
Table 5-1
Actions you can perform in the Software view and in the Software
Catalog (continued)
Your goal
Description
Resolve duplicate software
resources.
Two software resources can represent the same software but have different identifiers.
Duplicate software resources can occur when the same software is added to the
Software Catalog by different methods.
When you find two software resources that appear to be duplicates, you can resolve
the duplication.
See “Resolving duplicate software resources” on page 60.
Accessing the Software Catalog window
The Software Catalog window contains lists of all the software that is installed in
your organization. The Software Catalog window has a list for newly discovery or
undefined software, managed software products, and unmanaged software. You
can move the software from one of these lists to any of the other lists. When you
right-click a software resource in the list on the left, you can perform different actions
on the software resource.
See “About the Software Catalog” on page 30.
You can access the Software Catalog window in the following ways:
■
From the Manage menu
■
From the Software view
To access the Software Catalog window from the Manage menu
◆
In the Symantec Management Console, on the Manage menu, click Software
Catalog.
To access the Software Catalog window from the Software view
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, in the Installed Software subpane, right-click in the empty
space and click Manage Software Catalog.
96
Using the Enhanced Console View for Software Management
Finding software in the Software view and in the Software Catalog
Finding software in the Software view and in the
Software Catalog
In the Software view and the Software Catalog, the search results are not filtered
automatically. You can use a search to narrow the search results so that the list
pane contains only the objects that you want to work with.
The Software view lets you find and manage software efficiently. You can also
perform many other actions on your software from this view. To access the Software
view, on the Manage menu, click Software.
See “Finding software in the Software view and in the Software Catalog” on page 97.
You can also allow specific user roles to perform the specific key tasks that relate
to software management from the Software view. To enable the user role to perform
these key tasks, you must assign the user role-specific Software Management
privileges.
To find specific software, you can search by its full name or partial name. In the
Software view, you can also use advanced search criteria to further narrow the
information that is displayed in the results list. An advanced search lets you search
by the criteria that is stored in the Configuration Management Database. If the
information by which you want to sort is not shown in the advanced search list, you
can add custom search criteria.
In the Software view, you can save software searches if you are likely to search
for the same software more than once. After you save a software search, you can
manage it by modifying, hiding, or deleting it.
See “Managing a saved software search” on page 100.
See “Saving a software search” on page 99.
You can also use the Software Finder Web part to search for software. You can
add this Web part to any portal page in the Symantec Management Console. The
Software Finder lets you perform a Quick Search of the software resources that
are in the Software Catalog. The Software Finder performs simple searches only.
You can edit, delete, and perform other actions on the software resources that are
found.
See “Web parts for Software Management Framework” on page 19.
97
Using the Enhanced Console View for Software Management
Finding software in the Software view and in the Software Catalog
To find software in the Software view and in the Software Catalog
1
In the Symantec Management Console, on the Manage menu, click Software
or Software Catalog.
2
(Software view only) If you clicked Software on the Manage menu in the
previous step, in the left pane, click the category of software that you want to
search.
3
In the search field, type the search criteria.
In the Software view, the search field is in the middle pane. In the Software
Catalog, the search field is in the left pane.
For example, to find updates to an inventory software product, you can type
inv. All software updates that contain the letters inv anywhere in their names
are listed in the list pane. Search results appear in the content pane.
You can search by full or partial software name, full or partial manufacturer
name, or version.
When you search for software, the following general search conditions apply:
■
Quotation marks limit your search to an exact match.
If you enter "Microsoft SQL Server 2005 (64-bit)", it only returns the
software that has this exact name.
■
Omitting quotation marks allows for matching search text anywhere in a
string.
If you enter SQL, it returns all software that contains SQL anywhere in its
name.
You can use the following search operators to express various arguments:
To express this argument:
Use this symbol:
Or
Pipe ( | )
This operator does not require leading spaces.
Adobe|Microsoft = software manufacturer LIKE Adobe
OR LIKE Microsoft.
And, Add, or Include
Plus ( + ) sign
This operator requires a leading space.
Adobe +Microsoft = software manufacturer LIKE
Adobe AND Microsoft.
98
Using the Enhanced Console View for Software Management
Saving a software search
Not / minus / do not include
Minus ( - ) sign
This operator requires a leading space.
-Adobe -Microsoft = software manufacturer NOT LIKE
Adobe and NOT LIKE Microsoft
4
To add advanced search criteria, click the down-arrow to the right of the search
field, click Add Search Criteria, and select the search criteria.
To select multiple search criteria, continue to click the down-arrow next to the
drop-down list where the criteria appear. Select a criterion, and repeat the step
to add other criteria.
Note: To remove a search criterion, leave the field empty. Any field that does
not contain a value is ignored in the query.
5
If the criteria by which you want to search are not listed in a drop-down list, do
the following to add custom criteria:
■
In a criteria drop-down list, click Add Custom Criteria.....
■
In the Add Search Criteria dialog box, select the custom criteria by which
you want to search and click OK.
This dialog box is populated with Configuration Management Database
(CMDB) data and includes the following categories: DataClasses,
Associations, and Columns.
The columns of CMDB data on the right change based on the data classes
and associations that you select on the left. The more data classes you
select on the left, the larger the list of CMDB column data on the right.
When you search for software in the Software view of the Software Catalog, you
can use search conditions and search operators.
See “Finding software in the Software view and in the Software Catalog” on page 97.
Saving a software search
In the Software view and in the Software Catalog window, you can save a software
search. You could save a software search if you are likely to search for the same
software more than once. Saved searches appear in the Installed Software subpane
of the navigation pane on the left. You can then use saved searches like filters to
target software for tasks, jobs, and policies. You can also use saved searches to
deliver software to specific computers or groups of computers. After you save a
software search, you can manage it by modifying, hiding, or deleting it.
99
Using the Enhanced Console View for Software Management
Managing a saved software search
Note: When you save a search, any empty fields are not saved with the filter.
See “Managing a saved software search” on page 100.
To save a software search
1
Specify the search criteria.
Whenever you find software, you specify the search criteria.
See “Finding software in the Software view and in the Software Catalog”
on page 97.
2
If the advanced search options are not displayed, click the down-arrow to the
right of the search field.
3
Click the save icon.
4
In the Save Search dialog box, in the Name field, enter a name and click OK.
Managing a saved software search
After you save a software search in the Software view or the Software Catalog,
you can manage the saved search. You can modify a saved search, hide a saved
search, and display a saved search that is hidden. You can also delete a saved
search.
See “Finding software in the Software view and in the Software Catalog” on page 97.
To modify a saved software search
1
In Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, under Installed Software, select the saved search that you
want to modify.
3
In the center pane, in the search field, add or delete search criteria.
The search results in the list pane change to match the search criteria that you
enter.
100
Using the Enhanced Console View for Software Management
Installing software by drag and drop
4
In the advanced search area of the list pane, click the save option to save the
search.
5
In the Save Search dialog box, in the Name field, enter a name and click OK.
Select one of the following actions:
To replace a
search
Note that you cannot overwrite the default searches, but you can
overwrite the custom searches that you created.
Save the modified search without changing the name of the saved
search.
To modify and
Give the modified search a unique name.
save a search as a
variation
The saved search appears under Installed Software in the left pane.
To hide or display a saved software search
1
In Symantec Management Console, on the Manage menu, click Software.
2
In the Installed Software subpane, in the white space after the entries,
right-click and then click Manage Saved Searches.
3
In the Manage Saved Searches dialog box, do the following:
■
To hide a saved search, uncheck the box next to the search.
The search no longer appears in the list but can be restored.
■
To display a saved search, check the box next to the search.
The search appears in the list again.
■
Click Close
To delete a saved software search
1
In Symantec Management Console, on the Manage menu click Software.
2
In the Installed Software subpane, right-click the search in the Installed
Software subpane, click Delete, and click OK in the Delete dialog box.
Installing software by drag and drop
TheSoftware view lets you easily install software on a computer or group of
computers by drag and drop. You can install the software once by using a task, or
you can keep the software installed by using a policy. Consider a software that is
dropped to a group of computers or a group of computers that is dropped to a
101
Using the Enhanced Console View for Software Management
Installing software by drag and drop
software release. In each case software delivery is carried out by a Managed
Software Delivery policy rather than a Quick Delivery task.
To install software by drag and drop
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the navigation pane, click the software that you want to install, and drag it
to the right to initiate drag and drop.
Note that you can only install the software that has associated packages and
command lines.
3
4
To select the computers on which you want to install the software, do one of
the following:
■
To install the software on all listed computers, drop it onto the title icon in
the list pane.
■
To install the software on a specific computer, drop it onto the computer in
the list.
■
To install the software on a saved search, organizational view, or
organizational group, drag it to the Computers blade. Then drop it onto a
saved search, organizational view, or organizational group.
In the Deliver software dialog box, do one of the following:
To run a task to
■
install the software. ■
Click Deliver software.
To create a policy
to install the
software.
Check Ensure software stays installed using a policy, and
then click Deliver software.
In the new policy dialog box, specify the settings of the policy,
turn it on, and then click Save changes.
See “Creating a Managed Software Delivery policy”
on page 184.
■
■
In the New Schedule dialog box, specify the schedule of the
task, and then click Schedule.
For more information about the options, click the page and
then press F1.
102
Chapter
6
Importing data from a data
provider
This chapter includes the following topics:
■
Introducing data providers
■
Adding a data provider
■
Importing data from a data provider
■
Configuring the precedence settings for a data provider
■
Importing data from a data provider with a schedule
■
Importing data from a data provider manually
Introducing data providers
A data provider is a source of software resource data that can be imported into
Software Management Framework. You can import the metadata of a software
resource from a data provider into the Software Catalog. When you import metadata
from a data provider, a software resource is created in the Software Catalog if it
does not already exist. If the software resource is already in the Software Catalog,
precedence settings determine if the data provider can update the data.
See “Importing data from a data provider” on page 107.
The ability to import metadata eliminates the need to gather much of this data and
manually enter it into the Software Catalog. A data provider’s metadata might also
be used to enhance Notification Server’s ability to identify software resources on
your managed computers.
Importing data from a data provider
Introducing data providers
You can also import the software package that is associated with a software resource
if the data provider supports this functionality. A software package is imported into
the Software Library and is associated with the software resource in the Software
Catalog. If a software package is already associated with a software resource in
the Software Catalog, then a data provider cannot update the software package. If
a data provider’s software resource has an associated software package, you also
have the option of importing only the metadata of the software resource. With this
option, a software package resource is created in the Software Catalog, and it is
sourced from the location that the data provider specifies.
The ability to import the software packages into the Software Library lets you store
all of your managed packages in a secure, centralized repository. When you import
software packages into the Software Library, those responsible for software
distribution can easily deliver and manage the software.
Before you can import data from a data provider into Software Management
Framework, you must add the data provider. To add a data provider, you configure
a connection to the data provider. A data provider that has a configured connection
is a registered data provider. If a data provider has multiple databases, you can
configure a connection to each database.
See “Adding a data provider” on page 106.
A user of the Software Catalog or a Symantec Management Platform product that
adds data to the Software Catalog is a non-registered data provider. When you
configure precedence settings, the non-registered data providers are grouped
together and referred to as Other Software Providers.
You can import the metadata of software resources from a data provider into the
Software Catalog. When you import metadata, you eliminate the need to manually
enter it into the Software Catalog. This metadata then helps you manage the
software.
When you import the metadata of a software resource, it appears on the appropriate
tab in the Software Catalog for that software resource. For example, package data
appears on the Package tab.
If metadata is already in the Software Catalog for a software resource, precedence
settings determine whether a data provider can update the data. The exception is
File Inventory data, which is additive, so precedence settings don’t apply.
Table 6-1
The types of metadata that a data provider can import
Type of data
Description
Properties
The properties data defines the properties that identify a
software resource. This data includes its name, description,
version, company, and product name.
104
Importing data from a data provider
Introducing data providers
Table 6-1
The types of metadata that a data provider can import (continued)
Type of data
Description
Package
The package data defines the software packages that are
associated with a software resource. It also defines the
command lines for each software package.
A data provider can import package data for a software
resource for multiple types of software packages. However,
it cannot import package data for a software resource for two
software packages of the same type. For example, it can
import package data for a software resource for an MSI
package and a VSA package. However, it cannot import
package data for a software resource for two MSI files.
Detection rule
A detection rule is used to determine if a software resource
is installed. When a detection rule is updated, the existing
rule is preserved because another software resource may
still use it.
When you import metadata with a data provider, applicability
rules are not created.
Associations
The associations data defines the associations the software
resource has with other software resources in the Software
Catalog.
Any associations that a data provider defines are imported
as long as both software resources exist in the Software
Catalog. A data provider can only remove an association
from a software resource if it imported that association.
File Inventory
The File Inventory data defines the DLL and the EXE files
that a software resource installs. Detection rules can use this
data to detect if software is installed on a computer. Inventory
scans can also use this data to distinguish between known
and unknown files on a computer.
You can use different methods for importing data from a data provider. The method
you choose depends on how much control you want over what data is imported.
See “Importing data from a data provider” on page 107.
105
Importing data from a data provider
Adding a data provider
Table 6-2
Methods for importing data from a data provider
Import method
Description
Scheduled import
This method imports data when a scheduled task runs. It
imports all of the software resource data that the task is
designed to import. For example, if you schedule a task to
import data from a data provider, it imports data for all the
available software packages.
See “Importing data from a data provider with a schedule”
on page 110.
If you want more control over what is imported, use a manual
import.
Manual import
This method imports data for the software resources that you
select. This ability to select specific software resources gives
you complete control over what is imported. Before you can
use this method, a list of the available software resources
must be gathered.
See “Importing data from a data provider manually”
on page 112.
When you import data with either of these methods, an import task is created. The
import task is listed on the data provider’s page in the Providers folder. You can
access the Providers folder on the Settings menu at Software > Data Provider.
Adding a data provider
Before you can import data from a data provider into the Software Management
Framework, you must add the data provider. To add a data provider, you configure
a connection to the data provider. A data provider that has a configured connection
is a registered data provider.
See “Importing data from a data provider” on page 107.
Before you can add a data provider, you must install the product that lets you add
the data provider. If a data provider is added automatically when a product is
installed, then you do not add the data provider.
To add a data provider, you must be assigned the Symantec Software Librarian
security role. The Symantec Management Platform administrator can assign people
to this role.
In the following procedure, the data provider is added from the Data Provider
Management page.
106
Importing data from a data provider
Importing data from a data provider
For more information about the options, click the page and then press F1
You can also add a data provider on the Data Providers Web part.
For more information about the options, click the page and then press F1
See “Web parts for Software Management Framework” on page 19.
To add a data provider
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Data Provider > Data
Provider Management.
3
On the Data Provider Management page, click Add, and then select the data
provider.
For more information about the options, click the page and then press F1
If a data provider is not listed, you do not have the product installed that lets
you connect to that data provider.
4
On the page that appears, click the default title, and then type a title that is
descriptive of the data provider.
5
To add a description to the task, click Add description, and then type the
description.
6
Under Settings, configure the settings for connecting to the data provider.
Each data provider has its own connection settings.
7
If the data provider lets you validate the connection, click Validate.
8
To save the connection settings, click Save changes.
9
Close the data provider’s page.
You can access this page in the Providers folder and edit its settings or
schedule when you want to import or gather its data. The Providers folder is
under the Data Provider folder.
Importing data from a data provider
You can import the metadata of software resources from a data provider into the
Software Catalog. You can also import the software package that is associated with
the metadata into the Software Library if the data provider supports this functionality.
To configure and import data from a data provider, you must be assigned the
Symantec Software Librarian security role. The Symantec Management Platform
administrator can assign people to this role.
107
Importing data from a data provider
Importing data from a data provider
Table 6-3
Process for importing data from a data provider
Step
Action
Description
Step 1
Install the product that lets
you connect to the data
provider.
To import data from a data provider, you must
install the product that lets you connect to the
data provider.
Step 2
Add the data provider.
You must add a data provider before you can
import its data. To add a data provider, you
configure a connection to the data provider.
Each data provider has its own connection
settings.
See “Adding a data provider” on page 106.
Step 3
Configure the precedence
After you configure a connection to a data
settings for the data provider. provider, you should configure the
precedence settings for the data provider.
Precedence settings determine when a data
provider can update the metadata of a
software resource that is in the Software
Catalog.
See “Configuring the precedence settings for
a data provider” on page 109.
Step 4
Import the data of the
You can import the data on a schedule or
available software resources. manually. A scheduled task imports all of the
software resource data that the task is
designed to import. With a manual import,
you can select specific software resources to
import.
See “Importing data from a data provider with
a schedule” on page 110.
See “Importing data from a data provider
manually” on page 112.
Step 5
View the Software Data
Provider Status report.
This report lets you view the status of the
import tasks for all data providers or for a
specific data provider. You can double-click
a task to see the status of each software
resource that the task attempted to import.
This report is in the Data Providers folder,
which is in the Software reports folder.
108
Importing data from a data provider
Configuring the precedence settings for a data provider
Configuring the precedence settings for a data
provider
After you add a data provider, you should configure the precedence settings for the
data provider. The precedence settings determine whether the data provider can
update the metadata of a software resource that is in the Software Catalog.
See “Adding a data provider” on page 106.
Precedence settings determine whether a data provider can update the metadata
of a software resource in the Software Catalog. A data provider must have a higher
precedence setting to update data from another data provider. You should assign
the data provider that has the highest quality data the highest precedence so no
other data provider can update its data.
To configure precedence settings, you arrange a list of data providers. The data
provider that is highest in the list has the highest precedence settings. This list
includes all of the registered data providers. A data provider that has a configured
connection is registered data provider. This list also includes a data provider called
Other Software Providers. Other Software Providers includes any user of the
Software Catalog and any Symantec Management Platform product that puts data
in the Software Catalog. By default, Other Software Providers has the highest
precedence.
You can set precedence settings for the following types of metadata:
■
Properties
■
Packages
■
Detection rule
■
Associations
Table 6-4 displays the results when a Software Catalog user has the highest
precedence, data provider 1 the next highest, and data provider 2 the lowest.
Table 6-4
Examples of how precedence settings work
Data provider that last provided the Data provider that
data
attempts to update
the data
Result
Software Catalog user
Data provider 1 or 2
Data not updated
Any data provider
Software Catalog user
Data updated
Data provider 2
Any data provider
Data updated
109
Importing data from a data provider
Importing data from a data provider with a schedule
Table 6-4
Examples of how precedence settings work (continued)
Data provider that last provided the Data provider that
data
attempts to update
the data
Result
Data provider 1
Data provider 2
Data not updated
Data provider 1
Data provider 1
Data updated
If you remove a data provider, any metadata that it imported into the Software
Catalog is assigned the lowest precedence. Any other data provider can then update
its data.
To configure the precedence settings, you must be assigned the Symantec Software
Librarian security role. The Symantec Management Platform administrator can
assign people to this role.
To configure the precedence settings for data providers
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Data Provider > Data
Provider Management.
3
On the Data Provider Management page, click Set Precedence.
For more information about the options, click the page and then press F1
4
In the Set Data Provider Precedence dialog box, configure the precedence
settings for each type of metadata.
For more information about the options, click the page and then press F1
5
To save the changes, click OK.
Importing data from a data provider with a schedule
You can schedule the import of the metadata of the available software resources
of a data provider. A software resource is available, if it has data that is ready to
be imported. If the data provider supports importing software packages, you can
also schedule the import of the software packages that are associated with the
metadata.
See “Importing data from a data provider” on page 107.
If you want more control over what is imported, use a manual import.
See “Importing data from a data provider manually” on page 112.
110
Importing data from a data provider
Importing data from a data provider with a schedule
If the metadata for a software resource already exists in the Software Catalog,
precedence settings determine if a data provider can update the data. The exception
is File Inventory data, which is additive, so precedence settings don’t apply. If a
software resource in the Software Catalog already has an associated software
package, a data provider cannot update the package.
In the following procedure, you schedule the import task from the data provider in
the Providers folder. You can also schedule the task from the Data Providers
Web part.
See “Web parts for Software Management Framework” on page 19.
In addition to this method of scheduling the automatic import of data, a data provider
might have other methods for automatically importing its data.
To import data from a data provider with a schedule
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Data Provider > Providers,
and then select the data provider.
3
On the data providers page, under Task Status, click New Schedule.
You can also schedule the import from the right-click menu of the data provider
on the Data Providers Web part.
See “Web parts for Software Management Framework” on page 19.
4
In the New Schedule dialog box, under Schedule, specify a schedule for the
import task.
5
Under Input, type a description for the task.
This description identifies the task in the list of tasks that are associated with
the data provider. If the task is scheduled to run in the future, it is not assigned
this description until it runs.
6
Under Action, click one of the following options:
■
Import Data
This option imports only the metadata of the available software resources
into the Software Catalog. If a software package is associated with a
software resource, a software package resource is created in the Software
Catalog. This software package resource is sourced from the location that
the data provider specifies.
■
Import Data and Package
This option imports the metadata of the available software resources into
the Software Catalog and the associated software packages into the
Software Library. The software package resource in the Software Catalog
111
Importing data from a data provider
Importing data from a data provider manually
is sourced from the Software Library and not from the location that the data
provider specifies.
7
Click Schedule to complete the creation of the scheduled import task.
This import task is listed in the Task Status section of the data provider.
Importing data from a data provider manually
You can import data from a data provider for selected software resources instead
of importing all of the available software resources. This ability to select specific
software resources gives you complete control over what is imported. For example,
you might have an urgent need to import the metadata and the software package
of a specific software resource. You do not want to waste time importing data for
other software resources. You can select that software resource and import only
its data.
See “Importing data from a data provider” on page 107.
If your data provider has a large amount of data that is available for import, we
recommend that you import the data manually. When you import the data manually,
you can avoid cluttering the Software Catalog with the data that you do not use. If
you want to import all available software resources instead of specific software
resources, import the data on a schedule.
See “Importing data from a data provider with a schedule” on page 110.
To import data for selected software resources, you first gather a list of available
software. A software resource is available if it has data that is ready to be imported.
You then select from this list the software resources whose data you want to import.
If the metadata for a software resource already exists in the Software Catalog,
precedence settings determine if a data provider can update the data. The exception
is File Inventory data, which is additive, so precedence settings don’t apply. If a
software resource in the Software Catalog already has an associated software
package, a data provider cannot update the package.
To import data from a data provider manually
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, under Settings, click Software > Data Provider > Data
Provider Management.
3
In the right pane, select the data provider.
4
On the Actions menu, click View Data Provider Summary.
112
Importing data from a data provider
Importing data from a data provider manually
5
If the software resource is not listed on the Data Provider Summary page, do
the following to gather the software resource from the data provider.
■
On the Gather menu, select the data provider that has the data that you
want to import.
■
In the New Schedule dialog box, under Schedule, specify a schedule for
the gather task.
■
Under Input, type a description for the task, and then click Schedule.
The description identifies the task. If the task is scheduled to run in the
future, it is not assigned this description until it runs.
This task is listed on the data provider’s page in the Providers folder. You
can access the Providers folder on the Settings menu at Software > Data
Provider.
For more information about the options, click the page and then press F1
6
After the data is gathered, on the Data Provider Summary page, click the
Refresh symbol to display the software resources that were gathered.
Depending on the data provider, the gather can take several minutes. If no
new software resources appear, then the data provider did not have any
available software resources.
7
In the list of software resources, select the software resources to import.
8
On the Import menu, click one of the following options:
■
Data only
This option imports only the metadata of the available software resources
into the Software Catalog. If a software package is associated with a
software resource, a software package resource is created in the Software
Catalog. This software package resource is sourced from the location that
the data provider specifies.
■
Data and Package
This option imports the metadata of the available software resources into
the Software Catalog and the associated software packages into the
Software Library. The software package resource in the Software Catalog
is sourced from the Software Library and not from the location that the data
provider specifies.
113
Chapter
7
Managing Windows
Installer applications
This chapter includes the following topics:
■
Introducing Windows Installer applications
■
Updating the source paths of Windows Installer applications
■
Configuring a Source Path Update policy
■
Repairing Windows Installer applications
■
Configuring a Windows Installer Repair policy
■
Creating customized Windows Installer policies and tasks
Introducing Windows Installer applications
You can create policies and tasks to manage Windows Installer applications on
managed computers. The policies and the tasks work with Windows Installer to
enhance its functionality.
You can manage Windows Installer applications in the following ways:
Initiate the repair of Windows You can proactively identify and repair broken applications
Installer applications.
on selected computers. If an application needs repair, a repair
command is sent to the Windows Installer service to initiate
self-repair.
You can use a policy or a task to identify the applications that
need repair.
Managing Windows Installer applications
Updating the source paths of Windows Installer applications
Update the source paths for
Windows Installer
applications.
You can update the source paths of Windows Installer
applications with resilient source paths. The updated source
paths point to the package servers that you designate. If an
application needs modification or repair, Windows Installer
can access the needed installation file from one of these
servers.
You can use a policy or a task to update the source paths.
View reports to monitor the
state of Windows Installer
applications.
When you create policies or tasks to manage Windows
Installer applications, data is gathered on broken applications
and inaccessible source paths. The Application Management
reports that are listed under the Software reports display this
data. You can use this data to monitor the state of Windows
Installer applications. For example, the Software Resources
- Broken Elements report displays the computers that had
broken applications during a specified date range. For each
computer, the report lists each occurrence of a broken
application and identifies its broken element.
See “Running a Software Management Solution report”
on page 157.
Updating the source paths of Windows Installer
applications
You can update the source paths of Windows Installer applications with resilient
source paths. The updated source paths point to the package servers that you
designate. If an application needs modification or repair, Windows Installer can
access the needed installation file from one of these servers.
You can use a policy or a task to perform resilient source path updates of Windows
Installer applications on managed computers.
When a Windows Installer application is broken, Windows Installer can repair or
modify it, but only if the original installation file is accessible. When Windows Installer
tries to modify or repair an application, it uses the application’s source path to access
the installation file. This source path is based on the application’s package code.
Without resilient source paths, if the installation file is no longer available, the
modification or repair fails. With resilient source paths, Windows Installer can look
for the installation file on a set of package servers that you designate.
For example, the software delivery policies and tasks in Software Management
Solution typically install packages from a package server. If that package server
becomes unavailable, a Windows Installer application that was installed from that
115
Managing Windows Installer applications
Updating the source paths of Windows Installer applications
server cannot be repaired. To avoid this problem, update the application’s source
paths to point to additional servers from which the installation file can be accessed.
You can perform resilient source path updates of Windows Installer applications
with a policy or a task as follows:
Policy
Use a policy as your primary means to update the source paths of Windows
Installer applications. A policy can update the source paths of existing
applications, but also the source paths of the applications that are installed
in the future. To include the applications that are not yet installed, schedule
the policy to run repeatedly.
A Source Path Update policy updates all the Windows Installer applications
that are installed on the client computer.
Task
Use a task when you need to update the source path of a specific application
and the update needs to be done immediately. For example, a Windows
Installer repair might fail because the server that distributed the application
is out of service. You can create a task to update the source path for that
application.
A Source Path Update task can update a specific application or all the
Windows Installer applications that are installed on the client computer.
The Software Management Solution plug-in must be installed on the client computers
for you to update source paths.
See “Installing or upgrading the Software Management Solution plug-in” on page 65.
Table 7-1
Process for updating source paths for Windows Installer applications
Step
Action
Description
Step 1
Configure a policy or create
a task to update the source
paths of Windows Installer
applications.
A Source Path Update policy or task adds resilient source paths to
Windows Installer applications on managed computers.
See “Configuring a Source Path Update policy” on page 117.
See “Creating a task in Software Management Solution” on page 153.
You can also create a Source Path Update task from a software
resource in the Software Catalog. If you create the task from a software
resource, you select the computers that the task applies to and the task
runs immediately.
Step 2
(Optional, task only)
Configure the task settings.
Every task inherits the default settings that control how it runs. You can
override the default settings for a particular task.
You cannot change the settings for a Source Path Update policy.
116
Managing Windows Installer applications
Configuring a Source Path Update policy
Table 7-1
Process for updating source paths for Windows Installer applications
(continued)
Step
Action
Description
Step 3
(Task only) Schedule the task The options for scheduling the task are as follows:
and select the delivery
■ Run the task now.
destinations.
This option runs the task as soon as possible, unless it must wait
for a maintenance window.
■ Schedule the task to run at a specific time.
See “Scheduling a task and selecting computers in Software
Management Solution” on page 156.
This additional step is not necessary for the policy because you schedule
it as part of its configuration.
Step 4
View the Software
Resources - Inaccessible
Source Paths report.
This report lists the computers that had Windows Installer applications
with inaccessible source paths during the most recent scan. Use this
report to identify the changes that you need to make to resolve
inaccessible source path problems. This report is one of the Application
Management reports listed under the Software reports.
See “Running a Software Management Solution report” on page 157.
Configuring a Source Path Update policy
To update the source paths of Windows Installer applications with resilient source
paths, you need to configure a Source Path Update policy. Configuring the policy
is a step in the process of updating the source paths of Windows Installer
applications.
See “Updating the source paths of Windows Installer applications” on page 115.
After you configure the policy, it runs as scheduled on the specified computers or
for the specified users. If you schedule the policy to repeat, it can continue to check
and update the source paths.
To configure a Source Path Update policy
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand Software > Application Management > Windows,
and then click Source Path Update.
117
Managing Windows Installer applications
Configuring a Source Path Update policy
3
In the right pane, on the Source Path Update page, under Settings, specify
the package servers to use as follows:
First Server to
Use
Lets you select the first server to use as a source path. You can
click Any Server or you can select a specific server from the list.
The package server that you select must be accessible to the
computers that are specified in the policy.
To optimize bandwidth, select specific package servers to serve
as the source paths for Windows Installer applications. Servers
between the first and last are used in order of response speed.
If you do not select specific package servers, the update begins
with the fastest-responding server and works toward the slowest.
It then ends with the Notification Server computer.
Last Server to
Use
Lets you select the last server to use as a source path. You can
click Any Server or you can select a specific server from the list.
The package server that you select must be accessible to the
computers that are specified in the policy.
4
In Maximum Number of Servers, type the maximum number of servers to
use for the source path update.
5
Under Schedule, configure the schedule for the policy.
To run this policy on a recurring basis, under Schedule, click No repeat, and
then, in the Repeat Schedule dialog box, choose the repeat interval.
For more information, see the topics about specifying a policy schedule in the
Altiris™ IT Management Suite 7.5 Administration Guide from Symantec™at
the following URL:
http://www.symantec.com/docs/DOC5330
6
Under Applied to, choose the computers or users to which the policy applies.
For more information, see the topics about specifying the targets of a policy or
task in the Altiris™ IT Management Suite 7.5 Administration Guide from
Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
7
Turn on the policy.
At the upper right of the page, click the colored circle, and then click On.
8
Click Save changes.
118
Managing Windows Installer applications
Repairing Windows Installer applications
Repairing Windows Installer applications
You can proactively identify and repair broken Windows Installer applications on
managed computers even before the user encounters a problem. If an application
needs repair, a repair command is sent to the Windows Installer service to initiate
self-repair.
You can repair Windows Installer applications on managed computers with a policy
or task as follows:
Policy
Use a policy as your primary means to repair Windows Installer applications.
A policy not only repairs the applications that are currently broken, but it can
also repair any applications that break in the future. To repair current and
future applications, schedule the policy to run on a recurring basis.
A policy can perform a quick repair or a full repair.
Task
Symantec recommends that you use a task to repair a specific application.
For example, if a user reports a broken application, you can create a task
to repair that specific application on that user’s computer.
A task can perform a full repair only.
Note: Windows Installer repair task or policy fail on computers with Cloud-enabled
management if the software installation package for a broken Windows Installer
application is not available.
See “Repairing Windows Installer applications” on page 119.
The Software Management Solution plug-in must be installed on the client computers
for you to perform Windows Installer repairs.
See “Installing or upgrading the Software Management Solution plug-in” on page 65.
Instead of using a Windows Installer Repair policy or task to repair Windows Installer
applications, you can use the remediation feature of Managed Software Delivery.
Managed Software Delivery provides more control over the criteria that are used
to determine when a repair is needed. Instead of a predefined key path, it uses the
metadata that is associated with the software resource, that is defined in the
Software Catalog. Managed Software Delivery can also repair multiple software
resources with a single policy. A Windows Installer Repair policy or task can repair
one application or all applications.
See “About policy applicability, compliance, and remediation” on page 176.
119
Managing Windows Installer applications
Configuring a Windows Installer Repair policy
Table 7-2
Process for repairing Windows Installer applications
Step
Action
Description
Step 1
Configure a policy or create
a task.
Configure a Windows Installer Repair policy to check and repair
Windows Installer applications on a recurring basis.
See “Configuring a Windows Installer Repair policy” on page 120.
Create a Windows Installer Repair task to repair a specific application.
See “Creating a task in Software Management Solution” on page 153.
Step 2
(Optional, task only)
Configure the task settings.
Every task inherits the default settings that control how it runs. You can
override the default settings for a particular task.
You cannot change the settings for a Windows Installer Repair policy.
Step 3
(Task only) Schedule the task Your options for scheduling the task are as follows:
and choose the delivery
■ Run the task now.
destinations.
This option runs the task as soon as possible, unless it must wait
for a maintenance window.
■ Schedule the task to run at a specific time.
See “Scheduling a task and selecting computers in Software
Management Solution” on page 156.
This additional step is not necessary for the policy because you schedule
it as part of its configuration.
Step 4
View the Application
Management reports that
identify broken elements.
These reports display the Windows Installer applications that had broken
elements during a specified time range. The reports also identify the
element that is broken. If an application could not be repaired, the
Software Resources - Current Broken Elements report displays
details about why the repair failed.
Use these reports to help you resolve broken Windows Installer
applications. These reports are listed under the Software reports.
See “Running a Software Management Solution report” on page 157.
Configuring a Windows Installer Repair policy
To repair Windows Installer applications on managed computers, configure a
Windows Installer Repair policy. Symantec recommends that you use a policy to
check and repair Windows Installer applications on a recurring basis. This is a step
in the process for repairing Windows Installer applications.
See “Repairing Windows Installer applications” on page 119.
120
Managing Windows Installer applications
Configuring a Windows Installer Repair policy
After you configure the policy, it runs as scheduled on the specified computers or
for the specified users. Whenever the policy discovers a broken application, it
initiates a repair. If you schedule the policy to repeat, it can continue to check and
repair the applications.
You can clone a Windows Installer Repair policy to create policies with different
schedules for different computers. To do that, right-click a policy, and the click
Clone.
To configure a Windows Installer Repair policy
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand Software > Application Management > Windows,
and then click one of the following options:
■
Windows Installer Full Repair
Type of scan
Runs a Quick Scan, like the quick repair, and then runs a
deep scan. The deep scan identifies Windows Installer
applications and verifies that all of the component’s
resources are installed correctly. If any element of a
component is not installed correctly, the policy or the task
repairs that component and reports the results.
Scan time and
resources
A Windows Installer Full Repair takes more time and
resources than a Windows Installer Quick Repair.
What it discovers
A full repair discovers every Windows Installer application
that needs repair while a quick repair might not.
Method for performing Use a policy or a task.
the repair
■
Windows Installer Quick Repair
Type of scan
Runs a Quick Scan that identifies Windows Installer
applications and verifies that each component’s key path is
installed correctly. If the component’s key path is not installed
correctly, the policy tries to repair the component and reports
the results.
For example, if the Microsoft Word key path file,
winword.exe, is not installed in the correct path, the policy
tries to repair Word.
Scan time and
resources
A Windows Installer Quick Repair takes less time and fewer
resources than a Windows Installer Full Repair.
121
Managing Windows Installer applications
Creating customized Windows Installer policies and tasks
What it discovers
A quick repair discovers only broken or missing key paths.
If a component has other missing or broken files, a quick
repair might not repair them.
Method for
Use a policy.
performing the repair
3
In the right pane, under Schedule, on the toolbar, click Add schedule, and
then specify the schedule for the policy.
To run this policy on a recurring basis, under Schedule, click No repeat and
then, in the Repeat Schedule dialog box, select the repeat interval.
For more information, see the topics about specifying a policy schedule in the
Altiris™ IT Management Suite 7.5 Administration Guide from Symantec™at
the following URL:
http://www.symantec.com/docs/DOC5330
4
Under Applied to, specify the computers or users to which the policy applies.
For more information, see the topics about applying a policy to targets,
computers, resources, and users in the Altiris™ IT Management Suite 7.5
Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
5
Turn on the policy.
At the upper right of the page, click the colored circle, and then click On.
6
Click Save changes.
Creating customized Windows Installer policies and
tasks
A software resource for the Application Management agent is created in the Software
Catalog when Software Management Solution is installed. You can use this software
resource to create your own policies and tasks to repair Windows Installer
applications or to update their source paths. Create your own policies and tasks
only if the predefined policies and tasks do not meet your needs.
The policies and the tasks that perform Windows Installer repairs or source path
updates use the Application Management agent. When these tasks or these policies
run on managed computers, they install the agent if it is not already installed. The
122
Managing Windows Installer applications
Creating customized Windows Installer policies and tasks
Application Management agent works with Windows Installer to help you manage
Windows Installer applications.
The Application Management agent also gathers data about Windows Installer
applications on managed computers. You can view this data on the Application
Management reports that are listed under the Software reports. Create your own
policies and tasks only if the predefined policies and tasks do not meet your needs.
See “Running a Software Management Solution report” on page 157.
A software resource for the Application Management agent is created in the Software
Catalog when Software Management Solution is installed. You can use this software
resource to create your own policies and tasks to repair Windows Installer
applications or to update their source paths.
See “Creating customized Windows Installer policies and tasks” on page 122.
You can determine where the Application Management agent is installed. Create
a Targeted Software Inventory policy for the Application Management agent’s
software resource so you can look for the agent on selected client computers.
For more information, see the topics about Targeted Software Inventory in the
Inventory Solution User Guide.
Table 7-3
Process for creating and customizing Windows Installer policies and
tasks
Step
Action
Description
Step 1
Create a customized
command line for the
Application Management
agent package in the
Software Catalog.
You can either edit an existing command line
or create a new command line.
Deliver the Application
Management agent with the
customized command line.
You can use Quick Delivery or Managed
Software Delivery to deliver the agent. In
Managed Software Delivery, you can create
the command line when you create the policy.
Step 2
See “Creating a command line for a software
resource” on page 81.
See “Creating a Managed Software Delivery
policy with the Managed Software Delivery
wizard” on page 183.
See “Creating a Quick Delivery task with the
Quick Delivery wizard” on page 152.
123
Chapter
8
Managing virtual
applications
This chapter includes the following topics:
■
Introducing software virtualization and virtual applications
■
Installing the Symantec Workspace Virtualization Agent
■
Managing virtual applications
■
Virtualizing software during installation
■
Installing and managing a virtual software layer with a Software Virtualization
task
■
Installing and managing a virtual software layer with a Quick Delivery or Package
Delivery task
■
Installing and managing a virtual software layer with a Managed Software
Delivery policy
Introducing software virtualization and virtual
applications
Before you start managing virtual applications, it is a good idea to better understand
what they are and what you can use them for.
To help you get more familiar with software virtualization you can refer to the
following:
■
About software virtualization and virtual software layers
See “About software virtualization” on page 125.
Managing virtual applications
Introducing software virtualization and virtual applications
■
About how virtual software layers facilitate the management of software on client
computers
See “About managing virtual applications” on page 126.
■
About portable virtual software layers
See “About VSA and XPF virtual package files” on page 127.
■
About guidelines you can use to determine what you can and cannot virtualize
See “About the applications that you can virtualize” on page 127.
■
About data layers to prevent the loss of data that a virtual application creates
or modifies
See “About data layers, exclude entries, and preventing the loss of virtual
application data” on page 128.
■
About the methods you can use to virtualize software
See “Methods for virtualizing software” on page 130.
■
About the methods you can use to install and manage virtual software
See “Methods for installing and managing virtual software” on page 131.
■
About the actions that you can perform on a virtual software layer
See “Actions that you can perform on a virtual software layer” on page 133.
About software virtualization
Software virtualization lets you create virtual software layers. These layers consist
of one or more Windows-based applications or sets of data. A virtual software layer
contains all the files and registry settings of the application or the set of data.
Software virtualization requires a licensed version of the Symantec Workspace
Virtualization Agent to be installed on the client computers.
See “Installing the Symantec Workspace Virtualization Agent ” on page 134.
When you install a virtual software layer on a computer, the contents of the layer
are placed in a protected folder on the hard drive. This protected folder is referred
to as the redirection area. The files and registry settings of a layer are placed in
subfolders in the redirection area. When you activate a layer on a computer, its
contents are layered over the base file system and registry. The contents of the
layer appear where they would be if they were installed with a normal installation.
For example, if you install a virtual software layer for Firefox, its files are placed in
a subdirectory of C:\fslrdr. After you activate the layer for Firefox, the filter driver
displays the files for Firefox in C:\Program Files.
To accomplish this virtualization process, software virtualization uses a file system
filter driver. This filter driver intercepts requests to the file system and the registry,
and then redirects the requests to the active layer. The filter driver aggregates the
125
Managing virtual applications
Introducing software virtualization and virtual applications
real file system and the virtual file system into one view for the user. This filter driver
is the main component of the Symantec Workspace Virtualization Agent.
Because software virtualization uses redirection, it can maintain discrete settings
and file versions for different applications on a single computer. When you use
software virtualization, a required version of a file is never overwritten, and the
problem of conflicting DLL files is eliminated.
See “Managing virtual applications” on page 135.
See “About VSA and XPF virtual package files” on page 127.
See “About data layers, exclude entries, and preventing the loss of virtual application
data” on page 128.
About managing virtual applications
Software virtualization lets you install Windows-based applications into virtual
software layers.
See “About software virtualization” on page 125.
Virtual software layers facilitate the management of software on client computers
as follows:
You avoid conflicts
between applications.
A virtual application always uses the correct files and registry
settings and does not modify the operating system or interfere
with other applications. You can even install two versions of the
same application on the same computer.
You can repair broken
applications quickly.
If an application is broken, you can quickly reset its layer to restore
the application to its original installed state. When an application’s
layer is reset, other applications that are installed on the computer
cannot be damaged.
You can easily roll back When you install a new version of an application, you can
to an earlier version.
deactivate the earlier version. If the new version causes problems,
you can easily deactivate it and activate the earlier version.
Software Management Solution lets you perform the following virtualization actions:
■
Virtualize applications during a Managed Software Delivery installation.
See “Methods for virtualizing software” on page 130.
■
Deliver and manage virtual layers with any delivery policy or task in Software
Management Solution.
See “Methods for installing and managing virtual software” on page 131.
126
Managing virtual applications
Introducing software virtualization and virtual applications
About VSA and XPF virtual package files
Virtual software archive (VSA) and extensible package format (XPF) files are a
portable virtual software layer, which installs one or more Windows-based
applications or sets of data.
See “About managing virtual applications” on page 126.
XPF files replaced VSA files as the new default package format for the release of
Symantec Workspace Virtualization 6.1 SP4. In addition, Symantec now supports
XPF software packages in the Software Catalog. Symantec continues to support
the VSA format in the Software Catalog.
For more information on XPF see topics on understanding the packaging process
in the Wise™ Virtual Composer User's Guide.
You can use either of the following tools to repackage an application’s installation
file to create a VSA or an XPF file:
■
Wise Package Studio 7.0 or later
■
Symantec Workspace Virtualization (formerly known as Software Virtualization
Solution)
You can create a software resource for a VSA or an XPF file in the Software Catalog.
When you create the software resource, you can add the VSA or an XPF file to the
Software Library. In the Software Catalog, you can edit the software resource. For
example, you can define associations and additional command lines. The Command
Line Builder makes it easy to create syntactically correct command lines for the
software resource of a VSA or an XPF file.
After you create the software resource for a VSA or an XPF file in the Software
Catalog, you can use any delivery method to deliver it. You can also deliver a VSA
or an XPF file with a Software Virtualization task.
See “Methods for delivering software” on page 145.
See “Installing and managing a virtual software layer with a Software Virtualization
task” on page 138.
When you deliver a VSA or an XPF file, the Symantec Workspace Virtualization
Agent installs it to create a virtual software layer. After the layer is created and
activated, its files and registry settings become visible. If the layer contains an
application, the application functions as if it were not in a layer.
See “About software virtualization” on page 125.
About the applications that you can virtualize
(Windows only)
127
Managing virtual applications
Introducing software virtualization and virtual applications
Use the following guidelines to determine what you can and cannot virtualize:
What you can virtualize
Most Windows-based applications can be virtualized,
including the following types of applications:
■
Office applications
■
Databases
■
Internet browsers except for Internet Explorer
■
Media
Spyware utilities
Virtual applications function normally, and all configuration
options are available to the user.
What you cannot virtualize
You cannot virtualize the following applications or files:
■
Windows operating system components
■
Windows operating system patches
■
Drivers
■
Applications that have dedicated drivers
For example, client firewalls.
All management agents including antivirus software,
security scanners, encryption agents, or any agent that
is used in the Symantec Management Platform
Data files that you plan to encrypt
■
■
■
The diagnostic utilities or recovery utilities that run in safe
mode
Software virtualization does not run in safe mode.
See “About managing virtual applications” on page 126.
See “Methods for virtualizing software” on page 130.
About data layers, exclude entries, and preventing the loss of virtual
application data
(Windows only)
A data layer stores data that would otherwise be written to an application layer or
the base file system. You can use a data layer to prevent the loss of data that a
virtual application creates or modifies. You can use one or more data layers on a
computer.
If a virtual application saves data in the virtual software layer, the data is lost when
the layer is reset. To prevent the loss of application data, ensure that the application
data is not saved in the application’s layer.
See “About managing virtual applications” on page 126.
128
Managing virtual applications
Introducing software virtualization and virtual applications
The application data is not saved in the application’s layer in the following situations:
■
When the data is excluded with an exclude entry.
An exclude entry excludes files from a layer and saves them in the base file
system instead.
■
When the data is saved in a data layer.
You can create and deploy data layers to capture application data. When a data
layer captures data from a virtual application, it is excluded from the application’s
layer.
■
When the data is not saved locally.
For example, if a virtual application creates data and the data is saved on a
network share, the data is excluded from the application’s layer.
Exclude entries prevent the loss of data that a virtual application creates or modifies.
When a virtual application creates or modifies application data, the data files can
be saved in the application layer. If the layer is reset, the files are lost. An exclude
entry excludes files from a layer and saves them in the base file system instead.
An exclude entry can exclude a file type or a directory. If an exclude entry excludes
a directory, it can also exclude its subdirectories.
Exclude entries can be created with the following products:
■
Any WiseScript product such as WiseScript Editor or WiseScript Package Editor.
The Set SVS Exclude Entry script action can create exclude entries on client
computers.
■
Software Virtualization Solution or its new version, which is called Symantec
Workspace Virtualization.
For more information about exclude entries, see the respective product’s
documentation.
129
Managing virtual applications
Introducing software virtualization and virtual applications
Table 8-1
Types of exclude entries
Type
Description
Layer exclude entry
Redirects the files from a specific layer to the base file
system.
For example, a virtual software layer for Microsoft Word can
have a layer exclude for the following file types: DOC, RTF,
TXT. When Word saves a file with any of these file types, the
file is saved in the base file system and not in the layer.
Note: When you use Managed Software Delivery to virtualize
software during installation, the resulting layer has no layer
exclude entries.
See “Virtualizing software during installation” on page 136.
Global exclude entry
Redirects the files for every virtual software layer on a
computer to the base file system. For example, a computer
can have a global exclude for PDF files. If a layer creates
PDF files, the files are excluded from the layer and saved in
the base file system.
By default, when the Symantec Workspace Virtualization
Agent is installed on a managed computer, global excludes
are created for the My Documents and the Desktop
directories.
A data layer takes precedence over an exclude entry. If a data layer contains the
same data that an exclude entry excludes, the data is saved in the data layer.
You can create data layers in either of the following products:
■
Virtual Package Editor in Wise Package Studio 7.0 or later
■
Software Virtualization Solution or its new version, which is called Symantec
Workspace Virtualization.
Methods for virtualizing software
Software virtualization is the creation of virtual software layers. A virtual software
layer contains all the files and registry settings of one or more Windows-based
applications or sets of data.
See “Managing virtual applications” on page 135.
See “About the applications that you can virtualize” on page 127.
130
Managing virtual applications
Introducing software virtualization and virtual applications
Warning: If a virtual application is reset, it is possible to lose the data that the
application creates or modifies. Before you use virtual applications, make sure that
you understand how to prevent the loss of application data.
Table 8-2
Methods for virtualizing software
Method
Description
Virtualize the software during Lets you deliver the vendor’s installation file. For example,
installation
you can deliver an MSI or EXE. The installation file is
virtualized when it is installed. This method is only available
with Managed Software Delivery.
Symantec recommend this method for the following reasons:
■
■
It uses the installation file that the vendor created so that
you do not have to repackage the installation.
It preserves any logic that the vendor might have added
to the installation.
For example, an installation might contain logic to install
a different DLL file depending on the computer’s operating
system. If you repackage the software, this logic is lost.
A repackaged installation contains the DLL file for only
the operating system on which the installation was
repackaged.
See “Virtualizing software during installation” on page 136.
Virtualize the software before This method requires that you repackage the installation file
installation
to create a virtual software archive (VSA) or extensible
package format (XPF) file. VSA and XPF files are a portable
virtual software layer, which installs one or more
Windows-based applications or sets of data.
Use a tool other than Software Management Solution to
perform this step.
See “About VSA and XPF virtual package files” on page 127.
See “Methods for delivering software” on page 145.
Methods for installing and managing virtual software
(Windows only)
You can use any delivery task or policy to install software into a virtual layer on a
client computer. You can use the same methods to manage the layer after it is
installed.
131
Managing virtual applications
Introducing software virtualization and virtual applications
The task or policy installs and manages the layer by running a command line that
performs actions on the layer.
See “Actions that you can perform on a virtual software layer” on page 133.
See “About VSA and XPF virtual package files” on page 127.
The methods for installing and managing virtual software, are as follows:
Table 8-3
Methods for installing and managing virtual software
Method
Description
Software Virtualization task
Lets you install a virtual software archive (VSA) or extensible package format (XPF)
file to a managed computer and create a new virtual software layer. It also lets you
manage any virtual software layer regardless of how the layer was created. Each action,
including the installation, requires a separate task.
You can also add a Software Virtualization task to a job or a Managed Software Delivery
policy to perform more complex management tasks.
See “Installing and managing a virtual software layer with a Software Virtualization
task” on page 138.
Quick Delivery task
Package Delivery task
Lets you install a virtual software archive (VSA) or extensible package format (XPF)
file to a managed computer and create a new virtual software layer. It also lets you
manage a virtual software layer that was created by installing a virtual software archive
file. Each action, including the installation, requires a separate task.
You can also create a Quick Delivery task or a Package Delivery task and add it to a
Managed Software Delivery policy.
See “Installing and managing a virtual software layer with a Quick Delivery or Package
Delivery task” on page 140.
Managed Software Delivery
policy
Lets you perform more complex management tasks. A Managed Software Delivery
policy can create and manage new virtual software layers, and it can also manage
existing layers.
See “Installing and managing a virtual software layer with a Managed Software Delivery
policy” on page 141.
You can manage multiple virtual software layers at the same time. For example, you
can create a policy that installs a new version of an application into a layer, and then
deactivates the earlier version. To do this, you can add multiple Software Virtualization
tasks, Quick Delivery tasks, or Package Delivery tasks to a Managed Software Delivery
policy.
See “Delivering multiple software resources and tasks sequentially” on page 190.
If you need to manage a single virtual software layer, we recommend that you use one
of the other methods.
132
Managing virtual applications
Introducing software virtualization and virtual applications
Actions that you can perform on a virtual software layer
(Windows only)
After you install Windows-based software into a virtual software layer on client
computers, you can manage the layer. To do so, you run a command line that
performs actions on the layer.
See “Methods for installing and managing virtual software” on page 131.
Table 8-4
Actions that you can perform on a virtual software layer
Action
Description
Activate
Activates a virtual software layer that was installed on a managed computer. When a
layer is activated, its contents become visible to the user. If the layer contains an
application, the application is fully functional.
Deactivate
Deactivates a virtual software layer that was installed on a managed computer. When
a layer is deactivated, it is hidden from the user but is still on the computer.
If a process from the layer is running, this action fails unless you also select an option
to force the operation to complete.
Deactivate and Delete
Deactivates and deletes a virtual software layer that was installed on a managed
computer. Before you can delete some applications, you must first deactivate them.
For example, you must deactivate Yahoo! Messenger before you can delete it. This
action is not available with a Software Virtualization task.
Delete
Deletes a virtual software layer that was installed on a managed computer. This action
removes the layer and all of its contents.
Note: If the application you want to delete is open on the client computer, the Delete
command line does not delete the layer. The Delete command line does not delete the
layer even when you check Force this operation to complete. To delete the layer,
create a job with two tasks: the first with the Deactivate command line and the second
with the Delete command line. In both tasks, you must also check Force this operation
to complete. Alternatively you can use a single task using the Deactivate and Delete
command line with Force this operation to complete.
Import
Imports (installs) a virtual software archive (VSA) or extensible package format (XPF)
file to a managed computer and creates a new virtual software layer. After you install
the VSA or XPF file, you must activate the layer to make it functional.
See “About VSA and XPF virtual package files” on page 127.
Import and Activate
Imports a VSA or XPF file onto a managed computer, creates a new virtual software
layer, and activates the layer.
This action is not available in a Software Virtualization task.
See “About VSA and XPF virtual package files” on page 127.
133
Managing virtual applications
Installing the Symantec Workspace Virtualization Agent
Table 8-4
Actions that you can perform on a virtual software layer (continued)
Action
Description
Reset
Resets a virtual software layer to its original installed state.
Warning: When a layer is reset, it is possible to lose the data that the application
creates or modifies.
Reset and Activate
Resets a virtual software layer to its original installed state and activates the layer.
Warning: When a layer is reset, it is possible to lose the data that the application
creates or modifies.
This action is not available in a Software Virtualization task.
Reset and Deactivate
Resets a virtual software layer to its original installed state and deactivates the layer.
Before you can deactivate some applications that are in a bad state, you must first
reset them.
Warning: When a layer is reset, it is possible to lose the data that the application
creates or modifies.
This action is not available in a Software Virtualization task.
Set active on startup
Configures a virtual software layer to be activated when a computer starts. If a layer
is not activated on startup, a user can access it only if they can activate it manually.
This action is not available in a Software Virtualization task.
Set not active on startup
Configures a virtual software layer not to be activated when a computer starts. If a
layer is not activated on startup, a user can access it only if they can activate it manually.
You might perform this action if a user seldom uses a layer and the layer takes a
significant amount of time to activate.
This action is not available in a Software Virtualization task.
Installing the Symantec Workspace Virtualization
Agent
(Windows only)
If you plan to use software virtualization to manage Windows-based software on
client computers, install the Symantec Workspace Virtualization Agent on those
computers.
See “Managing virtual applications” on page 135.
See “Creating a command line for a software resource” on page 81.
134
Managing virtual applications
Managing virtual applications
The Symantec Workspace Virtualization Agent requires that the Software
Management Solution plug-in is installed on the client computers.
See “Installing or upgrading the Software Management Solution plug-in” on page 65.
To install the Symantec Workspace Virtualization Agent
1
In the Symantec Management Console, on the Settings menu, click
Agents/Plug-ins > All Agents/Plug-ins.
2
In the left pane, expand Software > Software Management > Workspace
Virtualization, and then click Install SWV agents.
3
On the Install SWV agents page, on the Software tab, click Advanced
options.
4
In the Advanced options dialog box, on the Results-based actions tab and
in the Upon sucess drop-down list select Restart computer.
Without this step, the installation process performs silently, and you have to
manually restart the computer to finish the installation. Note that a computer
restart is required before the Symantec Workspace Virtualization Agent operates
properly.
5
In the Applied to section, on the toolbar, click Apply to, and then choose
where to install the Symantec Workspace Virtualization agent.
6
In the Schedule section, configure the policy schedule.
7
At the upper right of the page, click the colored circle, and then click On.
8
Click Save changes.
Managing virtual applications
You can use software virtualization to facilitate the management of most
Windows-based software on client computers.
See “About software virtualization” on page 125.
See “About managing virtual applications” on page 126.
Software virtualization requires a licensed version of the Symantec Workspace
Virtualization Agent to be installed on the client computers.
See “Installing the Symantec Workspace Virtualization Agent ” on page 134.
135
Managing virtual applications
Virtualizing software during installation
Table 8-5
Process for managing virtual applications
Step
Action
Description
Step 1
Virtualize the software.
You can perform the virtualization during installation.
See “Methods for virtualizing software” on page 130.
See “About the applications that you can virtualize” on page 127.
You can also use the following options for virtualizing software:
■
■
Step 2
Install the software into a
virtual software layer.
Repackage an application into a portable virtual software layer.
See “About VSA and XPF virtual package files” on page 127.
Import an existing VSA or XPF file into the Software Catalog to
create a software resource.
See “Importing a package to create a software resource” on page 51.
You can install the software into a virtual layer on the client computer
at the same time that you virtualize the software.
See “Virtualizing software during installation” on page 136.
You also can use any delivery method to install a VSA or XPF file as
a new layer and activate it on the client computer.
See “Methods for installing and managing virtual software” on page 131.
Step 3
Manage the software that is
installed in virtual software
layers.
You can create a policy or task that executes a command line for a
specific virtual software layer. When the layer command line runs on a
managed computer, it performs an action on the layer.
For example, if a virtual application is broken, you can create a task
that executes a command line to reset the application’s layer. The
application is quickly restored to its original installed state.
See “Methods for installing and managing virtual software” on page 131.
See “Actions that you can perform on a virtual software layer”
on page 133.
Step 4
View the Virtualized Software You can use the reports to monitor the state of virtual applications.
Resources reports.
These reports are listed under the Software reports.
See “Running a Software Management Solution report” on page 157.
Virtualizing software during installation
(Windows only)
When you deliver Windows-based software with a Managed Software Delivery
policy, you can choose to virtualize the software when it is installed. You should
virtualize software if it conflicts with other software that could be installed on the
136
Managing virtual applications
Virtualizing software during installation
same computer. When you virtualize software, you avoid conflicts between that
application and other applications.
See “About managing virtual applications” on page 126.
When you choose to virtualize software during installation, the Managed Software
Delivery policy installs the software as follows:
If the Symantec Workspace
Virtualization Agent is
installed on the client
computer
The policy performs the following actions:
■
■
■
If the Symantec Workspace
Virtualization Agent is not
installed on the client
computer
Deactivates any active layers that are on the client
computer.
Installs the software into a new layer. You can specify the
layer name in the Managed Software Delivery policy.
If you do not provide a layer name, the layer name
defaults to the installation file name plus the command-line
name.
Reactivates any layers that it deactivated.
The policy installs the software normally.
See “Managing virtual applications” on page 135.
If a virtual application is reset, it is possible to lose the data that the application
creates or modifies. Before you use virtual applications, make sure that you
understand how to prevent the loss of application data.
The application data is not saved in the application’s layer in the following situations:
■
When the data is excluded with an exclude entry.
An exclude entry excludes files from a layer and saves them in the base file
system instead.
■
When the data is saved in a data layer.
You can create and deploy data layers to capture application data. When a data
layer captures data from a virtual application, it is excluded from the application’s
layer.
See “About data layers, exclude entries, and preventing the loss of virtual
application data” on page 128.
■
When the data is not saved locally.
For example, if a virtual application creates data and the data is saved on a
network share, the data is excluded from the application’s layer.
See “About software virtualization” on page 125.
137
Managing virtual applications
Installing and managing a virtual software layer with a Software Virtualization task
To virtualize software during installation
1
In the Symantec Management Console, create a Managed Software Delivery
policy for the software to be virtualized.
You can either use a Managed Software Delivery wizard, or create the policy
manually.
See “Creating a Managed Software Delivery policy with the Managed Software
Delivery wizard” on page 183.
See “Creating a Managed Software Delivery policy” on page 184.
2
On the policy page, on the Policy settings tab, under Software distribution
options, or on the Select software resource page in the wizard, check Install
this policy’s software into a virtual software layer.
Depending on how you create the policy, this check box appears in one of the
following places:
3
■
In the Managed Software Delivery wizard, this check box appears on the
Select software resource page.
In the wizard, if the software resource has any defined conflicts with other
software resources, those conflicts are listed with this option. Conflict
associations between software resources are defined in the Software
Catalog.
■
On the policy’s edit page, this check box appears in the Policy/Rules
Actions section, under Software distribution options on the Policy
settings tab.
Configure the policy schedule and application settings according to your needs.
See “Performing an advanced software delivery” on page 189.
4
At the upper right of the page, click the colored circle, and then click On.
5
Click Save changes.
Installing and managing a virtual software layer with
a Software Virtualization task
(Windows only)
You can create a Software Virtualization task to deliver and install a virtual software
archive (VSA) or extensible package format (XPF) file on managed computers. You
can also use a Software Virtualization task to manage any virtual software layer
regardless of how the layer was created.
138
Managing virtual applications
Installing and managing a virtual software layer with a Software Virtualization task
Note: If you want to create a Software Virtualization Command task that imports a
VSA file or an XPF file, you must specify a layer name. When you specify a different
layer name, the Software Virtualization import task fails. A workaround is to find
out the layer name that the VSA file or XPF file contains. Once you find the name,
you can type it in the Create new task dialog box, in the Layer name box.
See “About VSA and XPF virtual package files” on page 127.
A Software Virtualization task contains a command line for the specified virtual
software layer. When the task runs on a client computer, it executes the command
line that performs an action on the layer. Each action, including the installation,
requires a separate task.
See “Actions that you can perform on a virtual software layer” on page 133.
Table 8-6
Process for managing a virtual software layer with a Software
Virtualization task
Step
Action
Description
Step 1
Create a Software
Virtualization task.
When you create a task, you can choose the command to perform, and
the layer on which to perform the command.
If you install (import) a layer, you must select a VSA or an XPF file. If
you perform any other command, you can specify any existing layer.
See “Creating a task in Software Management Solution” on page 153.
Step 2
(Optional) Configure the task Every task inherits the default settings that control how the task runs.
settings.
You can override the default settings for a particular task.
Step 3
Schedule the task and
choose the delivery
destinations.
Define the schedule and the delivery destinations every time you run
the task.
Your options for scheduling the task are as follows:
■
■
Run the task now.
This option runs the task as soon as possible, unless it must wait
for a maintenance window.
Schedule the task to run at a specific time.
See “Scheduling a task and selecting computers in Software
Management Solution” on page 156.
Step 4
View the Virtualized
You can use the reports to monitor the state of virtual applications.
Software Resources reports. These reports are listed under the Software reports.
See “Running a Software Management Solution report” on page 157.
See “Managing virtual applications” on page 135.
139
Managing virtual applications
Installing and managing a virtual software layer with a Quick Delivery or Package Delivery task
Installing and managing a virtual software layer with
a Quick Delivery or Package Delivery task
(Windows only)
You can create a Quick Delivery or Package Delivery task to deliver and install a
virtual software archive (VSA) or an extensible package file (XPF) on managed
computers. You can also use these tasks to manage a virtual software layer that
was created by installing a virtual software archive file. If the software was virtualized
during a Managed Software Delivery installation, you must use a Software
Virtualization task to manage the layer.
See “Installing and managing a virtual software layer with a Software Virtualization
task” on page 138.
See “About VSA and XPF virtual package files” on page 127.
A Quick Delivery or Package Delivery task contains a command line for the specified
VSA or XPF file. When the task runs on a client computer, it executes the command
line that performs an action on the layer. Each action, including the installation,
requires a separate task.
Table 8-7
Process for installing and managing a virtual software layer with a
Quick Delivery or Package Delivery task
Step
Action
Description
Step 1
Create a Quick Delivery task The options for creating the task are as follows:
or a Package Delivery task.
■ Use the Quick Delivery wizard.
See “Creating a Quick Delivery task with the Quick Delivery wizard”
on page 152.
■ Create a Quick Delivery task manually.
See “Creating a task in Software Management Solution” on page 153.
■
Step 2
Create a Package Delivery task.
See “Creating a task in Software Management Solution” on page 153.
On the task page, specify the Select the software resource that represents the VSA or XPF file to
software to install or manage. install or manage. If you plan to manage an existing layer, select the
software resource that contains the VSAor XPF file that was installed
to create the layer.
In a Package Delivery task, you can also specify a virtual package that
is not assigned to a software resource.
140
Managing virtual applications
Installing and managing a virtual software layer with a Managed Software Delivery policy
Table 8-7
Process for installing and managing a virtual software layer with a
Quick Delivery or Package Delivery task (continued)
Step
Action
Description
Step 3
On the task, page specify the Select a command line that specifies the action to perform. For example,
action to perform.
you can install (import) the layer or you can deactivate an existing layer.
See “Actions that you can perform on a virtual software layer”
on page 133.
In a Package Delivery task, if you selected a VSA or XPF file that does
not have predefined command lines, you can type a valid command
line.
Step 4
(Optional) Configure the task Every task inherits the default settings that control how the task runs.
settings.
You can override the default settings for a particular task.
Step 5
Schedule the task, and
choose the delivery
destinations.
Define the schedule and the delivery destinations every time you run
the task.
Your options for scheduling the task are as follows:
■
■
Step 6
Run the task now.
This option runs the task as soon as possible, unless it must wait
for a maintenance window.
Schedule the task to run at a specific time.
See “Scheduling a task and selecting computers in Software
Management Solution” on page 156.
View the Virtualized
You can use the reports to monitor the state of virtual applications.
Software Resources reports. These reports are listed under the Software reports.
See “Running a Software Management Solution report” on page 157.
See “Managing virtual applications” on page 135.
Installing and managing a virtual software layer with
a Managed Software Delivery policy
(Windows only)
You can create Managed Software Delivery policies to create and manage new
virtual software layers or manage existing layers on client computers.
A Managed Software Delivery policy lets you perform complex layer management
tasks.
141
Managing virtual applications
Installing and managing a virtual software layer with a Managed Software Delivery policy
For example, you can create a Managed Software Delivery policy that manages
virtual software layers as follows:
■
Installs a new version of an application into a virtual software layer, and then
deactivates or deletes the earlier version.
■
Deactivates one version of an application and activates another version.
If you need to manage a single virtual software layer, use a Software Virtualization
task, a Quick Delivery task, or a Package Delivery task.
See “Methods for installing and managing virtual software” on page 131.
The process for managing virtual software layers with a Managed Software Delivery
policy is as follows:
Table 8-8
Process for managing virtual software layers with a Managed
Software Delivery policy
Step
Action
Step 1
Create one or more Software Virtualization tasks, Quick Delivery tasks, or Package Delivery tasks
that manage virtual software layers.
See “Installing and managing a virtual software layer with a Software Virtualization task” on page 138.
See “Installing and managing a virtual software layer with a Quick Delivery or Package Delivery task”
on page 140.
Step 2
Create a Managed Software Delivery policy that manages a virtual software layer in one of the following
ways:
■
Installs a software resource into a virtual software layer.
■
Manages a virtual software layer that was created by installing a virtual software archive (VSA) or
extensible package format (XPF) file.
See “Creating a Managed Software Delivery policy with the Managed Software Delivery wizard”
on page 183.
See “Creating a Managed Software Delivery policy” on page 184.
See “About VSA and XPF virtual package files” on page 127.
Step 3
Add the Software Virtualization tasks, Quick Delivery tasks, or Package Delivery tasks to the Managed
Software Delivery policy.
See “Delivering multiple software resources and tasks sequentially” on page 190.
142
Section
3
Delivering software
■
Chapter 9. Performing a quick delivery of a single software resource
■
Chapter 10. Delivering Packages
■
Chapter 11. Performing an advanced software delivery
■
Chapter 12. Delivering software from user requests using the Software Portal
Chapter
9
Performing a quick delivery
of a single software
resource
This chapter includes the following topics:
■
Introducing software delivery
■
Performing a quick delivery of a single software resource
■
Creating a Quick Delivery task with the Quick Delivery wizard
■
Creating a task in Software Management Solution
■
Editing a task in Software Management Solution
■
Running a Software Management Solution report
Introducing software delivery
Before you deliver software, it is a good idea to better understand what you can
deliver, how you can deliver, and other useful information.
To help you get more familiar with software delivery you can refer to the following:
■
A general overview of software delivery
See “About software delivery” on page 145.
■
The methods you can use to delivery software
See “Methods for delivering software” on page 145.
■
The methods you can uninstall software you have delivered and installed
See “Methods for uninstalling software” on page 148.
Performing a quick delivery of a single software resource
Introducing software delivery
About software delivery
Software Management Solution lets you deliver and install software safely and
accurately on managed client computers. You can create tasks and policies to
respond to software delivery needs from elementary to complex.
Software Management Solution integrates with the Software Catalog and the
Software Library that are part of the Symantec Management Platform. By leveraging
this information, Software Management Solution ensures that the correct software
gets installed, remains installed, and runs without interference from other software.
This integration lets your administrators focus on delivering the correct software
instead of redefining the packages, command lines, and so on for each delivery.
See “How Software Management Solution integrates with Software Management
Framework” on page 16.
Software Management Solution supports packages for the Windows, UNIX, Linux,
and Mac operating systems. With few exceptions, all the functions in Software
Management Solution work the same for all platforms. For example, you use the
same method to create a delivery task for a Windows, UNIX, Linux, or Mac OS
package.
You can use Software Management Solution tasks or policies to fulfill any of the
following delivery requirements:
■
Perform a quick delivery of a single software resource.
■
Perform one or more advanced delivery actions.
For example, you can deliver multiple software resources and periodically check
the client computer to verify that they are in the correct state.
■
Deliver software automatically in response to a direct request from a user.
■
Deliver a package that is not associated with a software resource.
■
Deliver software with a policy that you migrated from Software Delivery Solution
6.x.
■
Create a new virtual software layer on a client computer.
See “Methods for delivering software” on page 145.
Methods for delivering software
You can deliver software to one or more managed computers by creating and
running a Software Management task or policy. The method that you use to create
the task or policy depends on your delivery requirements.
145
Performing a quick delivery of a single software resource
Introducing software delivery
Table 9-1
Methods for delivering software
Your requirement
Delivery method
Description
Perform a quick delivery of a single
software resource.
Quick Delivery
You can use the task-based Quick Delivery
method to specify the software to deliver, the
action to perform, and the computers to
deliver to. Quick Delivery uses the default
task settings, which you can change when
necessary.
Because of its simplicity, Quick Delivery is an
ideal way for non-administrators, such as help
desk personnel, to deliver software safely and
accurately.
The software that you deliver in this way must
be defined as a deliverable software resource
in the Software Catalog.
Perform one or more of the following
advanced delivery actions:
■
Deliver on a recurring schedule.
■
Install to a known state and ensure
that the state is maintained.
Install software with the other
software that it depends on.
Install a software resource that
replaces other software.
Sequentially install multiple software
and tasks.
(Windows only) Install software into
a virtual software layer.
Run any client task at any stage of
the delivery.
A client task is one that is defined in
Notification Server and is intended
to run on a client computer.
■
■
■
■
■
Managed Software Delivery
Managed Software Delivery is a policy-based
delivery method that lets you fulfill advanced
delivery requirements. A single Managed
Software Delivery policy can perform multiple
delivery actions.
The software that you deliver in this way must
be defined as a deliverable software resource
in the Software Catalog.
Managed Software Delivery leverages the
software resource information and the logic
that is in the Software Catalog. For example,
Managed Software Delivery uses the software
resource’s dependencies, package, and
detection rule.
See “About advanced software deliveries”
on page 173.
146
Performing a quick delivery of a single software resource
Introducing software delivery
Table 9-1
Your requirement
Methods for delivering software (continued)
Delivery method
Deliver software in response to a direct Software Portal
request from a user.
Description
(Windows and Mac only) With the Software
Portal, users can request software and
responds to those requests. If the user is
pre-approved to install the software, the
installation occurs without the administrator’s
involvement. Otherwise, the administrator
only needs to approve the requests and
deliver the software that is not in the Software
Catalog.
See “About the Software Portal” on page 197.
Deliver a package that is not associated Package Delivery
with a software resource.
Package Delivery is a task-based delivery
method. It lets you deliver any package
regardless of whether it is associated with a
software resource.
Deliver software with a policy that you
migrated from Software Delivery
Solution 6.x.
Legacy Software Delivery
When you upgrade from Notification Server
6.x to Symantec Management Platform 7.x,
you can migrate your 6.x software delivery
tasks to Legacy Delivery policies. You can
continue to use those policies as they are.
You can also assign their packages to
software resources to deliver a 6.x software
package with Quick Delivery or Managed
Software Delivery.
(Windows only) Install software into a
new virtual software layer on a client
computer.
Software Virtualization task
Imports a virtual software archive (VSA) file
or extensible package format (XPF) file to a
managed client computer and creates a new
virtual software layer.
Quick Delivery
Package Delivery
See “About VSA and XPF virtual package
files” on page 127.
See “Methods for installing and managing
virtual software” on page 131.
147
Performing a quick delivery of a single software resource
Introducing software delivery
Table 9-1
Your requirement
Methods for delivering software (continued)
Delivery method
(Windows only) Virtualize an application Managed Software Delivery
and install it into a new virtual software
layer on a client computer.
Description
You can create and manage new virtual
software layers or manage existing layers on
client computers. A Managed Software
Delivery policy lets you perform complex layer
management tasks.
See “Installing and managing a virtual
software layer with a Managed Software
Delivery policy” on page 141.
Methods for uninstalling software
You can uninstall software from one or more managed computers by running a
Software Management policy or task.
The method that you use to uninstall software depends on how the software was
installed.
Table 9-2
Methods for uninstalling software
Installation method
Uninstall method
The software was installed
You can clone the original installation task or policy and then
with a Software Management edit the clone to select an uninstall command line.
Solution task or policy.
The software was not
installed with Software
Management Solution.
If a software resource is defined for that software, you can
create a software delivery task or policy and select an
uninstall command line.
See “Methods for delivering software” on page 145.
If a software resource is not defined for that software, you
can create one in the Software Catalog.
See “Creating a command line for a software resource”
on page 81.
The software was installed
into a virtual layer with a
Software Management
Solution task or policy.
You can clone the original installation task or policy and then
edit the clone to select a deactivate and delete command
line.
148
Performing a quick delivery of a single software resource
Performing a quick delivery of a single software resource
Table 9-2
Methods for uninstalling software (continued)
Installation method
Uninstall method
The software was installed
into a virtual layer, but not
with Software Management
Solution.
You can use a Software Virtualization task to deactivate and
delete any virtual software layer that was installed with one
of the following products: Altiris Software Virtualization
Solution or Symantec Workspace Virtualization. You can
specify the name of the layer to act upon.
See “Installing and managing a virtual software layer with a
Software Virtualization task” on page 138.
Managed Software Delivery provides the ability to perform more complex uninstall
tasks. For example, you can use a Managed Software Delivery policy to not only
uninstall obsolete software but also install new software at the same time.
See “About installing software that replaces other software” on page 181.
Managed Software Delivery can also regularly check computers for the presence
of unauthorized software and uninstall any unauthorized software that is found. For
example, you can use a Managed Software Delivery policy to remove game software
from client computers on a recurring basis.
Performing a quick delivery of a single software
resource
You can perform a quick delivery of a single software resource that runs with
minimum configuration. You can use the task-based Quick Delivery method to
specify the software to deliver, the action to perform, and the computers to deliver
to.
Because the software resources and the delivery settings are predefined, Quick
Delivery makes it easy for administrators and non-administrators to deliver software.
For example, help desk personnel can easily deliver hotfixes because all they have
to do is select the correct hotfix from the Software Catalog. They do not need to
know which package to select or how to create the command line.
Most organizations can use Quick Delivery for the majority of their software delivery
needs. Quick Delivery helps you reduce the amount of time that you spend on
routine deliveries so that you can devote more time to advanced activities.
The software that you deliver in this way must be defined as a deliverable software
resource in the Software Catalog. It must also have at least one command line.
After the initial instance of a Quick Delivery task runs, you can edit and rerun it. For
example, you can deliver the software to different computers or run a different
149
Performing a quick delivery of a single software resource
Performing a quick delivery of a single software resource
command line on the same computers. You can also edit the delivery settings for
the task. For example, you can change the user credentials under which the task
runs.
See “Editing a task in Software Management Solution” on page 155.
If you need to perform compliance checks or other advanced delivery activities,
use Managed Software Delivery instead of Quick Delivery.
See “About advanced software deliveries” on page 173.
Table 9-3
Process for performing a quick delivery of a single software resource
Step
Action
Description
Step 1
Create a Quick Delivery task. The options for creating a Quick Delivery task are as follows:
■
■
Step 2
Use the Quick Delivery wizard.
The Quick Delivery wizard let you create and run a Quick Delivery
task with minimum configuration.
See “Creating a Quick Delivery task with the Quick Delivery wizard”
on page 152.
Create and configure the task manually.
Use this method when you need to to configure the default settings
of the task or run the task on a specific schedule. You can also
configure the task that you created with a wizard.
See “Creating a task in Software Management Solution” on page 153.
(Optional) Configure the task Every task inherits the default run settings. You can override the default
settings.
settings for a particular task.
For example, if you want to deliver a large package over slow network,
you may want to increase the End task after value.
150
Performing a quick delivery of a single software resource
Performing a quick delivery of a single software resource
Table 9-3
Process for performing a quick delivery of a single software resource
(continued)
Step
Action
Description
Step 3
Schedule the task and
choose the delivery
destinations.
When you use the Quick Delivery wizard to create the task, you choose
the destinations in the wizard. Those destinations apply to that instance
of the task only. You do not have to schedule the task because it runs
as soon as possible.
When you edit the task or create it without the wizard, you define the
schedule and the delivery destinations every time you run the task.
The options for scheduling the task are as follows:
■
Run the task now.
This option runs the task as soon as possible, unless it must wait
for a maintenance window.
Note: On computers with Cloud-enabled Management this option
only works like a schedule. Computers with Cloud-enabled
Management receive the task from the task server that depends on
the task agent schedule. Symantec recommends that you increase
the default timeout period in the advanced options for the tasks that
are scheduled on computers with Cloud-enabled Management. An
increased timeout period can significantly improve software delivery
for Quick Delivery to computers with Cloud-enabled Management.
By default, the End task after is set to 300 minutes (five hours). A
recommended value to change the timeout period to is 1440 minutes
(24 hours). The maximum timeout is 2160 minutes (36 hours).
■
Schedule the task to run at a specific time.
See “Scheduling a task and selecting computers in Software
Management Solution” on page 156.
Step 4
After the task runs, view the
reports.
The Software Management reports let you monitor the software
deliveries.
The delivery reports provide information about the status of the software
downloads and executions. For example, the software downloads for
each computer, including the status and the download date.
See “Running a Software Management Solution report” on page 157.
151
Performing a quick delivery of a single software resource
Creating a Quick Delivery task with the Quick Delivery wizard
Creating a Quick Delivery task with the Quick Delivery
wizard
A Quick Delivery task lets you deliver software without the need to know which
package to select or how to create the command line. Creating a Quick Delivery
task is the first step in performing a Quick Delivery of a single software resource.
See “Performing a quick delivery of a single software resource” on page 149.
The Quick Delivery wizard is the fastest and easiest way to create and run a Quick
Delivery task with minimum configuration. During the wizard, you specify the software
resource to deliver, the action to perform, and the destinations to deliver to. The
resulting Quick Delivery task runs as soon as possible without further configuring
or scheduling. We recommend that non-administrators use the Quick Delivery
wizard because it provides the fewest options and therefore the fewest opportunities
for errors.
Warning: When a Quick Delivery task runs automatically, you can recall, stop, or
disable it only if the task needs to wait for a maintenance window.
The advantages of using the Quick Delivery wizard are as follows:
■
It speeds the task creation.
■
It does not let non-administrators change the delivery settings.
In most cases, it is important to prevent non-administrators from changing the
delivery settings when they deliver software.
■
It sets the task to run as soon as possible.
When you create a Quick Delivery task without the wizard, it does not run
automatically. You must run it or schedule it.
The software that you deliver in this way must be defined as a deliverable software
resource in the Software Catalog.
When you run the Quick Delivery wizard from the Software Catalog view, it
populates the most default information. However, you can run the Quick Delivery
wizard from other areas of the Symantec Management Console. Your point of entry
into the Quick Delivery wizard determines the amount of default information that
is populated.
If you need to change the task’s default settings or run the task on a specific
schedule, create the task without the Quick Delivery wizard.
See “Creating a task in Software Management Solution” on page 153.
152
Performing a quick delivery of a single software resource
Creating a task in Software Management Solution
To create a Quick Delivery task with the Quick Delivery wizard
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, under Deliverable Software, click Software Releases.
3
In the Software Releases pane, right-click a deliverable software resource
and then click Actions > Quick Delivery Task.
4
In the Quick Delivery Task dialog box, specify the following items:
Note: A script file needs the path to the program the script file requires on the
client computer for the task to deliver successfully. For example, consider a
python script file, test.py. If the install path on the client computer is
c:\python27\python.exe, then this path needs to be specified in the command
line as follows: "c:\python27\python.exe" "test.py". If you want to deliver
to different clients with different install paths, then you have to modify the task
for each different install path.
5
■
The software resource to deliver
■
The command line to run
The list contains the names of the command lines that are defined for the
software resource.
■
Whether to accept the maintenance windows
■
The destinations you want to deliver the software resource to
Click OK.
Creating a task in Software Management Solution
Creating a task is typically the first step in performing the software-related actions
in Software Management Solution. This procedure describes how to create any
type of task in Software Management Solution.
Every task inherits the default settings that control how the task runs. You can
override the default settings for a particular task.
For example, if you want to deliver a Quick Delivery on an Internet-managed
computer that uses Cloud-enabled Management, you can increase the default End
task after value. Such changes in settings can improve the performance of the
software delivery considerably.
See “Editing a task in Software Management Solution” on page 155.
153
Performing a quick delivery of a single software resource
Creating a task in Software Management Solution
Notification Server tasks let you download and run packages, programs, commands,
and other items to client computers. You use tasks to perform most of the actions
in Software Management Solution.
Table 9-4
Types of tasks in Software Management Solution
Type of task
Description
Package Delivery
Lets you deliver any package regardless of whether it is associated
with a software resource.
See “Delivering a package without defining a software resource”
on page 160.
Quick Delivery
Lets you perform a Quick Delivery of a single software resource.
Creating this task is the first step in the Quick Delivery process.
The software that you deliver in this way must be defined as a
deliverable software resource in the Software Catalog.
See “Performing a quick delivery of a single software resource”
on page 149.
Source Path Update
Lets you update the source paths of Windows Installer applications
with the resilient source paths that point to the package servers
that you designate.
See “Updating the source paths of Windows Installer applications”
on page 115.
Software Virtualization
(Windows only) Lets you manage virtual software layers on
managed computers or deliver a VSA or an XPF file to managed
computers.
See “Managing virtual applications” on page 135.
Windows Installer
Repair
Lets you proactively identify and repair broken Windows Installer
applications on selected computers.
See “Repairing Windows Installer applications” on page 119.
See “Scheduling a task and selecting computers in Software Management Solution”
on page 156.
To create a task
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the left pane, expand System Jobs and Tasks > Software.
3
Right-click the folder under which you want to create a task, and then click
New > Task.
154
Performing a quick delivery of a single software resource
Editing a task in Software Management Solution
4
In the Create new task dialog box, in the left pane, under Software click the
type of task that you want to create.
The type of task that you selected determines the options that appear, as
follows:
5
■
Package Delivery
For more information about the options, click the page and then press F1
■
Quick Delivery
For more information about the options, click the page and then press F1
■
Software Virtualization Command (Windows only)
For more information about the options, click the page and then press F1
■
Source Path Update (Windows only)
For more information about the options, click the page and then press F1
■
Windows Installer Repair
For more information about the options, click the page and then press F1
In the right pane, configure the task.
See “Editing a task in Software Management Solution” on page 155.
6
Click OK.
Editing a task in Software Management Solution
You can edit any type of Software Management Solution task.
To edit a task
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the left pane, expand System Jobs and Tasks > Software. Expand the
folder in which the task resides, and then click the task that you want to edit.
3
In the right pane, do any of the following:
■
In the top section, click Advanced to change the task’s settings for this
instance.
■
In the top section, edit the task’s details. The type of task that you selected
determines the options that appear.
For more information about the options, click the page and then press F1.
■
In the bottom section, click New Schedule to schedule the task and select
the destination computers.
155
Performing a quick delivery of a single software resource
Editing a task in Software Management Solution
Note: For a Quick Delivery task, on the Internet-managed computers that
use Cloud-enabled Management, the Now option works like a schedule.
Internet-managed computers receive the task from the task server that
depends on the task agent schedule. Symantec recommends that you
increase the default timeout period in the advanced options for the tasks
that are scheduled on Internet-managed computers. An increased timeout
period can significantly improve software delivery for Quick Delivery from
Internet-based computer. By default the End task after is set to 300 minutes
(five hours). A recommended value to change the timeout period to is 1440
minutes (24 hours). The maximum timeout allowable is 2160 minutes (36
hours).
See “Scheduling a task and selecting computers in Software Management
Solution” on page 156.
■
4
In the bottom section, double-click an existing instance of this task to
re-schedule it.
You might want to reschedule an existing instance if the task failed due to
an incorrect setting. In that case, you can fix the setting and reschedule the
task instead of creating a new task.
When you finish editing the task, on the task’s main page, click Save changes.
Scheduling a task and selecting computers in Software Management
Solution
Software Management tasks use the task management component of Notification
Server that provides flexibility in targeting computers and scheduling tasks. For
example, when you schedule tasks, you can configure multiple schedules for an
individual task, use maintenance windows, or use shared schedules. When you
select computers, you can build and re-use predefined groups of computers.
To schedule a task and to select computers
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the left pane, expand System Jobs and Tasks > Software > Quick
Delivery.
3
Under the Quick Delivery folder, click on the task you want to schedule.
4
On the task page, click either of the following:
■
Quick Run
156
Performing a quick delivery of a single software resource
Running a Software Management Solution report
Lets you run the task on a single destination as soon as possible, unless
it must wait for a maintenance window. This option is not available for some
tasks.
■
New Schedule
Lets you schedule the task to run at a specific time. The name of the option
depends on the type of task.
Note: On the Internet-managed computers that use Cloud-enabled
Management the Now option works like a schedule. Internet-managed
computers receive the task from the task server that depends on the task
agent schedule. Symantec recommends that you increase the default
timeout period in the advanced options for the tasks that are scheduled on
Internet-managed computers. An increased timeout period can significantly
improve software delivery for Quick Delivery from Internet-based computer.
By default the End task after is set to 300 minutes (five hours). A
recommended value to change the timeout period to is 1440 minutes (24
hours). The maximum timeout allowable is 2160 minutes (36 hours).
To see these options, you might have to click a tab or expand a section on the
task page.
For more information, see the topics about task schedule options in the Altiris™
IT Management Suite 7.5 Administration Guide from Symantec™at the following
URL:
http://www.symantec.com/docs/DOC5330
5
Select the computers to run the task on.
For more information, see the topics about specifying the targets of a policy or
task in the Altiris™ IT Management Suite 7.5 Administration Guide from
Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
6
(Optional) To create multiple schedules and computer lists for this task, repeat
step 4 through step 5.
Running a Software Management Solution report
You can view reports to get information about the actions that you perform in
Software Management Solution.
157
Performing a quick delivery of a single software resource
Running a Software Management Solution report
Predefined reports let you easily view and analyze your Software Management
Solution data. The reports are grouped in folders by type in the Symantec
Management Console.
You can also create your own custom reports.
By default, all the Software Management Solution reports support resource scoping,
which limits the data that users can access based on their security roles.
The Software Management Solution reports use the scoping feature as follows:
■
When a user runs a report, the report contains only the data that the user has
permissions for.
■
When a user saves a snapshot of a report, the snapshot is scoped according
to that user’s permissions. The users who have a lower security role than the
original user cannot view the snapshot. The users who have a higher security
role than the original user can see only the data that the original user was allowed
to access.
■
You can clone a report and edit the clone’s SQL query to customize how the
data is scoped when it is extracted for that report. You can also include scoping
information when you create an SQL query for a custom report.
■
You can clone a report and edit the clone to select the fields that are scoped
when data is extracted from that report’s snapshots.
For more information, see the topics about configuring the scoping fields in a report
and about defining an SQL query in the Altiris™ IT Management Suite 7.5
Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
Table 9-5
Types of predefined reports in Software Management Solution
Report type and folder
Description
6.0 Legacy Reports
Contains the reports that appeared in Software Delivery
Solution 6.x. This folder does not contain any custom reports
that were defined in 6.0.
The Legacy Reports can contain data from Software
Management Solution 7.x as appropriate. They can also
contain any data that you might have migrated from Software
Delivery Solution 6.x.
Application Management
Contains the reports that display information about the
Windows Installer applications that are broken or that have
inaccessible source paths.
158
Performing a quick delivery of a single software resource
Running a Software Management Solution report
Table 9-5
Types of predefined reports in Software Management Solution
(continued)
Report type and folder
Description
Compliance
Contains the reports that display information about the
compliance actions and the remediation actions that Managed
Software Delivery performs.
Delivery
Contains the reports that display information about the status
of the software downloads and executions.
If you migrated software delivery data from Software Delivery
Solution 6.x, the new delivery reports contain data from both
6.x and 7.x.
Portal
Contains the reports that display the status of software
requests that are made through the Software Portal.
Virtualized Software
Resources
Contains the reports that display information about the actions
(events) that have been performed on the virtual layers that
are installed on client computers.
To run a Software Management Solution report
1
In the Symantec Management Console, on the Reports menu, click All
Reports.
2
In the left pane, expand Software, and then expand the folder that contains
the report that you want to run.
3
Under the folder that you expanded, click a report.
4
When the report appears in the right pane, you can print the report or save it
in a variety of formats. Other actions might be available depending on the type
of report.
159
Chapter
10
Delivering Packages
This chapter includes the following topics:
■
Delivering a package without defining a software resource
■
Delivering software packages with the same configurations as 6.x Software
Delivery tasks
■
Accessing a Legacy Software Delivery policy
■
Assigning an Altiris 6.x software package to a software resource
■
Assigning multiple Altiris 6.x software packages to software resources
■
Adding 6.x software packages to a package assignment task
■
Editing 6.x software packages
Delivering a package without defining a software
resource
Package Delivery method lets you deliver any package regardless of whether it is
associated with a software resource.
You may need to use Package Delivery for the following purposes:
■
To deliver a package that you choose not to manage in the Software Catalog.
■
To quickly deliver a new package that is not yet in the Software Catalog.
■
To deliver a package that is in the Software Catalog, but with a command line
that is not defined for the package.
For example, a package is in the Software Catalog and is associated with
predefined command lines. You need to deliver that package with a specialized
command line, but you do not have the privileges to edit the package or its
Delivering Packages
Delivering a package without defining a software resource
software resource. You can create a Package Delivery task for that package
and type the command line that you need.
■
To run a task that you migrated from the Task Server Plug-in in Software Delivery
Solution 6.x to Software Management Solution 7.x.
The migrated tasks let you perform deliveries with the same configurations as
the 6.x tasks.
Table 10-1
Process for delivering a package without defining a software
resource
Step
Action
Description
Step 1
Create a Package Delivery
task.
A Package Delivery task lets you perform a
routine package delivery.
See “Creating a task in Software
Management Solution” on page 153.
Step 2
(Optional) Change the task
settings.
Every task inherits the default settings that
control how the task runs. You can override
the default settings for a particular task.
For example, if you want to deliver a large
package over slow network, you may want to
increase the End task after value.
Step 3
Schedule the task and
choose the delivery
destinations.
Define the schedule and the delivery
destinations every time you run the task.
Your options for scheduling the task are as
follows:
■
■
Run the task now.
This option runs the task as soon as
possible, unless it must wait for a
maintenance window.
Schedule the task to run at a specific time.
See “Scheduling a task and selecting
computers in Software Management Solution”
on page 156.
161
Delivering Packages
Delivering software packages with the same configurations as 6.x Software Delivery tasks
Table 10-1
Process for delivering a package without defining a software
resource (continued)
Step
Action
Description
Step 4
After the task runs, view the
reports.
The Software Management reports let you
monitor the software deliveries.
The delivery reports provide information about
the status of the software downloads and
executions. For example, the software
downloads for each computer, including the
status and the download date.
See “Running a Software Management
Solution report” on page 157.
Delivering software packages with the same
configurations as 6.x Software Delivery tasks
During the upgrade to Symantec Management Platform 7.x, you can migrate 6.x
Software Delivery tasks to 7.x Legacy Software Delivery policies. Legacy Software
Delivery lets you deliver a 6.x software package with the same configurations as
in the 6.x task.
Legacy Software Delivery policies deliver software packages with the same
configurations as the Software Delivery tasks that you migrated from Software
Delivery Solution 6.x.
For more information about the migration of software delivery data, see the Altiris™
IT Management Suite from Symantec™ Migration Guide version 6x to 7.5 at the
following URL:
http://www.symantec.com/docs/DOC5668
You can run an existing Legacy Software Delivery policy, or clone and configure it
according to your needs.
See “Delivering software packages with the same configurations as 6.x Software
Delivery tasks” on page 162.
See “Accessing a Legacy Software Delivery policy” on page 163.
You cannot create new Legacy Software Delivery policies.
Use Legacy Software Delivery policies only for 6.x packages that you cannot deliver
with Quick Delivery or Managed Software Delivery. Otherwise, Symantec
recommends that you use the latter delivery methods.
162
Delivering Packages
Accessing a Legacy Software Delivery policy
Because a Legacy Software Delivery policy uses some of the 7.x functionality, it is
not the same as a 6.x software delivery task.
Table 10-2
Delivering 6.x software packages
Step
Action
Description
Step 1
Access the migrated Legacy When you migrate 6.x Software Delivery tasks
Software Delivery policy.
to Legacy Software Delivery policies, the
resulting policies are placed in specific folders
in the Symantec Management Console.
See “Accessing a Legacy Software Delivery
policy” on page 163.
Step 2
(Optional) Edit the Legacy
Software Delivery policy.
You can edit the Legacy Software Delivery
policy to change or add functionality as
follows:
■
■
Step 3
Choose the delivery
destinations.
Edit or change the package or program
that the policy installs.
Change the settings for the policy.
Select the managed computers to deliver to.
The process for choosing a destination is the
same as in the case of the Managed Software
Delivery policy.
See “Selecting the delivery destinations for a
Managed Software Delivery policy”
on page 188.
Step 4
Schedule the policy.
Configure the schedule on which the Legacy
Software Delivery policy runs. The process
for choosing a destination is the same as for
other policies.
For more information, see the topics on
specifying a policy schedule in the Altiris™
IT Management Suite 7.5 Administration
Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
Accessing a Legacy Software Delivery policy
During the upgrade to Symantec Management Platform 7.x, you can migrate 6.x
Software Delivery tasks to 7.x Legacy Software Delivery policies. Access the Legacy
Software Delivery policies to edit, clone, and run them.
163
Delivering Packages
Assigning an Altiris 6.x software package to a software resource
Legacy Software Delivery policies deliver software packages with the same
configurations as the Software Delivery tasks that you migrated from Software
Delivery Solution 6.x.
For more information about the migration of software delivery data, see the Altiris™
IT Management Suite from Symantec™ Migration Guide version 6x to 7.5 at the
following URL:
http://www.symantec.com/docs/DOC5668
You can take the following actions on an existing Legacy Software Delivery policy:
■
Run the policy to deliver the software.
See “Delivering software packages with the same configurations as 6.x Software
Delivery tasks” on page 162.
■
Edit or clone an existing policy.
See “Accessing a Legacy Software Delivery policy” on page 163.
You cannot create new Legacy Software Delivery policies.
Use Legacy Software Delivery policies only for 6.x packages that you cannot deliver
with Quick Delivery or Managed Software Delivery. Otherwise, we recommend that
you use the latter delivery methods.
Because a Legacy Software Delivery policy uses some of the 7.x functionality, it is
not the same as a 6.x software delivery task.
To access a Legacy Software Delivery policy
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software.
3
Depending on the kind of task that you migrated, expand one of the following
subfolders:
Windows software delivery
task
Legacy Software Delivery folder
UNIX, Linux, or Mac OS
delivery task
Legacy Software Delivery for UNIX/Linux/Mac folder
Assigning an Altiris 6.x software package to a
software resource
After you migrate 6.x software packages to Software Management Solution, you
should assign them to software resources. You must assign them to software
164
Delivering Packages
Assigning an Altiris 6.x software package to a software resource
resources to deliver them with any of the following 7.x delivery methods: Quick
Delivery, Managed Software Delivery, or the Software Portal.
When you upgrade from Notification Server 6.x to Symantec Management Platform
7.x, you can migrate 6.x software packages for both Windows and non-Windows
software. After you migrate a 6.x software package, we recommend that you deliver
it with Quick Delivery, Managed Software Delivery, or the Software Portal. Before
you can use any of those delivery methods, you must assign the 6.x software
package to a software resource.
For more information about 6.x data migration, see the Altiris™ IT Management
Suite from Symantec™ Migration Guide version 6x to 7.5 at the following URL:
http://www.symantec.com/docs/DOC5668
You can assign a 6.x software package to a new software resource or an existing
software resource. If the existing software resource already contains packages, the
6.x package is added to the list of packages. When you assign software packages
to software resources, you can select a single package or multiple packages. If you
select a single package, the Assign Package to Software Resource wizard is
used. If you select multiple packages, a package assignment task is created for
the selected packages.
See “Assigning an Altiris 6.x software package to a software resource” on page 164.
See “Assigning multiple Altiris 6.x software packages to software resources”
on page 166.
When you assign a 6.x software package to a software resource, the location of
the package’s files does not change. However, after you assign a software package
to a software resource, you can add the package’s files to the Software Library.
When you assign a package to a software resource, the Software Portal settings
Install Software and Install On Approval are migrated to the software resource.
When you assign a 6.x software package to a software resource, you can edit the
package’s command lines. Afterwards, you can access the software resource in
the Software Catalog and edit any of its data.
You can also assign multiple packages to software resources at the same time. If
you migrated numerous 6.x software packages, you can save time by assigning
multiple packages at the same time.
See “Assigning multiple Altiris 6.x software packages to software resources”
on page 166.
165
Delivering Packages
Assigning multiple Altiris 6.x software packages to software resources
To assign an Altiris 6.x software package to a software resource
1
In the Symantec Management Console, on the Manage menu, click All
Resources.
2
In the left pane, expand All Resources > Package, and then click Software
Package.
3
In the right pane, on the package’s right-click menu, click Actions > Assign
to Software Resource.
This action appears only for the migrated packages that are not assigned to a
software resource.
4
On the Select software resource page, click one of the following options:
■
Create new software resource
Click this option if the software resource is not in the Software Catalog.
After you select this option, define the properties that identify the software
resource. These properties appear on the software resource’s Properties
tab.
■
Use existing software resource
Click this option if the software resource is in the Software Catalog. After
you click this option, click Select software resource, and select the software
resource to assign the package to.
5
Click Next.
6
(Optional) On the Set Command line properties page, edit the properties of
the package’s command lines, and select a default command line.
This page displays all the command lines that are associated with the package.
If you selected an existing software resource on the Select software resource
page, the command lines that are already associated with the software resource
are also displayed.
When a command line’s type is Custom, Set as the default command line
is disabled.
7
Click Finish.
Assigning multiple Altiris 6.x software packages to
software resources
When you upgrade from Notification Server 6.x to Symantec Management Platform
7.x, you can migrate 6.x software packages for both Windows and non-Windows
software. Then you can use Software Management Solution tasks and policies to
deliver the migrated packages.
166
Delivering Packages
Assigning multiple Altiris 6.x software packages to software resources
For more information about the migration of software delivery data, see the Altiris™
IT Management Suite from Symantec™ Migration Guide version 6x to 7.5 at the
following URL:
http://www.symantec.com/docs/DOC5668
Table 10-3
Methods for delivering Altiris 6.x software packages
Method
Description
Quick Delivery, Managed
Software Delivery, or the
Software Portal
These delivery methods use the enhanced delivery
functionality of Software Management Solution 7.x. They also
leverage the software resource information that is in the
Software Catalog and Software Library.
See “How Software Management Solution integrates with
Software Management Framework” on page 16.
Before you can deliver a 6.x software package with any of
these delivery methods, assign the package to a software
resource.
These delivery methods leverage the software resource
information that is in the Software Catalog and Software
Library.
Package Delivery
Whether or not you do assign a migrated package to a
software resource, you can use a Package Delivery task to
deliver that package.
You can also migrate 6.x Software Delivery Task Server
Plug-in tasks to Package Delivery tasks to deliver packages
with the same configurations as in 6.x.
See “Delivering a package without defining a software
resource” on page 160.
Legacy Software Delivery
Legacy Software Delivery policies are the result of migrating
6.x Software Delivery tasks to 7.x policies. Legacy Software
Delivery lets you deliver a 6.x software package with the
same configurations as in the 6.x task.
We recommend that you use this method only for 6.x
packages that you cannot deliver with Quick Delivery or
Managed Software Delivery.
167
Delivering Packages
Assigning multiple Altiris 6.x software packages to software resources
Table 10-3
Methods for delivering Altiris 6.x software packages (continued)
Method
Description
Software Virtualization task
Software Virtualization tasks let you deliver virtual software
archive (VSA) files and import them into virtual software layers
on client computers. Use this method when you migrate 6.x
VSA packages.
You also can migrate 6.x SVS Task Server Plug-in tasks to
Software Virtualization tasks.
See “Installing and managing a virtual software layer with a
Software Virtualization task” on page 138.
After you migrate 6.x software packages to Software Management Solution, you
should assign them to software resources. You must assign them to software
resources to deliver them with any of the following 7.x delivery methods: Quick
Delivery, Managed Software Delivery, or the Software Portal.
When you upgrade from Notification Server 6.x to Symantec Management Platform
7.x, you can migrate 6.x software packages for both Windows and non-Windows
software. After you migrate a 6.x software package, we recommend that you deliver
it with Quick Delivery, Managed Software Delivery, or the Software Portal. Before
you can use any of those delivery methods, you must assign the 6.x software
package to a software resource.
For more information about 6.x data migration, see the Altiris™ IT Management
Suite from Symantec™ Migration Guide version 6x to 7.5 at the following URL:
http://www.symantec.com/docs/DOC5668
You can assign a 6.x software package to a new software resource or an existing
software resource. If the existing software resource already contains packages, the
6.x package is added to the list of packages. When you assign software packages
to software resources, you can select a single package or multiple packages. If you
select a single package, the Assign Package to Software Resource wizard is
used. If you select multiple packages, a package assignment task is created for
the selected packages.
When you assign a 6.x software package to a software resource, the location of
the package’s files does not change. However, after you assign a software package
to a software resource, you can add the package’s files to the Software Library.
When you assign a package to a software resource, the Software Portal settings
Install Software and Install On Approval are migrated to the software resource.
You can assign multiple 6.x software packages to software resources at the same
time. If you migrated numerous 6.x software packages, you can save time by
168
Delivering Packages
Assigning multiple Altiris 6.x software packages to software resources
assigning multiple packages at the same time. When you assign multiple software
packages, a package assignment task is created. The package assignment task
lets you add packages and edit any of the packages before you assign them to
software resources. After you assign packages to software resources, you can then
access each software resource in the Software Catalog and edit its software resource
data.
You can also assign a single package to a software resource. Use this method if
you only have a few packages to assign to software resources.
See “Assigning an Altiris 6.x software package to a software resource” on page 164.
To assign multiple Altiris 6.x software packages to software resources
1
In the Symantec Management Console, on the Manage menu, click All
Resources.
2
In the left pane, expand All Resources > Package, and then click Software
Package.
3
In the right pane, select two or more 6.x packages that are not assigned to a
software resource.
You must select at least two packages to create a package assignment task.
After the task is created, you can add other packages.
4
Right-click the selected packages, and then, on the right-click menu, click
Actions > Assign to Software Resource.
If the Assign to Software Resource action does not appear, all of the
packages that you selected have been assigned to a software resource.
5
To add other 6.x packages, under the Software Settings section, click Add
Packages.
See “Adding 6.x software packages to a package assignment task” on page 170.
6
To edit a 6.x package, under the Software Settings section, double-click the
package name.
When you edit a package, you can modify its command lines and assign it to
a new software resource or existing software resource.
See “Editing 6.x software packages” on page 171.
169
Delivering Packages
Adding 6.x software packages to a package assignment task
7
To change the default command line for the software resource, under Software
Settings, in the Command Line Type drop-down list, click Install, Uninstall,
or Repair.
You can only set a command line as the default if that command line was
associated with the 6.x package. The default command line that you select
appears in the Default Command Line column. You can also set the default
command line when you edit the package.
See “Editing 6.x software packages” on page 171.
8
If you made any changes to the packages in the Software Settings section,
click Save changes.
9
Under the Task Status section, click New Schedule, and schedule when to
run the task.
When the task runs, it assigns the 6.x packages that are listed in the Software
Settings section to software resources. The task is saved in the Assign
Packages to Software Resources folder. To access this folder, on the Manage
menu, click Jobs and Tasks > System Jobs and Tasks > Software.
Adding 6.x software packages to a package
assignment task
A package assignment task is created when you select multiple 6.x software
packages and begin the process of assigning these packages to software resources.
The package assignment task lets you add other software packages. When you
add packages to the task, a list of the 6.x packages that are not assigned to a
software resource appears. This list makes it easy to identify the packages that are
not assigned to a software resource. You can then select from this list the packages
that you want to assign to software resources.
To add 6.x software packages to a package assignment task
1
Access the package assignments task.
See “Assigning multiple Altiris 6.x software packages to software resources”
on page 166.
2
Under Software Settings, click Add Package.
3
In the Add Software Packages dialog box, click > or >> to move packages
from the left pane to the right pane.
The > option moves any packages that are selected and the >> option moves
all of the packages . You can also use the search field to find packages.
4
On the Add Software Packages dialog box, click OK.
170
Delivering Packages
Editing 6.x software packages
Editing 6.x software packages
A package assignment task is created when you select multiple 6.x software
packages and begin the process of assigning them to software resources. This task
lists the 6.x software packages that were selected. You can edit any of the packages
in the task. When you edit a package, you can assign it to a new software resource
or to an existing software resource. You can also edit the command lines of the
package.
To edit 6.x software packages
1
Access the package assignment task.
See “Assigning multiple Altiris 6.x software packages to software resources”
on page 166.
2
Under Software Settings, double-click a package.
3
To define the package’s software resource, in the Edit Software Details dialog
box, on the Select Software tab, select one of the following options:
4
■
Create new software resource
Click this option if the software resource is not in the Software Catalog.
After you select this option, define the properties that identify the software
resource. These properties appear on the software resource’s Properties
tab.
■
Use existing software resource
Click this option if the software resource is in the Software Catalog. After
you click this option, click Select software resource, and select the software
resource to assign the package to.
To edit the package’s command lines, in the Edit Software Details dialog box,
on the Set Command Line tab, edit any of the fields for the listed command
lines.
If you select Custom as a Command type, then you cannot check Set as the
default command line option.
5
In the Edit Software Details dialog box, click OK.
171
Chapter
11
Performing an advanced
software delivery
This chapter includes the following topics:
■
Introducing advanced software deliveries
■
Viewing all Managed Software Delivery policies
■
Creating a Managed Software Delivery policy with the Managed Software
Delivery wizard
■
Creating a Managed Software Delivery policy
■
Editing a Managed Software Delivery policy
■
Selecting the delivery destinations for a Managed Software Delivery policy
■
Performing an advanced software delivery
■
Delivering multiple software resources and tasks sequentially
■
Performing an emergency policy update
■
Viewing emergency policy update reports
Introducing advanced software deliveries
Before you perform an advanced software delivery, it is a good idea to better
understand what it is, how it works, and other useful information.
To help you get more familiar with advanced software deliveries you can refer to
the following:
■
About advanced software delivery as a policy-based delivery method
Performing an advanced software delivery
Introducing advanced software deliveries
See “About advanced software deliveries” on page 173.
■
About the execution of advanced software delivery including an explanation of
compliance and remediation
See “About the execution of Managed Software Delivery policies” on page 174.
■
About the applicability, compliance, and remediation actions that let you not
only deliver software but also manage it
See “About policy applicability, compliance, and remediation” on page 176.
■
About the ways you can give the user some control over the software delivery
execution
See “About software delivery deferral options for the user” on page 178.
■
About how you can schedule the execution of the remediation of an advanced
software delivery
See “About deferring the execution of software remediation” on page 180.
■
About supersedence associations in which one software resource replaces
another software resource
See “About installing software that replaces other software” on page 181.
■
About the status of an advanced software delivery and determining a Managed
Software Delivery policy’s success
See “About the status of Managed Software Delivery policies” on page 182.
About advanced software deliveries
Managed Software Delivery simplifies advanced software deliveries by letting you
deliver software as a unit, which can include multiple software resources as well
as dependencies. For example, you can create a single Managed Software Delivery
policy that installs an application and its associated patches and service packs.
Managed Software Delivery can also run any task at any stage of the delivery. For
example, it can run a task that performs a restart or runs a script.
Managed Software Delivery is a policy-based delivery method that lets you configure
advanced delivery settings.
See “Performing an advanced software delivery” on page 189.
Managed Software Delivery allows you to do the following:
■
Intelligently perform the compliance checks and the remediation actions that let
you deliver software and manage it.
■
Leverage the software resource information and the logic that is in the Software
Catalog such as dependencies, packages, and detection rules.
173
Performing an advanced software delivery
Introducing advanced software deliveries
■
Save bandwidth by downloading packages only when they are needed. If a
client computer does not have the appropriate configuration for the software or
if the software is already installed, the package is not downloaded.
■
To perform multiple delivery actions with a single policy.
The software that you deliver in this way must be defined as a software resource
in the Software Catalog.
See “About the Software Catalog” on page 30.
If you need to perform a Quick Delivery of a single software resource, use Quick
Delivery instead of Managed Software Delivery.
See “Performing a quick delivery of a single software resource” on page 149.
About the execution of Managed Software Delivery policies
When a Managed Software Delivery policy runs on a managed computer, it performs
a series of tasks that are grouped into the following phases:
■
Compliance
See Table 11-1.
■
Remediation
See Table 11-2.
When you schedule a Managed Software Delivery policy, you can assign different
schedules for compliance and remediation. For example, you can schedule the
compliance status to be reported during the day and the remediation to occur only
during a maintenance window.
See “About policy applicability, compliance, and remediation” on page 176.
The ability to separate compliance and remediation also allows for the offline
execution of Managed Software Delivery policies. When the compliance check
determines that a remediation is required, the policy downloads the appropriate
package. Remediation can occur even if the client computer is not connected to
the server because the client computer already has the package that it needs.
See “About deferring the execution of software remediation” on page 180.
Table 11-1
How the compliance phase of Managed Software Delivery works
Step
Action
Description
Step 1
Policy execution
Starts the policy’s compliance process at the scheduled time on the client
computer.
174
Performing an advanced software delivery
Introducing advanced software deliveries
How the compliance phase of Managed Software Delivery works
(continued)
Table 11-1
Step
Action
Description
Step 2
Applicability check
(Windows only) Determines whether the client computer has the correct
environment for an installation of the software. If the computer does not have
the correct environment, the policy execution stops.
The applicability check runs for each software resource in the Managed
Software Delivery policy that is associated with an applicability rule.
Step 3
Compliance check
Evaluates the software resource’s unique identifier or detection rule to
determine whether the software resource is installed on the client computer.
The software resource’s unique identifier is used when the software resource
is not associated with a detection rule.
The compliance check runs for each software resource in the Managed
Software Delivery policy.
This compliance check determines whether the software is in the correct
state. The correct state of a software resource can mean that it is installed
or that it is not installed.
If all the software in the Managed Software Delivery policy is in the correct
state, it is compliant. Therefore, remediation is not needed and the policy
execution stops. If any or all of the software is not in the correct state, it is
out of compliance. Therefore, remediation is required and the policy execution
continues.
Step 4
Package download
Downloads the package for each software resource or task in the Managed
Software Delivery policy that requires a package.
The package download might not be required when the remediation action
is to uninstall the software. In that case, the package download is skipped.
The Managed Software Delivery policy downloads the package as follows:
■
Download the package to the client computer.
■
Create a snapshot of the package that is on the client computer and
compare it to the snapshot on the package server.
If the package is already on the client computer because of a recurring
delivery or a delivery re-attempt, its existing snapshot is used for
comparison.
If the snapshots do not match, re-download the package.
A mismatch can occur when some kind of interception has corrupted the
package.
■
When the package download is successful, the compliance process is finished
and the policy is ready for the remediation process.
175
Performing an advanced software delivery
Introducing advanced software deliveries
Table 11-2
How the remediation phase of Managed Software Delivery works
Step
Action
Description
Step 1
Compliance check
Determines whether the software is installed on the client computer.
This compliance check ensures that the software is still in the same state
as it was during the compliance process. For example, if the remediation
was scheduled to run later than the compliance process, the software might
have been installed or uninstalled in the interim.
If the remediation is still required, the process continues.
Step 2
Remediation action
Installs, uninstalls, or performs any other remediation action that the software
requires.
If the Managed Software Delivery policy contains multiple software resources
and tasks, they are executed in the order in which they appear in the policy.
You can override the policy’s remediation settings and schedule for individual
software resources and tasks within the policy.
Step 3
Compliance check
Determines whether the software resource is installed on the client computer.
This compliance check provides the information for reporting the results to
Notification Server.
Step 4
Report to Notification
Server
The Symantec Management Agent on the client computer reports the results
of the Managed Software Delivery process to Notification Server. You can
obtain information about the results from the compliance reports and the
delivery reports in Software Management Solution.
See “Running a Software Management Solution report” on page 157.
See “About advanced software deliveries” on page 173.
About policy applicability, compliance, and remediation
Managed Software Delivery can intelligently perform the applicability, compliance,
and remediation actions that let you not only deliver software but also manage it.
These actions ensure that you deliver the correct software to the correct computers
and that the software remains in the correct state on the computers.
See “About the execution of Managed Software Delivery policies” on page 174.
When you schedule a Managed Software Delivery policy, you can assign different
schedules for compliance and remediation. For example, you can schedule the
compliance process to occur during the day and the remediation to occur only during
a maintenance window.
176
Performing an advanced software delivery
Introducing advanced software deliveries
The compliance process and remediation process in Managed Software Delivery
are especially effective when you schedule the policy to run on a recurring basis.
The recurring policy ensures that the software remains in the correct state on the
client computers.
Table 11-3
Applicability, compliance, and remediation actions
Action
Description
Applicability
(Windows only) The applicability check determines whether the client computer has the correct
environment for an installation of the software. If the computer does not have the correct
environment, the policy execution stops.
Compliance
A compliance check uses the software resource’s unique identifier to determine whether the
software is installed on the client computer. For Windows-based software, you can define a
detection rule that contains additional information about the software and makes the detection
process even more accurate.
See “Creating or editing inventory rules” on page 83.
The compliance check always checks for the presence of the software on the client computer.
The check returns True if the software is installed and False if the software is not installed. The
correct state of a software resource can mean that it is installed or that it is not installed. A
Managed Software Delivery policy is considered compliant if all the software resources that it
contains are in the correct state on the client computer. If the software is not in the correct state,
it is considered to be out of compliance.
177
Performing an advanced software delivery
Introducing advanced software deliveries
Table 11-3
Applicability, compliance, and remediation actions (continued)
Action
Description
Remediation
Remediation is the act of fixing any software that is out of compliance on the client computer.
The nature of the remediation depends on the command-line action that the Managed Software
Delivery policy performs. For example, an installation command runs when the compliance check
returns False, and an uninstall command runs when the compliance check returns True.
Examples of how the type of command line determines the remediation action are as follows:
■
■
Installation command line
You want to install Symantec AntiVirus 2008 on all managed computers that do not have it
installed. You create the Managed Software Delivery policy and select an installation command
line. When the policy runs, the compliance check determines whether Symantec AntiVirus
2008 is installed.
If the software is installed, the check returns True. Because the correct state of the software
is to be installed, the software is considered to be compliant and the policy execution stops.
If the software is not installed, the check returns False. The software is out of compliance and
must be installed.
Uninstall command line
You want to ensure that Solitaire is not installed on any managed computers. You create the
Managed Software Delivery policy and select an uninstall command line. When the policy
runs, the compliance check determines whether Solitaire is installed.
If the software is installed, the check returns True. Because the correct state of the software
is to be uninstalled, the software is out of compliance and must be uninstalled. If the software
is not installed, the check returns False. The software is considered to be compliant and the
policy execution stops.
See “About deferring the execution of software remediation” on page 180.
About software delivery deferral options for the user
(Windows only)
You can give the user some control over when to execute a software delivery and
when to restart or log off after the execution. In Software Management Solution,
these options are available for Managed Software Delivery policies only.
178
Performing an advanced software delivery
Introducing advanced software deliveries
Table 11-4
User’s option
Software delivery deferral options for the user
Description
Defer the execution of a The ability to defer the policy
Managed Software
execution is useful when you
Delivery policy
deliver software during working
hours.
The user can dismiss the Starting
Task dialog box but cannot cancel
the policy altogether. The deferral
lets the user save work and close
any open files or programs.
Choose when to run the You might let the user control the
policy or choose not to execution when the software is
run the policy
optional or is not critical for that
user.
Location of the settings Settings
The settings for this option The required settings are
appear in the following
as follows:
places:
■ Prompt user before
■ On the Managed
running
Delivery Settings
■ Allow user to defer up
page, on the Run tab,
to a total of
under User run
Lets you allow the user
conditions.
to defer running the
■ In an existing Managed
policy up to the
Software Delivery
maximum amount of
policy, in the Advanced
time that you select.
options dialog box, on
the Run tab, under
User run conditions.
The settings for this option The settings are as follows:
appear in the following
■ Allow user to turn on
places:
policy from the Altiris
■ On the Managed
Agent
Delivery Settings
■ (Optional) User must
page, on the Schedule
turn on from Altiris
tab, under User
Agent
interaction.
Note: The policy’s
■ In an existing Managed
remediation options
Software Delivery
override this setting and its
policy, under the
related settings.
Schedule section.
179
Performing an advanced software delivery
Introducing advanced software deliveries
Table 11-4
Software delivery deferral options for the user (continued)
User’s option
Description
Location of the settings Settings
Defer a restart or a
logoff
You can set a Managed Software
Delivery policy to require a restart
or a logoff after the task finishes.
Because the restarts and logoffs
can cause a user to lose unsaved
work, you can let the user defer
them.
The settings for this option The required settings are
appear in the following
as follows:
places:
■ Upon success run
■ On the Managed
Lets you specify
Delivery Settings
whether to require a
page, on the Run tab,
restart or a logoff after
under Results-based
the policy runs
actions.
successfully.
■ In an existing Managed ■ Allow user to defer
Software Delivery
action up to
policy, in the Advanced
Lets you allow the user
options dialog box, on
to defer the
the Results-based
post-execution action
actions tab.
up to the maximum
amount of time that you
select.
About deferring the execution of software remediation
In a Managed Software Delivery policy, you can set different schedules for the
compliance check and the remediation. You can configure these options in the
default settings for all Managed Software Delivery policies. You can also change
the default settings for specific Managed Software Deliveries.
During a Managed Software Delivery, the package download occurs during the
compliance check and the program execution occurs during the remediation. When
you schedule a Managed Software Delivery policy, you define the schedule for the
compliance check and then select an option to schedule the remediation.
See “About the execution of Managed Software Delivery policies” on page 174.
The separate schedules allow for the offline execution of the Managed Software
Delivery. You can schedule an offline execution by selecting the option to perform
the remediation during the next maintenance window.
For example, you support a large number of remote users who connect to your
network a few times a week. You need to install a new application on all their
computers and you want the installation to occur during a maintenance window.
However, you cannot guarantee that the users are connected to the network when
a maintenance window is scheduled. Therefore, you can create a Managed Software
Delivery policy and schedule the compliance check to occur as soon as a user
connects to your network. Then you schedule the remediation (installation) to occur
180
Performing an advanced software delivery
Introducing advanced software deliveries
during the next maintenance window. When a user connects to the network, the
compliance check occurs and if a remediation is required, the package download
occurs. During the maintenance window, the installation occurs on the user’s
computer. The installation can occur even if the client computer is not connected
to the network, because the computer already has the package that it needs.
See “About advanced software deliveries” on page 173.
About installing software that replaces other software
Managed Software Delivery can use the supersedence associations that are defined
for software resources to install software that replaces other software. A
supersedence association is one in which one software resource replaces another
software resource.
Supersedence associations are supported in Managed Software Delivery installations
only.
See “About advanced software deliveries” on page 173.
When you create a Managed Software Delivery policy for a software resource that
has a supersedence association with other software, a message notifies you.
Depending on the nature of the association, your options are as follows:
The selected software
supersedes other software
The policy can uninstall the superseded software from the
client computer before the selected software is installed.
Other software supersedes
the selected software
You can take either of the following steps:
■
■
Create the Managed Software Delivery policy for the
superseding software instead and ensure that you
distribute only the current version of the software.
Install the superseded software anyway. You can make
the installation conditional by configuring it not to install
the software if a newer version is already installed.
The supersedence settings appear in the following places:
■
In the Managed Software Delivery wizard, on the Select software resource
page.
■
In the Policy Rules/Actions section that appears when you edit a Managed
Software Delivery policy or create one without the Managed Software Delivery
wizard.
See “Adding associations to a software resource” on page 88.
181
Performing an advanced software delivery
Viewing all Managed Software Delivery policies
About the status of Managed Software Delivery policies
The information in the Software Catalog lets Software Management Solution report
the status of Managed Software Delivery policies with greater accuracy than other
methods.
When a Managed Software Delivery policy completes an action on a client computer,
it performs a compliance check to evaluate the success of the execution. The
compliance check uses the software resource’s unique identifier to determine
whether that software is installed on a client computer. For Windows software, you
can define a detection rule that contains additional information about the software
and makes the detection process even more accurate. After the compliance check,
the Managed Software Delivery policy reports the status information to Notification
Server.
See “About policy applicability, compliance, and remediation” on page 176.
This method of determining a policy’s success is more accurate than using the
package’s exit code. A package can return an exit code that indicates success
when in fact, the delivery was completed but the installation was not successful.
For example, you can use a Package Delivery task to install an MSI package that
contains a custom action. However, because the custom action is placed in the
wrong section of the MSI, it is not installed on a Windows Vista computer. Even
though the package is not installed, the package execution is reported as successful
because the exit code is returned. If you use a Managed Software Delivery policy
instead, the compliance check can determine that the package is not installed.
Therefore, you get an accurate report of the delivery status.
See “About the execution of Managed Software Delivery policies” on page 174.
Viewing all Managed Software Delivery policies
You can view all your organization’s Managed Software Delivery policies.
To view all Managed Software Delivery policies
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software > Managed Software
Delivery.
3
To view a policy’s details, in the right pane, double-click the policy.
You can also add or take additional actions on a Managed Software Delivery
policy.
See “Creating a Managed Software Delivery policy” on page 184.
See “Editing a Managed Software Delivery policy” on page 186.
182
Performing an advanced software delivery
Creating a Managed Software Delivery policy with the Managed Software Delivery wizard
Creating a Managed Software Delivery policy with the
Managed Software Delivery wizard
You can perform one or more advanced software delivery actions with a single
Managed Software Delivery policy. Creating a Managed Software Delivery policy
is the first step in performing an advanced software delivery.
See “Performing an advanced software delivery” on page 189.
See “About advanced software deliveries” on page 173.
The Managed Software Delivery wizard provides a quick way to create and
schedule a policy for a single software resource and its dependency software. We
recommend that you use the wizard because it can include any dependency software
and warn you of software associations.
When you create a Managed Software Delivery policy with the Managed Software
Delivery wizard, the policy is enabled automatically. If you do not want the policy
to be available to managed computers immediately, edit the policy, and disable it.
You also might edit the policy to add information about what to deliver.
See “Editing a Managed Software Delivery policy” on page 186.
The software that you deliver in this way must be defined as a software resource
in the Software Catalog. If the software resource is not defined, contact an
administrator who can edit the Software Catalog.
You can run the Managed Software Delivery wizard from the Manage > Software
view or from other areas of the Symantec Management Console. Your point of entry
into the Managed Software Delivery wizard determines the amount of default
information that is populated.
Create the policy without the wizard if you need to perform any of the following
tasks:
■
Add multiple software resources and tasks.
■
Override the default settings.
■
(Windows and Mac OS only) Add the policy to the Software Portal.
See “Creating a Managed Software Delivery policy” on page 184.
See “About the execution of Managed Software Delivery policies” on page 174.
To create a Managed Software Delivery policy with the Managed Software Delivery
wizard
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, under Deliverable Software, click Software Releases.
183
Performing an advanced software delivery
Creating a Managed Software Delivery policy
3
Right-click a software resource and then click Actions > Managed Software
Delivery.
If the Managed Software Delivery option is not available, the software resource
does not have a package associated with it and cannot be delivered. Click
Actions > Edit Software Resource and configure the software resource.
4
In the Managed Software Delivery wizard, on the Select software page,
specify the software to deliver and other delivery options and then click Next.
5
On the Select destinations page, specify the destinations to deliver the
software to and then click Next.
See “Selecting the delivery destinations for a Managed Software Delivery
policy” on page 188.
6
On the Schedule delivery page, define the schedule for running the Managed
Software Delivery and then click Next.
7
(Optional) On the Specify dependencies and updates page, select any
dependencies, updates, or service packs that are defined for this software
resource and then click Next.
8
Dependencies
Check Verify dependencies and select the check box for each
dependency to include.
Updates or
service packs
Select the check box for each update or each service pack to
include.
To complete the wizard, click Deliver Software.
Creating a Managed Software Delivery policy
A single Managed Software Delivery policy lets you perform one or more advanced
software delivery actions. Creating a Managed Software Delivery policy is the first
step in performing an advanced software delivery.
See “Performing an advanced software delivery” on page 189.
See “About advanced software deliveries” on page 173.
When you create a Managed Software Delivery policy, you can add multiple software
resources and tasks or override the default settings. You also can publish the policy
to the Software Portal for Windows and Mac client computers.
The software that you deliver in this way must be defined as a software resource
in the Software Catalog. If the software resource is not defined, contact an
administrator who can edit the Software Catalog.
184
Performing an advanced software delivery
Creating a Managed Software Delivery policy
If you need to quickly create and schedule a Managed Software Delivery policy,
use the Managed Software Delivery wizard instead.
See “Creating a Managed Software Delivery policy with the Managed Software
Delivery wizard” on page 183.
To create a Managed Software Delivery policy
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software > Managed Software
Delivery.
3
In the left pane, right-click the Managed Software Delivery folder, and then
click New > Managed Software Delivery.
4
In the right pane, click and type over the following text:
New Managed
Type a name to identify this policy in any list of policies.
Software Delivery
Make the name descriptive enough for others to easily identify this
policy and the software that it delivers or manages.
Add description
Type a description to provide further information about this policy.
Do not include critical information in the description because it is
not intended to appear in all the lists that contain the name.
5
Under Policy Rules/Actions, on the Software tab, click Add. On the Add
menu, select one of the following options:
■
Software
Lets you select from the deliverable software resources that are defined in
the Software Catalog.
■
Task
Lets you select from the client tasks that are defined in Notification Server.
6
Repeat step 5 for each software resource and task that you want to add.
7
(Optional) To change the default settings for this policy, under Policy
Rules/Actions, enter additional settings on the Policy settings tab and the
Software Publishing tab.
8
(Optional) To change the default settings for a specific software resource or
task, under Policy Rules/Actions, click the software resource or task. At the
right of the page, do any of the following:
■
Change any of the options that are available on the page.
185
Performing an advanced software delivery
Editing a Managed Software Delivery policy
9
■
In a software resource, click Advanced options to display and change
additional settings.
■
In a task, click Show Task to display and change additional settings.
See “Editing a task in Software Management Solution” on page 155.
Expand the Applied to section to add or change the delivery destinations.
See “Selecting the delivery destinations for a Managed Software Delivery
policy” on page 188.
10 Expand the Schedule section to define the delivery schedule.
11 Turn on the policy.
At the upper right of the page, click the colored circle and then click On.
12 At the bottom of the page, click Save changes.
Editing a Managed Software Delivery policy
You can edit a Managed Software Delivery policy for any of the following reasons:
To add software resources
You can add any software resources to the execution queue.
Examples are as follows:
■
■
■
To add tasks
You can deliver multiple software resources that comprise
a set of base applications.
As you discover unauthorized software on client
computers, you can add that software to a recurring
uninstallation policy to keep it uninstalled.
If the software in the policy requires other software, you
can add the dependency software so that all the software
is installed together.
When you create a Managed Software Delivery policy
with the Managed Software Delivery wizard, the
dependencies are added automatically.
You can add any client task to the execution queue to perform
custom operations. For example, you can add a task that
runs a script. A client task is one that is defined in Notification
Server and is intended to run on a client computer.
To rearrange the order of the When you add multiple software resources and tasks to a
software resources and tasks Managed Software Delivery policy, you can set the sequence
in which they run.
186
Performing an advanced software delivery
Editing a Managed Software Delivery policy
To override the default policy Every new Managed Software Delivery policy inherits the
settings
default settings that are defined for Managed Software
Delivery. You can override the default settings for the entire
policy.
See “Configuring the default settings for Managed Software
Delivery” on page 71.
To override the policy settings The software resources and tasks that you add to the policy
for specific software
inherit settings from the policy. You can edit the settings for
resources and tasks
individual software resources and tasks.
To edit the destinations
When new managed computers are added to your
organization, you can add them to an existing Managed
Software Delivery policy.
To edit the schedule
You can add schedules for the compliance check or change
the remediation options.
When you change a Managed Software Delivery policy, the updated policy is sent
to the client computers, including those on which the policy has run.
To edit a Managed Software Delivery policy
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software > Managed Software
Delivery.
3
In the right pane, click a Managed Software Delivery policy.
4
On the policy page, do any of the following:
■
Change the policy’s name or description. Click either one in the upper left
of the page and type over the existing text.
Make the name descriptive enough for others to easily identify this policy
and the software that it delivers or manages.
Do not include critical information in the description because it is not
intended to appear in all the lists that contain the name.
■
Expand the Policy Rules/Actions section to add software resources and
tasks and to change the policy settings.
■
Expand the Applied to section to add or change the delivery destinations.
See “Selecting the delivery destinations for a Managed Software Delivery
policy” on page 188.
■
Expand the Schedule section to add or change the delivery schedule.
187
Performing an advanced software delivery
Selecting the delivery destinations for a Managed Software Delivery policy
5
On the policy page, turn on the policy or turn off the policy as needed.
At the upper right of the page, click the colored circle and then click On or Off.
6
When you finish editing the Managed Software Delivery policy, click Save
changes.
Selecting the delivery destinations for a Managed
Software Delivery policy
You can apply a Managed Software Delivery policy to selected resource targets,
computers, users, and resources. You can use any combination of these options
to define the computers to which the policy applies.
Managed Software Delivery supports user-based policies by letting you specify
users and user groups as policy targets. This feature lets you deliver software to
any managed computer that a specific user logs on to. When the user logs on to a
computer, the Symantec Management Agent refreshes any policy that targets that
user. The policy runs on that computer according to the schedule that you defined
for it.
For more information, see the topics about user-based policies in the Altiris™ IT
Management Suite 7.5 Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
See “Creating a Managed Software Delivery policy with the Managed Software
Delivery wizard” on page 183.
See “Creating a Managed Software Delivery policy” on page 184.
See “Editing a Managed Software Delivery policy” on page 186.
To select the delivery destinations for a Managed Software Delivery policy
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software > Managed Software
Delivery.
3
In the right pane, click a Managed Software Delivery policy.
4
On the policy page, expand the Applied to section to add or change the delivery
destinations.
For more information, see the topics about applying a policy to targets,
computers, resources, and users in the Altiris™ IT Management Suite 7.5
Administration Guide from Symantec™at the following URL:
http://www.symantec.com/docs/DOC5330
188
Performing an advanced software delivery
Performing an advanced software delivery
5
On the policy page, turn on the policy or turn off the policy as needed.
At the upper right of the page, click the colored circle and then click On or Off.
6
When you finish editing the Managed Software Delivery policy, click Save
changes.
Performing an advanced software delivery
You can perform advanced software deliveries and manage the software that is
installed on the managed computers.
See “About advanced software deliveries” on page 173.
The software that you want to deliver must be definded as a software resource in
the Software Catalog.
See “About the Software Catalog” on page 30.
Table 11-5
Process for performing advanced software deliveries
Step
Action
Description
Step 1
Create a Managed
The options for creating a Managed Software Delivery policy are as follows:
Software Delivery policy.
■ Use the Managed Software Delivery wizard.
The Managed Software Delivery wizard provides a quick way to create
and schedule a policy for a single software resource and its dependency
software. Symantec recommends that you use the wizard because it can
include any dependency software and warn you of software associations
automatically.
See “Creating a Managed Software Delivery policy with the Managed
Software Delivery wizard” on page 183.
■ Create the policy manually.
Use this method to create a Managed Software Delivery policy when you
need to add multiple software resources and tasks or override the default
settings. You also can publish the policy to the Software Portal. However,
you must add any dependency software or determine software
associations yourself.
You can also edit the policy that you created with the wizard.
See “Creating a Managed Software Delivery policy” on page 184.
189
Performing an advanced software delivery
Delivering multiple software resources and tasks sequentially
Process for performing advanced software deliveries (continued)
Table 11-5
Step
Action
Description
Step 2
(Optional) Edit the
Managed Software
Delivery policy.
You can edit the Managed Software Delivery policy to change or add
functionality as follows:
■
Add software resources or tasks and arrange the order in which they run.
■
Change the settings of the entire policy.
■
Change the settings of specific software resources and tasks.
■
Edit the schedule or the destinations.
See “Editing a Managed Software Delivery policy” on page 186.
Step 3
Choose the delivery
destinations.
Choose the computers that you want to deliver the software to.
See “Selecting the delivery destinations for a Managed Software Delivery
policy” on page 188.
When you use the Managed Software Delivery wizard to create the policy,
you select the destinations in the wizard.
Step 4
Schedule the policy.
Define the schedule on which a Managed Software Delivery policy runs. You
schedule the compliance check and the remediation check separately.
When you use the Managed Software Delivery wizard to create the policy,
you can define the schedule during the wizard.
Step 5
After the policy runs,
view reports.
The Software Management reports let you monitor the software deliveries.
The delivery reports provide information about the status of the software
downloads and executions. For example, the software downloads for each
computer, including the status and the download date. The compliance
reports provide information about the compliance actions and the remediation
actions.
See “Running a Software Management Solution report” on page 157.
Delivering multiple software resources and tasks
sequentially
You can deliver multiple software resources and tasks with a single Managed
Software Delivery policy. When Managed Software Delivery evaluates compliance
for a group of software, only the software that is out of compliance is downloaded
and installed. You can add any client tasks to the execution queue to perform custom
operations before, during, or after the software remediation process. A client task
is one that is defined in Notification Server and is intended to run on a client
computer.
190
Performing an advanced software delivery
Delivering multiple software resources and tasks sequentially
For example, you can create a single Managed Software Delivery policy that
performs the following actions:
■
Run a task that uses a script to set a registry key on the managed computer.
■
Determine whether the software resource or its dependencies are already
installed.
■
Install the software and any of its dependencies that are not already installed.
■
Install an additional software resource into a virtual layer because it is known
to conflict with other software that might be on the managed computer.
■
Run every week to determine whether the registry key is still correct and the
software is still installed.
■
Reset the registry key to the correct value if necessary.
■
Reinstall any software that the compliance check determines is broken or not
present.
The default settings for Managed Software Delivery determine what happens if the
policy fails. Initially, this setting is the same for each software resource and task
that the policy contains. You can edit the policy to override this setting for each
software resource and task. For example, if a critical execution in the sequence
fails, you can abort the remaining items in the sequence. Conversely, if a less-critical
execution fails, you might decide to run the subsequent tasks anyway.
Table 11-6
Process for delivering multiple software resources and tasks
Step
Action
Description
Step 1
Create a Managed Software The options for creating a Managed Software Delivery policy are as
Delivery policy.
follows:
■
■
Use the Managed Software Delivery wizard.
The Managed Software Delivery wizard provides a quick way to
create and schedule a policy for a single software resource and its
dependency software. We recommend that you use the wizard
because it can include any dependency software and warn you of
software associations automatically.
See “Creating a Managed Software Delivery policy with the Managed
Software Delivery wizard” on page 183.
Create the policy without the wizard.
Use this method to create a Managed Software Delivery policy when
you need to add multiple software resources and tasks or override
the default settings. You also can publish the policy to the Software
Portal. However, you must add any dependency software or
determine software associations yourself.
See “Creating a Managed Software Delivery policy” on page 184.
191
Performing an advanced software delivery
Performing an emergency policy update
Table 11-6
Process for delivering multiple software resources and tasks
(continued)
Step
Action
Description
Step 2
Select the delivery
destinations.
Select the managed computers to deliver to.
See “Selecting the delivery destinations for a Managed Software
Delivery policy” on page 188.
When you use the Managed Software Delivery wizard to create the
policy, you select the destinations during the wizard.
Step 3
Schedule the policy.
Define the schedule for the entire policy. You can schedule the
compliance check and the remediation separately.
When you use the Managed Software Delivery wizard to create the
policy, you can define the schedule during the wizard.
Step 4
Add the additional software
resources and tasks to the
policy.
You can add multiple software resources and tasks when you create
the policy without the Managed Software Delivery wizard. When you
use the Managed Software Delivery wizard to create the policy, you
can select only one software resource. Edit the policy to add software
and tasks.
Step 5
Arrange the sequence in
Move the software resources and tasks up or down in the list to
which the software resources rearrange their order. Plan the sequence before you enable the policy.
and tasks are run.
Step 6
(Optional) Change the
settings for individual
software resources or tasks.
When you add software resources and tasks to a Managed Software
Delivery policy, they inherit the settings from the policy. You can change
the settings for any specific software resource or task that is in the
policy.
The settings that you can change for a specific software resource or
task include the remediation schedule, the download settings, and the
run settings.
Performing an emergency policy update
The emergency policy update allows Managed Software Delivery policies to be
rapidly deployed throughout an environment without waiting for the normal agent
configuration update interval. Managed Software Delivery policies are only available
with Software Management Solution installed. For this reason, to use the emergency
policy update feature you need to ensure that you have Software Management
Solution installed.
See “Editing a Managed Software Delivery policy” on page 186.
192
Performing an advanced software delivery
Performing an emergency policy update
This feature is intended for emergency situations only, when you need to distribute
a software package as quickly as possible. This process can apply a heavy load
to your system, so it should not be used as a normal method for delivering software
policies.
The emergency policy update can be used in replication and hierarchy as well. The
emergency policy update first checks if the current Notification Server computer
supports hierarchy and it has child-level Notification Server computers. If any
child-level Notification Server computers are found for the current Notification Server
computer, then it starts replication immediately. After replication is completed, the
emergency policy update is executed on the child-level Notification Server
computers.
Note: On the Internet-managed computers that use Cloud-enabled Management
the emergency policy update only works like a schedule. The Symantec Management
Agent receives the policy according to the respective schedules of either the
configuration update schedule or when client checks for new tasks. In such cases,
the Notification Server computer cannot notify the computers of the pending tasks
using the tickle component of Task Management.
When you start an emergency policy update, Symantec Management Platform
sends out the appropriate client tasks. These are sent first to all of the package
servers that are assigned the relevant package, forcing those package servers to
update their configuration. Second, client tasks are sent to all of the Symantec
Management Agents that the policy targets, forcing those agents to update their
configuration. These client tasks ensure that the relevant package servers download
the required package as soon as possible. They also ensure that the targeted agents
also receive the policy as soon as possible.
Note that the policy still controls how and when the software package that the
updated policy specifies is installed on a managed computer. The emergency policy
update is a mechanism for distributing the policy as quickly as possible. The
emergency policy update delivers the Managed Software Delivery policy only, not
software.
You can perform an emergency policy update on Managed Software Delivery
policies to distribute a software package as quickly as possible.
Note the scenario when a Managed Delivery policy is scheduled to run once and
has already been received and evaluated on the targeted computer. If at this moment
the emergency policy update is launched, the policy does not re-evaluate again.
When you run an emergency policy update, you can monitor progress and results
with the emergency policy update reports. You can choose to have the appropriate
status report displayed in a new window when you start an emergency policy update.
193
Performing an advanced software delivery
Viewing emergency policy update reports
See “Viewing emergency policy update reports” on page 194.
To perform an emergency policy update
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software > Managed Software
Delivery.
3
In the left pane, locate the Managed Software Delivery policy that you want to
update.
4
On the policy page, turn on the policy.
At the upper right of the page, click the colored circle and then click On.
5
In the left pane, right-click on the policy and then click Emergency Policy
Update.
6
In the Emergency Policy Update dialog box, read the warning message and
the following information, and then check the appropriate options:
Replicate the policy to child If the Notification Server computer is in a hierarchy, the
Notification Servers
policy and any dependent items are replicated to each
node in the hierarchy tree. The emergency policy update
process is run on each node.
This option appears only when the Notification Server
computer is part of a Hierarchy.
Display status report in new Displays the appropriate status report in a new window:
window when OK is clicked
■ If the policy is not replicated, the Emergency Policy
(ensure popups are
Update Status Summary report is displayed.
enabled)
■ If the policy is replicated down a hierarchy, the
Emergency Policy Update Status by Hierarchy
Node report is displayed.
7
Click OK.
Viewing emergency policy update reports
When you run an emergency policy update, you can monitor progress and results
with the emergency policy update reports. You can choose to have the appropriate
status report displayed in a new window when you start an emergency policy update.
See “Performing an emergency policy update” on page 192.
194
Performing an advanced software delivery
Viewing emergency policy update reports
To view the emergency policy update reports
1
In the Symantec Management Console, in the Reports menu, click All Reports.
2
In the left pane, click Reports > Notification Server Management > Server
> Emergency Policy Update, and then click the report that you want to view:
■
Emergency Policy Update Status by Hierarchy Node shows each node
in the hierarchy.
The Depth column indicates the level in the hierarchy of the particular
Notification Server computer. A depth of 0 indicates the parent Notification
Server computer and is at the top of the hierarchy environment. A depth of
1 indicates a child Notification Server computer.
The report returns no results when the server is not in a hierarchy.
■
Emergency Policy Update Status Summary shows the number of package
servers and Symantec Management Agents that requested a new
configuration since the emergency policy update process was started.
195
Chapter
12
Delivering software from
user requests using the
Software Portal
This chapter includes the following topics:
■
Introducing software requests and the Software Portal
■
Setting up the Software Portal
■
Configuring security privileges for the Software Portal
■
Reviewing and approving software requests
■
Using the Software Portal on the client computer
Introducing software requests and the Software
Portal
Before you manage software requests, it is a good idea to better understand the
Software Portal.
To help you get more familiar with software requests and the Software Portal you
can refer to the following:
■
About the Software Portal and how it lets users submit requests and install
software through a Web-based interface with little or no administrator involvement
See “About the Software Portal” on page 197.
■
About what actions the end user can perform in the Software Portal
See “What you can do with the Software Portal” on page 198.
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
■
About how an administrator adds software to the Software Portal and the terms
that describe the software in the Software Portal.
See “About the software in the Software Portal” on page 198.
■
About methods for adding software to the Software Portal so that an end user
can request it
See “Methods for adding software to the Software Portal” on page 199.
■
About the status of a software request and how it indicates its place in the
Software Portal approval process
See “Statuses of software requests in the Software Portal” on page 200.
■
About how a software request is processed through the Software Portal
See “Software request workflow” on page 202.
■
About the delivery methods for delivering software from approved software
requests
See “Methods for delivering software from approved software requests”
on page 204.
About the Software Portal
The Software Portal lets users submit requests and install software through a
Web-based interface with little or no administrator involvement. This self-service
approach to software delivery reduces help desk calls and simplifies the process
of requesting and delivering software. Because the Software Portal uses predefined
software information and delivery settings, it can automate most of the deliveries
that result from the software requests.
The administrator who sets up the Software Catalog decides which software each
user or group of users is allowed and specifies which software requires approval.
These settings determine the amount of intervention that is required for specific
software requests. Requests for pre-approved software require no further action
from anyone. Requests for other standard software require approval from a manager
or an administrator but upon approval, the software delivery is automatic. Only the
requests for non-standard software require the manager or the administrator to take
further action to deliver the software.
The Software Portal is installed on the client computers. Therefore, the users can
create requests and the managers can approve the requests without requiring
access to the Symantec Management Console.
The Software Portal supports requests for Windows and Mac OS software.
See “Implementing the Software Portal” on page 205.
See “Software request workflow” on page 202.
197
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
See “Processing a software request on the Administrator Portal page” on page 214.
What you can do with the Software Portal
The actions that you can perform in the Software Portal are as follows:
■
Configure your profile to enter your user information and preferences.
See “Setting up the Software Portal with your user profile” on page 218.
■
Request software. (Windows and Mac OS only)
You can request the software that is standard for your organization, which is
known as listed software. You also can request non-standard software, which
is known as unlisted software. For example, unlisted software can be a special
utility that you need for your work but that no one else in the organization needs.
See “Requesting software in the Software Portal” on page 220.
■
Review and manage your software requests.
See “Reviewing or adding comments to a software request” on page 221.
See “Canceling a software request” on page 223.
■
Review the software requests and approve or deny them, if you are a manager.
See “Processing a software request” on page 224.
Some requests might also need an administrator’s approval.
About the software in the Software Portal
An administrator adds software to the Software Portal and configures the settings
and the permissions that let users request the software. The terms that describe
these settings and permissions appear on the Software Portal pages where the
software is displayed.
Note: When you publish a software resource to the Software Portal on a parent
Notification Server computer, you cannot search for and select local users and
groups of a child domain. You can assign permissions for the users and groups
that are visible on the parent domain only. The software publishing in hierarchy
works properly when the parent Notification Server computer and its children are
in the same domain.
See “About the Software Portal” on page 197.
See “Methods for adding software to the Software Portal” on page 199.
198
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
Table 12-1
Terms that describe the software in the Software Portal
Term
Description
Listed
The software that is in the Software Catalog and published to the
Software Portal for the current user.
Listed software is available for the user to request. If it is not
recommended for the current user, it does not appear on the user’s
Home page by default.
The term Listed can also apply to a request for listed software.
Unlisted
Software that meets any of the following conditions:
■
The software is not in the Software Catalog.
■
The software is in the Software Catalog but is not published to the
Software Portal.
The software is published to the Software Portal but not for the
current user.
■
Unlisted software cannot be delivered automatically on request.
The term Unlisted can also apply to a request for unlisted software.
Approved
The listed software that is pre-approved for a specific user. Typically,
the software that does not require a license is pre-approved. For
example, Adobe Reader and the Google Toolbar do not require a
license.
Approved software is delivered or scheduled for delivery as soon as
the user submits a request for it. No further action is needed.
The person who publishes the software to the Software Portal can
pre-approve it.
Recommended
The listed software that is recommended for a specific user. For
example, the software that is part of the user’s set of core applications
should be recommended.
Recommended software appears on the user’s Home page by default.
The user can also display all the software that is published for them.
The person who publishes the software to the Software Portal can
designate it as recommended.
Methods for adding software to the Software Portal
Before a user can request software from the Software Portal, you must add the
software that the user can request. The process of adding software to the Software
Portal is known as publishing.
199
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
Publishing software to the Software Portal consists of the following actions:
■
Selecting the software to publish
■
Defining the users who are allowed to request that software
■
Specifying whether a user needs approval to install that software
You can publish software to the Software Portal in the following ways:
Software resource
Publish a software resource to the Software Portal to deliver a
single piece of software with minimum configuration. Most
organizations can publish the majority of software in this way.
See “Adding a software resource to the Software Portal”
on page 207.
Managed Software
Delivery policy
Publish a Managed Software Delivery policy to the Software Portal
to deliver one or more software resources with complex delivery
requirements.
See “Adding a Managed Software Delivery policy to the Software
Portal” on page 209.
See “About advanced software deliveries” on page 173.
Statuses of software requests in the Software Portal
The status of a software request indicates its place in the Software Portal approval
process. As a software request is processed, the user, manager, and administrator
can check its status at any time.
A software request is created when a user uses the Software Portal to request
software. A manager or an administrator processes a software request by changing
its status.
See “Processing a software request on the Administrator Portal page” on page 214.
Users of the Software Portal can check the status of software requests from the
following locations:
■
Under the Request Status section on the user’s Home page, the Manager
Portal page, or the Administrator Portal page, depending on your user role.
■
In any of the Request Details dialog boxes that appear when a request is
opened.
■
In the reports that are available in the Symantec Management Console. Typically,
these reports are available to the administrator only.
See “Running a Software Management Solution report” on page 157.
■
In the Web parts that are associated with the Software Portal.
200
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
See “Web parts for Software Management Solution” on page 20.
Some of the statuses are used for reporting purposes only and do not appear on
any pages or dialog boxes in the Software Portal.
Table 12-2
Statuses of software requests in the Software Portal
Status
Description
Approved (Complete)
The request is approved and the software is either installed or
scheduled for installation.
Approved (Pending)
The request is for unlisted software and a manager approved it
and sent it to an administrator for approval.
Canceled
The user canceled the request.
Closed
A request is closed when it has any of the following statuses:
■
Approved (Complete)
■
Canceled
■
Denied
The Closed status does not appear in the Request Status list or
in the Request Details dialog boxes. However, it is included in
the messages that appear when someone tries to edit a request
that is closed.
Denied
The manager or the administrator denied the request.
Failure
An attempt to deliver the requested software was made and it
failed. This status describes the software delivery rather than the
software request. It appears on the Software Portal reports and
the Web parts that appear in the Symantec Management Console.
On Hold
The manager or the administrator placed the request on hold
pending further research.
For example, the manager might place a request on hold and enter
comments to ask the user to justify the need for the software. The
administrator might need to check the availability of a license or
obtain the software.
Open
The request is not closed. For example, an On Hold request is
considered to be Open.
Scheduled
The request is approved and is scheduled for delivery.
Submitted
The user created the request but no one has taken further action
on it.
201
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
Table 12-2
Statuses of software requests in the Software Portal (continued)
Status
Description
Success
The requested software was delivered successfully. This status
describes the software delivery rather than the software request.
It appears on the Software Portal reports and the Web parts that
appear in the Symantec Management Console.
See “About the software in the Software Portal” on page 198.
Software request workflow
Figure 12-1 shows how a software request is processed through the Software Portal.
See “About the Software Portal” on page 197.
This diagram does not illustrate the additional steps that are required to deliver
unlisted software. Unlisted software is either not in the Software Catalog or is not
published to the Software Portal. Therefore, it cannot be delivered automatically
and someone must take additional steps to deliver it.
202
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
Software request workflow diagram for listed software
Figure 12-1
The end user
requests the
software
The request goes to
the manager and
administrator
Is a manager
assigned?
No
No
Yes
Is the software
approved?
Is the manager
available?
Yes
Yes
The manager
reviews the request
No
The administrator
reviews the request
The request is held
until further action is
taken
Approve
Manager’s
decision
On Hold
The request is held
until further action is
taken
Deny
The request is
closed
Deny
The software is
delivered
Administrator’s
decision
Approve
On Hold
203
Delivering software from user requests using the Software Portal
Introducing software requests and the Software Portal
Methods for delivering software from approved software requests
When a manager or administrator approves a software request, the software is
delivered to the user.
The delivery method for requested software depends on whether the software is
listed or unlisted as follows:
Listed software
Listed software is delivered automatically upon approval of the software
request. The method that was used to publish the software to the
Software Portal determines whether a task or a policy performs the
delivery.
See Table 12-3 on page 204.
Unlisted software
Unlisted software cannot be installed automatically. The approver must
take additional action outside of the Software Portal to deliver the
software.
An unlisted software resource is not in the Software Catalog or is not
published to the Software Portal for the person who creates the request.
See Table 12-4 on page 205.
Table 12-3
Delivery methods for listed software
Publication method
Delivery method
Software resource
The first approved request for that software creates a Quick
Delivery task. Each subsequent request for that software creates
a new instance of the first Quick Delivery task. The new instance
is delivered to the user who requested the software.
Managed Software
Delivery policy
A request for that software adds the user to the destinations for
the policy. The software is delivered according the schedule that
is defined for that policy.
See “Methods for adding software to the Software Portal” on page 199.
204
Delivering software from user requests using the Software Portal
Setting up the Software Portal
Table 12-4
Delivery methods for unlisted software
Software resource’s state
Typical approver
The software resource is not in Administrator or
the Software Catalog and it does manager
not need to be added.
Delivery method
The administrator or the
manager obtains the software
and gives it to the user to install.
For example, the software might
be a special utility that only a
few people in the organization
need.
The software resource is not in Administrator
the Software Catalog and it
needs to be added.
For example, the software
application is one that you plan
to manage.
The software resource is in the Administrator
Software Catalog but was not
published at all or was not
published for the user who
requested it.
Add the software resource to the
Software Catalog and create a
software delivery policy or task
to deliver it.
See “Methods for delivering
software” on page 145.
Create a software delivery policy
or task to deliver the software.
See “Methods for delivering
software” on page 145.
Setting up the Software Portal
Implementing the Software Portal
Before you or any users can use the Software Portal, you must set it up and prepare
it for use.
See “About the Software Portal” on page 197.
The minimum prerequisites for implementing the Software Portal are as follows:
■
Software Management Solution must be installed on the Notification Server
computer. The Software Portal is installed on the Notification Server computer
when Software Management Solution is installed.
For more information, see the IT Management Suite 7.5 Installation Guide at
the following URL:
http://www.symantec.com/docs/DOC5697
■
The Software Management Solution plug-in must be installed on the computers
on which you implement the Software Portal.
205
Delivering software from user requests using the Software Portal
Setting up the Software Portal
See “Installing or upgrading the Software Management Solution plug-in”
on page 65.
Additional steps in the Software Management Solution implementation process can
be performed, but the Software Portal implementation does not require them.
See “Implementing Software Management Solution” on page 63.
Table 12-5
Process for implementing the Software Portal
Step
Action
Description
Step 1
Configure security roles for
the administrators and
managers who need to use
the Software Portal.
The security settings provide the permissions to manage and approve
the users’ software requests.
Step 2
Typically, users do not have access to the Symantec Management
Console and do not have Altiris security roles.
Configure the Software Portal The Software Portal settings customize the portal’s behavior and
settings.
appearance. You can change these settings at any time after you
implement the Software Portal.
See “Configuring the Software Portal settings” on page 209.
Step 3
Install the Software Portal
plug-in on the client
computers.
(Windows only) Perform this step every time that you need to install
the Software Portal on the client computers that do not have it.
The Software Portal plug-in provides access to the Software Portal Web
application from the client computer. The plug-in also installs shortcuts
to the Software Portal interface on the client computer.
See “Installing the Software Portal plug-in” on page 68.
206
Delivering software from user requests using the Software Portal
Setting up the Software Portal
Table 12-5
Process for implementing the Software Portal (continued)
Step
Action
Description
Step 4
Define the software that
appears in the Software
Portal.
Before a user can request software from the Software Portal, you must
define the software that the user can request. Perform this step
whenever you add users or software resources to Notification Server.
Examples are as follows:
■
■
When the finance department hires a new employee, you add that
employee to the software resources that the members of the finance
department require.
When an administrator adds a new software resource to the Software
Catalog, they add the users who are allowed to request that
software.
You can define software in the Software Portal in the following ways:
■
■
Step 5
Instruct the users and
managers to configure their
profiles.
Publish a software resource to perform a quick delivery of a single
software resource with a minimum of configuration.
See “Adding a software resource to the Software Portal” on page 207.
Publish a Managed Software Delivery policy to take advantage of
its ability to respond to complex delivery requirements.
See “Adding a Managed Software Delivery policy to the Software
Portal” on page 209.
Anyone who uses the Software Portal on a client computer must
configure their user profile before they can create and process requests.
See “Setting up the Software Portal with your user profile” on page 218.
Adding a software resource to the Software Portal
You can add (publish) a software resource to the Software Portal to deliver a single
piece of software with minimum configuration. You can publish only the resources
that have a command line. You can select one or more command lines that you
want to publish, and configure user and permission assignments for each of the
command lines individually. For example, you can choose to pre-approve the
software install command line, but require administrator's approval for the uninstall
command line.
When you publish a software resource, a hidden Quick Delivery task is created.
After a software request is approved, the Quick Delivery task runs and installs the
software on the user’s computer as soon as possible.
When a software resource is published to the Software Portal, its publishing settings
are saved in the Software Catalog as a reference to the software resource. You
cannot delete a software resource from the Software Catalog if references are
207
Delivering software from user requests using the Software Portal
Setting up the Software Portal
associated with that software resource. To ensure that you can delete the software
resource, you must delete its references first.
You can delete a software resource that is published to the Software Portal.
However, you cannot delete a software resource that has references. A reference
is an association between the software resource and another item in the Symantec
Management Platform.
When a software resource is published to the Software Portal, a reference to its
publishing settings is created. The publishing settings include the permissions,
software name, and software description. Because these references are saved with
the software resource, you can temporarily un-publish the software from the Software
Portal without losing its settings.
For example, you publish a software resource to the Software Portal and set
permissions for 12 user groups. Later, you need to make that software unavailable
for a specific time, so you uncheck the Publish to Software Portal check box on
the Software Publishing tab. When you decide to make the software available
again, you can check the Publish to Software Portal check box and the software’s
Software Portal settings are preserved. You do not have to reset the permissions
for those user groups.
Warning: If the software resource that you publish has dependencies on other
software, the dependency software is not delivered as a result of a user request.
Instead, create and publish a Managed Software Delivery policy for that software
so that the dependencies are installed.
See “Adding a Managed Software Delivery policy to the Software Portal” on page 209.
This task is a step in the process for implementing the Software Portal.
See “Implementing the Software Portal” on page 205.
To add a software resource to the Software Portal
1
In the Symantec Management Console, on the Manage menu, click Software.
2
In the left pane, under Deliverable Software, click Software Releases.
3
In the Software Releases pane, right-click a software resource and then click
Actions > Edit Software Resource.
4
On the software resource edit page, click the Software Publishing tab.
5
On the Software Publishing tab, select one or more command lines and
configure other settings for publishing this software resource.
6
Click Save changes.
7
Close the software resource edit page.
208
Delivering software from user requests using the Software Portal
Setting up the Software Portal
Adding a Managed Software Delivery policy to the Software Portal
You can add (publish) an existing Managed Software Delivery policy to the Software
Portal to deliver one or more software resources with complex delivery requirements.
See “About advanced software deliveries” on page 173.
For example, you can publish a Managed Software Delivery policy that installs a
software resource and the other software that it depends on. The user can request
the main software without having to request the dependency software or even know
that a dependency exists.
You can also publish software resources to the Software Portal.
See “Adding a software resource to the Software Portal” on page 207.
This task is a step in the process for implementing the Software Portal.
See “Implementing the Software Portal” on page 205.
To add a Managed Software Delivery policy to the Software Portal
1
In the Symantec Management Console, on the Manage menu, click Policies.
2
In the left pane, under Policies, expand Software > Managed Software
Delivery, and then click a managed software delivery policy.
3
In the right pane, expand the Policy Rules/Actions section and click the
Software Publishing tab.
4
On the Software Publishing tab, enter the details and select the settings for
publishing this software resource.
5
In the right pane, click Save changes.
Configuring the Software Portal settings
Before you use the Software Portal, configure the settings that customize its behavior
and appearance. You can change these settings at any time after you implement
the Software Portal.
This task is a step in the process for implementing the Software Portal.
See “Implementing the Software Portal” on page 205.
To configure the Software Portal settings
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand Software > Software Portal Settings, and then click
Software Portal Settings.
209
Delivering software from user requests using the Software Portal
Setting up the Software Portal
3
On the Software Portal Settings page, in the Maximum number of open
requests per user box, type the number of requests that a user can have open
at any time. The default number of requests is three, which is the recommended
number.
A user who exceeds the allowed number of requests cannot create a new
request until one of their other requests is closed.
A Managed Software Delivery policy that contains dependencies or multiple
tasks counts as one request.
4
On the Software Portal Settings page, under UI Settings, specify the following
information:
Company logo
Lets you brand the Software Portal with your organization’s logo
or another image.
Specify an image file to add to the Software Portal display. The
image appears in the upper-right corner of the Software Portal
window.
Specifications for the image file are as follows:
■
Format: JPG, GIF, BMP, PNG.
■
Maximum recommended image dimensions: 80 pixels wide by
20 pixels high.
Image resolution: The resolution is not restricted but we
recommend a low resolution such as 72 pixels per inch to
conserve bandwidth.
■
Company name
5
Type the name of your organization as it should appear in the
Software Portal window.
(Optional) On the Software Portal Settings page, under Publishing Settings,
check Publish software across all trusted domains.
Publishing software across all trusted domains can increase the Software Portal
loading time. When this option is not selected, the software is published for
the users or groups in the domain of the Notification Server computer only.
210
Delivering software from user requests using the Software Portal
Configuring security privileges for the Software Portal
6
(Optional) On the Software Portal Settings page, under Delivery Settings,
specify the default timeout period for the Quick Delivery tasks to deliver the
required software. An increased timeout period can significantly improve
software delivery for the Software Portal.
By default the End task after is set to 300 minutes (five hours). A recommended
value to change the timeout period to is 1440 minutes (24 hours). The maximum
timeout allowable is 2160 (36 hours).
The End task after option is only available for newly created Quick Delivery
tasks.
7
Click Save changes.
Configuring security privileges for the Software Portal
As part of the Software Portal implementation, you configure security privileges for
the administrators and managers who need to use the Software Portal.
See “Implementing the Software Portal” on page 205.
Several types of users interact with the Software Portal. Each type of user has its
own privileges and responsibilities. The security privileges in Notification Server let
specific user roles manage and approve the users’ software requests.
Table 12-6
User role
Users of the Software Portal
Privileges and responsibilities
Administrator, Software This administrator requires Software Portal privileges to administer software requests.
Portal
The Software Portal administrator’s tasks are as follows:
■
■
■
Approve users’ software requests when necessary.
For example, the administrator might approve a request that the manager is not allowed
to approve.
Approve any user’s request when a manager is not available.
Deliver the approved software that is not in the Software Catalog or that is not assigned
to the user.
The same person might perform both the Software Portal administrator and the Software
Catalog administrator roles.
211
Delivering software from user requests using the Software Portal
Configuring security privileges for the Software Portal
Table 12-6
User role
Users of the Software Portal (continued)
Privileges and responsibilities
Administrator, Software The Software Catalog administrator manages the Software Catalog, which represents the
Catalog
software that is known to be in your organization. This administrator requires Software
Management Framework privileges.
The Software Catalog administrator’s tasks in the Software Portal are as follows:
Manager
■
Define the software that appears in the Software Portal for specific users or groups.
■
Pre-approve software for specific users or groups.
Pre-approval streamlines the request process by eliminating the need for additional
intervention from the manager, administrator, or help desk. For example, the administrator
can pre-approve a group of software tools that users in a specific department require.
The Software Portal manager approves users’ software requests in the Software Portal.
The manager can be any employee in your organization who has the authority to allow users
to acquire software. Typically, a department manager fills this role.
Because the Software Portal is installed on the client computer, the manager can approve
requests without access to the Symantec Management Console.
The Software Portal manager requires Software Portal privileges to manage and approve
software requests.
User
The user on a client computer submits requests for software on the Home page in the
Software Portal. The user can be any employee in the organization who needs software.
Because the Software Portal is installed on the client computer, the user can create requests
without access to the Symantec Management Console.
Typically, users do not have access to the Symantec Management Console and do not have
Notification Server security roles.
212
Delivering software from user requests using the Software Portal
Configuring security privileges for the Software Portal
Table 12-7
Recommended privilege settings for the Software Portal
Security role
Recommended
privileges
Description
Software Portal
Administrators
Manage Software
Requests
This setting is on the Privileges tab,
under Software Portal Privileges.
This setting provides access to the
Administrator Portal page in the
Symantec Management Console.
The Software Portal administrator
approves special requests and can also
approve any requests if a manager is
not available. The administrator also
delivers the approved software that is
not in the Software Catalog or that is not
assigned to the user.
Software Portal
Managers
Manage and Approve
Software Requests
This setting is on the Privileges tab,
under Software Portal Privileges.
This setting provides access to the
Manage tab in the Software Portal, from
which the manager approves software
requests.
The manager can be any employee in
your organization who has the authority
to allow users to acquire software.
Typically, a department manager fills
this role.
To configure security privileges for the Software Portal
1
In the Symantec Management Console, on the Settings menu, click Security
> Account Management.
2
In the left pane, click Account Management > Roles.
3
On the Roles page, in the left pane, click the security role that you want to
configure.
4
In the right pane, on the Privileges tab, select the privileges that you want to
assign the role.
To select a privilege, check the corresponding check box.
213
Delivering software from user requests using the Software Portal
Reviewing and approving software requests
Reviewing and approving software requests
Finding and filtering software requests
You can search for specific types of software requests on the Administrator Portal
page.
To find and filter software requests
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand Software > Software Portal Settings, and then click
Administrator Portal.
3
On the Administrator Portal page, expand the Filtering options section.
4
Select the filter criteria.
For more information about the options, click the page and then press F1
5
Click Search.
Processing a software request on the Administrator Portal page
Some software requests require an administrator to approve or take other action
on a software request. To process a software request, you change its status.
The request statuses that you can set are as follows:
■
Approve
■
On Hold
■
Deny
See “Statuses of software requests in the Software Portal” on page 200.
Every software request that is created in the Software Portal must be approved
before the software is installed. Different user roles can approve the software
requests, depending on the type of request and the stage of the software request
process.
214
Delivering software from user requests using the Software Portal
Reviewing and approving software requests
Table 12-8
Users who can approve software requests
Approver
When their approval is needed
Administrator, Software The Software Catalog administrator can pre-approve software for
Catalog
specific users or groups when the software is published to the
Software Portal.
Pre-approval streamlines the request process by eliminating the
need for additional intervention from the manager, administrator,
or help desk. For example, the administrator can pre-approve a
group of software tools that users in a specific department require.
Administrator, Software A request requires an administrator’s approval in the following
Portal
situations:
■
■
■
When the user is not assigned to a manager
In this case, the request is sent directly to the administrator.
When a manager is out of the office or does not respond to a
software request.
When the request is for an unlisted software resource and the
manager assigns the request to the administrator
An unlisted software resource is not in the Software Catalog
or is not published to the Software Portal for the person who
creates the request. A request for an unlisted software resource
requires the manager or the administrator to take additional
action. A manager who has access to the software can approve
the request and provide the software to the user. A manager
who does not have access to the software can approve the
request and assign it to the administrator, who can provide the
software. For example, the administrator can obtain new
software or create a software delivery task.
See “Processing a software request on the Administrator Portal
page” on page 214.
Manager
A request requires a manager’s approval when the software is not
pre-approved for a user who is assigned to that manager. The
software can be listed or unlisted.
When a manager approves a request for listed software, the
software is delivered. When a manager approves a request for
unlisted software, the manager can choose to assign it to the
Software Portal administrator for additional action.
215
Delivering software from user requests using the Software Portal
Reviewing and approving software requests
To process a software request on the Administrator Portal page
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand Software > Software Portal Settings, and then click
Administrator Portal.
3
On the Administrator Portal page, under Requested Software, select the
software request.
Only the requests that require your attention are displayed. Use the search
feature to find and display other requests if necessary.
See “Finding and filtering software requests” on page 214.
4
5
Take either of the following actions:
■
To open the request for review, comments, or a status change, click Edit.
■
To quickly change the status without opening the request, click Change
Status and on the Change Status menu, select the status.
If you opened the software request, in the Listed Software Request Details
dialog box or the Unlisted Software Request Details dialog box, take any of
the following actions:
■
Change the status.
■
Enter comments to explain why you have changed the status or to request
additional information.
Comments are required whenever you change the status.
■
To review the request’s comments and actions, expand the Request History
section.
216
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
6
If this request is for unlisted software, you can click one of the following links:
Import new software
resource
If you know that the software resource is not in the
Software Catalog, click this link to import it. The Import
Software wizard opens.
See “Importing a package to create a software resource”
on page 51.
Search for available
software resource
The software resource might be in the Software Catalog.
However, it might not have been published at all or it
might not have been published for this user. Click this
link to open the Software Catalog so you can determine
if the requested software is in the catalog.
Create Quick Delivery task If the software resource is in the Software Catalog, click
this link to start the Quick Delivery wizard and create
a Quick Delivery task.
See “Creating a Quick Delivery task with the Quick
Delivery wizard” on page 152.
Create Managed Delivery
task
If the software resource is in the Software Catalog, click
this link to start the Managed Software Delivery wizard
and create a Managed Software Delivery policy.
See “Creating a Managed Software Delivery policy with
the Managed Software Delivery wizard” on page 183.
7
In the Listed Software Request Details dialog box or the Unlisted Software
Request Details dialog box, click OK.
8
If you approve a request for the unlisted software, take steps to obtain the
software.
Using the Software Portal on the client computer
Opening the Software Portal
The first time you open the Software Portal when logged into the system using the
domain user account the Home page appears. If you do not have pre-populated
user details Display Name and E-mail properties defined in the Active Directory,
the User Profile page appears. After you have set up your user profile, the Software
Portal opens your Home page.
217
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
Note: You cannot open the Software Portal from the Internet-managed computers
that use Cloud-enabled Management.
The Software Portal might not open properly on a computer that runs Windows
Server 2003 or 2008. This problem occurs when the computer’s browser security
settings are set to High, which disables the following Security Settings option:
Launching Programs and Files in an IFRAME. Because the Home page in the
Software Portal uses the IFRAME element, the page is not rendered properly. To
inquire about changing your browser’s security settings, contact your organization’s
system administrator.
To open the Software Portal
◆
Take one of the following actions:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
■
On the Start menu, click All Programs > Symantec > Symantec Software
Portal
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
Setting up the Software Portal with your user profile
The administrator installs the Software Portal on individual computers and provides
information about how you can access it. Before you can request or approve software
in the Software Portal, you must configure your user profile.
Your user profile contains the information that identifies you in the Software Portal.
If you are a manager, you also specify the users whose software requests you can
process.
You can also specify your preferences for the receipt of email messages about
requests.
To configure your user profile in the Software Portal
1
To open the Software Portal, do one of the following:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
■
On the Start menu, click All Programs > Symantec > Symantec Software
Portal
218
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
Note: The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
2
On the User Profile tab, enter or edit your user information and specify your
preferences for the receipt of email messages about requests.
Pre-populated user details are taken from the Active Directory if the required
fields are specified for the same user.
3
Click Save Changes.
Finding and filtering software requests on the Manager Portal page
You can search for specific types of software requests on the Manager Portal
page.
See “Finding and filtering software requests” on page 214.
See “Processing a software request” on page 224.
The Manager Portal page lets a manager view and approve the software requests
for the users who are listed on the manager’s User Profile page.
The Manager Portal page appears in the Software Portal on the client computer.
The page is available only to the users who have permission to approve and deny
software requests.
Table 12-9
Sections on the Manager Portal page
Section
Description
Filtering options
Lets the manager use filter options to find a specific group of
software requests.
Requested Software
Lets the manager review the software requests and decide what
action to take.
See “Processing a software request” on page 224.
To find and filter software requests
1
To open the Software Portal, do one of the following:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
219
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
■
On the Start menu, click All Programs > Symantec > Symantec Software
Portal
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
Note: The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
2
Click Manage.
3
On the Manager Portal page, expand the Filtering options section.
4
Select the filter criteria from any of the following lists:
Status
Request type
5
Lets you search for the requests with one of the following
statuses:
■
Approve
■
Deny
■
Open
■
On Hold
Lets you search for requests for listed or unlisted software.
If necessary, click Show only the requests from users who report directly
to me.
The users who report to you are those who are defined on your User Profile
page.
6
Click Search.
Requesting software in the Software Portal
In the Web-based Software Portal, you can request software and install it on your
computer with little or no administrator involvement.
By default, only the software that is recommended for you is displayed.
After you create a software request, it is processed as follows:
■
If the software is listed and it is pre-approved, the software delivery is scheduled
to occur on the date and time that you specify.
■
If the software is listed and it requires approval, the request is assigned to an
approver.
220
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
■
If the software is unlisted, the request is assigned to an approver.
The number of requests that you can have open at one time might be limited. When
you reach your limit you cannot create a new request until an open request is closed.
Before you can request software, you must configure your user profile.
See “Setting up the Software Portal with your user profile” on page 218.
To request software in the Software Portal
1
To open the Software Portal, do one of the following:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
■
On the Start menu, click Programs > Symantec > Symantec Software
Portal
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
Note: The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
2
If the Home page does not appear, click Home.
3
On the Home page, do one of the following:
■
If the software that you want is in the list, select the software in the list and
click Request Software.
■
If the software that you want is not in the list, click Show All to display all
the software that is available to you.
If the software that you want still does not appear in the list, click Request
Unlisted Software.
For more information about the options, click the page and then press F1
4
In the Request Confirmation dialog box or the Unlisted Request
Confirmation dialog box, enter information about the request.
For more information about the options, click the page and then press F1
5
Click OK.
Reviewing or adding comments to a software request
You can review a software request to check its status or to view the actions that
have been taken.
221
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
See “Statuses of software requests in the Software Portal” on page 200.
Comments provide a means to communicate information about software requests.
Users can add comments to justify their need for software or to provide details
about the unlisted software that they request. Managers can add comments to
explain the status that they assign to the request or to request additional information
from the user.
You cannot add comments to a request that is closed.
To review or add comments to a software request
1
To open the Software Portal, do one of the following:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
■
On the Start menu, click Programs > Symantec > Symantec Software
Portal
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
Note: The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
2
3
Depending on your role, do either of the following:
■
If you are a user, click Home.
■
If you are a manager and you need to add a comment to a user’s request,
click Manage.
Under Request Status, double-click the request.
(Manager Portal page only) Use the search feature to find the request if
necessary.
See “Finding and filtering software requests” on page 214.
4
In the Request Details dialog box, do either of the following:
■
Enter comments.
■
To review the request’s comments and actions, expand the Request History
section.
This dialog box displays the details about a software request. It lets you add
comments to a request and check the request history. The Request History
section lists all the comments and actions that are associated with the request.
222
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
Users can use this dialog box to review and add comments to their existing
requests.
See “Reviewing or adding comments to a software request” on page 221.
Managers can use this dialog box to review, add comments to, and process a
software request.
See “Processing a software request” on page 224.
5
Click OK.
Canceling a software request
You can cancel the requests that you create in case you request the wrong software
or you find that you no longer need the software.
You cannot cancel a request that is closed.
See “Requesting software in the Software Portal” on page 220.
See “Statuses of software requests in the Software Portal” on page 200.
To cancel a software request
1
To open the Software Portal, do one of the following:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
■
On the Start menu, click Programs > Symantec > Symantec Software
Portal
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
Note: The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
2
Click Home.
3
Under Request Status, select the request.
Use the search feature to find the request if necessary.
4
Click Cancel Request and click OK
223
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
Processing a software request
If the software is not pre-approved for the user who requests it, the manager must
review the request and decide what action to take. To process a software request,
the manager changes its status.
The request statuses that you can set are as follows:
■
Approve
■
On Hold
■
Deny
See “Statuses of software requests in the Software Portal” on page 200.
The Manager Portal page is available only to the users who have permission to
approve and deny software requests.
To process a software request
1
To open the Software Portal, do one of the following:
■
Double-click the Symantec Software Portal shortcut on your Desktop.
■
On the Start menu, click Programs > Symantec > Symantec Software
Portal
■
Right-click the Symantec Management Agent icon in the notification area
and then click Software Portal.
Note: The Software Portal might not be available from all these places on your
computer. Which option is available depends on the settings you chose in the
Software Portal installation policy.
2
Click Manage.
3
On the Manager Portal page, under Requested Software, select the software
request.
Only the requests that require your attention are displayed. Use the search
feature to find and display other requests if necessary.
See “Finding and filtering software requests” on page 214.
4
Do one of the following:
■
To open the request for review, comments, or a status change, click Edit.
■
To quickly change the status without opening the request, click Change
Status and on the Change Status menu, select the status.
224
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
5
6
If you opened the software request, on the Request Details dialog box, do
any of the following:
■
Change the status.
■
Check Assign request to the Software Portal Administrator.
This check box is available only when you approve a request for unlisted
software. For example, if you cannot provide the software yourself, approve
the request and pass it to the administrator.
■
Enter comments to explain why you changed the status or to request
additional information.
Comments are required whenever you change the status.
■
To review the request’s comments and actions, expand the Request History
section.
To close the Request Details dialog box, click OK.
Installing approved software
When your software request is approved, the software is delivered to and installed
on your computer. In most cases, the software is installed automatically.
(Windows only) Your administrator might configure the software delivery to require
you to initiate the software installation. In that case, you initiate the installation from
the Symantec Management Agent that is installed on your computer.
To install approved software
1
Open the Symantec Management Agent in one of the following ways:
■
On the Start menu, click Programs > Symantec > Symantec Management
Agent.
■
Right-click the Symantec Management Agent icon in the notification area
and then click Symantec Management Agent.
■
Run the following command:
installation path\Altiris\Altiris Agent\AeXAgentActivate.exe
2
In the Symantec Management Agent window, click the Software Delivery
tab.
On the Software Delivery tab, under Deliveries available for this computer,
click the software to install.
3
In the left pane, under Application Tasks, click the task to install the selected
software.
225
Delivering software from user requests using the Software Portal
Using the Software Portal on the client computer
For more information, see the topics about the Software Delivery page in the
Symantec Management Agent User Interface Help.
You can open the Symantec Management Agent User Interface Help when you
click Help in the upper right of the Symantec Management Agent window.
226
Index
Symbols
C
6.x software delivery
delivering 162
Legacy Software Delivery 162
reports 158
6.x software package
Legacy Software Delivery 162
catalog, software. See Software Catalog
clean up file resources
running 42
scheduling 41
CMDB
Software Catalog 30
command line
creating 81
software virtualization 133
comments, software request 221
compliance check
about 176
how it works 175
reports 158
returns delivery status 182
components
Software Management Framework 18
Software Management Solution 18
computer, delivery destination. See destination,
delivery
configuration item 30, 49
Configuration Management Database. See CMDB
context-sensitive help 25
creating
managed software delivery policy 184
A
activate virtual software 133
administrator, Software Portal
about 211
privileges 213
responsibilities 211
advanced software delivery. See Managed Software
Delivery
agent. See plug-in
Software Virtualization 134
applicability check
about 176
process 175
applicability rule 84
See also rule
about 84
application
installing from user requests 225
requesting in Software Portal 220
application management
reports 158
Application Management agent
customizing 122
software resource 123
approval, software request
about 214
granting 214, 224
requirements 214
approved software
about 199
approving 214
associations, software
adding 88
D
data layer 128
See also virtual software
about 128
data provider
adding 106
configuring precedence settings 109
connecting to 106
gathering available software resources 113
import process 107
importing from
manually 112
with a schedule 110
non-registered 104
Index
data provider (continued)
precedence settings 109
registered 104
security role requirements 107
selecting specific software resources 113
Data Providers
Web part 20
data providers
about 103
deactivate virtual software 133
deferral
software delivery 178
software installation 180
Definitive Software Library. See DSL
delete virtual software 133
deliverable software
about 50
delivery, software. See software delivery
destination, delivery
Managed Software Delivery 188
software task 156
detailed export, software resource 90
detection rule 84
See also rule
about 84
documentation 25
drag and drop
installing software 101
DSL
Software Library 33
duplicate software resources
about 60
merging 60
resolving 60
E
emergency policy update
performing 192
end user. See users, Software Portal
error code, installation
adding 42
exclude entry
global 130
layer 130
extensible package format
about 127
creation methods 127
delivering 127
F
file resource
about 89
adding to software resource 89
cleaning up 42
discovering on clients 54
purging 42
filter
creating installed software 61
installed software. See filter, installed software
filter driver
software virtualization 126
filter, installed software
about 61
creating 61
fslrdr 125
G
global exclude entry 130
H
help
context-sensitive 25
I
implementation
Software Management Framework 36
Software Management Solution 63
Software Portal 205
import virtual software 133
installation error code description
adding 42
installed software filter
about 61
creating 61
installing
Software management solution plug-in 65
inventory rule
creating 83
editing 83
K
known-as association
about 43
editing 45
wildcard, defining 43
228
Index
L
layer exclude entry 130
Legacy Software Delivery
accessing 163
delivering packages 162
legacy software package
adding to a package assignment task 170
assigning multiple packages to software
resources 168
editing 171
library, software. See Software Library
Linux 14, 16, 51
See also UNIX, Linux, and Mac
software delivery 145
support in Software Management Framework 14,
51
support in Software Management Solution 16
listed software
about 199
delivery 204
M
Mac 14, 16, 51
See also UNIX, Linux, and Mac
software delivery 145
support in Software Management Framework 14,
51
support in Software Management Solution 16
managed software 34
Managed Software Delivery
about 172–173
adding to Software Portal 209
compliance. See compliance check
delivery deferral 178
destination 188
editing policy 186
execution process 174
offline execution 180
policy creation 183–184
policy view 182
process for performing 189
publishing. See publish software
remediation. See remediation, software
replacing software 181
software request 204
status 182
supersedence 181
virtual software. See virtual software
wizard 183
managed software delivery policy
creating 184
manager, Software Portal
about 212
privileges 213
responsibilities 212
meta data, software resource 49
metadata
importing from a data provider 103, 107
types imported from a data provider 104
migrated package
adding to a package assignment task 170
editing 171
migrated software package
assigning multiple packages to software
resources 168
assigning to a software resource 165, 168
O
offline execution of software delivery 180
options, Software Management Solution. See settings,
Software Management Solution
P
package assignment task
adding 6.x packages to 170
Package Delivery
creating 153
editing 155
process 160
scheduling 156
virtual software
installing 140
managing 140
package download
Managed Software Delivery 175
package file
import to software resource
importing 51
package source
changing 80
Software Library 80
package, software
about 78
adding to Software Library 80
associating with software resource 78
delivering 160
source. See package source
229
Index
performing
emergency policy update 192
platform support, Software Management
Framework 14
platform support, Software Management Solution 16
plug-in
Software Portal. See Software Portal plug-in
policy
emergency update status reports 194
user-based, software delivery 188
portal
Software Portal. See Software Portal
precedence settings
configuring 109
data provider 109
examples of how they work 110
privileges
Software Portal 211
publish software
about 199
Managed Software Delivery policy 209
software resource 207
Q
Quick Delivery
about 149
creating 152–153
editing 155
process 149
scheduling 156
software request 204
virtual software
installing 140
managing 140
wizard
creating tasks 152
R
recommended security privileges
Software management solution 69
recommended software 199
recurring source path update 118
recurring Windows Installer repair 122
redirection area 125
Release Notes 25
remediation, software
about 176
deferring 180
remediation, software (continued)
how it works 176
repair applications. See Windows Installer repair
replace software on clients 181
report
emergency update status reports 194
reports, software
6.x software delivery 158
about 158
application management 158
compliance check 158
limiting access to data 158
running 157
scoping 158
software delivery 158
Software Portal 158
virtual software 136, 158
request, software. See software request
reset virtual software 134
resilient source paths
about 115
creating 115
resolve duplicate software resources 60
resource scoping
software reports 158
rule 84
See also inventory rule
applicability 84
detection 84
rule, inventory. See inventory rule
S
saved search
deleting 100
hiding 100
modifying 100
scoping resources. See resource scoping
security
Software Library 38
Software Management Framework 37
Software Management Solution 65
security role
data provider requirements 107
Software Portal privileges 211
software-related 32
sequential software delivery
delivering 190
server timeout
setting timeout value 40
230
Index
settings, Managed Software Delivery
defaults 71
settings, Software Management Solution
default 72
Managed Software Delivery. See settings,
Managed Software Delivery
task. See task options, Software Management
Solution
settings, Software Portal 209
smart rule
about 84
software 199
See also approved software
See also recommended software
adding to Software Portal. See publish software
discovering on clients 54
finding 97
installing 101
installing from user requests 225
listed. See listed software
requesting in Software Portal 220
search, advanced 97
uninstalling from clients 148
unlisted. See unlisted software
Software Catalog
about 30
accessing 96
actions you can perform 94
as CMDB 30
benefits 31
default entries 46
integration with Software Management
Solution 16
population methods 46
software delivery 14, 149, 172–173
See also Managed Software Delivery
See also Quick Delivery
See also Software Management Solution
about 145
advanced 172–173
deferral options for users 178
methods 145
remediation deferral 180
replacing software 181
reports 158
sequential. See sequential software delivery
Software Portal 204
UNIX, Linux, Mac 145
Software Discovery
about 54
process 54
running 57
scheduling 57
settings 57
tasks 57
Software Finder 20, 97
Software Library
about 33
as DSL 33
benefits 35
best practices 38
configuring 39
disk space 39
integration with Software Management
Solution 16
security 38
setting up 38
Software Management Framework
about 13
components 18
implementing 36
integration with Software Management
Solution 16
key tasks 22
platform support 14
Software Management Solution 72, 158, 197
See also reports, software
See also settings, Software Management Solution
See also Software Portal
about 14
components 18
implementing 63
integration, Software Catalog 16
integration, Software Library 16
integration, Software Management Framework 16
key tasks 23
platform support 16
task. See task, Software Management Solution
Software management solution
recommended security privileges 69
Software management solution plug-in
installing 65
upgrading 65
software package. See package, software
adding to a package assignment task 170
assigning multiple packages to software
resources 168
231
Index
software package (continued)
assigning to a software resource 165, 168
editing 6.x packages 171
importing from a data provider 103, 107
see package, software 160
Software Portal 197
See also software request
about 197
adding software. See publish software
implementing 205
key tasks 198
not opening properly 218
opening 217
privileges 211
process flow 202
publishing. See publish software
reports 158
settings 209
software 198
user profile 218
users. See users, Software Portal
work flow 202
Software Portal administrator. See administrator,
Software Portal
Software Portal manager. See manager, Software
Portal
Software Portal plug-in
installing 68
software reports. See reports, software
running 157
software request 199
See also approved software
approval. See approval, software request
approvers 214
canceling 223
closed 201
comments, adding 221, 223
creating 220
delivery methods 204
denied 201
finding 214, 219
history, viewing 221
listed. See listed software
Managed Software Delivery 204
on hold 201
open 201
process flow 202
processing 214, 224
Quick Delivery 204
software request (continued)
reviewing 214, 224
scheduled 201
status. See status, software request
submitted 201
unlisted. See unlisted software
work flow 202
software resource
about 49
adding 75
as configuration item 30, 49
assigning an 6.x package to 164
assigning multiple 6.x packages to 166
command line. See command line
creation methods 46
deleting 77
deliverable 50
duplicates
about 60
resolving 60
editing 75
exporting details to XML 90
import from package file
importing 51
managed 34
meta data 49
minimum data requirement 50
package. See package, software
predefined 46
publishing. See publish software
unassigned 59
unique identifier 53
unmanaged 34
software resource type
assigning 59
unassigned 59
software search
saving 99
Software view
actions you can perform 94
software virtualization
about 125
command lines 133
data layer 128
during installation 136
filter driver 126
methods 130
redirection area 125
task. See Software Virtualization task
232
Index
Software Virtualization agent. See Symantec
Workspace Virtualization Agent
Software Virtualization task 125
See also virtual software
creating 153
editing 155
process 138
scheduling 156
source path update 115
See also resilient source paths
about 115
customizing 122
policy. See Source Path Update policy
process 115
task. See Source Path Update task
Source Path Update policy
about 116
configuring 117
Source Path Update task
about 116
creating 153
editing 155
scheduling 156
source, package. See package source
standard rule
about 84
status, Software Management Solution
Managed Software Delivery 182
status, software request
about 200
approved. See approval, software request
canceled 201
changing 214, 224
closed 201
denied 201
on hold 201
open 201
scheduled 201
submitted 201
viewing 221
supersedence association
software delivery 181
SVS. See software virtualization
SVS agent. See Symantec Workspace Virtualization
Agent
Symantec Workspace Virtualization Agent
installing 134
T
task options, Software Management Solution
about 72
task settings, Software Management Solution. See
task options, Software Management Solution
task, Quick Delivery. See Quick Delivery
task, Software Management Solution
about 154
creating 153
editing 155
options. See task options, Software Management
Solution
scheduling 156
selecting computers 156
settings, default 72
types 154
type, software resource
assigning 59
unassigned 59
U
uninstall software from clients 148
unique identifier
software resource 53
UNIX 16
See also UNIX, Linux, and Mac
software delivery 145
support in Software Management Solution 16
UNIX, Linux, and Mac
support in Software Management Framework 14,
51
support in Software Management Solution 16
unlisted software
about 199
delivering 217
delivery 205
unmanaged software 34
upgrading
Software management solution plug-in 65
user profile, Software Portal 218
user-based policy
software delivery 188
users, Software Portal
about 211
administrator. See administrator, Software Portal
manager. See manager, Software Portal
privileges 211
profile 218
responsibilities 211
233
Index
users, Software Portal (continued)
user, client 212
V
virtual application. See virtual software
virtual package
about 127
creation methods 127
delivering 127
virtual software 125, 128, 138
See also software virtualization
See also Software Virtualization task
about 125
applications to virtualize 127
creating during installation 136
creation methods 130
guidelines for creating 127
installing. See virtual software installation
layer. See virtual software layer
managing. See virtual software management
reports 136, 158
virtualization restrictions 127
virtual software archive
about 127
creation methods 127
delivering 127
virtual software installation
about 126
Managed Software Delivery 141
methods 131
Package Delivery 140
Quick Delivery 140
Software Virtualization task 138
virtual software layer 125
See also software virtualization
See also virtual software
about 125
actions 133
activating 133
creating during installation 136
creation methods 130
deactivating 133
deleting 133
importing 133
resetting 134
set active on startup 134
set not active on startup 134
uninstalling 148
virtual software management
about 126
actions 133
Managed Software Delivery 141
methods 131
Package Delivery 140
process 135
Quick Delivery 140
Software Virtualization task 138
VSA 127
See also virtual software archive
W
Web part
Data Providers 19
Software Finder 19
Web parts
Software Management Framework 19
Software Management Solution 20
wildcard, known-as. See known-as association
Windows Installer applications
repairing 119
source path update 115
Windows Installer repair
about 119
customizing 122
Managed Software Delivery 119
policy 120
process 119
scheduling 156
task
creating 153
editing 155
X
XPF 127
See also extensible package format
234
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement