1. Manuals
  2. Brands
  3. Symantec Manuals
  4. Software
  5. SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO...
  6. Installation manual

Symantec SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Software Manager Reference

Advertisement

Table of Contents
loading

Related Manuals for Symantec SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0

Summary of Contents for Symantec SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0

  • Page 1 Software Manager Reference...

  • Page 2: Legal Notice

    Copyright © 2010 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris 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.

  • Page 3: Technical Support

    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 web site 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.

  • Page 4: Customer Service

    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/...
  • Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.

  • Page 6: Table Of Contents

    Contents Technical Support ............3 Chapter 1: Introduction to Software Manager .
  • Page 7 Generating a Software Manager Report ........47 Using the Report Viewer .

  • Page 8: Chapter 1: Introduction To Software Manager

    Chapter 1 Introduction to Software Manager This chapter includes the following topics: About Software Manager on page 8 Starting Software Manager on page 9 About the Software Manager Window on page 10 Icons in Software Manager on page 12 About the Wise Software Repository on page 14 About the Software Manager Database on page 15...

  • Page 9: Package Management With Software Manager

    Introduction to Software Manager Adding Packages to the Software Manager Database For packages to be managed, they must be in the Software Manager database. To get packages into the database, you can do any of the following: Add the package’s meta data in Windows Installer Editor. Import the package and its resources in Software Manager.

  • Page 10: About The Software Manager Window

    Introduction to Software Manager Software Manager opens. Which Database is Opened? The first time you start Software Manager, it opens the database that you connected to during installation. Thereafter, Software Manager opens the database most recently used. See also: About the Software Manager Window on page 10 About the Software Manager Window When you start Software Manager, the main Software Manager window appears.

  • Page 11: Customizing The Software Manager Workspace

    Introduction to Software Manager Groups Pane Displays the package groups defined for each database. A package group consists of a subset of the applications in the database. When a group is selected, the Applications/ Packages pane lists only the packages assigned to that group. This lets you reduce the number of packages you view at one time.

  • Page 12: Icons In Software Manager

    Introduction to Software Manager This rereads the package data and redisplays package information. This can be useful if packages have been added to the Software Manager database since you started this Software Manager session. Icons in Software Manager The following icons appear in Software Manager to help you quickly identify items in the database.

  • Page 13: Resource Icons

    Introduction to Software Manager Resource Icons The following icons appear in the Package Details pane in Software Manager. They indicate the types of resources that are installed by a package. Icon Resource Type File or Windows Installer component. Registry key or named value. Modification to Autoexec.bat.

  • Page 14: About The Wise Software Repository

    Introduction to Software Manager Icon Dependency relationship Association relationship Required. None. The dependency must precede the dependent package during installation. Required. Required. The dependency must precede the The dependent package must be dependent package during installed with the dependency. installation. Required.

  • Page 15: About The Software Manager Database

    Introduction to Software Manager Share Point Directory Contains shared resources used to create Windows Installer installations. It also contains source files for packages in the Software Manager database. All Wise Software Repository databases are associated with a specific share point directory. See About the Share Point Directory in the Windows Installer Editor Help.

  • Page 16: How Source Files Are Indexed

    Introduction to Software Manager See also: About the Wise Software Repository on page 14 Sharing the Software Manager Database With Wise Package Studio on page 16 How Source Files Are Indexed A sequentially-numbered directory structure is created under the share point directory to store occurrences of installation source files when: You distribute a package to the share point directory.

  • Page 17: About Applications And Packages

    Introduction to Software Manager repackage internally developed applications and lets them focus on other activities. It also assures the deployment team that applications will perform as expected and reduces calls to the help desk. Process for Sharing the Software Manager Database During development, the developer imports a new application to the shared Software Manager database.

  • Page 18: About Package Meta Data

    Introduction to Software Manager When you import the application/package names are obtained from: from the share point the application and package names that were directory specified during Package Distribution. If the application and package names were not specified during distribution, they are assigned as described below.

  • Page 19: Defining Custom Meta Data Fields

    Introduction to Software Manager Kinds of Meta Data You define and enter custom meta data in Software Manager. Predefined meta data is created when you create the package in Windows Installer Editor. See Adding Meta Data to the Software Manager Database in the Windows Installer Editor Help.
  • Page 20 Introduction to Software Manager The Meta Data Fields dialog box appears. Click Add. In Field Name, enter text to describe this meta data field and press Tab. From Data Type, select the kind of data this field will accept. Note If you change the data type for a field that is in use, the data associated with that field is deleted from all packages.

  • Page 21: Defining A Custom Meta Data Type

    Introduction to Software Manager Defining a Custom Meta Data Type When a meta data field requires the user to select from a set of predefined values, you define a custom data type and specify valid values. Example: If you add a meta data field to specify the type of license model the software uses, you might add a custom data type that contains these values: per seat;...

  • Page 22: Online Help

    The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. To access the release notes, select Release Notes from the Symantec program group on the Windows Start menu. Software Manager Reference...

  • Page 23: Chapter 2: Importing Packages

    Chapter 2 Importing Packages This chapter includes the following topics: About Importing Packages on page 23 How to Get Packages Into the Software Manager Database on page 23 Package Import on page 25 About Importing Packages Software Manager lets you import packages and their resource information into the Software Manager database.

  • Page 24: About Formatted Text Strings In Registry Entries

    Importing Packages See Adding Meta Data to the Software Manager Database in the Windows Installer Editor Help. Importing Package Resources When you use the Import Wizard in Software Manager: If the package is not already in the Software Manager database, it is added along with its meta data.

  • Page 25: Package Import

    Importing Packages WiseScript variable Resolves to %Common% Program Files\Common %fonts% Windows\Fonts %MainDir% Program Files\default maindir or, if default maindir is empty: Program Files %Program_Files% Program Files %Sys% Windows\System %Sys32% Windows\System32 %Win% Windows When the package resource appears in Software Manager and ConflictManager, the resolved value is displayed instead of the formatted text string.

  • Page 26: About Patch And Transform Import

    Easily deploy patches and transforms with distribution systems. If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the patch or transform from the Software Manager database into Software Management Framework.

  • Page 27: Importing From The Share Point Directory

    Importing Packages included in the imported patch or transform package and changes how it behaves when it is installed. Example: Suppose that two different transforms can be applied to a base package. The Base Package installs File A, File B, and File C. Transform 1 deletes File C.
  • Page 28 Importing Packages Select Packages menu > Import. The Import Type page appears. Mark Import from share point directory. Distribute source files to the share point directory is marked automatically and unavailable. It is unavailable because the source files were copied when the package was distributed to the share point.

  • Page 29: About .Que Files

    23. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the Windows Installer file from the Software Manager database into Software Management Framework. You can then use Software Management Solution to distribute the package.
  • Page 30 Importing Packages Distribute source files to the share point directory Mark this to copy all source files to a single, centralized location. Clear this check box to import the package description into the Software Manager database without copying its source files to the share point directory. Warning Distributing source files for a package that represents a Visual Studio integrated project breaks the integration with the Visual Studio solution.

  • Page 31: Importing A Merge Module File

    Importing Packages Package Name Enter a unique name to identify this package. Typically, you use the application name plus specific version information. Example: If the application name is Adobe Acrobat Reader, the package name might be Acrobat Reader 5.05. To replace an existing package, select a package from the drop-down list. Use Transactions for Import Mark this check box to import installation resources as database transactions instead of importing them individually.
  • Page 32 Importing Packages Manage and use the shared resources in merge modules. Add merge modules from the Software Manager database to installations in Windows Installer Editor, if you mark Read Merge Modules List from Wise Software Repository in Wise Options. To import a merge module file If multiple databases are open, select a database in the Applications/Packages pane.

  • Page 33: Importing A Transform File

    42. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the transform from the Software Manager database into Software Management Framework. Wise Connector imports the transform when it imports the base MSI package.
  • Page 34 Importing Packages If the transform contains file additions that are in components of the base installation, those files are not imported with the stand-alone transform package because they only apply to the specific base installation. Example: Suppose the base package contains Component A. The transform adds File 1 to Component A, and adds File 2 to a new Component B.
  • Page 35 Importing Packages If the existing package does not have resources, the new package’s resources are added to the existing package. To assign the imported package to one or more groups: Click Groups on the Import Type page. The Select Groups dialog box appears. Mark the check boxes of the groups to assign the package to.

  • Page 36: Importing A Windows Installer Patch File

    29. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the patch from the Software Manager database into Software Management Framework. Wise Connector imports the patch when it imports the base MSI package.
  • Page 37 Importing Packages To import a Windows Installer patch file Verify that the base package that the patch applies to is in the Software Manager database. If multiple databases are open, select a database in the Applications/Packages pane. Select Packages menu > Import. The Import Type page appears.

  • Page 38: Importing Multiple Files

    Importing Packages Package Name Enter a unique name to identify this package. To replace an existing package, select a package from the drop-down list. 10. Click Next on the Package Details page. The Select Target Package page appears, where you set dependencies for this package.
  • Page 39 Importing Packages Windows Installer installation (.MSI, .WSI) Merge Module (.MSM, .WSM) Note In general, do not import a package from a CD. If you do, you will not be able to export the package after resolving its conflicts, because you will not have access to its source files and you cannot write to a CD.
  • Page 40 Importing Packages Click OK. Click Next on the Import Type page. The Select Package Type page appears, containing options for the types of files you can import. Mark the option for the type of file to import and click Next. The Package Search page appears.

  • Page 41: Chapter 3: Managing Packages

    Chapter 3 Managing Packages This chapter includes the following topics: Package Groups on page 41 Viewing and Editing Package Attributes on page 45 Viewing Resource Properties on page 46 Software Manager Reports on page 46 Moving a Package to Another Application on page 47 Deleting a Package on page 48...

  • Page 42: Creating Package Groups

    Managing Packages Deploy multiple related packages at once, enforcing package dependencies and installation order, and defining command lines that run the package installations. Example: Group a package with its related transforms and patches, specify the order in which the transforms and patches are applied, and define the command lines that are needed to run the transforms.

  • Page 43: Selecting Superseding Packages

    Managing Packages No inheritance from parent or child When you assign a package to a group, the package stays within that group; it is not shared with other groups. Inherit from parent groups When you assign a package to a group, that package is also assigned to that group’s child groups.

  • Page 44: Adding Applications And Packages To Groups

    Managing Packages To select a superseding package Access the Superseding Packages dialog box. On the Edit Groups dialog box, add a package that has a supersedence relationship or click the Check Supersedence button. Creating Package Groups on page 42. On the Superseding Packages dialog box, the packages in the group are at the top level of the tree.

  • Page 45: Viewing And Editing Package Attributes

    Managing Packages Use the Move buttons to move packages back and forth between the Packages in Group and Packages not in Group lists. Select a different parent group from Parent. Delete the group by clicking Delete Group. Change the package inheritance by making a new selection in Inheritance. This affects all groups, not just the one you are editing.

  • Page 46: Viewing Resource Properties

    Managing Packages Defining Custom Meta Data Fields on page 19. Click the Source tab and view or edit the following information. Installation File Edit to change the location of the package installation file. You might need to do this if the server is renamed or reorganized. Note Selecting a new file location here does not move the installation file or its source files.

  • Page 47: Generating A Software Manager Report

    Managing Packages Report Name Reports Menu What This Report Does Command Package Contents Package Contents > Lists detailed information for every resource in an Summary Summary installation, including files, registry keys, shortcuts, file associations, and merge modules. You can generate this report for .WSI, .MSI, .WSM, and .MSM files.

  • Page 48: Deleting A Package

    Managing Packages To move a package to another application If multiple databases are open, select a database in the Applications/Packages pane. In the Applications/Packages pane, click the package to move. Select Packages menu > Attributes. The Package Attributes dialog box appears. In Application, enter the name of the application where you want to move the package.

  • Page 49: Changing The Package Status

    Managing Packages Warning If you delete a package’s source files, you will never be able to recompile that package because the source paths in the installation will refer to files that no longer exist. Delete source files only when you are sure you will not need to compile the package again.
  • Page 50 Managing Packages limited cases, you need to ensure that new applications don’t break the legacy application. To change to a different status, select it from Package Status. Software Manager Reference...

  • Page 51: Chapter 4: Software Manager Database Maintenance

    Chapter 4 Software Manager Database Maintenance This chapter includes the following topics: About Software Manager Database Maintenance on page 51 Changing the Server Path on page 51 Deleting a Server Path on page 53 Restructuring the Index on page 53 Rebuilding the Index on page 54 About Software Manager Database Maintenance...
  • Page 52 Software Manager Database Maintenance as the share point directory. However, you can add new server paths. You might do this if you distribute a large number of packages to the share point directory, and the drive containing the share point directory becomes full. When that happens, you can create a new directory on another network drive and set the new location as the active server path.

  • Page 53: Deleting A Server Path

    Software Manager Database Maintenance Deleting a Server Path You can delete a Software Manager server path, but only if you have not yet added data to it. Do this if you add a new server path in the Network Index Properties dialog box, then realize that you mis-typed the name or selected the wrong path.

  • Page 54: Rebuilding The Index

    Software Manager Database Maintenance To restructure the index Select Setup menu > Network Index Properties. The Network Index Properties dialog box appears. In the Rebuild Index Settings section: Location Leave this field blank. Block Size To increase the block size, select a higher number. Hash Table Size To increase the hash table size, enter a higher number.
  • Page 55 Software Manager Database Maintenance Rebuild using file/directory structure When you mark this, the rebuild process reads all files and directories in the share point directory and all its server paths in the Storage Paths list. This method is recommended because it gathers all possible data from the Software Manager database.

  • Page 56: Index

    Index Numerics manual, reference 22 merge module 000 directory 16 Getting Started Guide 22 importing 31 group, package importing multiples 39 about 41 resouces 9 adding packages 44 application meta data creating 42 about 17 about 18 editing 44 adding to group 44 adding to database 23 inheriting package 42, 42 naming 17...
  • Page 57 Package Contents reports 47 changing 51 Wise Software Repository deleting 53 about 14 Package Contents Summary report 47 share point directory Wise Software Repository database Package Details pane 11 importing from 27 See Software Manager database package import Scripts subdirectory 29 Workbench database See import temporary file 29...

This manual is also suitable for:

Software manager

Table of Contents