How it Works
Symantec
Loading...
N
O
P
R
S
U
V
W
X
Loading...
Loading...
SOFTWARE MANAGER 8.0
Reference
142 pgs978.76 Kb0

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

Download
Software Manager Reference
Software Manager
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.
Documentation version 8.0
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 t heir respective owners. 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 E XTENT THAT SUCH DISCLAIMERS ARE HELD T O BE LEGALLY INV ALID . SYMANTE C 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
Software Manager Reference 2
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 maintenance offerings include the following:
z A range of support options that give you the flexibility to select the right amount of
service for any size organization
z Telephone and Web-based support that provides rapid response and up-to-the-
minute information
z Upgrade assurance that delivers automatic software upgrade protection z Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Web site at the following URL:
www.symantec.com/techsupp/
Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support information at the following URL:
www.symantec.com/techsupp/
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:
z Product release level z Hardware information z Available memory, disk space, and NIC information z Operating system z Version and patch level z Network topology z Router, gateway, and IP address informa tion z Problem description:
Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Software Manager Reference 3
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:
z Questions regarding product licensing or serialization z Product registration updates, such as address or name changes z General product information (features, language availability, local dealers) z Latest information about product updates and upgrades z Information about upgrade assurance and maintenance contracts z Information about the Symantec Buying Programs z Advice about Symantec’s technical support options z Nontechnical presales questions z Issues that are related to CD-ROMs or manuals
Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows:
Asia-Pacific and Japan customercare_apac@symantec.com Europe, Middle-East, and Africa semea@symantec.com North America and Latin America supportsolutions@symantec.com
Additional enterprise services
Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Symantec Early Warning Solutions
Managed Security Services
These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur.
These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats.
Software Manager Reference 4
Consulting Services
Educational Services
To access more information about Enterprise services, please visit our Web site at the following URL:
www.symantec.com
Select your country or language from the site index.
Symantec Consulting Services provide on-site technical 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.
Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.
Software Manager Reference 5
Contents
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 1: Introduction to Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About Software Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Packages in Software Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Package Management with Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Starting Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Opening and Closing Software Manager Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About the Software Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Customizing the Software Manager Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Filtering the Package Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Refreshing the Software Manager Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Icons in Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Resource Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Conflict Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Relationship Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
About the Software Manager Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Multiple Software Manager Dat abases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Software Manager in a Multi-user Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Sharing the Software Manager Database With Corporate Developers . . . . . . . . . . . . . . . . . . . 21
About Applications and Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Setting Software Manager Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
About Package Meta Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Defining Custom Meta Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Defining a Custom Meta Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Scheduling Software Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Wise Software Repository Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 2: Importing Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
About Importing Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
How to Get Packages Into the Software Manager Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
About Formatted Text Strings in Registry Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Package Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Import Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
About Patch and Transform Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Importing From the Share Point Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
About .QUE Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Importing a Windows Installer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Importing a WiseScript or SMS Installer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Importing a Merge Module File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Importing a Transform File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Importing a Windows Installer Patch File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Importing an InstallShield Developer Executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Importing a Microsoft Hotfix File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Importing a Virtual Software Package File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Importing a Device Driver File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Importing a Group Policy Object File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Software Manager Reference 6
Importing an SOE Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Importing a Wise Package Definition File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Importing Multiple Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Performing a Universal Import Without Converting or Repackaging . . . . . . . . . . . . . . . . . . . . 71
About the Auto Import Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Package Subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Subscribing to Packages in Another Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Refreshing Package Subscriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Breaking Links to Subscribed Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Chapter 3: Managing Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
About Managing Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Revision Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Choosing to Use Revision Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Adding Packages to Revision Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Checking Packages Out of Revision Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Checking Packages Back Into Revision Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Undoing Check Outs from Revision Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Removing Packages from Revision Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Package Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Comparing Versions of a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Viewing a Version of a Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Retrieving a Version of a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Viewing Comments for a Version of a Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Reverting to a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Revision Control Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Package Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Creating Package Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Selecting Superseding Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Adding Applications and Packages to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Editing Package Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Setting Group Deployment Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Viewing and Editing Package Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Viewing Resource Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Windows Installer Table Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Creating a Table Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Viewing the Results of a Table Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Example Table Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Software Manager Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Generating a Software Manager Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Using the Report Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Removing Excluded Files From Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Merge Modules Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Adding Merge Modules to .MSI or .WSI Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Removing Merge Modules From .MSI or .WSI Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Replacing a Merge Module in an .MSI or .WSI Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Moving a Package to Another Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Deleting a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Compiling Multiple Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Changing the Package Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Chapter 4: Preparing Packages for Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
About Preparing Packages for Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Process for Deploying a Single Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Software Manager Reference 7
Process for Deploying a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
About Package Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Creating a Package Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Editing or Viewing a Wise Package Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Setting Exclusions in Package Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
About Package Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Creating and Editing Package Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Viewing Package Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
How Package Relationships Affect Group Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Impact and Risk Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Assessing a Package’s Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Assessing and Mitigating the Risk of Failing to Update Isolated Files. . . . . . . . . . . . . . . . . . . 126
Detecting Conflicts for Impact and Risk Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
About SVS Enabled Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Creating an SVS Enabled Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Package Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Group Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Distributing a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Chapter 5: Software Manager Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . 134
About Software Manager Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Changing the Server Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Deleting a Server Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Restructuring the Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Rebuilding the Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Software Manager Reference 8
Chapter 1
Introduction to Software Manager
This chapter includes the following topics:
z About Software Manager on page 9 z Starting Software Manager on page 12 z About the Software Manager Window on page 13 z Icons in Software Manager on page 16 z About the Software Manager Database on page 19 z About Applications and Packages on page 22 z Setting Software Manager Preferences on page 24 z About Package Meta Data on page 25 z Scheduling Software Manager Tasks on page 28 z Wise Software Repository Automation on page 30 z Product Documentation on page 30
About Software Manager
Software Manager provides the interface for working with packages in the Software Manager database, which contains information about all the software packages used by your organization. Storing all your package information in a central location lets you better manage packages during their lifecycle stages—from integration, testing, and deployment through retirement.
Use Software Manager to import and organize packages and their resource information in the Software Manager database, to obtain information about packages and their resources, to set the status of packages, and to prepare a package or group of packages for deployment. Corporate developers can use Software Manager as a centralized point for managing all resources used by applications that they develop.
Software Manager is a tool in the Professional Edition of Wise Package Studio. See Introduction to Wise Package Studio in the Wise Package Studio Help.
Note
With Enterprise Management Server, Software Manager menu commands that you do not have permission to use are unavailable. Functional security for Software Manager is set in the Wise Package Studio Security Setup.
See Setting Software Manager and ConflictManager Security in the Wise Package Studio Help.
Packages in Software Manager
In Software Manager, a package consists of any combination of the following:
Software Manager Reference 9
Introduction to Software Manager
z Meta data. This is the is minimum amount of information that constitutes a package. z The resources associated with each package’s installation. z The installation file. z A command line for running the installation when it is installed. z Additional files that should be deployed with the installation (example: an
informational text file).
The last three items above represent package definition information.
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:
z Add the package’s meta data in Windows Installer Editor. z Import the package’s definition from Workbench. z Import the package and its resources in Software Manager.
See How to Get Packages Into the Software Manager Database on page 32 and Package
Import on page 34.
Package Management with Software Manager
Once packages are in the Software Manager database, you can do the following:
Create and Manage Package Groups
A package group consists of a subset of the packages in the Software Manager database. You can use groups to:
z Organize your packages, which lets you filt er the displays and some of the reports in
Software Manager and ConflictManager.
z Deploy multiple related packages at once. z Install packages that you would not otherwise be able to repackage and deploy
because they are of unknown format, or because they require a command line to run.
See Package Groups on page 87.
Edit Package Information
Use Software Manager to maintain the packages in the Software Manager database.
z Change the package status so you can determine whether a package can be
deployed to end users.
z Edit package information. Example: You can rename the application or package, or
change the reference to the source file paths.
z Enter or edit user-defined package meta data. z Delete a package from the Software Manager database.
See Viewing and Editing Package Attributes on page 93 and Changing the Package
Status on page 108.
Software Manager Reference 10
Introduction to Software Manager
View Package Resources
z Use the panes in Software Manager to drill down to the resources (examples: files,
registry keys, merge modules, shortcuts, and so on) that are us ed by each package. See About the Software Manager Window on page 13 and Viewing Resource
Properties on page 94.
z Use the reports to obtain information about file, registry, and merge module
resources in the Software Manager database. See Software Manager Reports on page 98.
z Use a table query to query the package data of Windows Installer packages.
See Windows Installer Table Queries on page 95.
If an .MSI contains a merge module, the resources that appear under the Merge Modules folder also appear in the corresponding folders elsewhere in the package. (Example, if an .MSI contains a merge module that has .DLL files in the system32 folder, these files will appear in the system32 folder under the package’s Merge Modules folder and Files/Directories folder.) If a .WSI contains a merge module, the Merge Modules folder and some of its subfolders appear, but none of the merge module’s resources appear.
Files that you add when you define a package do not appear in Software Manager.
Update Packages
z Use the Merge Module Wizard to perform operations on .MSI or .WSI packages that
add, remove, or replace merge modules. See Merge Modules Wizard on page 102.
z Use the Multi-Package Compile Wizard to compile and update a set of packages.
See Compiling Multiple Packages on page 107.
Prepare Packages for Deployment
z Use a Wise package definition to define what is needed to install a package. This lets
you use group distribution to prepare the package for deployment. See About Package Definition on page 114.
z Use package relationships to define which packages depend on other packages.
During group distribution, package relationships determine the packages that are installed and the order in their installation.
See About Package Relationships on page 120.
z Use impact and risk assessment to identify problems that might occur as a result of
installing a hotfix or patch. See Impact and Risk Assessment on page 125.
z Use the SVS Enabled Package option to create a package that installs the package
as a layer if the Software Virtualization Agent is present. If the Software Virtualization Agent is not present, the package is installed normally.
See About SVS Enabled Packages on page 128.
z Use Package Distribution to share or distribute a single package from Workbench or
from Software Manager. See Package Distribution on page 129.
Software Manager Reference 11
z 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.
See Group Distribution on page 130.
Starting Software Manager
In Wise Package Studio, do one of the following:
z On the Projects tab, click the Run link to the right of the task or tool associated with
Software Manager.
z On the Tools tab, double-click 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 by either Software Manager or ConflictManager. With Enterprise Management Server, multiple databases might open.
Introduction to Software Manager
When you start Software Manager from a task that specifies the database in its command-line options, the specified database is opened.
See also:
Opening and Closing Software Manager Databases About the Software Manager Window on page 13
Opening and Closing Software Manager Databases
¾ Enterprise Management Server only .
You can open multiple Softw are Manager databases simultaneously. This lets you browse multiple databases in Software Manager and ConflictManager, and work in a second database without closing the first one.
One database must always be open in Software Manager.
To open an additional database
1. If the database does not exist, create a new database in the Wise Repository Manager. See Creating Software Manager Databases in the Wise Package Studio Getting Started Guide.
2. Select File menu > Open Database. The Select Data Source dialog box appears. This is a standard Windows ODBC
connection wizard, which lets you connect to a database through an ODBC data source.
3. Connect to the database. If you need help, ask your database administrator. The database’s contents are listed in the Applications/Packages pane.
4. To make a database active, click anywhere in its tree.
Software Manager Reference 12
All Software Manager activities are performed within the active database.
To close a database
1. Select File menu > Close Database. The Close Database dialog box appears.
2. 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 Multiple Software Manager Databases on page 19
About the Software Manager Window
When you start Software Manager, the main Software Manager window appears. Some of the panes might be empty if no packages are in the Software Manager database.
Software Manager Window
Introduction to Software Manager
Toolbar
Groups pane
Applications/ Packages pane
Database pane
Application/ Package Summary pane
Package Details pane
Toolbar
Contains buttons for quick access to many Software Manager commands. It also provides quick access to ConflictManager.
Database Pane
Displays summary information about the Software Manager database. If multiple databases are open (Enterprise Management Server only), the information
refers to the active database, which is the one selected in the Applications/Packages
Software Manager Reference 13
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 too lbar, but you can mov e or hide it.
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.
See Creating Package Groups on page 88. The Groups pane initially appears on the left side of the window below the Database
pane, but you can move or hide it.
Application/Package Summary
Displays different information depending on what is selected in the Applications/ Packages pane:
z When you select an application, this pane is named Application and it lists the
packages contained in that application.
z When you select a package, this pane is named Package and it displays a summary
of the package’s resources, information about when the package was imported and changed, and package meta data. It also contains a Package Status drop-down list, which you use to change the package’s status.
See Changing the Package Status on page 108.
If you are using Revision Control, revision control status and other revision control information appears in the Application/Package Summary pane.
The Application/Package Summary pane initially appears on the right side of the window below the Database pane, but you can move or hide it.
Applications/Packages Pane
Displays the applications and packages in the Software Manager database. Expand an application to display its packages. Select a package to make it the active package.
(Enterprise Management Server only.) When multiple databases are open, select a database in the Applications/Packages pane to make it the active database. All Software Manager activities are performed within the active database.
For information on the icons that appear in this pane, see Icons in Software Manager on page 16.
Package Details Pane
Displays the resources in the package selected in the Applications/Packages pane. For information on the icons that appear in this pane, see Resource Icons on page 17. If conflicts were detected for the active package in ConflictManager, the icons for these
conflicts are displayed as well. See Conflict Icons on page 17. Double-click an item in this pane to display the Properties dialog box.
Software Manager Reference 14
See Viewing Resource Proper t ies on page 94.
Customizing the Software Manager Workspace
z Hide or show the toolbar or one of the panes by selecting its name from the View
menu.
z Move, dock, and undock the panes as you would any Windows pane, by dragging
their title area.
The Applications/Packages pane and Package Details panes cannot be hidden or moved.
Filtering the Package Display
You can specify filter criteria to determine which packages appear in the Applications/ Packages pane. The filter criteria you specify remain the same for subsequent uses of Software Manager.
To filter the package display
1. Select Packages menu > Filter. The Filters dialog box appears.
Introduction to Software Manager
2. To filter by package status, mark any combination of check boxes in the Package Status to Display section.
3. To filter by whether the package is defined, mark check boxes in the Filter Based on Package Definition section.
Display Defined Packages
Displays packages that were defined in either Workbench or Software Manager.
Display Undefined packages
Displays packages that do not have a package definition.
4. To filter the display by a meta data value, mark Filter based on Meta Data. Then specify the following filter criteria:
Name
Select a meta data field name to filter packages by. The drop-down list cont ains meta data fields that are defined in the selected database.
Operation
Select the operation to use when comparing the meta data value to the value you enter below. The operations that are available depend on the data type of the meta data field.
Value
Specify the meta data value to match.
5. To filter by package type, mark any combination of check boxes in the Package Type to Display section.
6. Click OK.
See also:
Changing the Package Status on page 108 About Package Meta Data on page 25
Software Manager Reference 15
Refreshing the Software Manager Display
z 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.
Icons in Software Manager
The following icons appear in Software Manager to help you quickly identify items in the database.
Icon Represents Appears in this pane
Software Manager database Applications/Packages
Group Groups
Application Applications/Packages,
Introduction to Software Manager
Package Details
Windows Installer package (installation, transform, patch, or Microsoft hotfix)
When you import an InstallShield® Developer .EXE, it appears as a Windows Installer package because an .MSI is extracted from the .EXE.
Virtual software package (.WVP or .VSA) created in Virtual Package Editor.
Wise package definition file (.WPF) created in Workbench and imported.
WiseScript package Applications/Packages,
Merge module package Applications/Packages,
Any installation file imported using the Universal Import option
SOE Snapshot Applications/Packages,
Device driver package Applications/Packages,
Applications/Packages, Package Details
Applications/Packages, Package Details
Applications/Packages, Package Details
Package Details
Package Details Applications/Packages,
Package Details
Package Details
Package Details
See also:
Software Manager Reference 16
Group Policy Object package Applications/Packages,
Package Details
Resource Icons
Introduction to Software Manager
Conflict Icons on page 17 About the Software Manager Window on page 13
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.
See Resource Conflicts in the ConflictManager Help.
Icon Resource Type
File or Windows Installer component.
Registry key or named value.
Modification to Autoexec.bat. Not applicable in Windows Installer packages.
Conflict Icons
Modification to Config.sys. Not applicable in Windows Installer packages.
ODBC data source or driver.
Windows NT service.
Device driver ins talled in Win.ini. Not applicable in Windows Installer packages.
.INI file and entries.
Shortcut.
Change to the PA TH variable. Not applicable in Windows Installer packages.
See also:
About the Software Manager Window on page 13
The following icons appear in the Conflict List and Conflict Details panes in ConflictManager and in the Package Details pane in Software Manager to indicate the type of conflict.
See Types of Conflicts in the ConflictManager Help.
Software Manager Reference 17
Icon Conflict Type Represents
Warning Conflicts that are not critical but might require some
attention.
Error More serious conflicts that deserve careful inspection.
Introduction to Software Manager
See also:
Icons in Software Manager on page 16 About the Software Manager Window on page 13
Relationship Icons
In Software Manager, the following icons appear on the Dependencies tab on the Package Relationships dialog box. These icons represent:
z The dependency relationship, which is what should happen to th e dependency
z The association relationship, which is what should happen to the dependent package
See About Package Relationships on page 120.
Information
package if the dependent package is installed.
if the dependency package is installed.
z When multiple packages install a non-16-bit file
with identical file information to the same directory or to different directories.
z When multiple packages set the same registry
key to the same value.
Because these are not true conflicts, they do not appear in ConflictManager.
Icon Dependency relationship Association relationship
Software Manager Reference 18
Required. The dependency must precede the
dependent package during installation.
Required. The dependency must precede the
dependent package during installation.
Required. The dependency must precede the
dependent package during installation.
None.
Required. The dependent package must be
installed with the dependency.
Optional. Installing the dependent package
with the dependency is optional.
Introduction to Software Manager
Icon Dependency relationship Association relationship
Optional. Installing the dependency package
is optional. If it is installed, it must precede the dependent package.
Optional.
None.
Required.
Installing the dependency package is optional. If it is installed, it must precede the dependent package.
Optional. Installing the dependency package
is optional. If it is installed, it must precede the dependent package.
Supersedes. The dependency replaces the
dependent package during installation.
The dependent package must be installed with the dependency.
Optional. Installing the dependent package
with the dependency is optional.
None.
About the Software Manager Database
The Software Manager database contains:
z All software packages used or created by an organization. Package resources might
be included also (examples: files, merge modules, registry keys).
z Merge modules used by an organization. z Other resources used by an organization, such as device drivers and Group Policy
Objects.
z Snapshots of standard operating environments used by an organization, for use
during conflict resolution. Create these snapshots with SOE Snapshot.
You manage the data in the Software Manager database through Software Manager.
See also:
About the Wise Software Repository in the Wise Package Studio Help
Sharing the Software Manager Database With Corporate Developers on page 21 Multiple Software Manager Databases on page 19 Software Manager in a Multi-user Environment on page 20
Multiple Software Manager Databases
You might want to use multiple Software Manager databases in these instances:
z If you import a large number of applications for a large organization, you can use
multiple databases to reduce the database size.
z If you are repackaging for multiple operating systems, you can use a separate
database for each target operating system.
Software Manager Reference 19
Introduction to Software Manager
z 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. Running multiple databases on a single server degrades performance. In addition, you cannot run the Wise scheduled tasks, which import packages and refresh package subscriptions on a server-based installation, on more than one database on a single computer.
For configuration recommendations, see Additional Wise Package Studio Configurations in the Getting Started Guide.
(Enterprise Management Server only.) You can open multiple Software Manager databases simultaneously . This lets you browse multi ple databases in Software Manager and ConflictManager, and work in a second database without closing the first one.
See Opening and Closing Software Manager Databases on page 12. (Enterprise Management Server only.) You cannot perform conflict management
operations across databases. However, you can copy, or subscribe to, packages in another database. Examples:
z Suppose a corporate-level repackaging team maintains a database of packages
used throughout the corporation, and regional teams maintain separate databases of packages unique to their regions. A regional repackager can subscribe to the corporate-level packages and resolve conflicts between the regional packages and the subscribed corporate packages.
z When corporate developers, using a Software Manager database with Windows
Installer Editor, subscribe to packages in the database used by system administrators in Wise Package Studio. This lets developers check the shared resources in the applications they are building against applications that have been deployed.
See also:
About the Software Manager Database on page 19 Package Subscription on page 74
Creating Software Manager Databases in the Getting Started Guide
Software Manager in a Multi-user Environment
Most organizations that use Software Manager work in a multi-user, team-based environment. Software Manager accommodates a multi-user environment in several ways:
z Users can run Software Manager and ConflictManager from their local computers or
in a client-server configuration, in which the full installation of Wise Package Studio resides on a server and the client computers are configured to run the software from the server.
z Multiple users can simultaneously access a single Software Manager database that is
stored on a shared server. In this situation:
Multiple users can distribute to the share point directory. When a package is added to the Software Manager database, all Software
Software Manager Reference 20
Manager users can view and work with it.
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. This could happen when using one of the aggressive resolution rule sets or when using the Copy Down button in the ConflictManager Resolve wizard.
z You can set up multiple Software Manager databases within your organization. Each
database might contain packages used by a different department, or packages managed by a different regional repackaging team.
z (Enterprise Management Server only.) Users can open multiple Software Manager
databases simultaneously, and can share packages between databases.
See also:
About the Software Manager Database on page 19 Multiple Software Manager Databases on page 19
Additional Wise Package Studio Configurations in the Getting Started Guide
Sharing the Software Manager Database With Corporate Developers
Developers who create applications for internal, corporate use might want to obtain information about external applications that have been tested and deployed throughout their organization.
If the development team in your organization uses Wise Installation Studio, developers can connect to the deployment team’s Software Manager database.
Why share information in the deployment Software Manager database? Because the Software Manager database used by Wise Package Studio contains approved versions of applications that have been deployed, developers can use this information to build installations that adhere to corporate standards.
Example: By checking the Software Manager database when building an installation, and selecting
source files from the database, developers can be sure to use the correct versions of critical files (examples: the Visual Basic runtime or MDAC). The result is that developers produce more reliable installations that will not conflict with applications already deployed to end-users’ computers. This eliminates the need for the repackaging team to 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
1. During development, the developer imports a new application to the shared Software Manager database. The developer can view resources used by applications that are in development and those that have been deployed.
2. When development is finished, the developer notifies a member of the deployment team.
3. The deployment process begins.
Software Manager Reference 21
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
When you add a package to the Software Manager database, you assign it an application name and a package name. An application is a group of similar packages. Packages represent different versions of a single application installation, or different components of a larger suite. Group packages that are not likely to coexist on the same computer under a single application. This prevents y ou from seeing resources th at are not relev ant to a specific application. Also, because ConflictManager does not look for conflicts between packages of the same application, this speeds the conflict detection process and avoids showing you conflicts that are not relevant.
Example:
Introduction to Software Manager
Your Software Manager database might contain three Microsoft Office packages: Office 97, Office 2000, and Office XP. Because you are not likely to install multiple versions of Microsoft Office on a single computer, you can group them under one application, named Microsoft Office.
Obtaining Application and Package Names for Installations
If the package’s meta data is in the Software Manager database or the package was created in Wise Package Studio, the application and package names are p re-filled dur ing import.
Otherwise, they are assigned as described below.
When you import the application/package names are obtained
from:
a single installation file (any type)
from the share point directory
multiple Windows Installer installations
prompts during import.
the application and package names that were specified during Package Distribution. If the application and package names were not specified during distribution, they are assigned as described below.
The product name and version from the Product Details page in Windows Installer Editor. Application name = product name. Package = product name + version. Example: If the product name is Sample and the version is 1.0.0, the application name will be Sample and the package name will be Sample 1.0.0.
Software Manager Reference 22
Introduction to Software Manager
When you import the application/package names are obtained
from:
z multiple Windows
Installer installations that do not have a product name and version, or
z multiple WiseScript
installations
the file name. Example: If you import Sample.msi, the application name and package name will both be Sample.
Naming Applications and Packages for Other Items
z SOE Snapshot
Application name: Enter the operating system name. Package name: Enter the operating system name, its service pack, and the base
applications or a department name. Example: An application named Windows XP might contain packages named
Windows XP SP1 with Office, and Windows XP SP1 for Accounting.
z Device driver (.INF)
Application name: Obtained from the manufacturer name. Package name: Obtained from the device name. Example: An application named HP Printers might contain packages for the LaserJet
1200, LaserJet 2200, LaserJet 4100, and so on.
z Group Policy Object (.POL)
It is best to import each Group Policy Object as a separate application, rather tha n grouping multiple packages under a single group policy application. This is because different group policies might conflict with each other, but ConflictManager doe s not look for conflicts between packages of the same application.
z Merge module
You might group merge modules by manufacturer or function. Example: Create an application named MDAC, and then import merge module files to packages named MDAC 2.5, MDAC 2.6, MDAC 2.7, and so on.
z Microsoft hotfix
Application name: You might group Microsoft hotfixes by product. Example: Windows 2000.
Package name: Describe the hotfix or refer to the hotfix file name. Example: Windows 2000 Hotfix - KB329115.
z Patch
Application name: Use the base package’s application name. Package name: Describe the patch. Example: Sample_5.01_Update.
z Transform
Application name: If the transform is applied to a blank database, you might give it a unique application name, or group all such transforms under one application name (example: General Application Registration Transforms). If the transform is applied to a base package, use the base package’s application name.
Software Manager Reference 23
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. By default, a minimum number of critical .MSI tables are imported. However, you can import additional tables or all tables from the .MSI. Importing additional tables might significantly increase the time it takes to import a Windows Installer package.
Note
If you include the Binary table, the binary data itself is not imported to the Software Manager database. Instead, the CRC representation (checksum) of the binary data is imported.
You can create queries to v iew table data in Windows Installer packages in the Softw are Manager database. This provides complete access to the package data and lets you analyze that data. (Example: You can display all packages that contain isolated components, or all packages that contain certain launch conditions.)
See Windows Installer Table Queries on page 95. Software Manager preferences are stored in an .INI file located in the share point
directory. Therefore, these preferences affect all users who access the same share point. Do not edit the .INI file outside the Preferences dialog box.
To set Software Manager preferences
1. Select Setup menu > Preferences. The Preferences dialog box appears.
2. Specify the tables to include when a Windows Installer package is imported to the Software Manager database.
Import required tables only
This is the default. Mark this to import only the tables that are required for working in Software Manager and ConflictManager.
Import all tables
Mark this to import all columns in all tables in the .MSI. This includes any custom columns or tables.
Import required tables and additional tables
Mark this to include the required tables plus other tables you specify. When you mark this option, you must specify tables to include; see the next step.
Custom tables are not imported when you select this option, because they are not listed in the check boxes.
3. If you select Import required tables and additional tables, the check boxes become enabled.
Expand the top level check boxes to see lists of tables. To import a table, mark the top level check box as well as the table name below
Software Manager Reference 24
it. To mark all the check boxes, click Check All.
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.
4. Click OK.
Now, when a Windows Installer package is imported to the Softw are Manager database, the tables you specified are imported, provided they contain data. This does not affect packages that have already been imported.
About Package Meta Data
Expand the value of the Software Manager database by using meta data to store package information that is not otherwise recorded when the package is created.
z You can view meta data in the Package pane in Software Manager, provided
Package Pane is marked on the Meta Data Fields dialog box.
z You can view meta data on the Package Attributes dialog box in Software Manager
and ConflictManager.
z You can filter the Applications/Packages pane in Software Manager and
ConflictManager by a meta data value.
Introduction to Software Manager
z You can add meta data to custom reports as you would any other data in the
Software Manager database.
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.
Editing Meta Data
Edit custom meta data on the Package Attributes dialog box in Software Manager. If no meta data values are enabled, it means that custom meta data fields have not been defined.
The predefined meta data is read-only in Software Manager. To edit predefined meta data, use the Product Details page in Windows Installer Editor.
With Enterprise Management Server, Security Setup determines whether you can edit meta data in Software Manager.
See:
Viewing and Editing Package Attributes on page 93 Defining Custom Meta Data Fields on page 26
Examples of Package Meta Data
You can use meta data to specify:
z Whether an application is developed internally or purchased from a third party. z The type of license model the software uses.
Software Manager Reference 25
z How many licenses are purchased, in use, and available. z The language of the application. z Links to the purchasing department, such as purchase order number or URL to the
purchasing system.
z Package description. z Packager comments about limitations of the package. z Path to original source files. z Path to the package’s end user license agreement. z Path to support documents such as installation instruction s or con figuration options.
Defining Custom Meta Data Fields
You can define custom meta data fields to store package information that is not otherwise recorded when the package is created. Example: You can specify the type of license model the software uses.
See About Package Meta Data on page 25. You must define meta data fields before you can edit their values. The fields you define
appear on the Product Details page in Windows Installer Editor.
Introduction to Software Manager
They also appear on the Package Attributes dialog box in Software Manager and ConflictManager.
With Enterprise Management Server, Security Setup determines whether y ou can define meta data fields.
To define custom meta data fields
1. Select Setup menu > Meta Data Fields. The Meta Data Fields dialog box appears.
2. Click Add.
3. In Field Name, enter text to describe this meta data field and press Tab.
4. 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.
String
This field will accept any text entry.
External Link
This field will accept entry of a UNC path and file name or a URL, which will become an active hyperlink on the Package pane.
Integer
This field will only accept entry of a numeric character. The user can precede numeric characters with a hyphen to represent a negative number. Decimal points are not accepted.
Software Manager Reference 26
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.
See Defining a Custom Meta Data Type on page 27.
5. The text you enter in Description appears in a tooltip for this meta data field on the Product Details page in Windows Installer Editor.
6. Package Pane is marked by default, which causes this field to appear in the Package pane in Software Manager. If you clear this check box, this field will be visible in the Package Attributes dialog box only.
7. The meta data fields are displayed to the user in the order they are listed here . To rearrange the order, click Move Up or Move Down.
8. When you finish adding meta data fields, click OK.
Changing and Deleting Meta Data Fields
z When you change the data type for a meta data field, data in that field is deleted
from all packages.
z When you delete a meta data field that is in use, that field is deleted from all
packages.
z You cannot delete or make changes to the predefined meta data fields.
See also:
Viewing and Editing Package Attributes on page 93
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 cont ains these values: per seat; per server; freeware; and none.
With Enterprise Management Server, Security Setup determines whether y ou can define custom meta data types.
To define a custom meta data type
1. Select Setup menu > Meta Data Fields. The Meta Data Fields dialog box appears.
2. Click Custom Data Types. The Custom Data Types dialog box appears. Two custom data types are predefined:
True/False and Yes/No. You can delete them if you don’t need them.
3. Click Add Type.
4. In Data Type Name, enter a descriptive name for the new data type.
5. Click Add Value.
6. In Values, enter a value that is valid for this data type.
Software Manager Reference 27
Introduction to Software Manager
7. Continue adding values as needed.
8. 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.
9. When you finish adding custom data types, click OK. The Data Type drop-down list on the Meta Data Fields dialog box contains the
custom data types you added.
Changing and Deleting Custom Meta Data Types
z When you change a value that is in use, fields using that value are changed to use
the new value.
z When you delete a custom data type that is in use, fields using that data type, and
all data associated with those fields in packages, are deleted.
z When you delete a value that is in use, records containing that value are deleted
from all packages.
See also:
Defining Custom Meta Data Fields on page 26
Scheduling Software Manager Tasks
¾ Enterprise Management Server only .
You can run Windows scheduled tasks that:
z Import packages into the Software Manager database from the share point
directory.
z Refresh package subscriptions.
To run these tasks, schedu le th em in the Wise Task Scheduler. The tasks run from the server and update information in the Software Manager database that is associated with that server. The tasks run in the background with a specified user account.
Note
The Wise Task Scheduler is not available in client installations of Wise Package Studio.
Note
If an error is encountered while running these tasks, a message is logged in the ImportServer.log file and the task continues with the next package. The ImportServer.log file is created in the Wise Package Studio\Import Server directory.
Requirements
z Wise Package Studio must be installed on the server that will run the tasks. The
tasks run on a single server for the share point directory and Software Manager database associated with that server.
To run the tasks on multiple Software Manager databases, install Wise Package Studio and schedule the tasks on the server associated with each database.
Software Manager Reference 28
Introduction to Software Manager
z The user account associated with each task must be the one under which Wise
Package Studio was installed and must be able to run Software Manager on the server.
z On the server, a data source must be registered for the database containing
package subscriptions and for each database that contains packages that are subscribed to. The data source name must match across all servers.
Example: Suppose your company has three teams, each with its own Software Manager database: Central, Region1, and Region2. The Region1 team subscribes to the Central database, so you must register the following data sources on the Region1 server: Region1, Central. The Region2 team subscribes to both the Central and the Region1 databases, so you must register the following data sources on the Region2 server: Region2, Region1, Central.
To schedule Software Manager tasks
1. Log on to the server.
2. Select Start menu > Programs > Symantec > Wise Package Studio > Wise Task Scheduler.
The Wise Task Scheduler dialog box appears.
3. From Task, select an option:
Wise Auto Import Service Wise Package Subscriptions
The Schedule list displays any tasks that have been created.
4. Click Add to create a new schedule, or double-click an existing schedule line to change it.
The Schedule Details dialog box appears.
5. Select options to schedule the task.
Frequency
Specify whether the task should run every minute, every hour, d aily, or weekly.
Account
Enter the domain name and user name under which the task should run. This defaults to the user who is currently logged on. To change the account, enter the domain name and user name using this syntax:
DOMAINNAME\user_name
Password
Enter the password for the user specified above.
Note
When this password is changed for this domain, it is updated in all scheduled tasks containing that password.
Starting Time
Specify the time at which the task should run. This field is not available if the frequency is every minute.
Select the day(s) of the week below
Software Manager Reference 29
If the frequency is weekly, mark the check box for each day on which the task should run.
Introduction to Software Manager
6. To save the changes, click OK. The new or updated task is displayed on the Wise Task Scheduler dialog box.
7. 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
Wise Software Repository Automation
Wise Software Repository Automation lets you automate the manipulation of objects in the Wise Software Repository without having to know the structure of the Software Manager database. You can use the Wise Software Repository Automation object model to automate the following:
z The import of packages into the Wise Software Repository
This includes any type of package that you can import with Software Manager except an InstallShield Developer Executable and any package that requires the Universal Import.
z The generation of custom Wise Software Repository reports
You can gener ate reports for files, registry keys, or shortcut s. Y ou use the properties of objects to specify the data that gets generated in the report. After you create collections of packages or resources, you can filter the collections to produce the desired output.
z The creation of groups and the generation of reports on groups
When you automate the import of packages into the Wise Software Repository, you can automate the creation of groups. You can also automate the generation of reports on groups.
To view the Wise Software Repository Automation Help, open RepositoryCOM.chm, which is in the Technical Documentation subdirectory of the Wise Package Studio installation directory.
Product Documentation
This documentation assumes that you are proficient in the use of the Windows operating system. If you need help using the operating system, consult its user documentation.
Use the following sources of information to learn about this product.
Online Help
The online help contains detailed technical information and step-by-step instructions for performing common tasks.
Access help in the following ways:
z To display context-sensitive help for the active window or dialog box, press F1. z To select a help topic from a table of contents, index, or search, select Help menu >
Help Topics.
Software Manager Reference 30
Introduction to Software Manager
Reference Manual
All the material in the online help is also available in a .PDF-format reference manual, which you can access by selecting Help menu > Re ference Manual.
Getting Started Guide
The Getting Started Guide contains system requirements and installation instructions. You can access a .PDF version of the Getting Started Guide from the Windows Start menu.
The installation and repository management sections of the Getting Started Guide are also available as online help. In the Wise Repository Manager, select Help menu > Help Topics, or click the Help button on any of the Wise Package Studio installation dialogs.
Release Notes
The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. T o access the release not es, select Release
Notes from the Symantec program group on the Windows Start menu.
Software Manager Reference 31
Chapter 2
Importing Packages
This chapter includes the following topics:
z About Importing Packages on page 32 z How to Get Packages Into the Software Manager Database on page 32 z About Formatted Text Strings in Registry Entries on page 34 z Package Import on page 34 z Package Subscription on page 74
About Importing Packages
Software Manager lets you import packages and their resource information into the Software Manager database.
You can copy, or subscribe to, packages from a different Software Manager database. When you import packages that are different versions of the same application, you
normally assign them to the same application. See About Applications and Packages on page 22.
How to Get Packages Into the Software Manager Database
When a package is referred to as being in the Software Manager database, it can mean any of the following:
z The package’s meta data has been added to the Software Manager database. z The package’s definition has been imported to the Software Manager database. z The package’s resources have been imported to the Software Manager database.
Adding Package Meta Data
(.MSI and .WSI files only.) When you specify an application and package name on the Product Details page in Windows Installer Editor and save the installation:
z A record for the package is created in the Software Manager database. z The package’s meta data is added. z The package status is set to New. z Resources are not added.
This lets you add package information to the Software Manager database early in the application integration process. It also eliminates the need to enter the meta data manually in Software Manager and ensures that every package in the database has meta data that meets your corporate standards.
Software Manager Reference 32
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:
z A record for the package is created in the Software Manager database. z The package status is set to Under Development. z Resources are not added. Typically, a package that you create in this way doesn’t
have resources, because the package might consist of a single file or command li ne.
See Creating a Package Definition File in the Wise Package Studio Help.
Importing Package Resources
When you use the Import Wizard in Software Manager, or when you use the Auto Import Service:
z If the package is not already in the Software Manager database, it is added along
with its meta da ta.
z Information about the package’s resources is added to the database. z Depending on the import options you select, the resources themselves might be
copied to the share point directory and their source paths updated in the installation.
This lets other team members view and share resources from the package. It also lets you manage the package in Software Manager and resolve conflicts.
See Package Import on page 34.
When to Add Packages to the Software Manager Database
Typically, you add packages to the Software Manager Database when certain milestones in the repackaging process are reached. Develop corporate standards for these milestones. Your Wise Package Studio process templates should reflect these standards and ensure that the importing occurs at the appropriate time.
Recommendations:
z When the installation is first created, add its meta data. z When the installation is ready for conflict management and testing, import its
resources.
z (For corporate developers.) When the installation is ready for release, import its
resources. If you import package resources too early in the development process, they are
likely to become outdated. (Example: .DLLs and .EXEs are updated frequently during a typical development process.) This makes it possible for others to use those outdated resources in their installations. Consider this when you develop corporate standards and procedures for importing and sharing resources.
Software Manager Reference 33
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.
Example: Application 1 creates a registry key under HKLM\Software\InstallDirK ey with a value of [$comp1]. Application 2 creates a registry key under HKLM\Software\InstallDirKey with a value of [$comp4]. During installation, both [$comp1] and [$comp4] evaluate to the same value. If these values were not resolved, ConflictManager would identify this as a conflict. However, because Software Manager resolves the values during import, and stores them in the Software Manager database, a conflict is not detected, which is the correct behavior.
SoftwareManager resolves all properties in a Windows Installer installation. In a WiseScript installation (.WSE), SoftwareManager resolves only the following predefined variables:
WiseScript variable Resolves to
%Common% Program Files\Common %fonts% Windows\Fonts %MainDir% Program Files\default maindir
%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.
Package Import
Use the Import Wizard in Software Manager to add a package and information about its resources into the Software Manager database.
The Import Wizard provides several options for importing packages. The pages in the Import Wizard differ depending on the type of package you import and where you import it from.
See Import Methods on page 35. During the import process, the following options might be available:
z Detect conflicts.
You can detect conflicts between the imported package and all other packages in the Software Manager database.
or, if default maindir is empty: Program Files
Software Manager Reference 34
Import Methods
Importing Packages
z Add the package to Revision Control.
See Revision Control on page 80.
z 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. With Enterprise Management Server, Security Setup determines whether this option appears.
The Wise Task Manager dialog box appears during package import and remains open until the operation is completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio.
See Wise Task Manager in the Wise Package Studio Help.
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. However, when you import a package as part of the Package Definition process, you can use a CD as the source because Package Definition copies the source files to the share point directory.
Import from the share point directory
To place a package into the share point directory and queue it for import, do either of the following:
z Use Package Distribution to distribute a package to the share point.
See Copying a Package to the Share Point Directory in the Wise Package Studio Help.
z Use the Package Definition tool in Work bench to create a package; clear the Import
into Software Manager check box.
See Creating a Package Definition File in the Wise Package Studio Help.
Then, open Software Manager and import the package. See Importing From the Share Point Directory on page 37. (Enterprise Management Server only.) You also can use the Auto Import Service
scheduled task to import packages from the share point automatically. See About the Auto Import Service on page 74.
Import a single package from any network or local drive
You can import a single package from any accessible drive. Use this method when packages have been distributed to a network drive, or when an installation has been saved to a local or network drive.
The following topics describe the types of packages you can import and provide instructions for importing each type of package:
Importing a Windows Installer File on page 40 Importing a WiseScript or SMS Installer File on page 43
Software Manager Reference 35
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 on page 61 Importing a Group Policy Object File on page 62 Importing an SOE Snapshot on page 64 Importing a Wise Package Definition File on page 66 Performing a Universal Import Without Converting or Repackaging on page 71
Import multiple packages from any network or local drive
You can import a group of packages from any accessible drive. Use this method when packages have been distributed to a network drive, or when an installation has been saved to a local or network drive.
See Importing Multiple Files on page 68.
Copy (subscribe to) packages from another database
(Enterprise Management Server only.) Use this method to resolve conflicts between your packages and packages in another Software Manager database. Also use this method to view resources from another database.
See Package Subscription on page 74.
Note
To export a package after resolving its conflicts, you must have access to the original installation and its associated files.
See also:
How to Get Packages Into the Software Manager Database on page 32
About Patch and Transform Import
You have two options for importing Windows Installer patches and transforms into the Software Manager database:
z Apply the patch or transform when you import the base package
The resources installed by the patch or transform are combined with the resources installed by the base package and displayed together as a single package in Software Manager.
This lets you resolve conflicts in files that are installed by the patch or transform. The package is changed so that when you distribute it, the changes made by the patch or transform are included.
z Import the patch or transform separately from the base package
A relationship is created between the patch or transform package and the base package. The resources installed by the patch or transform a re di splay ed se par ately in Software Manager. This lets you:
Maintain dependencies and sequencing of patches and transforms. Store meta data for a patch or transform.
Software Manager Reference 36
Importing Packages
Group patches and transforms to determine the collective impact of those
patches or transforms during testing and deployment.
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. Wise Connector imports the patch or transform when it imports the base MSI package. You can then use Software Managem ent Solution to deploy the patch or transform.
Defining the State of the Base Package
When you import a patch or transform, you can specify additional transforms to be applied to the base package before the patch or transform you are importing. This changes the state of the base package, which determines the resources that are 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.
z The Base Package installs File A, File B, and File C. z Transform 1 deletes File C. z Transform 2 installs Registry Key X and modifies File C.
When you apply the transforms like this:
Base Package Transform 2 Base Package Transform 1 Transform 2
See:
Importing a Windows Installer Patch File on page 51 Importing a Transform File on page 48 Package Groups on page 87
Importing From the Share Point Directory
When the Database pane displays a number of packages that are queued for import, use the Import from share point directory option in the Import Wizard to import the packages into the Software Manager database.
When a package is distributed to the share point directory, the package and its source files are copied to several subdirectories of the share point directory, and a .QUE file is created to represent the package that is waiting to be imported into the Software Manager database.
Transform 2 does this during installation:
installs Registry Key X modifies File C installs Registry Key X File C is not present, because the state of
the Base Package has been changed by applying Transform 1.
When a package is created with Package Definition and not imported directly into the Software Manager database, the package definition file (.WPF) is saved in the share point directory, its files are copied to the share point directory, and a .QUE file is created.
Software Manager Reference 37
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.
See About .QUE Files on page 40 and How Source Files Are Indexed in the Wise Package Studio Help.
(Enterprise Management Server only.) You also can use the Auto Import Service scheduled task to import packages from the share point automatically.
See About the Auto Import Service on page 74.
Note
When you use either Windows Installer Editor or WiseScript Editor to add files to a package that has already been distributed to the share point directory and imported, a prompt appears asking if you want to add the new files to the share point directory. If you do so, the .QUE file for that package is reset and you must re-import the package in Software Manager. If you have already detected conflicts for that package, you must also redo the conflict detection process.
To import a package from the share point directory
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. 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 or because Wise package definition files do not have source files.
The following items become enabled:
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of meta data or a package definition.
Do not modify the original package
Normally, when you import a Windows Installer installation (.MSI or .WSI), the original installation file is updated with Wise-specific version information that speeds future subscriptions and imports of the installation. Mark this to prevent the original file from being changed.
Software Manager Reference 38
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
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.
4. To assign all packages that are imported during this session to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
5. Click Next on the Import Type page. The Packages to Import page appears, listing all packages that are in the share
point and have not been imported.
6. All check boxes in the Packages to Import page are marked. Clear the check boxes for any packages you do not want to import.
Packages you do not select now will reappear on this page the next time you import from the share point directory.
7. Click Finish. The packages you selected are imported into the active Software Manager database.
When the import process is finished, the Import Complete page appears, displaying a log of the import process.
8. T o sav e the import log as a text file, click Sav e and then choose a name and location for the log file. The default file name is Import Log.log.
9. To close the Import Complete page, click Close.
For information on how the application and package names are assigned, see About
Applications and Packages on page 22.
When you import a Windows Installer package, Software Manager preferences determine which of the .MSI tables are imported into the Software Manager database: a minimum number of required tables; or the required tables plus additional tables you specify; or all tables. Importing additional tables can significantly increase the time it takes to import a Windows Installer package. Empty tables are not imported.
Software Manager Reference 39
Importing Packages
See Setting Software Manager Preferences on page 24.
See also:
Revision Control on page 80 Package Import on page 34
About .QUE Files
When you use Package Distribution to distribute to the share point directory or Package Definition to queue a package for imp ort, temporary files are created in the Scripts subdirectory. These files, which have the same name as the installation file but with the extension .QUE, represent packages that have been distributed but not imported into the Software Manager database.
In Software Manager, the Database pane displays the number of packages that are Queued for Import. This represents the number of .QUE files in the Scripts directory.
When you import from the share point directory , eit her manually in Software Manager or by running the Auto Import Service scheduled task, the share point is searched for .QUE files. When one is found, the package it represents is imported into the Software Manager database. The .QUE file is removed after the package is imported.
Importing a Windows Installer File
You can import a single Windows Installer installation (.MSI or .WSI) into the Software Manager database from a network or local drive.
When you import an .MSI, you can specify one or more transforms or patches to be applied to the package. The additional resources in the transform or patch are added to the installation package’s resources in Software Manager so that they can be included in queries or reports of shared resources. To add the additional resources to a separate package in the Software Manager database instead, import the transform or patch separately.
See Importing a Transform File on page 48 or Importing a Windows Installer Patch File on page 51.
Software Manager preferences determine whi ch of the .MSI tabl es are import ed into the Software Manager database: a minimum number of required tables; or the required tables plus additional tables you specify; or all tables. Importing additional tables can significantly increase the time it takes to import a Windows Installer package. Empty tables are not imported.
See Setting Software Manager Preferences on page 24. 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.
See How to Get Packages Into the Software Manager Database on page 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.
Software Manager Reference 40
Importing Packages
To import a Windows Installer file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify an .MSI or .WSI to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. 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.
Warning
Distributing source files for a package that represents a Visual Studio integrated project breaks the integration with the Visual Studio solution.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of meta data or a package definition.
Do not modify the original package
Normally, when you import a Windows Installer installation (.MSI or .WSI), the original installation file is updated with Wise-specific version information that speeds future subscriptions and imports of the installation. Mark this to prevent the original file from being changed.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
Detect conflicts during package import
Software Manager Reference 41
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.
Importing Packages
If this is marked, conflict detection checks for conflicts between the imported package and all other packages in the Software Manager database.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.MSI/.WSI File
The file you specified is displayed.
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.
Note
If the package’s meta data is in the Software Manager database or the package was created in Wise Package Studio, Application Name and Package Name are pre-filled. In that case, don’t change these names. Otherwise, you will have two packages in the database for the same installation: a package with just meta data and the package you import.
For information on application and package names, see About Applications and
Packages on page 22.
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. This speeds the import, but can lock Software Manager database records temporarily during the update. Use this option if you are the only person importing packages. If multiple people are importing packages at one time, do not mark this check box.
9. If you specified a .WSI, click Finish and skip the remaining steps.
10. If you specified an .MSI, click Next. If the Software Manager database contains one or more patches (.MSP) that apply
to this .MSI, the Existing Patches page appears and lists them. Otherwise, the Transforms and Patches page appears.
Software Manager Reference 42
Importing Packages
11. If the Existing Patches page appears, you can click Save to save the list of patches to a text file.
12. Click Next on the Existing Patches page. The Transforms and Patches page appears.
13. To apply a transform or patch to this .MSI before importing it into the Software Manager database, click Add on the Transforms and Patches page and specify the transform or patch. Specify additional transforms or patches if needed. The transforms and patches are applied to the package in the order they appear in the list. To rearrange the order, click Move Up or Move Down.
14. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
Note
If the import fails and its log file indicates that some files cannot be found, the source file paths might be absolute or the source files might have been deleted. Verify that the source files are in the correct locations. To avoid this problem, store installations and their source files in a shared directory instead of on a local drive.
See also:
Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Importing a WiseScript or SMS Installer File
You can import a single WiseScript installati on (.WSE) or SMS Installer installation (.IPF) into the 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 c a n then use Software Management Solution to distribute it.
To import a WiseScript or SMS Installer File
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify a .WSE or .IPF to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
Software Manager Reference 43
5. 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.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
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.
Importing Packages
If this is marked, conflict detection checks for conflicts between the imported package and all other packages in the Software Manager database.
Add to Revision Control
Mark this to add the package to Revision Control during import.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.WSE/.IPF File
The file you specified is displayed.
Software Manager Reference 44
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.
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. This speeds the import, but can lock Software Manager database records temporarily during the update. Use this option if you are the only person importing packages. If multiple people are importing packages at one time, do not mark this check box.
Setup Executable
This option is used only with .WSE files created in version 7.03 or earlier of InstallMaster, any version of InstallMaker and InstallBuilder, or any version of the Wise Installation System - Standard Edition. Specify the compiled .EXE file for this installation. If Software Manager can’t find the necessary file information stored in the installation file or in the package’s source path, it extracts the necessary files from the setup executable to a temporary directory, then collects the data and removes the temporary directory and its contents.
9. Click Finish.
Importing Packages
The Wise Task Manager dialog box appears and remains open until the operation is completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
Note
If the import fails and its log file indicates that some files cannot be found, the source file paths might be absolute or the source files might have been deleted. Verify that the source files are in the correct locations. To avoid this problem, store installations and their source files in a shared directory instead of on a local drive.
See also:
Importing Multiple Files on page 68 Package Import on page 34 Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Importing a Merge Module File
You can import a Windows Installer merge module (.MSM or .WSM) into the Software Manager database from a network or local drive. This lets you:
Software Manager Reference 45
Importing Packages
z 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.
z 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.
You cannot resolve conflicts in or export a merge module package, because changing a merge module affects all packages that use the merge module. However, you can change packages that conflict with the merge module. Typically, you do this outside Software Manager, by removing the files and other resources included in the merge module from the package, and adding the merge module to the package.
To import a merge module file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify an .MSM or .WSM to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. 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.
If you mark this check box, the source files are ava ilable so you can add a merge module from the Software Manager database to an installation.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Software Manager Reference 46
Mark this to add the package to Revision Control during import.
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.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.MSM/.WSM File
The file you specified is displayed. For information on application and package names, see About Applications and
Packages on page 22.
Package Name
Enter a unique name to identify this package. 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. This speeds the import, but can lock Software Manager database records temporarily during the update. Use this option if you are the only person importing packages. If multiple people are importing packages at one time, do not mark this check box.
9. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Software Manager Reference 47
Importing a Transform File
You can import a Windows Installer transform (.MST) into the Software Manager database from a network or local drive. This creates a separate package for the transform and keeps the transform’s resources separate from the resources in the base package.
T o add the transform’ s resources to the base package instead, apply the transform when you import the base installation. When you do this, you cannot distribute the transform as a separate entity.
You can distribute the transform as part of a group for easy deployment by a distribution system.
See Creating a Package Definition on page 115 and Creating Package Groups on page 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 databa se int o So f t ware Management Framework. Wise Connector imports the transform when it imports the base MSI package. You can then use Software Management Solution to distribute the package.
Importing Packages
See Importing a Windows Installer File on page 40.
Options for Applying Imported Transforms
z Apply the transform to a blank Windows Installer database (schema.msi).
The resulting transform package includes additions only and excludes deletions and modifications. The transform package has no dependencies. You might use this option when you have a standard, corporate transform that you apply to all packages. (Example: General Application Registration Transforms.)
When you apply the transform to a blank Windows Installer database, you cannot resolve conflicts in or export the transform package.
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. When you import the transform and apply it to a blank database, File 2 is imported as a resource but not File 1.
Certain transforms cannot be applied to a blank database. The transform you specify is checked before the import begins and a message appears if it cannot be applied to the blank database.
z Apply the transform to a base package.
The resulting transform package includes all additions, deletions, and modifications to the base package. The transform package is designated as a dependent of the base package.
When you apply the transform to a base package, you can resolve conflicts in and export the transform package.
Software Manager Reference 48
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.
See About Patch and Transform Import on page 36.
To import a transform file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify an .MST to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. 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.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
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.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears.
Software Manager Reference 49
Importing Packages
b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.MST File
The file you specified is displayed.
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.
Package Name
Enter a unique name to identify this package. To replace an existing package, select a package from the drop-down list.
9. Click Next on the Package Details page. The Select Target Package page appears, where you set dependencies for this
package.
10. Complete the page. You have two options:
Mark Apply transform to a blank Windows Installer database to include
only additions in the transform package.
Select the Application Name and Package Name of the base package to
include all additions, deletions, and modifications in the transform package. The drop-down lists contain only packages that are in the Software Manager
database. If the base package is not in the Software Manager database, cancel this import process and import it. If the base package you specify is a .WSI with multiple releases, select the release that this transform applies to.
11. Do one of the following:
If you marked the Apply transform to a blank Windows Installer database
check box, click Finish on the Select Target Package page and skip the next steps.
If you cleared the Apply transform to a blank Windows Installer database
check box, click Next on the Select Target Package page. The Select Additional Transforms page appears, listing other transform
packages in the Software Manager database.
12. To define the state of the base package, you can specify additional transforms to be applied to the base package before the transform you are importing.
Software Manager Reference 50
Importing Packages
Select a transform and click one of the Move buttons to move it to or from the
Transforms Not Included and Included Transforms lists.
The transforms are applied to the package in the order they appear in the list.
To rearrange the order, click Move Up or Move Down.
13. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
Note
If the import fails and its log file indicates that some files cannot be found, the source file paths might be absolute or the source files might have been deleted. Verify that the source files are in the correct locations. To avoid this problem, store installations and their source files in a shared directory instead of on a local drive.
See also:
Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Importing a Windows Installer Patch File
You can import a single Windows Installer patch (.MSP) into the Software Manager database from a network or local drive. This creates a separate package for the patch and keeps the patch’s resources separate from the resources in the base package. The patch package is designated as a dependent of the base package. Y ou can distri bute the patch as part of a group for easy deployment by a distribution system.
A patch can apply to multiple packages. To apply a patch to another package, re-import the patch and specify a different base package on the Select Target Package page. The contents of this second package might differ from the first one, depending on the contents of the base packages.
You can define the state of the base package, which determines the resources that are included in the imported patch package and changes how it behaves when it is deployed.
See About Patch and Transform Import on page 36. To add the patch’s resources to the base package instead, apply the patch when you
import the base installation. When you do this, you cannot distribute the patch as a separate entity.
See Importing a Windows Installer File on page 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. You can then use Software Management Solution to distribute the package.
Software Manager Reference 51
Importing Packages
To import a Windows Installer patch file
1. Verify that the base package that the patch applies to is in the Software Manager database.
2. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
3. Select Packages menu > Import. The Import Type page appears.
4. Mark Import a single file into the Software Manager database.
5. In File, specify an .MSP to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
6. 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.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
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.
7. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. Click OK.
Software Manager Reference 52
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.
8. Click Next on the Import Type page. The Package Details dialog box appears.
9. Complete the dialog box:
.MSP File
The file you specified is displayed.
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.
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.
11. Complete the page. The drop-down lists contain only packages in the Software Manager database that
are valid targets of the patch you are importing. If the base package is not in the Software Manager database, cancel this import process and import it.
Application Name
Select the application that contains the base package that this patch applies to.
Package Name
Select the base package that this patch applies to. You can apply a patch to another patch.
Release
If the base package you specify is a .WSI with multiple releases, select the release that this patch applies to.
12. Click Next on the Select Target Package page. The Select Additional Transforms page appears, listing transform packages in the
Software Manager database.
13. To define the state of the base package, you can specify transforms to be applied to the base package before the patch you are importing.
Select a transform and click one of the Move buttons to move it to or from the
Transforms Not Included and Included Transforms lists.
The transforms are applied to the package in the order they appear in the list.
14. Click Finish.
Software Manager Reference 53
To rearrange the order, click Move Up or Move Down.
The Wise Task Manager dialog box appears and remains open until the operation is completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The patch you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Importing an InstallShield Developer Executable
You can import an InstallShield® Developer executable (version 7 or 8 only) into the Software Manager database from a network or local drive. Do this to detect file and resource conflicts between an InstallShield Developer installation and other packages, but you cannot or do not want to repackage the InstallShield installation. Corporate developers also can do this when they have applications whose installations were created in InstallShield Developer and they cannot or do not want to convert them.
The Import Wizard reads the .EXE, extracts information about any .MSI that is embedded in the .EXE, then creates an application and package for the .MSI in the Software Manager database. If multiple .MSIs are embedded in the InstallShield .EXE, then an application and package is created for each .MSI. You also can choose to have the installation’s source files copied to the share point directory.
Importing Packages
You cannot resolve conflicts in or export an InstallShield Developer package, because neither the original .EXE nor its embedded .MSIs can be edited or recompiled. However, you can change packages that conflict with the InstallShield Developer installation.
You can distribute an InstallShield package as part of a group for easy deployment by a distribution system. To do so, import the InstallShield package, create a package definition file, and then add it to a group for deployment.
See Creating a Package Definition on page 115 and Creating Package Groups on page 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.
Note
You can convert an InstallShield Profes sional installation to an .MSI if you have access to a script project file (.IPR) that was created in version 5.5 or higher of InstallShield® Professional.
See InstallShield Professional Conversion Guidelines in the Wise Package Studio Help.
To import a single InstallShield Developer executable
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Software Manager Reference 54
Importing Packages
2. Select Packages menu > Import. The Import Type page appears.
3. 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.
4. In File, specify an InstallShield Developer .EXE to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. 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.
Even though you cannot export or compile an InstallShield Developer package, you might want to copy the source files so you can use them for conflict management. Example: If the InstallShield Developer installation uses version
2.0 of report.dll, and another package uses version 1.0, you can change the other package to use the newer version of report.dll contained in the InstallShield Developer package.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
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.
If the package you specify is not recognized as an importable package type, the Universal Import page appears. To continue the import, click Next and see
Performing a Universal Import Without Converting or Repackaging on page 71.
6. Click Next on the Import Type page.
Software Manager Reference 55
Importing Packages
The Package Details page appears. The file you specified is displayed. You do not have to specify an application and
package name because they are obtained from information in the executable.
7. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The InstallShield Developer executable you selected is imported to the active Software Manager database. If the .EXE contains multiple .MSIs, a separate application and package is created for each .MSI.
See also:
Importing Multiple Files on page 68 Package Import on page 34 Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Importing a Microsoft Hotfix File
You can import a Microsoft hotf ix file (.EXE) into the Softw are Manager database from a network or local drive. This lets you:
z Group hotfixes with their related packages during distribution. z View the contents of a hotfix in Software Manager so you can determine exactly
what it installs.
z Resolve conflicts between hotfixes and other packages.
The Import Wizard supports most of the Microsoft hotfix file formats. Hotfix files of unsupported formats are imported using the Universal Import feature.
See Performing a Universal Import Without Converting or Repackaging on page 71. You can import a hotfix as a stand-alone package or as a dependent of a base package.
A hotfix can be a dependent of multiple packages. Use Package Relationships to define additional dependencies on a hotfix.
You can distribute a hotfix as part of a group for easy deployment by a distribution system. To do so, import the hotfix file, create a package definition file, and then add it to a group for deployment.
See Creating a Package Definition on page 115 and Creating Package Groups on page 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 it.
Software Manager Reference 56
Importing Packages
To import a Microsoft hotfix file
1. If you will apply the hotfix to a base package, verify that the base package is in the Software Manager database.
2. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
3. Select Packages menu > Import. The Import Type page appears.
4. Mark Import a single file into the Software Manager database.
5. In File, specify a hotfix .EXE to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
6. 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.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
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.
If the package you specify is not recognized as an importable package type, the Universal Import page appears. To continue the import, click Next and see
Performing a Universal Import Without Converting or Repackaging on page 71.
7. To assign the imported package to one or more groups:
Software Manager Reference 57
Importing Packages
a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
8. Click Next on the Import Type page. The Package Details dialog box appears.
9. Complete the dialog box:
.EXE File
The file you specified is displayed.
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.
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.
11. Complete the page:
Mark Import hotfix standalone?. Because a hotfix contains full files instead
of binary differences, it does not have to depend on a base installation.
Select the Application Name and Package Name of the base package.
T ypically, this will be an SOE Snapshot (example: Microsoft 2000). The resulting hotfix package will have a dependency on the base package.
The drop-down lists contain only packages that are in the Software Manager database. If the base package is not in the Software Manager database, cancel this import process and import it. If the base package you specify is a .WSI with multiple releases, select the release that this hotfix applies to.
12. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The hotfix you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Software Manager Reference 58
Package Import on page 34 Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Importing a Virtual Software Package File
You can import a single virtual software package (.WVP or .VSA) into the Software Manager database from a network or local drive. One reason to import virtual software packages is for purposes of impact and risk assessment.
See Impact and Risk Assessment on page 125. A .VSA file is a virtual software archive file. A .WVP file is a virtual software project file
that compiles to a .VSA file. See Integration with Software Virtualization Solution in the Wise Package Studio Help. When you import a .VSA file into Software Manager, it is converted to a .WVP file.
Because of this, only .WVP files are actually imported into the Software Manager database. However, when you import a .VSA file, it is copied to the share point, and when you distribute a .WVP file, its compiled .VSA file is distributed.
Importing a .VSA or .WVP file requires the Software Virtualization Agent to be installed on your computer.
Importing Packages
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 c a n then use Software Management Solution to distribute it.
To import a virtual software package file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify a .WVP or .VSA to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. The following item becomes 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.
Overwrite existing application and package
Software Manager Reference 59
Mark this to overwrite any package that is already in the database with the same application and package names. If you clear this check box and the application and package names are already in the database, the new package is not imported.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.WVP/.VSA File
The file you specified is displayed. For information on application and package names, see About Applications and
Packages on page 22.
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.
9. Click Finish on the Package Details page. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The .WVP file package is imported into the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Package Import on page 34 Revision Control on page 80
Wise Task Manager in the Wise Package Studio Help
Software Manager Reference 60
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:
z Identify file and registry conflicts that could occur if you were to introduce a specific
device into your desktop environment. You cannot resolve conflicts in or export a device driver package, because the changes would not be supported by the vendor. However, you can change packages that conflict with the device driver.
z Distribute a device driver package as part of a group for easy deployment by a
distribution system. To do so, import the device driver, create a package definition file, and then add it to a group for deployment.
See Creating a Package Definition on page 115 and Creating Package Groups on page 88.
An .INF file can contain multiple manufacturers and devi ces. When yo u import the dr iver information, an application is created for each manufacturer, and a package is created for each device. The device ID is appended to each device name. File information (example: version, date, time, and so on) is obtained from .CAB files that are referenced by the .INF file. Enumerated registry keys are identified in Software Manager and ConflictManager as ENUM(0000). Enumerated entries do not cause conflicts because their values are set at run time.
Importing Packages
To import a single device driver file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify an .INF to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. The following item becomes enabled:
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Software Manager Reference 61
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.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Finish on the Import Type page. You do not have to specify an application and package name because .INF files are
imported using the manufacturer as the application name and the device as the package name.
If you perform a local import and a .CAB referenced in the .INF file could not be found, you are prompted to insert the manufacturer’s installation disk and specify the source file location. If the .INF does not contain a reference to the .CAB, y ou are prompted to browse for the source file. If you perform the import on the Wise Package Studio Server, no prompts appear and these errors are added to the log file for the import.
The Wise Task Manager dialog box appears and remains open until the operation is completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The device driver you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Importing Multiple Files on page 68 Package Import on page 34
Wise Task Manager in the Wise Package Studio Help
Importing a Group Policy Object File
You can import registry-based group policies found in administrative templates into the Software Manager database from a network or local drive. Policies in an administrative template (.ADM) file relate to registry settings that control the behavior and appearance of the desktop and components of the operating system. To import the policies to Software Manager, you must export the .ADM file to a .POL file, using the Group Policy snap-in. For more information about group policy and administrative templates, see Administrative Template File Format and Registry Poli cy File Format in the MSDN Library (msdn.microsoft.com/library/), or refer to the Group Policy snap-in Help.
Software Manager Reference 62
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. This isn’t a typical conflict that you can resolve by changing the registry keys; you cannot change or export a Group Policy Object. However, the conflict provides information to help you manage your desktops; you can make a decision about installing a package that will override your policy, or you might work with your system administrator to change the group policy for end users who need that package.
You can distribute a group policy package as part of a group for easy deployment by a distribution system. T o do so , import the group policy object, create a package definition file, and then add it to a group for deployment.
See Creating a Package Definition on page 115 and Creating Package Groups on page 88.
To import a group policy object file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify a .POL to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. The following item becomes enabled:
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
Detect conflicts during package import
Software Manager Reference 63
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.
Importing Packages
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.POL File
The file you specified is displayed.
Application Name, Package Name
Normally, an application can have multiple packages. However, for best results when working with Group Policy Objects, create one application/package combination per Group Policy Object. Enter the application and package name to use for this Group Policy Object in the Software Manager database.
Policy Type
Because the .POL file does not contain the root registry key in which the Group Policy Object key is installed, you must specify it here. Select User
Configuration if the GPO key is installed in HKEY_CURRENT_USER, or select Computer Configuration if the GPO key is installed in
HKEY_LOCAL_MACHINE.
9. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The Group Policy Object you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Importing Multiple Files on page 68 Package Import on page 34
Wise Task Manager in the Wise Package Studio Help
Importing an SOE Snapshot
You can import an SOE Snapshot file (.SOE) from a network or local drive into the Software Manager database to represent the base software of a computer in your organization. This lets you look for conflicts not just between applications, but also between applications and the operating system.
See SOE Snapshot in the Wise Package Studio Help.
Software Manager Reference 64
Importing Packages
To import an SOE snapshot
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify an .SOE to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. 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 source files in the SOE Snapshot from being used to resolve conflicts in other packages.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
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.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. Click OK.
Software Manager Reference 65
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.
7. Click Next on the Import Type page. The Package Details dialog box appears.
8. Complete the dialog box:
.SOE File
The file you specified is displayed.
Application Name
To create a new application, enter the operating system name. (Example: Windows 2000.) To add this package to an existing SOE Snapshot application, select the application from the drop-down list.
For information on application and package names, see About Applications and
Packages on page 22.
Package Name
Enter a unique name to identify this SOE Snapshot package in the Software Manager database. Typically, enter the operating system name, its service pack, and the base applications. If the base applications are for a particular department, you could replace them with the department name. Example: An application named Windows XP might contain packages named Windows XP SP1 with Office or Windows XP SP1 for Accounting.
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. This speeds the import, but can lock Software Manager database records temporarily during the update. Use this option if you are the only person importing packages. If multiple people are importing packages at one time, do not mark this check box.
9. Click Finish. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The SOE Snapshot file you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Package Import on page 34
Wise Task Manager in the Wise Package Studio Help
Importing a Wise Package Definition File
You can import a single Wise package definition file (.WPF) into the Software Manager database from a network or local drive. This refers only to package definition files that
Software Manager Reference 66
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. However, if the package definition file is saved in a different share point directory from the one you’re using, use the procedure below to import it.
For information on creating and using a package definition file in Workbench, see InstallShield .MSI Conversion Guidelines in the Wise Package Studio Help.
The files in the Wise package definition are in the Projects subdirectory of the share point. When you import a package definition file, its files do not appear in Software Manager.
To import a Wise package definition file
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify a .WPF to import. Be sure to select the appropriate file type from the Files of type drop-down list on the Open dialog box.
5. The following item becomes enabled:
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names. If you clear this check box and the application and package names are already in the database, the new package is not imported.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
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.
6. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. Click OK.
Software Manager Reference 67
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.
7. Click Finish on the Import Type page. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The package you selected is imported to the active Software Manager database. During the import process, errors are displayed as they are encountered.
See also:
Package Import on page 34 Importing From the Share Point Directory on page 37
Wise Task Manager in the Wise Package Studio Help
Importing Multiple Files
You can import a bat ch of package s from an y network or local di re ctory you can access. Use this method when you use the Network distribution method in Package Distribution, or when the installations are saved on a network or local directory. When you import multiple packages, all packages you specify must be of the same type. You can import multiple packages of the following types:
z Windows Installer installation (.MSI, .WSI) z Virtual software package (.VSA, .WVP). z WiseScript / SMS Installer installation (.WSE, .IPF) z Merge Module (.MSM, .WSM) z (Not available in Standard Edition.) InstallShield Developer setup.exe (.EXE) z (Not available in Standard Edition.) Device driver (.INF) z (Not available in Standard Edition.) Group Policy Object (.POL)
When you import a Windows Installer package, Software Manager preferences determine which of the .MSI tables are imported into the Software Manager database: a minimum number of required tables; or the required tables plus additional tables you specify; or all tables. Importing additional tables can significantly increase the time it takes to import a Windows Installer package. Empty tables are not imported.
See Setting Software Manager Preferences on page 24.
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. However, when you import a package as part of the Package Definition process, you can use a CD as the source because Package Definition copies the source files to the share point directory.
Software Manager Reference 68
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.
See How to Get Packages Into the Software Manager Database on page 32.
To import multiple files
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Import multiple files into the Software Manager database. 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.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of meta data or a package definition.
Do not modify the original package
Normally, when you import a Windows Installer installation (.MSI or .WSI), the original installation file is updated with Wise-specific version information that speeds future subscriptions and imports of the installation. Mark this to prevent the original file from being changed.
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. If the packages and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setu p determines whether this option appears.
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.
4. To assign all packages that are imported during this session to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears.
Software Manager Reference 69
If this is marked, conflict detection checks for conflicts between the imported package and all other packages in the Software Manager database.
Importing Packages
b. Mark the check boxes of the groups to assign the package to. c. 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.
5. Click Next on the Import Type page. The Select Package Type page appears, containing options for the types of files you
can import.
6. Mark the option for the type of file to import and click Next. The Package Search page appears.
7. In Search Directory, specify a directory to search for files to import. To search for files in subdirectories of the directory you specify, mark Search subdirectories.
Example: If you are using projects to or ganize y our package files, y ou might specify the Projects subdirectory of your share point directory, and mark the check box to search all subdirectories of the Projects directory.
8. Click Next on the Package Search page. The Packages to Import page appears, listing all packages of the specified type that
are in the directory you entered.
9. All check boxes in the Files to Import page are marked. Clear the check boxes for any packages you do NOT want to import.
The Files to Import page lists all packages of the specified format in the directory you specified, including packages you have already imported. If you don’t want to re-import those packages, either clear their check boxes on this page or back up to the Import Type p age and clear Overwrite existing application and package.
10. T o import a package that is not listed on the P ackages to Import page, click Add and specify the file.
The package you specified is added to the list on the Packages to Import page with its check box marked. Repeat this step to add other files to the list.
11. Click Finish on the Packages to Import page. The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your work in Wise Package Studio. From this dialog box, you can view a log file for the import.
The packages you selected are imported into the active Software Manager database. However, if you selected .VSA packages, they are converted to .WVP packages and only the .WVP packages are imported.
For information on how the application and package names are assigned, see About
Applications and Packages on page 22.
See also: Wise Task Manager in the Wise Package Studio Help
Software Manager Reference 70
Importing Packages
Performing a Universal Import Without Converting or Repackaging
You can use the Import Wizard’s Universal Import option to import any 32-bit setup program into the Software Manager database from a network or local drive without converting or repackaging. Do this to get information about the resources installed by a non-Windows Installer or non-WiseScript installation. This provides a quick way to determine if the installation conflicts with other packages. If no conflicts are found when you import the installation directly, and if you do not need to make any other changes to the installation, you might decide to distribute the original executable. In other instances, you might use this to identify conflicts between ne wly repackaged applications and legacy setup.exe installations that have already been deployed and that you have no intention of repackaging. Corporate developers can use this to view resources for non-Windows Installer installations without converting them.
The Universal Import is also triggered when you mark the option to import a single file, and you specify an .EXE file that is not recognized as an importable package type.
The Import Wizard uses Virtual Capture™ technology to extract information from the installation file, and then saves the captured information to the Software Manager database, creating an application and package. You also can choose to have the installation’s source files copied to the share point directory.
Universal Import uses a Virtual OS created in the Virtual OS Creation utility, which you must create before using the procedure below. See Creating a Virtual OS in the Wise Package Studio Help. Verify that your environment meets the conditions for using Universal Import. See Using SetupCapture With Virtual Cap ture in the Wise Package Studio Help. The Virtual Capture process described in this procedure uses the same SetupCapture Configuration settings you have set in Wise Package Studio. (See SetupCapture Configuration in the Wise Package Studio Help.)
You cannot resolve conflicts in or export a non-Windows Installer or non-WiseScript package, because the original installation file cannot be edited. However, you can change packages that conflict with the installation.
You can distribute a non-Windows Installer or non-WiseScript package as part of a group for easy deployment by a distribution system. To do so, import the package, create a package definition file, and then add it to a group for deployment.
See Creating a Package Definition on page 115 and Creating Package Groups on page 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.
To import any installation file without converting or repackaging
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Packages menu > Import. The Import Type page appears.
3. Mark Universal Import. The following items become enabled:
Software Manager Reference 71
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. Example: If the installation uses version 2.0 of report.dll, and another package uses version 1.0, you can change the ot her package to use the n ewer version of report.dll contained in the installation file.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the same application and package names.
If you clear this check box and the application and package names are already in the database:
If the existing package has resources, the new package is not imported.If the existing package does not have resources, the new package’s
resources are added to the existing package. An ex istin g pac kage mi ght not have resources if it consists only of a package definition.
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. If the package and the Software Manager database reside on the server, this significantly improves the performance of this operation for large packages. With Enterprise Management Server, Security Setup determines whether this option appears.
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.
4. To assign the imported package to one or more groups: a. Click Groups on the Import Type page. The Select Groups dialog box appears. b. Mark the check boxes of the groups to assign the package to. c. 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.
5. Click Next on the Import Type page. The Virtual OS File Selection page appears.
6. On the Virtual OS File Selection page, specify a Virtual OS to use. You must have run the Virtual OS Creation utility on the current computer or another computer.
See Creating a Virtual OS in the Wise Package Studio Help.
Software Manager Reference 72
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 another network directory. Then specify the .WOS file to use.
7. Click Next. The Begin Installation Capture page appears.
8. Click Next.
If you selected the existing Virtual OS file, the Virtual OS is cleaned. This means
that installed remnants from the last capture or universal import are removed from the Virtual OS directory and registry structure.
If you selected a .WOS file, it is expanded onto your computer to form a Virtual
OS directory and registry structure. This process takes several minutes and requires a substantial amount of free disk space.
The Package Details dialog box appears.
9. Complete the dialog box:
.EXE File
Specify an .EXE to import. This cannot be a 16-bit application (designed to run on 16-bit operating systems). Virtual Capture only works on 32-bit applications.
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.
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.
10. Click Next on the Package Details page.
Note
It is very important to start installations from this page by clicking Next. If you start them outside this page, the Import Wizard is unaware of the changes that occur.
The installation opens. Run through the installation normally. The installation is simulated; it is not really installed on your computer. Files and registry entries are redirected into the Virtual OS on your computer.
The Finish page appears.
11. Click Finish to complete the import process.
Software Manager Reference 73
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 excl usion settings in SetupCapture Configuration.
See also:
Package Import on page 34
About the Auto Import Service
¾ Enterprise Management Server only .
You can run a Windows scheduled task that im ports packages i nto the Softwa re Manager database automatically. The Wise Auto Import Service task periodically searches the share point directory for .QUE files, which represent distributed packages that are waiting to be imported. When the service finds a .QUE file, it imports that package into the Software Manager database and then removes the .Q UE file. The next time you open the Software Manager database, it includes that package.
See About .QUE Files on page 40.
Importing Packages
To run the Wise Auto Import Service task, schedule it in the Wise Task Scheduler. For requirements and information on scheduling the task, see Scheduling Software Manager
Tasks on page 28.
See also:
Importing From the Share Point Directory on page 37
Package Subscription
¾ Enterprise Management Server only .
Use package subscription in Software Manager to copy packages from another Software Manager database. This lets you maintain separate Software Manager databases for performance reasons while avoiding duplication of efforts. You might do this if your corporate-level repackaging team maintains a database of packages used throughout the corporation, while regional teams maintain separate databases of packages unique to their regions. A regional repackager can subscribe to the corporate-level packages and resolve conflicts between the corporate and regional packages.
Package subscription is supported for Windows Installer, WiseScript, and virtual software packages only.
When you subscribe to a package in another Software Manager database, that package is imported to your database. A link is maintained between the subscribed package’s source and the copy, so that when the source installation of the original package is changed, it is re-imported into the Software Manager database. Device driver and Group Policy Object subscriptions are not linked to the source file. If the source file changes for these types of packages, the changes are not re-imported.
When you resolve conflicts between your package and a subscribed package, make the changes in your package instead of the subscribed package. You cannot export a
Software Manager Reference 74
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.
See Breaking Links to Subscribed Packages on page 77. You can subscribe to a single package or application, or to a group. Typically,
subscription packages are placed in a separate group within a central database to make it easier to subscribe to them. You might want to create a new group in your local database for subscribed packages.
See also:
Subscribing to Packages in Another Database on page 75 Refreshing Package Subscriptions on page 77
Subscribing to Packages in Another Database
¾ Enterprise Management Server only .
When you subscribe to a package in another Software Manager database, that package is imported to the current database and linked to the original source installation files. When you change the source package, you can refresh the subscription, that is, re­import the packages in the subscription.
Importing Packages
See Refreshing Package Subscriptions on page 77. Package subscription is supported for Windows Installer, WiseScript, and virtual software
packages only.
To subscribe to packages in another database
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. To place the subscribed packages in a specific package group in your database, verify that group exists.
3. Select Setup menu > Package Subscription. The Package Subscriptions page appears. This lists any package subscriptions that
have already been added to the current database.
4. Click Add. The Package Subscription Details page appears.
5. Complete the page:
Datasource
Select the database that contains the package to subscribe to. If the database you want does not appear in the drop-down list, click Open to add it.
Group
Select the package group that contains the packages to subscribe to.
Application
Software Manager Reference 75
To subscribe to a single application from the group, select an application. To subscribe to all applications in the group, leave the default <Any Application>.
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.
Delete applications when the source application is deleted
Mark this to delete the subscribed package from the current database if the original package is deleted from the source database.
Add to Group
To add the subscribed package(s) to a specific package group in the current database, select a group. You must have created the group before starting the subscription process.
6. Click OK on the Package Subscription Details page. The Package Subscriptions page reappears, showing the subscription information
you just entered.
7. Click OK.
8. When you are prompted to refresh the subscribed packages, click Yes. The package or packages to which you subscribed are imported into the current
Software Manager database and appear in the Applications/Packages pane. Verify the package group to which you imported the packages is displayed.
To edit a subscription
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Setup menu > Package Subscription. The Package Subscriptions page appears. This lists any package subscriptions that
have already been added to the current database.
3. Click the subscription to change and click Details. The Package Subscription Details page appears.
4. Edit the subscription; the package subscription fields are described above.
5. When you finish editing the subscription, click OK.
6. Click OK on the Package Subscriptions page.
7. Depending on the changes you make, you might be prompted to refresh the subscribed packages, move them to a new package group, or delete them from a group. At the prompt, click Yes.
The package or packages to which you subscribed are re-imported into the current Software Manager database.
See also:
Package Subscription on page 74
Software Manager Reference 76
Refreshing Package Subscriptions
¾ Enterprise Management Server only .
Refreshing package subscriptions consists of re-importing all subscribed packages to the local database. Do this when:
z The source installation files change. z The original pac kage is deleted from the source database. z 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.
See Subscribing to Packages in Another Database on page 75. Device driver and Group Policy Object subscriptions are not linked to the source file. If
the source file changes for these types of packages, the changes are not re-imported.
Refreshing Subscriptions Manually
Do one of the following:
z Click Update on the Software Manager toolbar.
Importing Packages
z Select Packages menu > Refresh Subscriptions.
Refreshing Subscriptions Automatically
You can run a Windows scheduled task that refreshes package subscriptions. The Wise Package Subscriptions task periodically searches the external databases for changes to the source installation files or for subscription packages that have been deleted from the source database. When it finds subscription changes, the service refreshes the subscriptions by re-importing the subscribed packages.
To run the Wise Package Subscriptions task, schedule it in the Wise Task Scheduler. For requirements and information on scheduling the task, see Scheduling Software Manager
Tasks on page 28.
Breaking Links to Subscribed Packages
¾ Enterprise Management Server only .
You cannot export subscribed packages, because multiple databases cannot export to the same installation file and because the source installations for subscribed packages typically have been approved and deployed and should not be changed. Exporting of packages is prevented by the Prevent Package Export check box on the Package Attributes dialog box, which is marked by default for subscribed packages.
There are situations in which you might need to update a subscribed package. Example: Suppose your corporate repackaging team maintains a package for Microsoft Office. Y ou subscribe to the Office package to resolve conflicts between it and packages in your regional database. Now, suppose you want to make changes to the Office package, but you don’t have permission to change the corporate version. If you break the link to the original Microsoft Office package, change the path to the installation file, and redistribute the installation to the new location, you can change and export the Office package.
Software Manager Reference 77
Importing Packages
To break a link to a subscribed package
1. Distribute the original package installation to a new location. See Package Distribution in the Wise Package Studio Help.
2. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
3. In the Applications/Packages pane, click a package.
Note
Be sure to click a package; you cannot break a subscription link for an application.
4. Select Packages menu > Attributes. The Package Attributes dialog box appears.
5. Clear Prevent Package Export.
6. In Installation File, specify the new location of the package installation file. Example: If you distributed the package to a network directory, specify that directory here.
7. Click OK. The link to the original installation is broken and the package is re-imported to the
current database.
8. If the package is in a special subscription package group in the current database, you might want to move it to a more appropriate group.
See Creating Package Groups on page 88.
See also:
Subscribing to Packages in Another Database on page 75
Software Manager Reference 78
Chapter 3
Managing Packages
This chapter includes the following topics:
z Revision Control on page 80 z Package Groups on page 87 z Viewing and Editing Package Attributes on page 93 z Viewing Resource Properties on page 94 z Windows Installer Table Queries on page 95 z Software Manager Reports on page 98 z Removing Excluded Files From Packages on page 101 z Merge Modules Wizard on page 102 z Moving a Package to Another Application on page 106 z Deleting a Package on page 107 z Compiling Multiple Packages on page 107 z Changing the Package Status on page 108
About Managing Packages
After a package has been imported into the Software Manager database, you can do the following to manage it:
z Add the package to Revision Control to protect it from unauthorized changes and to
track changes to the package.
z Group packages for more efficient management and for group deployment. z View package resources, either on-screen or by running any of the predefined
Software Manager reports or a Window Installer table query report.
z Use ConflictManager to detect and resolve conflicts between packages in the
Software Manager database. See About Conflict Detection and Resolution in the Conflict Manager Help.
z Remove files that are in the SetupCapture exclusion list from package in the
Software Manager database.
z Perform operations on .MSI or .WSI packages to add, remove, or replace merge
modules.
z Compile multiple packages.
For information on preparing a package for deployment, see About Preparing Packages
for Deployment on page 111.
Software Manager Reference 79
Revision Control
Use Revision Control to:
z Protect packages from unauthorized changes and changes to multiple copies of a
package at one time.
z 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, R evision Control protects packages.
Revision Control handles all installation file types except package definition files, group policy files, .INF files, and SOE files. Revision Control stores package versions in the Revisions subdirectory of the share point directory.
When a user tries to modify a package that is in Revision Control using a Wise Package Studio tool, that tool prompts the user to check the package out of Revision Control, if the package is available. If the user chooses to check the file out, the tool performs the check out.
Revision Control does not track changes made to package attributes in Software Manager. Example: package relationships. Also, packages added to Software Manager as part of a Workbench process are not added to Revision Control. You must add them manually.
Managing Packages
You cannot use both Revision Control in Software Manager and a third-party source control product for Wise Package Studio projects. You must choose one or the other.
See Choosing to Use Revision Control on page 80.
See also:
Adding Packages to Revision Control Checking Packages Back Into Revision Control Undoing Check Outs from Revision Control Removing Packages from Revision Control Package Revision History Reverting to a Previous Version Revision Control Settings
Choosing to Use Revision Control
You cannot use both Revision Control in Software Manager and a third-party source control product for Wise Package Studio projects. You must choose one or the other. How you choose to use Revision Control in Software Manager depends on whether you currently use a source control product for Wise Pa ckage Studio projects. (See Choosing a Revision Control System in the Getting Started Guide.)
If you use source control for package files:
If you use another source control product, either through Windows Installer Editor or directly, choose to use Revision Control in Software Manager by marking the Wise
Revision Control System check box in the Wise Repository Manager. See Choosing a Revision Control System in the Wise Package Studio Getting Started Guide.
Software Manager Reference 80
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. You can begin adding packages to Revision Control.
See also:
Adding Packages to Revision Control on page 81
Adding Packages to Revision Control
You can add a package to Revision Control when you import it into Software Manager. If a package is already in Software Manager, you can add it to Revision Control from within Software Manager.
When you add a package to Revision Control, it is locked and cannot be edited without being checked out.
Managing Packages
To add a package to Revision Control during import
When you import a package into Software Manager, mark the Add to Revision Control check box.
See Package Import on page 34. A blue padlock icon appears next to the package in the Applications/Packages pane to
indicate that the package is under revision control and is checked in. The installation file for the package is set to read-only.
To add a package in Software Manager to Revision Control
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > Add. The Add Package dialog box appears.
3. In Revision Description, enter a description of the package.
4. Click OK. A blue padlock icon appears next to the package in the Applications/Packages pane
to indicate that the package is under revision control and is checked in. The installation file for the package is set to read-only.
You can view revision control status information for the package in the Application/ Package Summary pane.
See also:
Checking Packages Out of Revision Control on page 82 Removing Packages from Revision Control on page 84
Software Manager Reference 81
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 i n the Package Attributes dialog box.
See Viewing and Editing Package Attributes on page 93. Only the user who checks out a package can edit the package or check it back in.
However, the user account under which Wise Package Studio was installed can undo any check out.
If the package you are checking out has dependents, a w arning message appears saying that modifying the package may render the dependent packages unusable.
See About Package Relationships on page 120.
To check packages out of Revision Control
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > Check Out.
For the user who checked out the p ackage, a red check mark icon appears next
to the package in the Applications/Packages pane to indicate that the package is checked out. The read-only setting is removed from the installation file, and the file can be edited by the user who checked out the package.
Managing Packages
For other users, a blue check mark icon appears next to the package in the
Applications/Packages pane to indicate that the package is checked out by another user. Other users cannot modify a package that is checked out by someone else.
See also:
Checking Packages Back Into Revision Control on page 82 Undoing Check Outs from Revision Control on page 83
Checking Packages Back Into Revision Control
Checking a package back into Revision Control commits any changes that were made to the package to the Software Manager database.
Note
To view changes made to the packa ge before checking it in, select the latest version in the Applications/Packages pane and then select Compare from the right-click menu.
You cannot check in packages that were checked out by another user, with one exception: The NT user who installed Wise Package Studio Server can check in packages that were checked out by other users. This lets the administ rator check i n packages that were checked out by a user who is no longer with the company.
To check in a package
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > Check In. The Check In Package dialog box appears.
Software Manager Reference 82
Managing Packages
3. 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.
See Comparing Versions of a Package on page 84.
4. Complete the dialog box:
Packages
Packages that you checked out appear in this list. Select the package to check in. To check in multiple packages, select the packages; the same Revision Description will be applied to all of the packages that you select.
Revision Description
Enter a description of changes that were made to the package. Depending on a setting in Wise Repository Manager, you might not be able to complete the check in without entering a description.
Reimport package
Clear this check box if you made no changes to files or registry keys. If you made changes to files or registry keys, leave this check box marked.
If you selected Reimport package, the Wise Task Manager dialog box appears, showing the progress of the check in.
5. Revision Control checks the package back in. The blue padlock icon reappears next to the package in the Applications/Packages
pane, and the installation file for the package is set to read-only.
Note
In client installations, Software Manager does not refresh the view when you check packages back in. Click Refresh on the toolbar.
See also:
Undoing Check Outs from Revision Control on page 83 Checking Packages Out of Revision Control on page 82
Undoing Check Outs from Revision Control
Undoing a check out puts the package back under Revision Control, without committing changes that were made to the package while it was checked out. If the package was changed while it was checked out, it is re-imported.
You cannot undo check outs that were performed by another user.
To undo check outs from Revision Control
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > Undo Check Out. The blue padlock icon re-appears next to the package in the Applications/Packages
pane, and the installation file for the package is set to read-only.
See also:
Checking Packages Out of Revision Control on page 82 Checking Packages Back Into Revision Control on page 82
Software Manager Reference 83
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.
To remove packages from Revision Control
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > Remove. The blue padlock indicating that the package was under Revision Control no longer
appears next to the package.
See also:
Adding Packages to Revision Control on page 81
Package Revision History
In Revision Control in Software Manager, you can track the changes that have been made to a package by:
Managing Packages
z Comparing Versions of a Package z Viewing a Version of a Package z Retrieving a Version of a Package z Viewing Comments for a Version of a Package
Comparing Versions of a Package
For most file types, when you compare versions of a package, Revision Control uses Visual MSIDiff™ to find and display the differences between the ve rsio ns. Visu al MSIDiff is a tool in Windows Installer Editor.
See Comparing Windows Installer Files in the Windows Installer Editor Help for information on using Visual MSIDiff.
For patches, there is no compare function. For .EXE files and WiseScripts, Software Manager does not use a comparison tool but displays a message saying either that the files are identical or that the files are different.
Note
This procedure describes how to use the compare function from the Revision History dialog box. You can also compare a checked out package to the most recent version of the package in Software Manager when you check packages in.
See Checking Packages Back Into Revision Control on page 82.
To compare versions of a package
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > History. The Package Revision History dialog box appears.
Software Manager Reference 84
Managing Packages
3. 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.
If there are differences between the versions, the comparison tool displays the
differences.
If there are no differences between the versions, a message appears saying
that the versions are identical.
See also:
Retrieving a Version of a Package on page 85 Reverting to a Previous Version on page 86
Viewing a Version of a Package
If you are using Revision Control, you can view a copy of a current or previous version of a .WVP file and most Windows Installer files. You cannot view .EXE files or patch files (.MSP). Windows Installer files open in Windows Installer Editor and .WVP files open in Virtual Package Editor. This is a convenient way to learn more about a version of a package without having to retrieve or check out the version.
To view a version of a package
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > History. The Package Revision History dialog box appears.
3. Select the version and click View. If the outdated path variables message appears, click Yes.
A copy of the version of the package opens in Windows Installer Editor or Virtual Package Editor.
When you close the version of the package, the copy is deleted.
See also:
Revision Control on page 80
Retrieving a Version of a Package
When you want a copy of a previous version of a package, you can retriev e it. When you retrieve a version of a package, you save a copy of that version to a location other than the package’s source path or current location.
To retrieve a version of a package
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > History.
Software Manager Reference 85
Managing Packages
The Package Revision History dialog box appears.
3. Select the version and click Get.
4. 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
Viewing Comments for a Version of a Package
When users check packages back into Revision Control, they can enter a description of the changes that were made to the package. The Require Comments for Each Revision check box in the Wise Repository Manager determines whether users must enter a comment.
See Choosing a Revision Control System in the Getting Started Guide.
To view comments for a version of a package
1. In the Applications/Packages pane, select a package.
2. Select Packages menu > Revision Control > History. The Package Revision History dialog box appears.
3. Select the version and click Comments. The Comments dialog box appears, displaying the comment for that version. Click
OK.
See also:
Reverting to a Previous Version on page 86 Retrieving a Version of a Package on page 85
Reverting to a Previous Version
To revert to a previous version of a package in Software Manager, you overwrite the current version with a previous version.
To revert to a previous version
1. Check out the current version of the package. See Checking Packages Out of Revision Control on page 82.
2. Retrieve or view the previous version to which you want to revert. See Package Revision History on page 84.
3. Save the previous version to the location the current version is checked out to, overwriting the current version.
4. Check the package back in. See Checking Packages Back Into Revision Control on page 82. The previous version is now the current version in Software Manager.
Software Manager Reference 86
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. Y ou can add file t ypes to compare. Y ou can also change the comparison tool. However, because Visual MSIDiff™ is the best comparison tool for installation file types, we recommend that you do not change it.
See also:
Revision Control on page 80
Package Groups
A package group consists of a subset of the packages in the Software Manager database. It can represent a functional area within your company, any other entity that uses a subset of your packages, or a series of applications that are likely to be installed together. A group can contain a single package, and it can have many levels of subgroups.
Managing Packages
You can use groups to:
z Organize your packages, which lets you filt er the displays and some of the reports in
Software Manager. In addition, some of the reports in ConflictManager can be run by package group.
Example: You might create a package group for each department in your organization. Your Accounting and Engineering departments never use the same packages, so you put them in separate groups. Then in ConflictManager, you can view conflicts for Engineering alone, because it doesn’t matter whether their applications conflict with those of the Accounting department.
z 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. Or, group several packages that are always installed together.
z Install packages that you would not otherwise be able to repackage and deploy.
Example: Create a group containing a single package that consists of a Setup.exe file of unknown format and the command line needed to run the .EXE.
Package Inheritance
A package group can inherit package assignments from its parent or child groups. This affects which packages are displayed when a group i s selected. The Inheritance setting on the Package Groups dialog box determines how groups inherit packages. When you delete, or unassign, a package from the group it was originally assigned to, it is also deleted from any inheriting groups.
Software Manager Reference 87
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. However, it is not inherited by the Accounting group.
Package inheritance is different from package relationships, which define dependencies between packages.
Group Deployment Properties
Group deployment properties define how a group is deployed. They specify which packages in a group will be installed, the order in which they will be installed, and the command lines that will be used to run the package installations.
When you define group deployment properties, you can add one or more subgroups to a group. Example: You define a group named Acrobat, which installs Adobe Acrobat Reader. You define another group named Word Processor, which installs a word processing application. The word processor contains .PDF help files, so you want to install Acrobat at the same time as the word processor. To do so, you can add the Acrobat group as a subgroup of the Word Processor group.
Setting Group Deployment Properties on page 91
Creating Package Groups
Use the Groups pane in Software Manager to create and edit package groups. You can set up groups and subgroups, add packages to groups, and delete packages from groups. To show the Groups pane, select View menu > Groups.
The right-click menu provides quick access to most of the tasks that you can accomplish in the Groups pane. You also can drag packages into package groups.
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 box es during distri bution.
With Enterprise Management Server, Security Setup determines whether you can edit package groups.
To create a package group
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. Select Setup menu > Groups > Edit Groups. The Edit Groups dialog box appears.
Software Manager Reference 88
Managing Packages
3. 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.
Inherit from child groups
When you assign a package to a group, that package is also assigned to that group’s parent groups.
Inherit from both parent and child groups
When you assign a package to a group, that package is also assigned to all parent and child groups above and below that group.
Note
The Inheritance setting affects all package groups, not just the specific group you are creating.
4. Click New Group. The New Group dialog box appears.
5. Complete the dialog box: a. In Group Name, enter a name for the new group. b. If this is a subgroup, select its parent group from Parent Name.
6. On the Edit Groups dialog box, in the Packages not in Group list, select all the packages to include in this group and click <<Move.
You can select more than one package simultaneously. To move just one package, double-click it. To remove a package from the Packages in Group list, select it and click Move>>.
7. If you add a package that has a supersedence relationship, the Superseding Packages dialog box appears, where you specify whether the package will be superseded. This dialog box also appears if you click Check Supersedence. Complete the dialog box and click OK.
See Selecting Superseding Packages on page 89.
8. When you finish defining the new package group, click OK.
Setting Group Deployment Properties on page 91
Selecting Superseding Packages
In a supersedence relationship, one package replaces another package. Example: If you have two versions of the same package, you would make the latest version a dependency that supersedes the earlier version.
When a package has a supersedence relationship, you must specify whether the package will be superseded. You do this in the Superseding Packages dialog box, either when you add the package to a group or when you distribute the group.
Software Manager Reference 89
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
1. 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. See Creating Package Groups on page 88.
On the Select Group dialog box of Group Distribution, when you select a group
containing a package that has a supersedence relationship, a message asks you to edit the group. Click Yes.
See Distributing a Group on page 131.
On the Superseding Packages dialog box, the packages in the group are at the top level of the tree. Superseding packages are listed below the top level.
2. For each top-level package, select its superseding package by marking its check box. To prevent the top-level package from being superseded, m ark the top-level check box.
3. Click OK. The group is updated. This does not affect the package relationships in other
groups.
Adding Applications and Packages to Groups
In Software Manager, you can add applications and packages to groups in several ways. When you add an application or package to a group, the application or package might
also be added to parent or child groups, depending on the Inheritance setting on the Edit Groups dialog box.
z During the Import wizard
On the Import T ype page, click Groups. On the Select Groups page, mark the check boxes of the groups to assign the package to.
See Package Import on page 34.
z On the Edit Groups dialog box
In the Groups pane, right-click a group and select Edit Groups. Use the Move buttons to move packages back and forth between the Packages in Group and Packages not in Group lists.
See Editing Package Groups on page 91.
z In the Groups pane
Drag the entire application or package over a group name in the Groups pane. You can select multiple applications or packages.
z On the Group Properties dialog box
In the Groups pane, right-click a group and select Properties. On the Group Properties dialog box, click Add Package and select one or more packages.
See Setting Group Deployment Properties on page 91.
Software Manager Reference 90
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 box es during distri bution.
See also:
How Package Relationships Affect Group Distribution on page 123
Editing Package Groups
In Software Manager, you can edit a package group to add or delete packages or assign the group to a different parent group.
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 box es during distri bution.
With Enterprise Management Server, Security Setup determines whether you can edit package groups.
To edit a package group
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. In the Groups pane, right-click a group and select Edit Groups. The Edit Groups dialog box appears, with the selected group displayed.
3. Edit the package group in any of the following ways.
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.
When you add a package that has a supersedence relationship or click the
Check Supersedence button, the Superseding Packages dialog box appears. Complete the dialog box and click OK.
See Selecting Superseding Packages on page 89.
4. When you finish editing the package group, click OK.
Setting Group Deployment Properties on page 91
Setting Group Deployment Properties
Use the Group Properties dialog box to add packages to a group and to define which packages in a group will be installed, the order in which they will be installed, and the command lines that will be used to run the package installations. These settings provide
Software Manager Reference 91
Managing Packages
the defaults for Group Distribution. Y ou 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. The order in which you add packages to a group on the Group Properties dialog box can affect the state of the package check box es during distri bution.
With Enterprise Management Server, Security Setup determines whether you can edit package groups.
To set group deployment properties
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. In the Groups pane, right-click a group and select Properties. The Group Properties 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. Although merge modules appear in the list, they cannot be distributed through Group Distribution.
3. Set the group’s deployment properties:
To add a package to the group, click Add Package and select one or more
packages. If the package has a dependency on another package, the dependency package
appears in the list even if it does not belong to this group. Y ou cannot re move a dependency package without removing its dependent package first.
To add a subgroup, click Add Group and select a group. The subgroup appears
in the group list. Packages in the subgroup will be distributed with the current group but they are not added to the group.
To remove a package from the deployment, clear its check box. It does not
delete the package from the group. During Group Distribution, this package’s check box will be cleared by default in the Select Packages dialog box. You can mark the check box in Group Distribution to include the package in a particular distribution instance. Example: Suppose this group contains an .MSI and three patches. In most instances, you want to distribute the .MSI and the latest patch, so you clear the check boxes for the other two patches. Occasionally, when you want to distribute all three patches, you can mark the check box es for those two patches during Group Distribution.
You can mark or clear a subgroup as a whole but not the individual packages in the subgroup.
Packages and subgroups are installed in the order they are listed. To rearrange
the order, click Move Up or Move Down. You cannot change the order of a dependency package or group because it must always be installed before its dependent package.
To change a package command line, click a package, click its command line in
Software Manager Reference 92
the Command Lines list, and then click Edit. Changing a command line here changes it for this particular group only.It does
not change the command line in the package definition file or in other groups that the package might belong to. You cannot change the command line for a package in a subgroup.
4. 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
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
Note
Be sure to click a package; you cannot display attributes for an application.
2. Select Packages menu > Attributes. The Package Attributes dialog box appears.
Managing Packages
3. Click the General tab and view or edit the following information.
Application
Change this to rename the application in the Software Manager database. This changes the application name for the selected package only and not for other packages within the application. If an application with this name already exists in the Software Manager database, this package is moved to that application. If that application already has a package with the same name, a 1 is added to the name of the package you move.
This does not change the application name in the Workbench project or the installation file.
Package
Change this to rename the package in the Software Manager database. This does not change the package name in the Workbench project or the installation file.
Read Only
If this check box is marked, you cannot resolve conflicts or export the package in ConflictManager. This check box is marked by default for SOE snapshot files, device drivers, Group Policy Objects, and InstallShield Developer packages.
Prevent Package Export
If this check box is marked, the package cannot be exported from ConflictManager. This check box is marked by default for subscribed packages, which should not be exported. If you clear this check box for a subscribed package, the link between the subscribed package and its copy in the Software Manager database is broken, and you must change the path in Installation File.
Software Manager Reference 93
See Breaking Links to Subscribed Packages on page 77.
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.
Package Meta Data
The Package Meta Data section contains both predefined and custom meta data fields. To edit custom meta data, click in the Value column and enter or select a value. If the field requires a URL, include http:// or other tag (mailto:, ftp:, file:) so that the field will become an active hyperlink on the Package pane.
The predefined meta data is read-only. To edit predefined meta data, use the Product Details page in Windows Installer Editor.
If no meta data values are enabled, it means that custom meta data fields hav e not been defined.
See Defining Custom Meta Data Fields on page 26. With Enterprise Management Server, Security Setup determines whether you
can edit meta data in Software Manager.
4. Click the Source tab and view or edit the following information.
Managing Packages
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.
You also need to change the file location when you break the link to a subscribed package.
See Breaking Links to Subscribed Packages on page 77.
Note
Selecting a new file location here does not move the installation file or its source files. You must redistribute the package installation to the new location.
Transforms and Patches applied
Lists the transforms and patches that were applied to the package in the order in which they were applied (read-only).
5. Click OK.
See also:
About Package Meta Data on page 25
Viewing Resource Properties
In Software Manager, you can view properties for any package resource item by displaying a read-only Properties dialog box, which shows additional information about the resource.
You also can view properties in the Conflict Details pane in ConflictManager. See Viewing Conflicts in the ConflictManager Help.
Software Manager Reference 94
To view resource properties
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. In the Applications/Packages pane, expand a package to display its resource folders.
3. Expand the resource folder until the resource items are displayed in the Package Details pane.
4. In the Package Details pane, double-click the resource item for which to view properties.
The Properties dialog box appears. The information on the dialog box differs depending on the type of resource you are viewing; typically it includes resource details and conflict information, if any.
If the resource has conflicts that were detected in ConflictManager, they are displayed on the Conflicts tab on the Properties dialog box.
Windows Installer Table Queries
Software Manager lets you query the data in Windows Installer packages that are in the Software Manager database. This gives you complete access to the package data and lets you analyze that data. Example: You can display all packages that contain isolated components, or all packages that contain certain launch conditions.
Managing Packages
See Example Table Queries on page 98. By default, only a small set of .MSI tables are imported into the Software Manager
database. However, you can set preferences in Software Manager to import additional tables or all tables from the .MSI. Changing the preferences does not affect packages that have already been imported.
To add and view queries, you use the Table Query dialog box. See:
z Creating a Table Query z Viewing the Results of a Table Query on page 97
See also:
Setting Software Manager Preferences on page 24
Creating a Table Query
A table query provides a report of Windows Installer packages in the Software Manager database that contain data that meets certain conditions. Each query can evaluate columns in a single table in the Software Manager database. In order for you to create a query for a table, the table must be in the Software Manager database. That means you must have set the Software Manager preferences to import that table, and you must have imported a package that contained data in that table.
See Setting Software Manager Preferences on page 24. Table queries are stored in the Software Manager database, so the queries you create
will be available to anyone who has access to the same Software Manager database. For information on running queries, see Viewing the Results of a Table Query on
page 97.
Software Manager Reference 95
Managing Packages
To create a table query
1. Select Packages menu > Table Query. The Table Query dialog box appears.
2. Click Add. The Query Details dialog box appears.
3. 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.
4. From Table, select the table containing the data to view. This drop-down list shows only the tables that are currently in the Software Manager database. If a table was not imported, either because it was not specified in the Software Manager preferences or because it was empty, it is not listed.
Note
The names of Windows Installer-specific tables are prefixed with Msi. Example: The Dialog table is represented here as MsiDialog.
5. In Description, enter text to identify the query. This description appears at the top of the table report.
6. In Query, click Build to specify the criteria to evaluate. This ensures that you use the correct syntax.
The Criteria Builder dialog box appears.
7. Complete the dialog box:
Column
Select the table column that contains the data to evaluate. Only columns from the currently selected table are listed.
The Application and Package columns are not in the original .MSI tables, but are added to the imported tables so that you can create queries that evaluate a specific application or package.
Expression
Specify how to evaluate the data.
Criteria
Enter the string to search for. This field is unavailable if the Expression you select does not require it.
If you select LIKE as the Expression, you can use the following wildcard characters in the criteria string:
Wildcard Description Example
% matches any string %MDAC%
returns all strings containing MDAC
[] matches any value in
the specified set
1.06.[1-3] returns 1.06.1, 1.06.2, and 1.06.3
because it includes all values between one and three
Software Manager Reference 96
Managing Packages
Wildcard Description Example
[^] matches any characters
not in the specified set
_ (underscore) matches any single
character
Criteria Operator
This is unavailable for the first cri teria statemen t you bu ild. It becomes enabled for subsequent statements. Select the operator (AND or OR) to use when appending additional criteria to the Query field.
8. Click OK on the Criteria Builder dialog box. The query criteria appears in Query. To append additional criteria, click Build again
and complete the Criteria Builder dialog box. Repeat until the criteria statement is finished.
9. To view the results of the query you just created, click Run. The table report is generated and displayed.
1.06.[1-4^2] returns 1.06.1, 1.06.3, and 1.026.4
1.06._ returns 1.06.0, 1.06.1, 1.06.2, and
so on through 1.06.9
10. Click Close to close the table report.
11. Click OK on the Query Details dialog box. The Table Query dialog box reappears.
12. Click Close the exit the Table Query dialog box.
See also:
Example Table Queries
Viewing the Results of a Table Query
Running a table query produces a report that displays all Windows Installer packages in the Software Manager database that meet the query criteria. Use table queries to view and analyze package data. Example: You can display all packages that contain isolated components, or all packages that contain certain launch conditions.
The table report is displayed in XML format. The template used to format the report, TableReport.xsl, is located in the Reports subdirectory of the share point directory. You can customize the template to supply branding information, to filter data, or to transform the data to another format.
If a package that you think should appear on the table report is missing, it might mean that the table containing the query data was not imported for that package. This can happen if the table was empty, if the table was not specified in the Software Manager preferences, or if the Software Manager preferences were changed after the package was imported.
Before you perform the following steps, one or more queries must have been created. See Creating a Table Query on page 95.
Software Manager Reference 97
To view the results of a table query
1. Select Packages menu > Table Query. The Table Query dialog box appears.
2. 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. Saving to HTML is
available only on computers that contain MSXML.DLL, which is included in Internet Explorer 5.x and higher.
3. Click Close to exit the Table Report dialog box. The Table Query dialog box reappears.
4. Run additional queries or click Close to exit the Table Query dialog box.
See also:
Example Table Queries
Example Table Queries
Managing Packages
The following table shows examples of table queries. You create queries on the Query Details dialog box.
See Creating a Table Query on page 95. The Table column below shows the table column you would select for the sample query.
You select the column in the Column drop-down list on the Criteria Builder dialog box. The Query Criteria column shows the criteria statement you would build in the Query field on the Query Details dialog box.
Example Table Query Criteria
Display all custom actions in all packages.
Display all packages that contain a version of the MDAC merge module.
Display all launch conditions in all packages.
Display all packages that require Internet Explorer 5.0 or higher.
Display all files that have a lock permission of “GENERIC_ALL” (decimal value 268435456).
Display all packages that have isolated components.
MsiCustomAction (Package IS NOT NULL)
MsiWiseModuleSignature (ModuleID LIKE '%MDAC%')
MsiLaunchCondition (Package IS NOT NULL)
MsiLaunchCondition (Condition LIKE 'IEVERSION >= 5%')
MsiLockPermissions (Permission = 268435456)
MsiIsolatedComp (Package IS NOT NULL)
Software Manager Reports
Software Manager lets you generate reports that provide information about the packages in the Software Manager database.
Software Manager Reference 98
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
Command
File Resources Resources > Files Lists all files in the selected packages, arranged by
Registry Resources Resources > Re gistry
Keys
Packages by Merge Module
File Details File Details > All Files
Package Contents Summary
Package Contents by Feature
Resources > Packages by Merge Module
File Details > DLLs File Details > EXEs
Package Cont ents > Summary
Package Contents > By Feature
What This Report Does
package and key. Lists all registry keys in the selected packages,
arranged by package and key. Lists all packages that contain a specified merge
module. Lists details of files in the Software Manager database,
arranged by package and path. The All Files option generates a report on any file or files. The DLLs and EXEs options generate reports on all .DLL or .EXE files.
A developer contemplating using a particular .DLL can use the ALL Files option and generate a report that displays every package that uses that .DLL. A manager wanting to find out which software packages require Adobe Acrobat Reader to be installed on the destination computer can use the All Files option to obtain a list of all packages that install .PDF files.
Lists detailed information for every resource in an installation, including files, registry keys, shortcuts, file associations, and merge modules. Y ou can generate this report for .WSI, .MSI, .WSM, and .MSM files.
Contains the same information as the Package Contents Summary report, but arranges it by feature. You can generate this report for .WSI and .MSI files.
Generating a Software Manager Report
To generate Resources and File Details reports
1. (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane.
2. From the Reports menu, select a report. The Report Parameters dialog box appears. The fields that appear on this dialog box
vary depending on the type of report that is selected.
3. Complete the Report Parameters dialog box:
Entries Per Page
Software Manager Reference 99
Enter the number of entries to display per page. (Example: If you enter 1, each page of the report will display just one entry. If the report contains 10 entries, it will then be a 10 page report.) The lower the number, the faster the report
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.
Application Name, Package Name
(Resources reports only.) Specify the applications and packages on which to run reports. SQL wildcards are accepted. If you select an application from Application Name, only its packages appear in Package Name.
File Name
(File Details for All Files only.) Specify the files on which to run reports. SQL wildcards are accepted.
Merge Module
(Packages by Merge Module only .) Select the merge module on which to run the report.
4. Click OK. The report opens in the report viewer window.
Managing Packages
See Using the Report Viewer on page 100.
To generate Package Contents reports
If a package’s path to its installation file is missing or broken, you cann ot generate thes e reports.
1. From the Reports menu, select a report. The Select Package dialog box appears. For the Package Contents Summary report,
it lists all .WSI, .MSI, .WSM, and .MSM packages in the selected database that have resources. For the By Feature report, it lists all .WSI and .MSI packages that have resources.
2. Select a package and click OK. The report is generated and opens in a dialog box.
Use a report’s table of contents to quickly access information about a specific type of resource. You can print the report or save it as an HTML or XML file.
Using the Report Viewer
After you generate a report, it is displayed in a report viewer window.
z To save a report, click Save As in the lower right of the report viewer window. You
can save a report in HTML, XML, or CSV format. When you save a report as HTML, an HTML file is created for each page of the report, and each file has the same name with its page number appended.
z To print a report, click Print in the lower right of the report viewer window. z The date and time when the report was generated appears in the lower left corner of
the report.
z To perform a text search, click on the report and press Ctrl+F.
Software Manager Reference 100
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use