Wise Package Studio Getting Started Guide 004

7/22/2019 Wise Package Studio Getting Started Guide 004

1/58


2/58

2

Wise Package Studio, Version 5.6

Copyright 2001-2005Wise Solutions, Inc. All Rights Reserved.

This documentation and the accompanying software are copyrighted materials. Making unauthorized copies is prohibited

by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrievalsystem or translated into any human or computer language without prior written permission of Wise Solutions, Inc. Wise

Solutions, Inc. asserts its Moral Right to be identified as the author of this work, in all jurisdictions which recognize the

Moral Right.

NoticeUnless otherwise provided by written agreement with Wise Solutions, Inc., this publication, and the software sold with

this publication, are provided as is without warranty of any kind either express or implied, including but not limited to

the implied warranties of merchantability and fitness for a particular purpose. The entire risk arising out of the use or

performance of this publication and software remains with you. In no event will Wise Solutions, Inc., or any of its

suppliers, be liable for any lost profits, lost savings, direct, incidental or indirect damages or other economic or

consequential damages, even if Wise Solutions, Inc., or its suppliers, have been advised of the possibility of such

damages. Wise Solutions, Inc. reserves the right to modify this document at any time without obligation to notify

anyone. In no event shall Wise Solutions, Inc.s or its suppliers liability under this agreement exceed the sum of any

amounts paid hereunder by the customer to Wise or the supplier.

TrademarksWise Solutions, Inc. owns a number of registered and unregistered Trademarks and Service Marks (the Marks). These

Marks are extremely valuable to Wise Solutions, Inc. and shall not be used by you, or any other person, without Wise

Solutions, Inc.s express written permission. The Marks include, but are not necessarily limited to the following:

Application Isolation Wizard; ApplicationWatch; ConflictManager; ExpressBuild; Installation Development Life

Cycle; InstallBuilder; InstallMaker; InstallManager; InstallTailor; MSI Debugger; MSI Script;

PackageManager; Preflight Deployment; SetupCapture; SmartMonitor; SmartPatch; Software Distribution

Made Easy; Software Installations Made Easy; Visual MSIDiff; Virtual Capture; WebDeploy; Wise Installation

System; Wise Package Studio; Wise Software Repository; Wise Solutions; WiseScript; WiseScript Express;

WiseUpdate; WiseUser; and the Wise Solutions logo.

In addition to Wise Solutions, Inc.s Marks, some Wise Products may include Trademarks or Service Marks owned by

other corporations. These other Marks include, but are not necessarily limited to Microsoft Windows and Microsoft

Visual Studio .NET, which are registered Trademarks of Microsoft Corporation.

You shall not use any of the Trademarks or Service Marks of Wise Solutions, Inc., Microsoft Corporation, or any other

entity, without the express written permission of such Trademark or Service Mark owner.

Wise Solutions, Inc.47911 Halyard Drive; Plymouth, Michigan 48170 USAPhone: 734-456-2100 Fax: 734-456-2456 [email protected] www.wise.com
http://www.wise.com/http://www.wise.com/


3/58

3

Contents

1 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Getting Help and Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Getting Updates Over the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Installing Wise Package Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . 10

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Before You Install Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Choosing the Location for the Share Point Directory . . . . . . . . . . . . . . . . . . . 15

What Do You Want to Install? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing Wise Package Studio Standard Edition . . . . . . . . . . . . . . . . . . . . . 17

Installing Wise Package Studio Professional Edition . . . . . . . . . . . . . . . . . . . 17Quality Assurance - Core Files Installation. . . . . . . . . . . . . . . . . . . . . . . . . . 19

Quality Assurance - Web Applications Installation. . . . . . . . . . . . . . . . . . . . . 19

Enterprise Management Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . 19

Management Reports Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Application Gateway Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Database Configuration for Web Applications. . . . . . . . . . . . . . . . . . . . . . . . 20

Setting Up Database Connections and Authentication . . . . . . . . . . . . . . . . . . 21

About the Client-Server Configuration of Wise Package Studio . . . . . . . . . . . . . . 26

Installing Wise Package Studio in a Client-Server Configuration . . . . . . . . . . . 27

Installing Wise Package Studio Client Silently . . . . . . . . . . . . . . . . . . . . . . . 27

Integrating Application Gateway and Wise Package Studio . . . . . . . . . . . . . . . . . 29

Bypassing the Proxy Server for Application Gateway. . . . . . . . . . . . . . . . . . . 30

Configuring IIS for Application Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Starting Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

If Your Logon Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Wise Package Studio Logon Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Registering Your Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3 Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Import a Sample Package into the Software Manager Database. . . . . . . . . . . 36

Create a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Create the QuickFacts Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Edit the Package Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Validate the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Test the Package Without Test Expert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Test the Package With Test Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Distribute the Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Import into the Software Manager Database . . . . . . . . . . . . . . . . . . . . . . . . 52

Resolve Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Make the Package Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Distribute the Finished Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


4/58

4

Remove Tutorial Packages from the Software Manager Database. . . . . . . . . . 55

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


5/58

5

Chapter 1

Welcome

Wise Package Studio helps system administrators and desktop integration labs

streamline the process of packaging software applications for delivery to end users. It

encompasses all phases of an applications lifecycle, starting with the users request,

continuing with repackaging, and ending with testing and distribution.

Wise Package Studio improves on traditional packaging practices by combining best

practice methodologies with industry-leading software installation technology. In

addition, software packages created with Wise Package Studio can be distributed

through many of the leading software distribution products currently on the market.

Topics include:

! Documentation Roadmap.

! Getting Help and Product Support.

! How to Check Online Help.

! Getting Updates Over the Web.


6/58

6

Documentation Roadmap

Documentation Roadmap

The Wise Package Studio 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 Wise Package Studio.

Online Help

The online help contains detailed technical information and step-by-step instructions for

performing common tasks. For details on using help, see Check Online Helpon page 7.

Reference Manuals

All the material in the online help is also available in .PDF-format reference manuals.

Reference manual .PDFs are provided for Wise Package Studio, Software Manager,

ConflictManager, WiseScript Editor, and Windows Installer Editor. To access the .PDF

reference manuals, select Help menu > Reference Manual from within each Wise

Package Studio module.

Getting Started

The printed Getting Started Guidecontains system requirements, installation

instructions, and a tutorial. To access a .PDF version of the Getting Started Guide, in

Wise Package Studio, select Help menu > Getting Started.

Release Notes

A release notes document, in .HTM format, covers new features, enhancements, bug

fixes, and known issues for the current version of this product. It also contains links to

release notes for other versions. Access the release notes in the following ways:

! Browse the product CD.

! In Wise Package Studio, select Help menu > Release Notes.

! If you are a registered user, visit http://support.wise.comto enter the SupportCenter, and then click the Downloads link.

Windows Installer SDK Help (Windows Installer Editor only)

You can get technical details about Windows Installer from its own help system, which is

written by Microsoft for a developer audience. Select Help menu > Windows Installer

SDK Help in Windows Installer Editor.
http://support.wise.com/http://support.wise.com/


7/58

7

Getting Help and Product Support


Wise Solutions offers many resources to help you use our products. You can search the

product help or reference manual .PDF for answers, or you can use one of the many

support resources available to you as a registered Wise Solutions customer.

Check Online Help

You can access help in the following ways:

! To display context-sensitive help for the active page or dialog, press F1.

! To select a help topic from a table of contents, index, or search, select Help menu >

Help Topics.

Select other commands from the Help menu to view the .PDF-format reference manual

or getting started guide, to view Wise Solutions resources on the Web, or to upgrade to

the latest point release. Windows Installer Editor has an additional option in the Help

menu for displaying the Windows Installer SDK Help.

If you need help and cannot find the answer in the documentation, read about our

technical support options below.

Use the Wise Solutions Technical Support Center

Registered Wise Solutions customers can use the Technical Support Center, located at

www.wise.com/support.asp, to submit online support requests, register products,

manage customer information, download updates, or search the Knowledgebase. The

Knowledgebase contains how-to procedures, answers to common support questions,

and workarounds.

Visit Our Newsgroups

Visit Wise Solutions Newsgroups at www.altiris.com/support/forum/default.asp.

Newsgroup postings by your peers contain answers, tips, analysis, and other comments.

Contribute your own expertise to help others.

Subscribe to TechInfo

TechInfo is a free e-mail newsletter that contains technical tips, product updates, and

other important technical information. To subscribe or to read back issues, visit

www.wise.com/techinfo.asp.

Ask Our Support Team

If you cant find an answer in our online resources, you can obtain support by phone or

online at www.wise.com/support.asp. Wise Solutions offers flexible payment options to

meet your support needs. For additional details about our support services, visit

www.wise.com/supportoptions.aspor call 1-734-456-2600.

Before you contact technical support, obtain the following:

! Serial number and product version, which you can find by selecting Help menu >

About.

! Operating system version and service pack version if applicable.

! A description of what you do before the problem occurs.

! The text of any error messages that appear.

! Your name, company name, and how to contact you.

! Contract number or payment information, if applicable.
http://www.wise.com/support.asphttp://www.altiris.com/support/forum/default.asphttp://www.wise.com/techinfo.asphttp://www.wise.com/support.asphttp://www.wise.com/supportoptions.asphttp://www.wise.com/supportoptions.asphttp://www.wise.com/support.asphttp://www.wise.com/techinfo.asphttp://www.altiris.com/support/forum/default.asphttp://www.wise.com/support.asp


8/58

8


Take Advantage of our Consulting and Training Services

When you have a challenging repackaging or installation problem, turn to Wise

Solutions. Our consultants can help with script writing, repackaging, installation

development, and other solutions that are fully customizable to fit your project and

budget. Visit www.wise.com/consulting.aspfor details.

To upgrade your installation and packaging skills, consider Wise Solutions training. Ourcertified instructors draw from practical experience to provide relevant course content.

Visit www.wise.com/training.aspfor course descriptions and schedules.

Contact Wise Solutions Sales

Contact Wise Solutions Sales department to purchase additional products, upgrades,

support services, or consulting and training services.

U.S.: 1-800-554-8565

Europe/Netherlands: +31 70 392 72 20

Other International: 734-456-2100 (in U.S.)

Web Site: www.wise.com/ordercentermain.asp
http://www.wise.com/consulting.asphttp://www.wise.com/training.asphttp://www.wise.com/ordercentermain.asphttp://www.wise.com/training.asphttp://www.wise.com/ordercentermain.asphttp://www.wise.com/consulting.asp


9/58


10/58

10

Chapter 2

Installing Wise Package Studio

Wise Package Studio is comprised of several software components. Before you install

Wise Package Studio, refer to the information in this section to learn about the product

configurations and options that will achieve your installation goals.

Topics include:

! The system requirements for using Wise for Windows Installer.

! How to install and launch Wise Package Studio.

! How to register your Wise Solutions software.


11/58

11

System Requirements

System Requirements

You can install different modules of Wise Package Studio. There are separate

requirements for Web applications, and small differences for some modules.

Wise Package Studio Requirements

Note

Wise Package Studio cannot be installed on any computer that contains the Enterprise Edition

of Wise for Windows Installer 5.x or later.

The requirements below apply to the following, except as noted:

! Wise Package Studio Standard Edition

! Wise Package Studio Professional Edition

Client: Full or Minimal

Complete

! Wise Package Studio Quality Assurance module

Wise Package Studio

RequirementValue

Computer/processor PC with a Pentium II-class processor, 450

MHz

Operating system Windows 98 *

Windows NT 4.0 SP6** or later (SP6a or

later recommended)

Windows 2000 or later (SP4

recommended)

Windows XP Professional (SP2recommended)

* Management Reports are omitted from

Enterprise Management Server module on

Windows 98.

** required by Windows Installer 2.0.

Microsoft Internet

Explorer

5.5

RAM 128 MB; 256 MB recommended

Free space on boot

drive

150 MB

Free space oninstallation drive

150 MB*

* Negligible space required for Client

installation.


12/58


13/58

13

System Requirements

.NET Framework System Requirements

The .NET Framework is required for advanced .NET support in Windows Installer Editor.

The .NET Framework requires Microsoft Internet Explorer 5.01 or later and one of the

operating systems supported by Wise Package Studio.

Microsoft Internet

Explorer

5.5*

* Required for client computers that

connect to Web applications.

RAM 128 MB; 256 MB recommended

Free space on boot

drive

150 MB

Free space on

installation drive

10 MB

Database (not

applicable to Standard

Edition)

One of the following:

! Microsoft Access runtime, version 3.x

or higher. (This is included in the

Professional Edition installation .EXE.)

! Microsoft Data Engine (MSDE)

environment.! MSDE Tools.

! Microsoft SQL Server (English version

only). Version 7.0 required; 2000

recommended.

! Microsoft SQL Server Client Tools

(English version only). Version 7.0

required; 2000 recommended.

Web Application

RequirementValue


14/58


15/58

15

Before You Install Wise Package Studio

Choosing the Location for the Share Point DirectoryThe recommended location of the share point directory depends on your environment

and the parts of Wise Package Studio you have purchased.

Where to Locate the Share Point Directory

When the share point directory is on a shared network drive, all users in a workgroup

must specify the same share point directory during installation. This lets all users access

the same packages and data.

Do You Need to Create the Share Point Directory?

Environment Edition Share Point Location

Single user Standard Local or network directory.

Team, sharing project

files

Professional,

Quality

Assurance

Shared network directory

accessible to team

members. In a large

enterprise with multiple

teams, each team might

have a different share

point directory.

Corporate teams

maintaining a globalprocess database

Professional,

EnterpriseManagement

Server

Shared network directory

accessible to all otherteams.

If Then do this:

!

Multiple teammembers plan to

share Wise Package

Studio data, and

! You are installing

the first copy of

Wise Package Studio

in your workgroup.

Before installation:Create and share a directory on an

accessible network location.

During installation:

When prompted for the Wise Share Point,

specify that shared directory in UNC

notation (preferred) or mapped drive

notation. (Example of UNC:

\\SERVER\WISE SHARE POINT)


16/58

16

Before You Install Wise Package Studio

! Multiple team

members plan to

share Wise Package

Studio data, and

! Another team

member already

created and shared

a share point

directory

Before installation:

Obtain the location of the existing share

point directory.



specify the existing share point in UNC

notation (preferred) or mapped drive

notation.

You do not plan to

share data with others



specify any directory, existing or not,

shared or not, as the Wise Share Point. It

can be specified with a local path

(example: C:\Wise Share Point).

If Then do this:


17/58

17

What Do You Want to Install?


You can install different configurations of Wise Package Studio. For details on each

option, see:

! Installing Wise Package Studio Standard Edition

! Installing Wise Package Studio Professional Edition

! Quality Assurance - Core Files Installationon page 19

! Quality Assurance - Web Applications Installationon page 19

! Enterprise Management Server Installationon page 19

! Management Reports Installationon page 20

! Application Gateway Installationon page 20

! Database Configuration for Web Applicationson page 20

! Setting Up Database Connections and Authenticationon page 21

For help during installation, click the Help button on any dialog.

Installing Wise Package Studio Standard EditionConsists of the Workbench interface and tools for package creation. The Standard

Edition can only be installed in one basic configuration. During installation, follow the

prompts.

Installing Wise Package Studio Professional EditionConsists of the Workbench interface and tools for package creation, management, and

and conflict resolution. You can install Wise Package Studio Professional Edition in

several different configurations and purchase additional modules that extend its

functionality.

The Professional Edition has 3 options: Complete, Client, and Web. The Web optionappears only if IIS is installed and if youve entered at least one serial number that

includes a Web application. See Quality Assurance - Web Applications Installationon

page 19or Application Gateway Installationon page 20.

Complete

You have several options for the Complete installation:


18/58


19/58

19


Client Minimal

Do this if you only need to capture installations and if you already installed the Complete

configuration of Wise Package Studio on a server. This keeps the repackaging computer

clean. This installs a shortcut to SetupCapture only, which points to SetupCapture on a

server.

During installation, select Clientfor the installation type and then select MinimalClient. Specify the same share point directory and Wise Package Studio directory that

were specified during the server installation.

See About the Client-Server Configuration of Wise Package Studioon page 26.

Quality Assurance - Core Files InstallationInstalls Workbench and quality assurance tools, consisting of Test Expert, Package

Validation with the ability to create ICE files, and Package Instrumentation.


! Enter a valid serial number for the Quality Assurance module.

! Select Completeas the installation type.

! Verify that this feature is enabled on the Select Features dialog.

Quality Assurance - Web Applications InstallationInstalls Web applications that are needed for Preflight Deployment, a Quality Assurance

tool for evaluating installations.


Verify that Microsoft Internet Information Services 4.0 or later is installed (5.0 is

recommended).


! Enter a valid serial number for the Quality Assurance module.

! For the installation type, either select Completeand verify that this feature is

enabled on the Select Features dialog, or select Web.

! When prompted to create the Preflight Database, specify a Microsoft SQL Server or

MSDE database server.

When a Wise Package Studio user accesses Preflight Analysis, the Preflight Analysis Web

application uses the same account that provides Web browser access to the IIS server.

Therefore, the browser account must have access to change the Preflight database. If

you know that the browser accesses this IIS server via the IIS guest account, then

during database setup for the Preflight database, mark the Grant database access to

IIS Guest Accountcheckbox. See Database Configuration for Web Applicationson

page 20.

Enterprise Management Server InstallationInstalls components needed for project management, viewing reports, accessing

multiple databases, and automatically importing package information. Includes user and

group-based security, which can be integrated with NT authentication. It includes

Management Reports and also lets you set up Application Gateway security. This module

can only be installed with Wise Package Studio Professional Edition.


20/58

20



! Enter a valid serial number for both Wise Package Studio and Enterprise

Management Server.


! Verify that Wise Package Studio Professional Edition and Enterprise Management

Server are enabled on the Select Features dialog.

Management Reports InstallationConsists of 2 pieces: a Web application that communicates with the Workbench

database and a Web interface that accesses the Web application. Managers can use the

Web interface to view management reports stored in the Software Manager database

without having installed any Wise Package Studio software on their computers.



recommended).



! Verify that Wise Package Studio Professional Edition and Enterprise Management

Server are enabled on the Select Features dialog, or select Web.

See Database Configuration for Web Applicationson page 20.

Application Gateway InstallationInstalls a Web application that lets users request applications. Requests appear in Wise

Package Studio as requests for repackaging. At least one license for Enterprise

Management Server is needed to manage users and permissions for Application

Gateway.



recommended).


! If prompted, either select Completeas the installation type and then verify that

Application Gateway is enabled on the Select Features dialog, or select Web.

! If you entered only an Application Gateway serial number, the installation skips to

the Wise Share Point Directory dialog. Specify the same share point as other team

members.

See Integrating Application Gateway and Wise Package Studioon page 29.

Database Configuration for Web Applications

Recommended Database

If you will use the Management Reports or Application Gateway Web applications, which

use ASP code, we strongly recommend using SQL Server or MSDE, rather than Microsoft

Access, to host the Workbench database. Microsoft recommends using SQL or MSDE-


21/58


22/58

22


Workbench database

Stores information that Wise Package Studio creates and uses, such as project, process,

and security information.

Software Manager database

Contains all software packages as well as other resources that are used by anorganization. Examples: merge modules, device drivers, Group Policy Objects, and

standard operating system environment images.

Preflight database

Stores the results generated from running preflight packages, which are made with the

Package Instrumentation tool. You see the contents of the Preflight database with the

Preflight Analysis tool. (Quality Assurance module only)

Database Setup Dialogs

" Not available in Standard Edition.

Representative dialogs that appear during database setup are shown below. A separatenumbered set of dialogs appears for each database to be set up. Slightly different

dialogs appear depending on what databases and Wise Package Studio features are

being installed. These dialogs might also appear during execution of Workbench if any

database connection information has become invalid or if the share point directory

cannot be found or if it becomes invalid. In that case, you are asked to re-specify

database connection and authentication information and the share point directory.

Type of Database Dialog

Specify the database name to create or connect to, the type of database, and database

server for the database whose name is specified at the top of this dialog. If you do not

have appropriate software installed (example: SQL Client Tools), the corresponding

option is disabled.


23/58


24/58

24


Create New Users Dialog

If you selected SQL Server authentication, or marked a checkbox to Create logon ID

as part of database creation, then the following dialog appears during installation.

The DBA logon information you entered earlier will be used to create database users that

you specify on this dialog for all databases that are being created (Workbench database,

Software Manager database, Prefight database). These users will have modification

privileges in all databases.

Wise Share Point Directory DialogThis dialog might appear at any time during execution of Workbench if the share point

directory cannot be found or if it has become invalid. If it appears, specify a valid share

point directory or contact your team leader.


25/58

25


Creation Options Dialog

! Import sample applications into the Wise Software Repository

Imports a set of sample application installation data into the Wise Software

Repository. This option lengthens installation time.

! Overwrite existing share point and repository

This option appears only if the share point or databases you specified already exist.

Mark this option to overwrite it with a blank share point or database.


26/58


27/58

27

About the Client-Server Configuration of Wise Package Studio

For other Wise Package Studio configuration concepts, see Sharing the Workbench

Databasein the Wise Package Studio Help.

Installing Wise Package Studio in a Client-Server Configuration


1. Create and share 2 directories:

A Wise Package Studio application directory, where the application will be

installed.

A share point directory, where shared data will be stored.

2. Install a Complete installation of Wise Package Studio Professional on a computer

designated as your workgroup packaging server. During installation, specify the 2

directories above as the Wise Package Studio Destination Directory and the Wise

Share Point Directory. To specify the directories, we recommend that you use UNC

paths. Otherwise, map separate drive letters to both these directories before

performing the client installation.

3. On each client computer, run the Wise Package Studio installation and select Clientwhen prompted. Specify the same share point directory and Wise Package Studio

directory that were specified during the Complete installation. After you select

Client, you are prompted to choose between Full Clientand Minimal Client.

Selecting Minimal Clientinstalls SetupCapture only.

Note

To minimize client installation steps further, create a drive image of the client after a

successful client installation. Use that image each time you subsequently re-image the

computer, and then skip all of the client installation steps.

You can install Wise Package Studio Client silently from the command line. See Installing

Wise Package Studio Client Silentlyon page 27.

Also see About the Client-Server Configuration of Wise Package Studioon page 26.

Installing Wise Package Studio Client Silently


You can install Wise Package Studio Client silently from the command line, using the

following Windows Installer command line options:

! /qn causes installation to be silent.

! /i causes installation.

These options are described in the Windows Installer SDK Help, which is included in

Windows Installer Editor.

To install the Full Client with the .EXE installer:

MODE="Client" CLIENT="Full" SHAREPOINT="\\SERVER1\Wise

Share Point" WPSDIR="\\Server1\Wise Package Studio" SERIALS="ABCD-ABCD-ABCD-

ABCD|LMNO-LMNO-LMNO-LMNO|WXYZ-WXYZ-WXYZ-WXYZ" /qn /i


28/58


29/58


30/58


31/58

31

Integrating Application Gateway and Wise Package Studio

6. The Proxy Settings dialog appears, which contains an Exceptionslist. The

Exceptions list consists of a semicolon-delimited list of Web addresses that access

the Internet directly without using the proxy server.

7. In the Exceptionslist, add the Application Gateway URL. (Example: http://server/

gateway)

8. Click OK on the Proxy Settings dialog, and then click OK on the Local Area Network(LAN) Settings and Internet Options dialogs.

Configuring IIS for Application Gateway

" Application Gateway module only.

Internet Information Server 5.0 or later only

You cannot configure these settings on versions of IIS earlier than 5.0 because the earlier

versions do not have the Internet Services Manager that is needed to configure the settings.

If you have Internet Information Server 5.0 or later, you should change certain settings

in Internet Services Manager after you install the Application Gateway server. These new

settings provide a custom error page for Application Gateway to use instead of the

default error page.

Do the configuration on the same computer on which you installed the Application

Gateway server.

1. Access Internet Services Manager for the computer that is running Application

Gateway.

2. Under the default Web site tree in Internet Services Manager, navigate to the

Application Gateway virtual directory and display its Properties dialog.

3. Click the Custom Errors tab.

4. In the HTTP Error list, click the HTTP Error 500 and click Edit Properties.

The Error Mapping Properties dialog appears.

5. Set the properties:

From Message Type, select URL.

In URL, enter:

/Application Gateway/_ScriptLibrary/ErrorReport.asp

Click OK to save the changes and close the dialog.

6. In the HTTP Errors list, click the HTTP Error 500;100 and click Edit Properties. Set

the properties the same as you did in the preceding step.

7. When you finish setting properties, click Apply on the Gateway Properties dialog and

then click OK.


32/58


33/58


34/58

34

Registering Your Software

Registering Your Software

It is very important that you register your software. By registering, you are qualified to

receive technical support via newsgroups and e-mail, plus notifications about future

product upgrades. If you did not register your software online during installation, you

may do so in either of the following ways.

Register Online

1. Connect to the Internet.

2. Do either of the following:

In Workbench, select Help menu > Wise on the Web > On-Line Registration.

In your browser, go to www.wise.com/product_registration.asp.

Your browser opens to the Product Registration page on the Wise Solutions Web

site.

3. Click the Wise Technical Support Center link on the Web page and create a new user

profile or log into an existing user profile. Follow the on-screen instructions to

complete the registration.

Register by Mail

If you are unable to register online, you can register by completing the registration card

included with your software and mailing it to Wise Solutions. Complete all the

information on the card and mail it. If you are not mailing in the United States, affix the

proper postage before mailing.
http://www.wise.com/product_registration.asphttp://www.wise.com/product_registration.asp


35/58


36/58

36

! This tutorial assumes that you are installing the sample application, QuickFacts, on

your computer for the first time. If you have installed QuickFacts on your computer,

uninstall it and remove any files and registry keys related to it. Files left from

previous installations can cause your results to deviate from the information

presented in this tutorial.

Import a Sample Package into the Software Manager DatabaseIn this procedure, you import a sample package into the Software Manager database.

Later in the tutorial, you will detect conflicts between this sample package and the new

package you create.

Frequently, you will need to import a package into the Software Manager database

without repackaging. You might do this with a package that has already been approved

and deployed so that all packages that have been installed throughout your company

are in the Software Manager database.

To import a sample package:

1. Click Start and select Programs > Wise Solutions > Wise Package Studio.

The Wise Package Studio Logon dialog appears.

2. Enter your logon information and click OK.

Wise Package Studio opens.

3. Click the Tools tab. At the top of the Tools tab, double-click Software Manager.

Software Manager opens.

4. Select Packages menu > Import.

The Import Type dialog appears.

5. Mark Import a single file into the Software Manager databaseand complete

the dialog:

File

Browse to the Tutorial subdirectory under the Wise Package Studio directory and

open Sample Conflict.msi.

Distribute source files to the share point directory

Mark this checkbox to copy the packages source files to the share point

directory.

Overwrite existing application and package

Mark this checkbox to overwrite any package that is already in the database with

the same application and package names.

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.

6. Click Next on the Import Type dialog.

The Package Details dialog appears.

7. Complete the Package Details dialog:

Application Name

Enter Sample Conflict. This identifies the application in the Software Manager

database.


37/58

37

Package Name

Enter Conflict 1.0. Typically, you use the application name plus specific version

information as the package name.

Use Transactions for Import

Leave this checkbox cleared.

8. Click Next on the Package Details dialog.

The Transforms and Patches dialog appears.

9. Click Finish.

The package you selected is imported into the Software Manager database. It

appears in Software Managers Applications/Packages pane.

10. Close Software Manager.

The right pane in Workbench reappears.

You have finished importing a package into the Software Manager database. Next, you

will create a new project in Wise Package Studio.

Create a New ProjectIn this procedure, you create a new project named QuickFacts in Wise Package Studio.

The project defines the name and location of files, as well as the project name and other

information. You also assign a repackaging process to the project. This process contains

tasks that you will complete as you follow this tutorial. The tasks guide you through the

basic steps of repackaging. All tasks automatically access the appropriate project files.

Note

Follow the instructions exactly as presented, otherwise your results can deviate from the

information presented in this tutorial.

To create a new project:

1. If Wise Package Studio is not open, open it and log on.

2. Select File menu > New Project.

The Project Setup dialog appears. A new project appears in the Project list on the

left and is selected by default.

3. Complete the right pane:

Project Name

Type: QuickFacts

Project Directory

Leave the default.

Status

Leave the default of Open.

Product VendorSelect Wise Solutions.

Application Name

Type: QuickFacts

Package Name

Type: QuickFacts version 2.0

File Name

If a default does not appear, type: QuickFacts


38/58

38

Vendor Package

Do not type in this field. Instead, click the button next to the field. Navigate

to the Tutorial subdirectory under the Wise Package Studio directory and open

QuickFactsInstall.exe.

Project Owner

This field appears with Enterprise Management Server only. Leave the default.

Process

Select Repackage for Windows Installer. The Repackage for Windows

Installer process contains the tasks for repackaging an installation into a

Windows Installer package.

Your Project Setup dialog should look like this:

4. On the Project Setup dialog, click Close.

5. If the Projects tab is not displayed in the left pane of Wise Package Studio, click it.

6. From Active Project, select QuickFacts.

The Projects tab displays the process youll follow to repackage the QuickFacts

application. This process consists of a set of tasks that appear in the Tasklist.


39/58


40/58

40

4. Click Settings.

The SetupCapture Configuration dialog appears.

5. Click the File and Folder Exclusions tab.

If a message about file exclusions located under your user profile appears, click Yes.

6. Click Add on the File and Folder Exclusions tab.

The File Exclude dialog appears.

7. Leave the Directoryfield blank.

8. In File/Wildcard, enter *.tmp and click OK on the File Exclude dialog.

This adds *.tmp to the list of files that SetupCapture will ignore when it captures an

installation.

9. Click the Directories to Watch tab and note the drive letter that will be watched.

When you install QuickFacts later in this tutorial, install it to this watched drive.

10. Click OK on the SetupCapture Configuration dialog.

The Welcome dialog reappears.

11. Click Next on the Welcome dialog. What happens next depends on the version of

Windows you are using.

If you are using Windows NT, 2000, or XP, the Capture Methodology dialog

appears.

If you are using Windows 95, 98, or Me, the Capture Methodology dialog is

skipped. The capture methodology is permanently set to use snapshot

comparisons because of operating system limitations. You can skip the next

step.

12. If the Capture Methodology dialog appears, do the following:

Mark Snapshot.

Make sure Use SmartMonitor in conjunction with Snapshotis cleared.

Click Next.


41/58

41

Note

Snapshot comparisons look at the difference between a before snapshot of the system

and an after snapshot to determine what happened during the installation.

13. If SetupCapture previously scanned your computer, the Initial Scan dialog appears.Mark Rerun the initial scanand click Next.

The Begin Installation Capture dialog appears.

14. Click Next on the Begin Installation Capture dialog.

SetupCapture scans your computer; this might take several minutes. When the scan

finishes, the Execute Installation dialog appears. The vendor package that you

specified in the QuickFacts project appears in the .EXE Namefield. This is the

installation that you will capture.

15. Click Execute on the Execute Installation dialog.

The QuickFacts 2.0 Setup program opens in front of SetupCapture:

16. In the QuickFacts 2.0 Setup program, step through the installation and accept all

default settings.

This installs a sample application named QuickFacts on your computer.

17. When the QuickFacts installation finishes, click Next on the Execute Installation

dialog.

The End Installation Capture dialog appears.

18. Click Next on the End Installation Capture dialog.

SetupCapture scans your computer for a second time to determine what changed.

This might take several minutes. When the scan finishes, the SetupCapture

Inclusions dialog appears, which lists all the files, registry entries, shortcuts, and

.INI file changes that will be included in the repackaged installation.


42/58

42

Typically, you exclude from your installation those files and registry entries that are

not applicable to all computers, or are not applicable to Windows Installer

technology. Additional files that are not related to QuickFacts might be included in

the list. Examples: temporary Internet files, cookies, and files that have to do with

software that runs constantly in the background, such as virus protection software.

Note

You can enlarge the window in the SetupCapture Inclusions dialog by dragging the lower

right corner. You can also widen the Directory or File columns.

19. To exclude extraneous files, select the file name in the list box and click Exclude.Keep the QuickFacts files listed below. Exclude any other files.

Consulting and Training.bmp

Consulting and Training.qft

Developer Products.bmp

Developer Products.qft

License.txt

QckFacts.exe

QFGUITAM.dll

QuickFacts.cnt

QuickFacts.hlp

ReadMe.txt

System Administrator Products.bmp

System Administrator Products.qft

20. To display registry entries on the SetupCapture Inclusions dialog, select Registry

keysfrom Inclusion Type.

21. If necessary, exclude extraneous registry keys (example: those related to

uninstalling) by selecting the key in the list box and clicking Exclude.

Keep all registry entries with QuickFacts or QckFacts in their Key name. Registry

keys for file associations vary by operating system. The list should include registry

keys with the following ValueNames:

CaptionFontName


43/58


44/58

44

25. Click Finish.

This saves the captured installation in Windows Installer format and copies the

directory structure and source files of the installation to the Projects\QuickFacts

subdirectory of your share point directory. This lets you create and edit your

QuickFacts.msi package using relative paths, independent of the original

installation.

26. If the Files in Repository dialog appears, click OK.

You have finished capturing the QuickFacts installation. On the Projects tab, the

checkbox next to the Create package task is marked to indicate that the task is

complete. Next, you will customize the QuickFacts installation.

Edit the Package InstallationIn this procedure, you open the QuickFacts installation package you captured in the

previous procedure, and then customize it for your organization. The Edit Package task

runs Windows Installer Editor, which is an installation development environment for

Windows Installer.

Windows Installer Editor has 3 views: Installation Expert, MSI Script, and Setup Editor.

Each view provides a different development environment. In this tutorial, you use

various pages in Installation Expert. Each page lets you review and edit a specific aspect

of your installation.

Before you follow this procedure, you must have completed the previous procedure inthis tutorialCreate the QuickFacts Packageon page 39as well as all preceding

procedures.

To edit the package installation in Windows Installer Editor:

1. Make sure you are in Wise Package Studio with the Projects tab selected and

QuickFactsselected in the Active Projectdrop-down list.

2. Click the Run link next to the Edit package task.


45/58

45

The repackaged QuickFacts installation (QuickFacts.msi) opens in Windows Installer

Editor.

3. Make sure you are in Installation Expert by clicking the Installation Expert tab at the

lower left of the window.

NoteAlong the left side of the window are page group headings (example: Project Definition),

below which appear linked page names. Click a page group name (example: Project

Definition) to expand or collapse it. Click the page names below the page group names to

go to a particular page.

4. In the Project Definition page group, click Product Details.

The Product Details page appears, which contains the installations meta data.

Because you entered much of the required information during SetupCapture, most

of the fields are populated.

Enter the information that is not populated:

Application

Enter: QuickFacts

Package

Enter: QuickFacts version 2.0

Product Type

(Read-only.)

Product Name

QuickFacts

Manufacturer

Wise Solutions

Version

2.0

Default Directory

Program Files\QuickFacts

Package Path

(Read-only.)

Repository ID

Leave this blank.

Product Code

Leave the default. This is a unique code, called a GUID, that Windows Installer

uses to identify the product.

Target Platform

(Read-only.)

Application Type

Make sure this is set to Win32 (non .NET). Installation Target

Make sure this is set to Windows-based desktop/server PC.

Description

(Optional.) Enter: This is a sample application

5. (Optional.) In the Project Definition page group, complete the General Information

page and the Add/Remove Programs page. To display context-sensitive help on

these or any other Installation Expert pages, press F1.


46/58


47/58

47

Turn on the Readme dialog by marking its checkbox.

Select the Readme dialog and click Import Text, which is to the right of the

dialog preview.

On the Open dialog, navigate to \Projects\QuickFacts\Program

Files\QuickFacts, where is the path to your share point directory.

This is the location of the source files for this package, which were copied duringSetupCapture. Change the Files of typedrop-down list to Text files (.txt).

Open the ReadMe.txt file.

The ReadMe text appears in the Readme Information dialog preview and will

appear in this dialog during installation.

13. Save the installation by selecting File menu > Save.

14. Close Windows Installer Editor.

You have finished customizing the QuickFacts installation and the Application Integration

phase of the Repackaging for Windows Installer process is now complete. On the

Projects tab, the checkbox next to the Edit package task is marked to indicate that the

task is complete. Next, you will validate the package you created.

Validate the Installation PackageIn this procedure, you validate the QuickFacts package, which is the first step in the

Package Testing phase. The Validate compliance with standards task runs Package

Validation, which verifies that the package complies with Microsofts Application

Specification for Windows 2000.

Before you follow this procedure, you must have completed the previous procedure in

this tutorialEdit the Package Installationon page 44as well as all preceding

procedures.

To validate the package:

1. Make sure you are in Wise Package Studio with the Projects tab selected and

QuickFactsselected in the Active Projectdrop-down list.

2. Click the Run link next to the Validate compliance with standardstask.

Dialogs appear briefly and the .WSI is compiled into a .MSI. The Welcome dialog for

the Package Validation tool appears, listing the predefined validation tests that can

be performed. To see a description of each test, click the test name, and the

description appears at the right of the dialog.

3. Mark Windows Installer SDK Internal Consistency. If necessary, clear all other

checkboxes.

4. Click Next.

The test runs. This might take a few minutes. When the test finishes, the View /

Correct dialog appears, which lists all the possible problems detected.

Normally, no errors appear for QuickFacts, although for more complex installations,

errors are more likely to appear. If there were errors and if the Correct buttonbecame enabled when the error was selected, you could click Correct to resolve the

problem. Otherwise, you would open the installation in Windows Installer Editor, fix

the error, and recompile. Errors are documented in the Windows Installer SDK Help.

Start with the topic Internal Consistency Evaluators - ICEs.

5. Click Finish on the View / Correct dialog.


48/58


49/58


50/58

50

When you open a package in Test Expert, the Master Test Plan for that package is

displayed. Each time you open the package, the package is read and test cases are

generated based on the contents of the package. In addition to the Master Test Plan,

you can add user-defined test cases to fully test the package for the requirements of

your organization. In this tutorial, you only perform 2 of the test cases provided in

the Master Test Plan.

5. In the Installation Tests section in the left pane, select the Verify Installation test

case.

The Verify Installation page appears in the right pane. This test case ensures that

the installation runs without errors by installing the QuickFacts package you created

during SetupCapture.

6. Click Install on the toolbar at the top of the window. Then, in the Welcome dialog,

click Cancel to skip the Machine Capture.

Machine Capture is only necessary if you plan to perform Uninstall Tests, which are

skipped in this tutorial.

The QuickFacts Setup program opens in front of Test Expert.

7. In the QuickFacts Setup program, step through the installation and accept all default

settings. This installs the QuickFacts package.

8. If the QuickFacts installation ran without errors, from Status of Test Case, select

Passed. A check mark icon appears next to the Verify Installation test case.

9. In the Application Execution Tests section, select the File Coverage test case.

A list of all f iles accessed by the QuickFacts application appears on the All Test Items

tab in the right pane. The File Coverage test case indicates which installed files are

accessed as the application is run.

10. Click Run on the toolbar.

The Run Application Execution Tests dialog appears.

11. In the File to Run list, select QckFacts.exeand click OK.

The QuickFacts application opens and the Application Monitor window appears.

Note

You must leave the Application Monitor window open while you exercise the functionality

of the application because your system is monitored only when it is open. Move or

minimize it if necessary.

12. To test the QuickFacts application, use every function.

In the Select an item to see factslist, select all 3 items, one at a time.

Select Help menu > Help Contents.

Select Help menu > QuickFacts Readme.

Click About in the lower right of the QuickFacts dialog.

As files are accessed, the Application Monitor window is updated. When you finish

testing, the File Coverage graph in Application Monitor indicates the percentage of

the files that were accessed.

Note

Some files are not accessed by an application during normal use. Example: In the

QuickFacts application, License.txt is not accessed during normal application execution.


51/58


52/58


53/58

53

Conflict detection begins, and may take a few minutes. While the conflict detection

is running, the status is displayed at the right end of the toolbar.

4. When the status of the conflict detection process is Idle, expand the QuickFacts tree

in the Applications/Packages pane and select the QuickFacts version 2.0 package.

In the Conflict List pane, a conflict for QFGUITAM.dll appears. The red exclamation

point next to it indicates that it is classified as an error. If warnings existed, whichare not as serious as errors, they would appear in this list with yellow question mark

icons.

5. To fix the conflict, select Conflicts menu > Resolve.

The Welcome dialog of the Resolve wizard appears.

6. From Application, select QuickFacts.

QuickFacts version 2.0appears in the Packagefield.

7. From Isolation method, select Isolated Components (Windows 98 SE/Me/

2000/XP).

Isolating a conflict means that each application will use its own version of the

conflicting file. The files will be stored in different directories, and will be managed

by Windows Installer.8. Click Next.

The File Conflicts dialog appears. The upper list box contains the name and

information of the file in your package that has conflicts (QFGUITAM.dll). The lower

list box contains the package and file that QFGUITAM.dll conflicts with.

9. Select QFGUITAM.dll in the upper list box and click Move on the right of the File

Conflicts dialog.

The exclamation point becomes white to indicate that the problem has been fixed.

Because you selected Isolated Componentsas the Isolation Method, the Move

button isolates the file so that each package that uses QFGUITAM.dll will use its own

version. This means that a copy of QFGUITAM.DLL will be installed into the

QuickFacts directory, and QuickFacts will reference its own copy of the .DLL file.

10. Click Next on the File Conflicts dialog.The File Conflicts in Registry dialog appears, which should be empty.

11. Click Finish.

In the Conflict List pane, a yellow question mark icon appears next to QFGUITAM.dll.

The file conflict has been resolved by isolating the file in different directories but is

still listed as a warning. This is because 2 installation packages install a non-16-bit

file with the same file name but different file information (file version number or

date/time) to different directories. Also, the File Conflicts bar graph in the Summary

pane indicates 1 warning.

12. To view only errors (red exclamation points) in ConflictManager, not warnings

(yellow question marks), do the following:

Select Conflicts menu > Filter to display the Conflict Filter dialog.

In the Conflict Types to Display section, clear Warnings.

Click OK.

The conflict filter is globally set to show only errors in the Conflict List display.

13. Select Packages menu > Export and Recompile.

The Export Changed Packages and Recompile dialog appears, listing your QuickFacts

package.


54/58


55/58


56/58

56

6. Close Software Manager and Wise Package Studio.

You have completed this tutorial.


57/58

57

Index

Symbols.NET Framework

requirements 13

AAccess 12

Application Gateway 20

about 29

bypassing proxy 30

custom configuration 31

database configuration 20

default URL 29

IIS version 31

illustration 30integration issues 29

requirements 12

authentication

databases 21

Available status 54

Cchecking for updates 9

client installation

about 26

full 18

installing 27

minimal 19

silently 27

why use 26

complete installation 17

conflict resolution 52

ConflictManager 52

create new users 24

creation options (database) 25

Ddatabase

configuration issues 20

connection 21

creating new users 24

creation options 25

requirements 12

specifying type 22

database setup dialogs 22

distribution

to end users 54

to share point 51

documentation, using 6

domain logon 33

EEnterprise Management Server 19

Ffull client 18

GGetting Started Guide 6

grant db access 19, 21

guest account 21

Hhelp

about 6

using 7

Windows Installer SDK 6

IIIS

grant db access 19

version for Application

Gateway 20, 31

version for Quality Assurance 19

import package 36, 52

installation

client 27

complete 17

what you need 14

Llaunching Wise Package Studio 32

logon

current Windows logon 33

if logon fails 32

options 32

specifying 23

to network 33

Windows NT domain 33

Workbench 32

MManagement Reports 20

database configuration 20system requirements 12

manual

accessing online 6

Microsoft Access 12

Microsoft Data Engine 12

Microsoft Internet Information Service

see IIS

Microsoft SQL Server 12

minimal client 19

MSDE 12

Nnetwork logon 33

new features

Refer to Release Notes

newsgroups 7

Ppackage

creating 39

distributing 51, 54editing installation 44

importing QuickFacts 52

importing sample 36

making available 54

removing samples 55

repackaging 39

testing 48, 49

validating 47

Package Distribution 51, 54

Package Validation 47

Preflight

about 19

database 22

database configuration 20

system requirements 12

prerequisites

.NET Framework 13

database 12

installation 11

tutorial 35

Professional Edition 17

project creation 37

proxy server, bypassing for

Application Gateway 30

QQuality Assurance module 19

Rreadme

See release notes

reference manual

See manual

registration, product 34

release notes 6

resolve conflicts 52


58/58

Wise Package Studio Getting Started Guide 004

Documents

Transcript of Wise Package Studio Getting Started Guide 004