Corel PaintShop Pro - X9 Deployment Guide

Introduction

As you read through this guide,
you’ll find that the right column
of each page contains the main
content, while the left column
contains the following categories
of information:

definition — explains the
italicized term or concept

tip — presents a helpful
detail, such as a shortcut,
variation, or benefit

note — presents an
additional detail about the
specified topic or task

warning — presents a
crucial detail about the
specified topic or task

The left column also gives you
room to jot down notes.

This guide is intended to help you deploy Corel® PaintShop® Pro X9
(Corporate and Education Edition) to your network as quickly and
easily as possible.

Contents

Stage 1: Preparing for deployment . . . . . . . . . . . . . . . . . . . . . . . 2

Stage 2: Creating the server image . . . . . . . . . . . . . . . . . . . . . . . 3

Stage 3: Installing the software . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Stage 4: Maintaining the installations . . . . . . . . . . . . . . . . . . . . 15

Additional resources

If you are new to software deployment or otherwise require more

®

basic information on deploying Corel

software products, please
refer to the Corel® Beginner’s Guide to Network Deployment. You
can request a copy of this guide from your Corel® Support Services
representative.

For even more information, see the following Web resources.

Web resource Description

Corel® website:

www.corel.com

®

Corel

Support Services

website:

www.corel.com/support

®

Corel

Knowledge Base™:

www.corel.com/kb

Information about Corel Corporation
and its portfolio of software products

Information about product features,
specifications, pricing, availability,
services, and technical support

A searchable repository of articles
written by the Corel Support Services
team

For help with the Microsoft Windows Installer (MSI) technology
that is used to install the software, please refer to the Microsoft
website

Deployment Guide
Introduction 1

Stage 1: Preparing for deployment

As used in this guide, the
term “network” signifies

two or more computers
that are connected to each
other for the purpose of
exchanging information.

Workstations are the

computers from which

the average user works,
and servers are the computers
that manage the shared
resources of the network.

To more easily manage

the access rights of

workstation users, you
may want to use Group Policy
Objects (GPOs, or “system
policies”). See “Managing
permissions with Group Policy
Objects” on page 5.

To deploy the software to your network as smoothly as possible,
you can prepare by doing the following:

• Check the system requirements for the software.

• Prepare the server.

• Prepare the workstations.

For details, see below.

Checking the software requirements

To begin, make sure that your server and workstations are eligible
for the software. Consult the following:

• Readme file for the software (if available)

• product-information page on the Corel website (

• any other special instructions for the software

Preparing the server

• Make sure that the server meets the minimum system
requirements for the software, and that it has enough free disk
space for the installation.

• Make sure that the operating system on the server has been
updated with the latest service packs and security patches.

• Make sure that you have the proper permissions for creating a
software image on the server. You must be either a local
administrator or an administrator for the domain that you are
managing, and you must have read/write access to the server
location.

www.corel.com)

Preparing the workstations

• Make sure that the workstations meet the minimum system
requirements for the software, and that they have enough free
disk space for the installation.

• Make sure that the operating systems on the workstations have
been updated with the latest service packs and security patches.

• Make sure that anyone who will be installing the software from
the server image has the proper permissions to do so. To install
the software on a workstation, you must be either a local
administrator or an administrator for the domain that you are
managing, and you must have read access to the server location.

Deployment Guide
Stage 1: Preparing for deployment 2

Stage 2: Creating the server image

A server image, also called
an “administrator image”

or simply an “image,” is a
set of uncompressed application
files on the server that is created
from a set of compressed files on
the installation disc.

A command line is a textual

command that lets you

specify desired settings.

To mount an ISO file,
you might require third-

party software that
helps you create a virtual drive.
Alternatively, you can burn the
ISO file to a CD/DVD and
access the files from the disc.

After preparing for deployment, you’re ready to create a server
image of the software, from which you can install the software to

the workstations. (If you want to support multiple installation
types, you can even create multiple server images: one for each
desired configuration.)

Contents

Creating a server image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Finalizing the server image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Creating a server image

To create a server image, you run a command line that initializes
the software setup and specifies your desired installation settings.

To run a command line

1 Open the Run dialog box (shortcut key: Windows Logo + R).

2 Type the command line in the Open box, and then click OK.

To create a server image

1 Do one of the following:

• If you have an installation disc, insert the disc into the CD/DVD
drive.

• If you downloaded an ISO file, mount the ISO to a directory or
extract the files from the ISO image to a directory on your
server by using a utility such as WinZip® (available from
www.winzip.com).

If the AutoRun screen opens, click Exit.

2 Run the following command line, where X: is the directory

where the disc, ISO, or extracted files are located.

X:\Setup.exe /a

3

Type your user name and serial number (with or without hyphens) in the boxes provided, and then click Next.

The customer information that you provide is passed on to the
workstations when the software is deployed to the network. By
default, users can change the user name but not the serial
number.

4 Specify a network location for the server image. To change the

default location, type a valid server path in the Network location
box, or click Browse to browse to a valid network location.

Deployment Guide
Stage 2: Creating the server image 3

5 If you want to allow workstations to detect and download

Proceed with extreme
caution when using the

/q switch to create a

server image.

To change the location of
a server image, you must

create a new image at the
new location. You cannot copy
an image from one location to
another.

product updates, enable the Product updates check box.

6 Click Install to begin copying the files to the server.

If you click Cancel, you are prompted to confirm that you want
to cancel creating the server image. Cancelling “rolls back” the
setup and undoes most of the changes made; however, some
manual clean-up may be required.

7 Click Finish.

You can also

Create a server
image silently
(or with limited
UI)

Create an error
log

Use the following command line (where X: is the
directory where the disc, ISO, or extracted files are
located; image_location is the desired location of
the server image; and serial_number is the assigned
serial number for the product):

X:\Setup.exe
TARGETDIR="image_location"
SERIALNUMBER="serial_number" /q /a

The /q switch is used to restrict the amount of the
user interface that appears during installation. For a
list of switch parameters, see page 7.

Use the following command line (where
is the location and filename of the log file):

X:\Setup.exe /l "log_file" /a

For a list of the parameters that are available for
the

/l switch, see page 8.

log_file

Finalizing the server image

Before deploying from the server image, you may want to take the
following steps.

Check for software updates

Check for software updates, and apply them to the image as
necessary. This way, you can avoid having to deploy the software
twice. For details, see page 16.

Test the image

Test the image with a small subset of workstations before rolling it
out to your entire organization.

Deployment Guide
Stage 2: Creating the server image 4

Stage 3: Installing the software

Looking for command-

line switches and public

properties? See “Pushing
the software” on page 6.

Pulling the software

involves having the

workstation users
themselves execute the
software installation and
perhaps even choose their own
installation options.

Group Policy Objects

(sometimes called

“system policies”) reside
in a central location on a
Windows-based network and
define how each workstation is
configured.

You can install the software on the workstations in two main ways:

• by having the users themselves install (or “pull”) the software
from the server image to their workstations

• by using a command line to install (or “push”) the software from
the server image to the workstations on the users’ behalf

Contents

Pulling the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Pushing the software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Pulling the software

Workstation users themselves can install (or “pull”) the software by
using one of the following methods:

• browsing to the location of the server image, double-clicking
Setup.exe, and following the instructions in the setup. This is the
most common method for pulling the software.

• running a command line that installs the software from the
setup on the server image. Typically, this method is reserved for
push-installation scenarios (see page 6).

Managing permissions with Group Policy Objects

To install the software, workstation users require administrator­level privileges. To assign such privileges, Windows-based networks
use Group Policy Objects (or “GPOs”): items stored in a central
network location and used to automatically update the registry
settings on each workstation when its user logs in to the network.

If you want to give users administrator-level access rights (either
temporarily or permanently), you may need to configure the GPOs
for your network by using a Group Policy Editor.

For general help with GPOs, please refer to the Software
Development Kit (SDK) for Group Policy.

To access the Group Policy Editor for Windows

1 Open the Run dialog box (shortcut key: Windows Logo + R).

2 Type gpedit.msc in the Open box, and then click OK.

Deployment Guide
Stage 3: Installing the software 5