Page 1 Software Manager Reference...
Page 2: Legal Notice
Copyright © 2009 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
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.
Page 4: Customer Service
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/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following types of issues:...
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 Importing an SOE Snapshot..........64 Importing a Wise Package Definition File .
Page 8 Process for Deploying a Group ..........112 About Package Definition.
Page 9: Chapter 1: Introduction To Software Manager
Chapter 1 Introduction to Software Manager This chapter includes the following topics: About Software Manager on page 9 Starting Software Manager on page 12 About the Software Manager Window on page 13 Icons in Software Manager on page 16 About the Software Manager Database on page 19 About Applications and Packages on page 22...
Page 10: Package Management With Software Manager
Introduction to Software Manager Meta data. This is the is minimum amount of information that constitutes a package. The resources associated with each package’s installation. The installation file. A command line for running the installation when it is installed. Additional files that should be deployed with the installation (example: an informational text file).
Page 11 Introduction to Software Manager View Package Resources Use the panes in Software Manager to drill down to the resources (examples: files, registry keys, merge modules, shortcuts, and so on) that are used by each package. About the Software Manager Window on page 13 and Viewing Resource Properties...
Page 12: Starting Software Manager
Introduction to Software Manager Use Group Distribution to deploy multiple related packages at once, enforcing package dependencies and installation order, and defining command lines that run the package installations. Group Distribution on page 130. Starting Software Manager In Wise Package Studio, do one of the following: On the Projects tab, click the Run link to the right of the task or tool associated with Software Manager.
Page 13: About The Software Manager Window
Introduction to Software Manager All Software Manager activities are performed within the active database. To close a database Select File menu > Close Database. The Close Database dialog box appears. Mark the check box next to the database or databases to close and click OK. See also: About the Software Manager Database on page 19...
Page 14 Introduction to Software Manager pane. This pane also displays information about the packages in the current database, and shows the current filter criteria. The Database pane initially appears immediately below the toolbar, but you can move or hide it. Groups Pane Displays the package groups defined for each database.
Page 15: Customizing The Software Manager Workspace
Introduction to Software Manager Viewing Resource Properties on page 94. Customizing the Software Manager Workspace Hide or show the toolbar or one of the panes by selecting its name from the View menu. Move, dock, and undock the panes as you would any Windows pane, by dragging their title area.
Page 16: Refreshing The Software Manager Display
Introduction to Software Manager Refreshing the Software Manager Display Select File menu > Refresh. 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.
Page 17: Resource Icons
Introduction to Software Manager Conflict Icons on page 17 About the Software Manager Window on page 13 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. The icons also appear in the Conflict List and Conflict Details panes in ConflictManager, where they indicate resources that have conflicts.
Page 18: Relationship Icons
Introduction to Software Manager Icon Conflict Type Represents Warning Conflicts that are not critical but might require some attention. Error More serious conflicts that deserve careful inspection. Information When multiple packages install a non-16-bit file with identical file information to the same directory or to different directories.
Page 19: About The Software Manager Database
Introduction to Software Manager Icon Dependency relationship Association relationship Optional. None. Installing the dependency package is optional. If it is installed, it must precede the dependent package. Optional. Required. Installing the dependency package The dependent package must be is optional. If it is installed, it must installed with the dependency.
Page 20: Software Manager In A Multi-User Environment
Introduction to Software Manager If your organization has multiple, decentralized departments, each using a different set of packages, you can use a separate database for each department. This concept is similar to using package groups, but on a larger scale. Each database should reside on its own server.
Page 21: Sharing The Software Manager Database With Corporate Developers
Introduction to Software Manager Multiple users can resolve conflicts in ConflictManager, provided each user resolves conflicts for a different package. Typically, each user is assigned to work on a specific package or packages. Your corporate standards should specify whether a user can update a package that is assigned to someone else.
Page 22: About Applications And Packages
Introduction to Software Manager Note Because applications that are still in development will be mixed with those that have been tested and deployed, members of the deployment team must be careful not to deploy applications that are still in development. See also: Installation Resources and Their Locations in the Windows Installer Editor Help About Applications and Packages...
Page 23 Introduction to Software Manager When you import the application/package names are obtained from: multiple Windows the file name. Example: If you import Sample.msi, the Installer installations application name and package name will both be that do not have a Sample. product name and version, or multiple WiseScript...
Page 24: Setting Software Manager Preferences
Introduction to Software Manager Package name: Describe the transform. Example: If the base installation’s application name is Sample, and the transform changes the language of the installation dialog boxes to French, name the transform package Sample_French. Setting Software Manager Preferences Software Manager preferences let you specify the .MSI tables that are included when you import a Windows Installer package into the Software Manager database.
Page 25: About Package Meta Data
Introduction to Software Manager Both the top level and the table check boxes in the second level must be marked or the tables will not be imported. When you mark a second-level check box, its parent is marked as well. When you clear a parent check box, its second-level check boxes are cleared.
Page 26: Defining Custom Meta Data Fields
Introduction to Software Manager How many licenses are purchased, in use, and available. The language of the application. Links to the purchasing department, such as purchase order number or URL to the purchasing system. Package description. Packager comments about limitations of the package. Path to original source files.
Page 27: Defining A Custom Meta Data Type
Introduction to Software Manager True/False Yes/No Any custom data types that you have defined are also listed. You typically define a custom data type when a meta data field requires the user to select from a set of predefined values. To define a custom data type, click Custom Data Types. Defining a Custom Meta Data Type on page 27.
Page 28: Scheduling Software Manager Tasks
Introduction to Software Manager Continue adding values as needed. To rearrange the order, click Move Up or Move Down. The values will appear in this order in a drop-down list on the Package Attributes dialog box and on the Product Details page in Windows Installer Editor. When you finish adding custom data types, click OK.
Page 29 Region2 server: Region2, Region1, Central. To schedule Software Manager tasks Log on to the server. Select Start menu > Programs > Symantec > Wise Package Studio > Wise Task Scheduler. The Wise Task Scheduler dialog box appears. From Task, select an option:...
Page 30: Wise Software Repository Automation
Introduction to Software Manager To save the changes, click OK. The new or updated task is displayed on the Wise Task Scheduler dialog box. When you finish adding or updating tasks, click OK. See also: About the Auto Import Service on page 74 Refreshing Package Subscriptions on page 77...
Page 31: Release Notes
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 32: Chapter 2: Importing Packages
Chapter 2 Importing Packages This chapter includes the following topics: About Importing Packages on page 32 How to Get Packages Into the Software Manager Database on page 32 About Formatted Text Strings in Registry Entries on page 34 Package Import on page 34 Package Subscription on page 74...
Page 33 Importing Packages See Adding Meta Data to the Software Manager Database in the Windows Installer Editor Help. Importing a Package Definition When you use the Package Definition tool in Workbench to create a package, and you mark the Import into Software Manager check box: A record for the package is created in the Software Manager database.
Page 34: About Formatted Text Strings In Registry Entries
Importing Packages About Formatted Text Strings in Registry Entries Registry entries in Windows Installer and WiseScript packages can use formatted text strings that, when evaluated literally, might lead to false positives during conflict detection. To avoid this problem, Software Manager resolves the formatted text strings during import of the following types of packages: .WSI, .MSI, .MSM, .MSP, .MST, .WSE.
Page 35: Import Methods
Importing Packages Add the package to Revision Control. Revision Control on page 80. Perform the operation on the Wise Package Studio server. If you are working on a client computer, you can perform the import on the Wise Package Studio server. You must use a UNC path to specify the imported package. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages.
Page 36: About Patch And Transform Import
Importing Packages Importing a Merge Module File on page 45 Importing a Transform File on page 48 Importing a Windows Installer Patch File on page 51 Importing an InstallShield Developer Executable on page 54 Importing a Microsoft Hotfix File on page 56 Importing a Virtual Software Package File on page 59 Importing a Device Driver File...
Page 37: Importing From The Share Point Directory
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 38 Importing Packages When you successfully import a package from the share point directory, its .QUE file is deleted and the package information is added to the Software Manager database. Paths to the new source file locations are also updated in the package installation file, except for Wise package definition files.
Page 39 Importing Packages Perform this operation on the Wise Package Studio server If you are working on a client computer, mark this to perform this operation on the Wise Package Studio server. You must use a UNC path to specify the imported package.
Page 40: About .Que Files
32. 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 41 Importing Packages To import a Windows Installer file (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. Select Packages menu > Import. The Import Type page appears. Mark Import a single file into the Software Manager database. In File, specify an .MSI or .WSI to import.
Page 42 Importing Packages If this is marked, conflict detection checks for conflicts between the imported package and all other packages in the Software Manager database. 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 43: Importing A Wisescript Or Sms Installer File
Software Manager database from a network or local drive. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import a WiseScript installation file from the Software Manager database into Software Management Framework. You can then use Software Management Solution to distribute it.
Page 44 Importing Packages The following items become enabled: 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. This prevents other users from exporting the package, unless source files are stored on a shared network drive.
Page 45: Importing A Merge Module File
Importing Packages Application Name To create a new application, enter a unique name. To add this package to an existing application, select an application from the drop-down list. For information on application and package names, see About Applications and Packages on page 22.
Page 46 Importing Packages Detect file and resource conflicts between the merge module and other packages. It also lets corporate developers 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.
Page 47 Importing Packages Detect conflicts during package import The default for this option is provided by the Detect conflicts during package import check box in Conflict Settings. Mark or clear this to override the default. If this is marked, conflict detection checks for conflicts between the imported package and all other packages in the Software Manager database.
Page 48: Importing A Transform File
88. 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 49 Importing Packages You can define the state of the base package, which determines the resources that are included in the imported transform package and changes how it behaves when it is deployed. About Patch and Transform Import on page 36. To import a transform file (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Page 50 Importing Packages Mark the check boxes of the groups to assign the package to. Click OK. Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check boxes during distribution.
Page 51: Importing A Windows Installer Patch File
40. 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 52 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. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. Select Packages menu >...
Page 53 Importing Packages Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check boxes during distribution.
Page 54: Importing An Installshield Developer Executable
88. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the InstallShield package from the Software Manager database into Software Management Framework. You can then use Software Management Solution to distribute the package.
Page 55 Importing Packages Select Packages menu > Import. The Import Type page appears. Mark Import a single file into the Software Manager database. Although this option refers to a single file, the number of files that are imported depends on the number of .MSI files that are compiled into the InstallShield .EXE. In File, specify an InstallShield Developer .EXE to import.
Page 56: Importing A Microsoft Hotfix File
88. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the hotfix file from the Software Manager database into Software Management Framework. You can then use Software Management Solution to distribute...
Page 57 Importing Packages To import a Microsoft hotfix file If you will apply the hotfix to a base package, verify that the base package is in the Software Manager database. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Page 58 Importing Packages 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. Click OK. Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box.
Page 59: Importing A Virtual Software Package File
Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the virtual software package from the Software Manager database into Software Management Framework. You can then use Software Management Solution to distribute it.
Page 60 Importing Packages Perform this operation on the Wise Package Studio server If you are working on a client computer and you mark this option, then this operation is performed on the Wise Package Studio server. The Software Virtualization Agent must be installed on the server computer. You must use a UNC path to specify the imported package.
Page 61: Importing A Device Driver File
Importing Packages Importing a Device Driver File You can import device driver information contained in an .INF file into the Software Manager database from a network or local drive. This lets you: Identify file and registry conflicts that could occur if you were to introduce a specific device into your desktop environment.
Page 62: Importing A Group Policy Object File
Importing Packages Detect conflicts during package import The default for this option is provided by the Detect conflicts during package import check box in Conflict Settings. Mark or clear this to override the default. If this is marked, conflict detection checks for conflicts between the imported package and all other packages in the Software Manager database.
Page 63 Importing Packages Importing a Group Policy Object lets you determine whether any of your packages will change or conflict with policies on your desktops. Example: Suppose you set a group policy to disable the Registry Editor (regedit.exe). You import that Group Policy Object to Software Manager and, when you detect conflicts, you find that one of your packages requires the use of regedit.exe.
Page 64: Importing An Soe Snapshot
Importing Packages 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. Click OK. Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box.
Page 65 Importing Packages To import an SOE snapshot (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. Select Packages menu > Import. The Import Type page appears. Mark Import a single file into the Software Manager database. In File, specify an .SOE to import.
Page 66: Importing A Wise Package Definition File
Importing Packages Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check boxes during distribution.
Page 67 Importing Packages are created with the Package Definition tool in Workbench, not those that are created within Software Manager. Typically, the Package Definition tool in Workbench either imports the Wise package definition file to the Software Manager database or queues it for import in the share point directory.
Page 68: Importing Multiple Files
Importing Packages Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check boxes during distribution.
Page 69 Importing Packages When you add a Windows Installer package’s meta data to the Software Manager database from Windows Installer Editor, its resources are not imported. To get the resources into the database, you must import them. How to Get Packages Into the Software Manager Database on page 32.
Page 70 Importing Packages Mark the check boxes of the groups to assign the package to. Click OK. Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check boxes during distribution.
Page 71: Performing A Universal Import Without Converting Or Repackaging
88. Note If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise Connector to import the package from Software Manager into Software Management Framework. You can then use Software Management Solution to distribute the package.
Page 72 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. Even though you cannot export or recompile the installation file, you might want to copy the source files so you can use them for conflict management.
Page 73 Importing Packages Use the existing Virtual OS file Mark this if you are working in a clean build environment and you previously ran the Virtual OS Creation utility on the current computer. This option is enabled only if a Virtual OS is found on this computer. Use a different Virtual OS file from the share point directory or network Mark this if you previously ran the Virtual OS Creation utility on another computer and the resulting .WOS file is available in the share point directory or...
Page 74: About The Auto Import Service
Importing Packages Note When you display the installation resources for this package, you might see additional files that do not belong to the installation; this is because of the inclusion and exclusion settings in SetupCapture Configuration. See also: Package Import on page 34 About the Auto Import Service Enterprise Management Server only.
Page 75: Subscribing To Packages In Another Database
Importing Packages subscribed package because the original package typically has been approved and deployed and shouldn’t be changed. If you do want to change a subscribed package, you must break the link to the source installation. Breaking Links to Subscribed Packages on page 77.
Page 76 Importing Packages Package If you chose a single application, select a single package to subscribe to. To include all packages, leave the default <Any Package>. Update applications as their source is modified Mark this to re-import the subscribed package whenever the original installation .WSI or .MSI is changed.
Page 77: Refreshing Package Subscriptions
Importing Packages Refreshing Package Subscriptions Enterprise Management Server only. Refreshing package subscriptions consists of re-importing all subscribed packages to the local database. Do this when: The source installation files change. The original package is deleted from the source database. You make changes on the Package Subscriptions dialog box. Options on the Package Subscription Details dialog box determine whether a specific subscription is updated when subscriptions are refreshed.
Page 78 Importing Packages To break a link to a subscribed package Distribute the original package installation to a new location. See Package Distribution in the Wise Package Studio Help. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. In the Applications/Packages pane, click a package.
Page 79: Chapter 3: Managing Packages
Chapter 3 Managing Packages This chapter includes the following topics: Revision Control on page 80 Package Groups on page 87 Viewing and Editing Package Attributes on page 93 Viewing Resource Properties on page 94 Windows Installer Table Queries on page 95 Software Manager Reports on page 98 Removing Excluded Files From Packages...
Page 80: Revision Control
Managing Packages Revision Control Use Revision Control to: Protect packages from unauthorized changes and changes to multiple copies of a package at one time. Track changes to packages. Revision Control performs standard source control functions, including: check in, check out, undo check out, and view and retrieve previous versions. Whereas other source control products protect source files used to compile packages, Revision Control protects packages.
Page 81: Adding Packages To Revision Control
Managing Packages Source control options in Windows Installer Editor are unavailable, and you can begin adding packages to Revision Control. Packages that are checked into Revision Control cannot be added to another source control product. If you do not use source control for package files: If you do not use source control for package files, the Wise Revision Control System check box is marked by default in the Wise Repository Manager.
Page 82: Checking Packages Out Of Revision Control
Managing Packages Checking Packages Out of Revision Control When you check a package out of Revision Control, Software Manager unlocks the package in its source path. You can view the package’s source path on the Source tab in the Package Attributes dialog box. Viewing and Editing Package Attributes on page 93.
Page 83: Undoing Check Outs From Revision Control
Managing Packages To compare a checked out package to the most recent version of that package that is in Software Manager, select the package and click Compare. Comparing Versions of a Package on page 84. Complete the dialog box: Packages Packages that you checked out appear in this list.
Page 84: Removing Packages From Revision Control
Managing Packages Removing Packages from Revision Control When you remove a package from Revision Control, the package remains in Software Manager but is no longer protected or tracked by Revision Control. A package that is checked out cannot be removed from Revision Control. Packages that are removed and then added back to Revision Control retain their history.
Page 85: Viewing A Version Of A Package
Managing Packages Select two versions and click Compare. Note If you select only one version and click Compare, Software Manager compares the selected version to the working version, which is the copy stored in the package’s source path, which is usually the scripts directory or the Projects directory under the share point directory.
Page 86: Viewing Comments For A Version Of A Package
Managing Packages The Package Revision History dialog box appears. Select the version and click Get. In the Save As dialog box that appears, select a location and file name under which to store the retrieved version. The retrieved version is set to read-only unless it is checked out. See also: Reverting to a Previous Version on page 86...
Page 87: Revision Control Settings
Managing Packages See also: Comparing Versions of a Package on page 84 Retrieving a Version of a Package on page 85 Revision Control Settings When you compare versions of a package, Revision Control uses Visual MSIDiff™ to find and display the differences between the versions. You can add file types to compare. You can also change the comparison tool.
Page 88: Creating Package Groups
Managing Packages Example: Suppose a package group named Corporate contains two child groups: Accounting and Engineering. The Engineering group contains a child group named Testing. If your package groups are set up to inherit from both parent and child groups, then whenever you assign a package to the Engineering group, that package is inherited by the Corporate group and the Testing group.
Page 89: Selecting Superseding Packages
Managing Packages Verify the Inheritance setting. This affects the way package assignments are shared between groups. 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 90: Adding Applications And Packages To Groups
Managing Packages It is possible to create complex supersedence relationships, in which one package might be superseded by two different packages. In such cases, you must select which superseding package to use. To select a superseding package Access the Superseding Packages dialog box in any of the following ways: On the Edit Groups dialog box, add a package that has a supersedence relationship or click the Check Supersedence button.
Page 91: Editing Package Groups
Managing Packages Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check boxes during distribution. See also: How Package Relationships Affect Group Distribution on page 123...
Page 92 Managing Packages the defaults for Group Distribution. You can change these settings in Group Distribution, but only for that particular distribution instance. Note If you will use Group Distribution, it is best to add packages to groups on the Group Properties dialog box.
Page 93: Viewing And Editing Package Attributes
Managing Packages When you finish setting the deployment properties, click OK on the Group Properties dialog box. See also: Package Groups on page 87 Creating Package Groups on page 88 Editing Package Groups on page 91 Viewing and Editing Package Attributes To view and edit package attributes (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Page 94: Viewing Resource Properties
Managing Packages Package could require a reboot Mark this if you will distribute this package with Group Distribution, and if a restart will be required during the package’s installation. When Group Distribution creates the deployment wrapper .EXE, it inserts Pause statements immediately following the Execute Program action that runs the package.
Page 95: Windows Installer Table Queries
Managing Packages To view resource properties (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. In the Applications/Packages pane, expand a package to display its resource folders. Expand the resource folder until the resource items are displayed in the Package Details pane.
Page 96 Managing Packages To create a table query Select Packages menu > Table Query. The Table Query dialog box appears. Click Add. The Query Details dialog box appears. In Name, enter a descriptive name to help you identify this query. You can accept the default name, but the default name will not be useful if you have many queries.
Page 97: Viewing The Results Of A Table Query
Managing Packages Wildcard Description Example matches any characters 1.06.[1-4^2] not in the specified set returns 1.06.1, 1.06.3, and 1.026.4 _ (underscore) matches any single 1.06._ character returns 1.06.0, 1.06.1, 1.06.2, and so on through 1.06.9 Criteria Operator This is unavailable for the first criteria statement you build. It becomes enabled for subsequent statements.
Page 98: Example Table Queries
Managing Packages To view the results of a table query Select Packages menu > Table Query. The Table Query dialog box appears. In the list of queries, click the query to view and click Run. The Table Report dialog box appears and displays the results of the query. You can save the or print the table report from this dialog box.
Page 99: Generating A Software Manager Report
Managing Packages Note When you install Wise Package Studio, triggers are added to the Software Manager database. Because the default SQL Server backup process does not include triggers, you should change your backup configuration to include them. Report Name Reports Menu What This Report Does Command File Resources...
Page 100: Using The Report Viewer
Managing Packages generates. The default value is 6000. This field does not appear for the Packages by Merge Module report. Note If you save a report as an HTML file, an HTML file is created for each page of the report.
Page 101: Removing Excluded Files From Packages
Managing Packages Removing Excluded Files From Packages SetupCapture uses an exclusion list to determine which items on a computer to ignore. As repackagers in an organization use SetupCapture over time, they typically continue to add to the exclusion list, making it more robust and eliminating more unnecessary files from their captures.
Page 102: Merge Modules Wizard
Managing Packages System. When the operation is completed, you must check the package back into Revision Control manually. Checking Packages Out of Revision Control on page 82. Mark Duplicate Package to create a new package instead of modifying the existing package. If the package has already been distributed, you could use this option to retain a copy of the distributed package.
Page 103: Adding Merge Modules To .Msi Or .Wsi Packages
Managing Packages See: Adding Merge Modules to .MSI or .WSI Packages Removing Merge Modules From .MSI or .WSI Packages Replacing a Merge Module in an .MSI or .WSI Package Adding Merge Modules to .MSI or .WSI Packages In Software Manager, you can perform an operation that adds one or more merge modules to one or more .MSI or .WSI packages.
Page 104: Removing Merge Modules From .Msi Or .Wsi Packages
Managing Packages A selected package is checked in and the Check out from Revision Control option is not marked. The dialog box explains how the listed packages will be processed. To proceed, click The Wise Task Manager dialog box appears and remains open until the operation is completed.
Page 105: Replacing A Merge Module In An .Msi Or .Wsi Package
Managing Packages The Revision Control Status dialog box appears if one of the following is true: A selected package is checked out by another user. A selected package is checked in and the Check out from Revision Control option is not marked. The dialog box explains how the listed packages will be processed.
Page 106: Moving A Package To Another Application
Managing Packages Mark Duplicate Package to create a new package instead of changing the existing package. If the package has already been distributed, you can use this option to retain a copy of the distributed package. The duplicate package has the same application name as the original package, with a number in parenthesis appended to its package name.
Page 107: Deleting A Package
Managing Packages Deleting a Package You can delete a package from the Software Manager database. However, the Software Manager database should contain all packages used by your organization, even those that are obsolete. Deleting a package from the Software Manager database removes information about that package from the database.
Page 108: Changing The Package Status
Managing Packages Example: You have a group of applications that run reports and use the Crystal Report runtime, and you need to update this runtime in each of these applications. You create a macro that updates the runtime and runs when you compile. You then use the multi- package compile option in Software Manager to compile the packages.
Page 109 Managing Packages In Windows Installer Editor, when you open an Available package from the Wise Software Repository, you are prompted to change the status to Under Development. To change the package status manually (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Page 110 Managing Packages To change to a different status, select it from Package Status. To change the package status automatically Create a task that runs Software Manager with the option Change package status to Available. When you run that task from a project in Workbench, the option sets the package’s status to Available and copies the installation and its associated files to the Available Packages directory.
Page 111: Chapter 4: Preparing Packages For Deployment
Chapter 4 Preparing Packages for Deployment This chapter includes the following topics: About Preparing Packages for Deployment on page 111 Process for Deploying a Single Package on page 111 Process for Deploying a Group on page 112 About Package Definition on page 114 About Package Relationships on page 120...
Page 112: Process For Deploying A Group
Preparing Packages for Deployment Complete the repackaging process. Make sure that the package is ready for deployment. This includes resolving conflicts and testing. Make packages available. Change the package’s status to Available to indicate that it is ready for deployment. Changing the Package Status on page 108.
Page 113 Preparing Packages for Deployment formats, you can add additional files to the installation or change the default command line. Import the package into the Software Manager database. The order in which you perform these tasks varies: Perform the tasks in this order: Add the package and its resources to Import the package.
Page 114: About Package Definition
Preparing Packages for Deployment Make packages available. Change the package’s status to Available to indicate that it is ready for deployment. Changing the Package Status on page 108. Distribute the package group. Using Group Distribution creates a deployment wrapper .EXE, which contains the files that will install all packages in the group, the command lines that will run the installations, and any additional files that will be installed.
Page 115: Creating A Package Definition
Preparing Packages for Deployment Setting Group Deployment Properties on page 91 and Distributing a Group page 131. See: Creating a Package Definition on page 115 Editing or Viewing a Wise Package Definition on page 118 Defining a Package in Workbench Define a package in Workbench, using Package Definition, when you need to install: A package that you could not otherwise repackage or deploy.
Page 116 Preparing Packages for Deployment The Specify Files dialog box appears. The upper panes of this dialog box display the directories and files that are accessible from your computer. The lower pane contains the package’s installation file. (Optional.) To include files in the package definition, use the following buttons: Add Directory Adds the entire contents of the directory you select in the upper-left pane.
Page 117 Preparing Packages for Deployment This step depends on the file that you are creating the command line for: If the file is: Then: An .MSI that is in the package Click Select File. definition. Select the .MSI and click OK. The Command Line Builder for Windows Installer opens.
Page 118: Editing Or Viewing A Wise Package Definition
Preparing Packages for Deployment Editing or Viewing a Wise Package Definition Use Software Manager to edit, view, or delete Wise package definitions. With Enterprise Management Server, Security Setup determines whether you can edit a package definition file. To edit a package definition (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Page 119 Preparing Packages for Deployment The default Package Definition exclusion list is the same as the default Setup Capture exclusion list, except that it only includes files. To set exclusions in Package Definition Access the Specify Files dialog box in Package Definition. Creating a Package Definition on page 115.
Page 120: About Package Relationships
Preparing Packages for Deployment About Package Relationships In Software Manager, package relationships define which packages depend on other packages. During Group Distribution, package relationships determine the packages that are installed and the order of their installation. How Package Relationships Affect Group Distribution on page 123.
Page 121 Preparing Packages for Deployment About Patch and Transform Import on page 36. You cannot create cyclic dependencies. Example: If package A depends on Package B, then you cannot make Package B depend on Package A. With Enterprise Management Server, Security Setup determines whether you can edit package relationship properties.
Page 122: Viewing Package Relationships
Preparing Packages for Deployment Required Association (must go with) The dependent package must be installed with the dependency. Optional Association (optionally goes with) During Group Distribution, you have the option to include the dependent package with the dependency. Example: An .MSI is a dependency of an .MST and you only need to distribute the .MST to certain departments.
Page 123: How Package Relationships Affect Group Distribution
Preparing Packages for Deployment Package relationship information is displayed in the Package Details pane. This information is read-only. If you click the Package Dependencies folder, the current package’s dependencies are displayed in alphabetical order. Subdependencies are not displayed. If you click the Dependent Packages folder, packages that are dependent on the current package are displayed in alphabetical order.
Page 124 Preparing Packages for Deployment .MSI package with a required patch and an optional dependency Package Relationships dialog box Group Properties dialog box Add MSI Package 2 to Group B. The other packages are pulled in because of their relationships to MSI Package 2. = Required/Required.
Page 125: Impact And Risk Assessment
Preparing Packages for Deployment Impact and Risk Assessment The Impact Assessment and Risk Assessment features let you identify problems that might occur as a result of installing hotfixes or patches. Impact Assessment Use this feature to quickly assess the potential impact of installing a package (usually a hotfix or security patch) without taking the time to perform extensive testing.
Page 126: Assessing And Mitigating The Risk Of Failing To Update Isolated Files
Preparing Packages for Deployment In Software Manager, select Tools menu > Impact and Risk Assessment. In Workbench, on the Projects tab, click the Run link to the right of the task or tool associated with Impact and Risk Assessment. In Workbench, on the Tools tab, double-click Impact and Risk Assessment. If the Detect Conflicts dialog box appears: To detect conflicts, select applications and click OK.
Page 127: Detecting Conflicts For Impact And Risk Assessment
Preparing Packages for Deployment The Impact and Risk Assessment dialog box appears. In Package, select the patch or hotfix. Mark Isolated Files at Risk. The list displays the packages that contain isolated files that will not be updated by the selected package. To display isolated files that will not be updated, select a package in the list and click the Files tab.
Page 128: About Svs Enabled Packages
(SVS). You can enable .MSI and .WSI packages or any type of package that has an associated package definition file. For more information about Software Virtualization Solution (SVS), search for Workspace Virtualization on the symantec.com Web site. About Package Definition on page 114.
Page 129: Package Distribution
Preparing Packages for Deployment The SVS Enabled Package dialog box appears. Complete the dialog box: Name This is the name of the layer. By default it is the package’s application and package name. If you change this name, it does not change the application and package name.
Page 130: Group Distribution
Preparing Packages for Deployment For information on the distribution methods available and instructions on using Package Distribution, see Package Distribution in the Wise Package Studio Help. The following types of packages should be distributed through Group Distribution instead of Package Distribution: device drivers, Group Policy Objects, transforms, and packages imported using the Universal Import option.
Page 131: Distributing A Group
Preparing Packages for Deployment .MSP, .MST, .WSE, and .IPF. Those formats have default command lines, and Group Distribution determines the installation file. However, by defining packages for any of those formats, you can add additional files to the installation or change the default command line.
Page 132 Preparing Packages for Deployment The Select Packages dialog box appears. Dependency packages appear in the list, even if they are not part of this group. A red dot on the package icon indicates a required package. For examples of how package relationships affect what appears in this dialog box, see How Package Relationships Affect Group Distribution page 123.
Page 133 Preparing Packages for Deployment Software Manager Reference...
Page 134: Chapter 5: Software Manager Database Maintenance
Chapter 5 Software Manager Database Maintenance This chapter includes the following topics: About Software Manager Database Maintenance on page 134 Changing the Server Path on page 135 Deleting a Server Path on page 136 Restructuring the Index on page 136 Rebuilding the Index on page 137 About Software Manager Database Maintenance...
Page 135: Changing The Server Path
Software Manager Database Maintenance Changing the Server Path The Software Manager server path contains the subdirectories in which the source files associated with an installation package are stored. Initially, the server path is the same 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.
Page 136: 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 137: 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 138 Software Manager Database Maintenance Restructuring the Index on page 136. 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 139: Index
Index comparison tool 87 hotfix 56 InstallShield Developer 54, 68 compile multiple packages 107 active database 12 Universal Import 71 conflict detection add merge module 103 export during import 34 add package to revision control 81 preventing 93 conflict type ADM file 62 icons 17 administrative template, importing 62...
Page 140 InstallShield Developer .EXE multiple databases importing 54 about 19 icons importing multiples 68 opening 12 conflict type 17 InstallShield Pro, converting to multiple files, importing 68 relationship 18 Windows Installer 54 multiple-package compile 107 resource 17 IPF file, importing 43, 68 Software Manager 16 multi-user environment 20 isolated file...
Page 141 Package Contents by Feature reference manual 31 undoing checkout 83 report 99 viewing a version 85 refresh display 16 Package Contents reports 100 revision history, package 84 refresh subscription Package Contents Summary report 99 about 77 Revisions directory, in share point 80 automatically 77 package definition risk assessment...
Page 142 about 74 VSA file, importing 59, 68 breaking link 77 command disabled 9 deleting when source is wamdb.idx deleted 76 corrupt 137 editing 76 rebuilding 137 refreshing 77 restructuring 136 refreshing automatically 77 Windows Installer file re-importing 76, 77 importing 40 scheduling refresh 28 importing multiples 68 subscribing to packages 75...

This manual is also suitable for:

Software manager 8.0

Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Technical Support

Chapter 1: Introduction to Software Manager

Chapter 2: Importing Packages

Chapter 3: Managing Packages

Chapter 4: Preparing Packages for Deployment

Chapter 5: Software Manager Database Maintenance

Index

Quick Links

Need help?

Questions and answers

Related Manuals for Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0

Summary of Contents for Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0

This manual is also suitable for:

Table of Contents