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:
  • 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.
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.
  1. To associate a package with a software resource
  2. In the
    Symantec Management Console
    , on the
    Manage
    menu, click
    Software
    .
  3. In the left pane, click
    All Software > All Software Components
    , and then double-click the software resource.
  4. On the software resource page, click the
    Package
    tab.
  5. On the
    Package
    tab, click
    Add package
    .
  6. In the
    Add or Edit Package
    dialog box, enter the package details and assign the package to package servers.
    To specify a folder with a structure, add the folder as a compressed ZIP file.
    When you add the ZIP file, you need to decide whether to extract the archived content. If you choose to extract the content, you can edit it according to your needs and create subfolders after extracting. If you choose to add the content without extracting, you can only view the content.
  7. On the software resource page, click
    OK
    .