This guide was developed as a step-by-step resource for deploying
Corel® Painter™ 12 to your network.
In this introductory section, you’ll learn a bit about the software, this
guide, and Corel Corporation.
• About Corel Painter 12
• About this guide
• About Corel
About Corel Painter 12
Corel Painter 12 is the ultimate digital art studio. Its inventive drawing
tools, realistic brushes, cloning capabilities, and customizable features let
you expand your creative output in exciting new ways. When you use
the pressure-sensitive brushes of Corel Painter, they become fluid
extensions of your hand, so the resulting brushstrokes are unrivaled in
texture and precision. What’s more, features such as the ability to build
your own Natural-Media® brushes and customize how brushes interact
with the canvas give you countless ways to develop your artistic ideas.
Corel Painter 12 takes you far beyond what’s possible in a traditional art
environment.
This guide focuses on the
Windows®-based version of
Corel Painter 12. For information
specific to the Mac OS®–based
version, see “Can I deploy the software
in a Mac OS environment?” on
page 46.
This software is an excellent choice for networked environments because
it offers a robust deployment process for easy installation and
enance.
maint
About this guide
This guide applies to all network-deployable editions of the software.
However, please note that some features are available only in certain
editions. (Any such features are specially noted.)
This guide contains the following chapters:
• Chapter 1: Getting started introduces you to the processes and
terms that are used when deploying Corel® software to a network. If
you’re new to software deployment, you’ll find that this chapter
walks you through the basics — but if you’re an “old pro,” feel free
to skip this chapter entirely.
Deployment Guide
Introduction1
Page 5
• Chapter 2: Understanding the software lists the system
requirements and technical specifications for
Corel Painter 12.
• Chapter 3: Creating the server image describes how to create an
image of the software on a server. This step is mandatory if you
want to maintain all workstation installations from a central
location.
• Chapter 4: Installing with command lines illustrates how to
customize a command line that installs the software on the
workstations.
• Chapter 5: Pulling the software to the workstations shows how
to enable workstation users to install the software on their own.
• Chapter 6: Pushing the software to the workstations explains
how to establish an automatic process for installing the software on
the workstations.
• Chapter 7: Maintaining the software demonstrates how to
repair, update, and remove the workstation installations of the
software.
The appendixes provide useful supplementary information:
• Appendix A includes quick-reference topics for key deployment
information. If you print only one section of this guide, make sure
that it’s this one!
• Appendix B covers some of the most frequently asked questions
(or “FAQs”) about deploying the software.
You’ll also find a glossary, which defines the terms that are used in this
guide.
What’s the best way to use this guide?
If you’re new to the field of network deployment, you may want to read
this guide from cover to cover. You’ll find that the right column of each
page contains the main content, while the left column contains
additional details — definitions, tips, notes, and warnings. The left
column also gives you room to jot down notes.
If you are familiar with deployment processes, or if you want to focus on
a particular topic or specific question, try the following techniques when
using this guide:
• Skim the table of contents for relevant headings.
• See the index for key features and important concepts.
• Check Appendix A for quick-reference topics.
• Consult Appendix B for frequently asked questions.
Deployment Guide
Introduction2
Page 6
The documentation conventions that are used in this guide are explained
in the following table.
Wherever you see thisYou’ll find
A definition — explains a term or
concept
A tip — presents helpful information,
such as procedure shortcuts, variations,
or benefits
A note — presents supplementary
information about the specified topic or
task
A warning — presents crucial
information about the specified topic or
task
bold textInformation that is emphasized for
clarity, such as the name of a control or
other element on the user interface
italicized textThe first instance of a term that is
defined in the glossary
<italicized text between angle brackets> A placeholder for user-specified
information, such as a path or filename
bold monospace textA reference to programming syntax.
For clarity, some programming
elements are further distinguished by
italics.
Where can I find more information about the software?
For comprehensive information about the software and its features,
you can consult the product documentation. From within the software,
you can access a Help system by clicking Help ` Help topics. In
addition, you can find a PDF-based user guide at the following location
(where X: is the drive where the software is installed):
X:\Program Files\Corel\Corel Painter 12\Resources\<language>\
Help
Deployment Guide
Introduction3
Page 7
For even more information about the software, please see the following
online resources.
ResourceDescription and URL
Corel Painter websiteProvides the latest news, tips and
tricks, and information about upgrades
www.corel.com/painter
Corel® Support Services websiteProvides prompt and accurate
information about product features,
specifications, pricing, availability,
services, and technical support
www.corel.com/support
® Knowledge Base™Provides a repository of articles, written
Corel
by the Corel® Technical Support
Services team in response to questions
by users, that you can search by
keyword
www.corel.com/knowledgebase
Corel Painter online communityProvides interaction with other users
through sharing experiences, asking
questions, and receiving help and
suggestions
www.painterfactory.com
If you have any comments or suggestions about this software or its
deployment guide, please submit them by using the contact information
provided at www.corel.com/contact.
For help with the Microsoft® Windows® Installer technology
that is used to install the software, please refer to information on the
Microsoft® website.
About Corel
Corel is one of the world’s top software companies, with more than 100
million active users in over 75 countries. We develop software that helps
people express their ideas and share their stories in more exciting,
creative, and persuasive ways. Through the years, we’ve built a
reputation for delivering innovative, trusted products that are easy to
Deployment Guide
Introduction4
Page 8
learn and use, helping people achieve new levels of productivity. The
industry has responded with hundreds of awards for software
innovation, design, and value.
Our award-winning product portfolio includes some of the world's most
widely recognized and popular software brands, including
CorelDRAW® Graphics Suite, Corel® Painter™, Corel DESIGNER®
Technical Suite, Corel® PaintShop Photo® Pro, Corel® VideoStudio®,
Corel® WinDVD®, Corel® WordPerfect® Office, WinZip®, and
Corel® Digital Studio™ 2010. Our global headquarters are in Ottawa,
Canada, and major offices are in the United States, the United
Kingdom, Germany, China, Taiwan, and Japan.
For more information
about Corel Corporation, please visit www.corel.com.
Deployment Guide
Introduction5
Page 9
Chapter 1
p
A
Getting started
If you’re new to software
deployment, you’ll find that
this chapter walks you through the
basics. However, if you’re an “old
ro,” feel free to skip this chapter
entirely.
For an at-a-glance overview of
the deployment process, see
ppendix A.
For a list of the terms that are
used in this guide, see the
administration server.
So you want to learn how to deploy Corel software to your organization’s
network...
Maybe you’re already an expert in software deployment. Or maybe you
were chosen for this task because you have the most experience with
computers. Either way, this chapter walks you through the basics of
what you need to know to successfully deploy this product to your
network.
Depending on your situation, the deployment may consist of a few
simple steps or a complex set of procedures. This chapter provides a
nontechnical overview of software deployment and can help you choose
the best deployment process for your needs. Subsequent chapters
instruct you on how to carry out the deployment.
This chapter also introduces much of the terminology that is used
throughout the guide.
This chapter answers the following questions:
• What is a network?
• How is a network managed?
• How is software deployed to a network?
• How is installed software best maintained?
What is a network?
A network is made up of
workstations and servers.
Workstations are the computers from
which the average user works, and
servers are the computers that manage
the shared resources of the network.
Servers are sometimes referred
to as “administration servers.”
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.
Most computers in a network are workstations — computers from which
average users do their work and access the common resources of the
network, such as shared folders and printers. Most workstations are
desktop computers that run software such as the Windows® operating
system.
Networks also contain servers. These are the computers that manage the
shared resources of the network, such as files, printers, and applications.
Most servers use a specially designed operating system, such as the
Windows Server® operating system.
Deployment Guide
Chapter 1: Getting started6
Page 10
How is a network managed?
Deployment is the systematic
and strategic distribution of
software to a network.
A network administrator
specializes in running a
network and deploying software to it.
A separate software license is
required for each workstation
in your network.
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.
Every network needs one person to make sure that all required software
is installed on — or, more typically, deployed to — its workstations. This
person is the administrator. An administrator may be a project manager, a
network administrator, or a deployment specialist. Regardless of these
differences in title or role, one of the administrator’s chief responsibilities
is to ensure that the software deployment runs smoothly.
You don’t need to be an expert in computer science to be an
administrator; you just need to know how to configure your network to
meet the needs of its users. By the time you finish reading this guide,
you’ll have no trouble doing just that!
How is software deployed to a network?
Most organizations require multiple users to have access to the same
applications. For this reason, when an organization chooses a software
product, it purchases one license for each workstation. Somebody must
then install one copy of the licensed software on each workstation.
Your organization may require you to provide a customized installation
of the software. However, installing the software on one workstation at a
time is not practical: Not only would you invest a lot of time, but you’d
have to redo your work if you forgot to set a desired option along the
wa y. Ob v i o u s l y, t h e m o r e co m pu t er s t h at your organization has, the less
viable it is to install and maintain your software manually.
Consequently, administrators typically use a deployment process to
install software on the workstations in their network. To do this, they
create a server image of the software and deploy the software from that
server image to the workstations.
A command line is a textual
command that lets you specify
desired settings.
A feature (or “component”) is a
set of files that makes up part of
an installed product.
How is a server image created?
A server image is created by using a command line to run the installation
wizard (or “setup”) which typically provides you with a few installation
options. Creating a server image is mandatory if you want to maintain
all workstation installations from a central location.
If you want to provide users with more than one installation type, you
can create more than one image. (For example, you may want to allow
some users to install a basic set of features and other users to install a
more advanced set. To do this, you would create one server image for the
basic version of the software and another for the more advanced version.)
Be sure to use a naming convention that lets you remember what each
server image contains.
Deployment Guide
Chapter 1: Getting started7
Page 11
For detailed information on creating a server image, see Chapter 3.
How is a server image used to deploy software?
To deploy software from a server image, you must design a
command line that specifies which options and features to make
available to your users. For detailed information on command lines, see
Chapter 4.
Deployment of the software to the workstations can be accomplished in
one of two ways:
• manually, by pull installation — Users “pull” the software to their
workstations by running the setup from the server image.
• automatically, by push installation — The administrator uses a
particular method to “push” the software from the server image to
the workstations so that the users themselves do not participate in
the installation.
How does a pull-installation scenario work?
If users have access to the server and administrator-level rights to their
workstations, they can install the software themselves. To do this, they
pull the software to their workstations by running the setup from the
server image.
Corel Corporation cannot
guarantee that all available
third-party push technologies work
with all Corel software products
Some products can be set to provide users with installation options when
the setup is run from the server image. For example, you may be able to
let users create a “run-from-network” installation by choosing to install
only the files that are necessary to run the software. However, it is
recommended that users install the software locally and in its entirety.
For detailed information on allowing users to pull the software to their
workstations, see Chapter 5.
How does a push-installation scenario work?
To push the software from the server image to the workstations, you
must begin by designing a command line that specifies your desired
installation options. For detailed information on command lines, see
Chapter 4.
From there, you can choose a push method for your command line.
Many administrators choose to use a third-party tool (or “push technology”) such as Microsoft® Systems Management Server or
IntelliMirror® management technologies.
Chapter 6 provides suggestions on using this third-party push
technology. For complete information on using a third-party push
technology, please refer to the manufacturer’s documentation.
Deployment Guide
Chapter 1: Getting started8
Page 12
What is the best way to prepare for deployment?
p
f
A Readme file contains
“release notes” or other
important information about the
roduct. Always consult the Readme
ile before deployment.
Before beginning to deploy the software, you must ensure that the
software is compatible with the server and all workstations. To do this,
you must check the system requirements for the software against the
capabilities of the server and the workstations. It’s also a good idea to
familiarize yourself with the Readme file (if available) or any other special
instructions for the software.
In addition, it’s wise to start thinking about how you want to deploy the
software to the workstations. Do you want to have the users pull the
software themselves? Or do you want to install the software for them by
using a third-party push technology? Your answers to these questions
will determine your ideal deployment process.
Before you begin the deployment, be sure to do the following:
• Get to know your network. Make sure that you have all the
required access rights for deploying software to it.
• Make sure that your inventory of the workstations is up-to-date, so that you know how the workstations are configured.
• Get to know your users and how they work. Do they use their
workstations all the time? Do they shut down their workstations at
night? Do they use laptops to access the network remotely? These
factors help determine how to deploy and manage the software.
• Consider how much disk space is required for the software to run on the workstations. Again, the amount of available space
influences how to deploy and manage the software.
• On the server, create a shared network location for installing
the server image.
• Configure test systems that mirror the workstations as closely
as possible, so that you can more easily diagnose issues.
Read Chapter 2 for deployment instructions specific to this product.
How is installed software best maintained?
An important part of administering a network is maintaining the
software that is deployed to it.
The registry is the Windows
repository for application
settings. The registry stores
information in keys.
You can help keep the workstations in top shape by repairing the
installed software when necessary. Repairing the software installs
missing files and by replacing any files, shortcuts, and registry entries (or
“keys”) that have become corrupt in the software.
The software may allow you to enhance the users’ experience by
modifying the installations. Modifying the software lets you add features
to (or remove features from) the installations on the workstations.
Deployment Guide
Chapter 1: Getting started9
Page 13
A service pack typically
f
contains a set of patches that
combine to make a major update to
the software.
You are strongly encouraged to keep the software up-to-date by
installing patches, such as the service packs that Corel Corporation provides
free of charge.
It’s always a good idea to upgrade to the latest version of the software.
Upgrading lets you take advantage of new features that can help
increase the productivity of your users. However, to make the transition
to the new version as easy as possible, you must correctly uninstall the
old version.
For information on repairing, modifying, updating, or removing the
installations, please see Chapter 7.
The Corel Knowledge Base is
an online repository of answers
to frequently asked questions about
Corel products. You can use it to search
or a specific topic.
Finally, administrators must be prepared to troubleshoot any problems
that arise. This guide contains some of the most noteworthy solutions,
such as for the frequently asked questions provided in Appendix B. You
can also look for answers in the Corel Knowledge Base — just go to
www.corel.com/support and click the appropriate link.
Deployment Guide
Chapter 1: Getting started10
Page 14
Chapter 2
Understanding the software
This chapter provides the system requirements and technical
specifications for Corel Painter 12. It can help make your network
deployment of the software as easy as possible.
This chapter answers the following questions:
• What is included in Corel Painter 12?
• What are the system requirements for the software?
• Where is the Readme file for the software?
• What access rights are required for installing the software?
• What files are required by the setup?
• What types of files can interact with the setup?
• How do I register the software?
• How do I maintain the software?
What is included in Corel Painter 12?
For information specific to the
Mac OS version of
Corel Painter 12, see page 46.
For information on making the
clipart available on
workstations, see “Can I make the
extra content on the DVD available
to workstation users?” on page 48.
Corel Painter 12 includes the Corel Painter application in both Windows
and Mac OS versions. Although this guide focuses on the Windows
version of Corel Painter 12, information specific to the Mac OS version is
provided in the section “Can I deploy the software in a Mac OS
environment?” on page 46.
What’s on the DVD?
The Corel Painter 12 DVD contains the installation files and application
files. These files are compressed, so you cannot simply copy them from
the installation disc to create a server image. For information on the
required installation files, see “What files are required by the setup?” on
page 14.
The Corel Painter 12 DVD also includes a folder of extra content, which
contains libraries of unique gradients, nozzles, patterns, stock photos,
paper textures, and brushes.
Deployment Guide
Chapter 2: Understanding the software11
Page 15
What are the system requirements
for the software?
For information on using
Windows Terminal Server, see
“Which server operating systems are
supported?” on page 19.
Additional hard-disk space
may be required for
Microsoft® .NET Framework 4.0.
To allow the installation of Corel Painter 12, workstations must include
the following:
• Operating system with the latest service pack and critical updates:
32-bit or 64-bit version of Windows 7, Windows Vista® or
Windows XP
•1 GHz (or greater) processor
•1 GB of RAM
• 600 MB of hard-disk space for installation of program files
• Mouse or tablet
• 1200 × 800 (or greater) screen resolution
• Microsoft® Internet Explorer® 7.0 or later
Where is the Readme file for the software?
The Corel Painter 12 DVD provides a Readme file that contains
important technical information about the software. It’s a good idea to
review the contents of this Readme file before you begin the
deployment.
To access the Readme file
You can also access the Readme
file from the Release notes
button on the AutoRun screen.
On a multi-language DVD,
each Readme file is stored in
its respective language folder.
1 Insert the Corel Painter 12 DVD into the disc drive.
2 On the Windows taskbar, do one of the following:
• In Windows 7 or Windows XP, click Start ` Run.
• In Windows Vista, click the Start button, and then click
All programs ` Accessories ` Run.
3 Ty p e X:\Readme.htm, where X: is the disc drive.
NOTE: If you’re using a multi-language DVD, you’ll find the
Readme file in its respective language folder.
What access rights are required
for installing the software?
To create a server image, you must
• be either a local administrator or an administrator for the domain
that you are managing
• have read/write access to the server location
Deployment Guide
Chapter 2: Understanding the software12
Page 16
To deploy the software to the workstations, you must
p
• be either a local administrator or an administrator for the domain
that you are managing
• have read access to the server location
Group Policy Objects,
sometimes called “system
olicies,” reside in a central location
on a Windows-based network and
define how each workstation is
configured.
If you want workstation users to be able to install (or patch) the software
themselves, you must ensure that they have administrator-level access
rights. To assign access rights to workstation users, Windows-based
networks use Group Policy Objects or “GPOs” (also called “system policies”).
Stored in a central network location, GPOs are 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. Administrators can configure GPOs by using a
Group Policy Editor. To access the Group Policy Editor that installs with
the Windows operating system, do the following:
• In Windows 7 or Windows XP, click Start ` Run, and then run the
file gpedit.msc.
• In Windows Vista, click the Start button, click All programs`Accessories`Run, and then run the file gpedit.msc.
To successfully install the software on the workstations, users require the
following three system policies to be enabled:
Windows Components\Windows Installer\
Enable user to patch elevated products
Deployment Guide
Chapter 2: Understanding the software13
Page 17
For help with using Group Policy Objects with Corel software, contact
p
Corel Support Services (www.corel.com/support). Please note that
charges will apply.
Windows Installer technology
is used to carry out the
installation. The Software
Development Kit (SDK) for
Windows Installer — available
online from the MSDN® developer
rogram — provides additional
information as well as companion
utilities.
In this guide, “Setup.exe”
refers to the Setup.exe file for
Corel Painter 12, unless otherwise
noted.
What files are required by the setup?
The Corel Painter 12 DVD contains all the files that are used by the
setup.
The three main files used by the setup are the following:
• Setup.exe
• Setup.msi
• Setup.xml
The setup is designed to interact with additional types of files, some of
which are included with the software. For more information, see “What
types of files can interact with the setup?” on page 16.
What is Setup.exe?
Stored at the root of the Corel Painter 12 DVD, the Setup.exe file lets
you run an installation wizard to create a server image of the software.
When you create a server image, a copy of the Setup.exe file is created
on that server image. You can use this copy of the Setup.exe file to
deploy the software to the workstations by using a command line (see
Chapter 4), as in a pull-installation scenario (see Chapter 5) or a pushinstallation scenario (see Chapter 6). You can also use the file to repair,
update, or remove the workstation installations of the software (see
Chapter 7).
The filename Setup.exe is a standard one for utilities that are used to
install applications. In this guide, “Setup.exe” refers to the Setup.exe
file for Corel Painter 12, unless otherwise noted.
What is Setup.msi?
For 64-bit installations,
Setupx64.msi is used
instead of Setup.msi.
You can modify an MSI table
by using a database editor
such as Orca, which is a tableediting tool provided with the
Windows Installer SDK. For more
information on any database editor,
refer to its documentation.
Located in the Painter folder on the Corel Painter 12 DVD, the
Setup.msi file is a Microsoft Windows Installer (MSI) file that contains a
database of all the setup features and registry keys that are required for
the software. The file also defines the folders and shortcuts that must be
installed with the software.
The server image contains a copy of the Setup.msi file. You can
customize this copy of the Setup.msi file by modifying the content
stored within the file’s MSI tables. When the Setup.msi file is modified
on the server image, the workstation installations created from that
Deployment Guide
Chapter 2: Understanding the software14
Page 18
server image are modified accordingly. If you want, you can create
multiple server images, each with its own Setup.msi file customized
with the desired settings — just be sure to name the various server
images clearly so that they can be easily distinguished from one another.
What additional MSI files are required by the setup?
Besides Setup.msi, the setup requires additional MSI files to carry out
the installation. Among these required MSI files are the following:
• ICA.msi or ICAx64.msi
In addition, the setup requires at least one language module, MSI files
for which are stored in the Painter folder on the Corel Painter 12 DVD.
The language modules that are available vary with each edition of the
software.
• CS.msi (or CSx64.msi, for 64-bit installations) — installs the
Chinese (Simplified) language module
• CT.msi (or CTx64.msi, for 64-bit installations) — installs the
Chinese (Traditional) language module
• DE.msi (or DEx64.msi, for 64-bit installations) — installs the
German language module
• EN.msi (or ENx64.msi, for 64-bit installations) — installs the
English language module
• FR.msi (or FRx64.msi, for 64-bit installations) — installs the
French language module
• IT.msi (or ITx64.msi, for 64-bit installations) — installs the Italian
language module
• JP.msi (or JPx64.msi, for 64-bit installations) — installs the
Japanese language module
• KR.msi (or KRx64.msi, for 64-bit installations) — installs the
Korean language module
What additional MSI files are used by the setup?
To install Corel Painter 12, the setup uses one of the following MSI files
(stored in the Painter folder on the Corel Painter 12 DVD):
• Painter.msi — installs the 32-bit version of Corel Painter 12
• Painterx64.msi — installs the 64-bit version of Corel Painter 12
To install extra content, the setup uses one of the following MSI files
(stored in the Painter folder on the Corel Painter 12 DVD):
• Content.msi — installs the 32-bit version of the content
• Contentx64.msi — installs the 64-bit version of the content
Deployment Guide
Chapter 2: Understanding the software15
Page 19
What is Setup.xml?
Located at the root of the Corel Painter 12 DVD, Setup.xml is a text
file that lists all the features that are included in the setup. It is the main
configuration file for the setup.
When you create a server image, a copy of the Setup.xml file is created
on that server image.
What types of files can interact with the setup?
The setup is designed to interact with the following types of files:
• package definition (SMS) files
• Microsoft® transformation (MST) files
What are SMS files?
SMS files are used in
push-installation scenarios, as
explained in Chapter 6.
You can also use a command
line to specify the default
location of installation files. For
information, see page 29.
For information about other
methods of editing registry
entries, see page 23.
SMS files, often called “package definition files” or simply “packages,” are
used with Microsoft Systems Management Server, a third-party push
technology that can be used to deploy software.
What are MST files?
Microsoft transformation (MST) files, sometimes called simply
“transformation files” or even “transforms,” apply a group of customized
settings to the software. Some administrators choose to create their own
MST files to make the deployment easier. Third-party applications that
can be used to create MST files include the following:
• Wise Installation Studio
•AdminStudio®
• Orca (a free utility that comes with the Windows Installer SDK,
which is available online from the MSDN developer program)
By using MST files, you can do any of the following:
• Specify which features are installed. You can select which features
or programs are installed locally and which are not installed at all (as
in a customized installation of the software).
• Change the default location of files. Default folder settings
typically reside in the registry, so you can modify default pointers by
using an MST file.
• Add the ability to bundle customized files with the software.
Including your own files is one way to customize the software.
• Add the ability to make registry modifications. You can change
the default application settings by adding or changing the registry
entries for the software.
Deployment Guide
Chapter 2: Understanding the software16
Page 20
Public properties are
p
f
command-line elements that
are used to customize the software.
For information on the available
ublic properties, see page 43.
Advertisements are used in
push-installation scenarios, as
explained in Chapter 6.
• Specify values for any available public properties. Yo u c a n
customize settings such as the installation path or the user name by
specifying values for the corresponding public properties.
There are three types of MST files:
• embedded transforms — Stored inside the MSI file of a package,
these files guarantee that the transformations are available to users
when the installation package is available.
• secured transforms — Stored locally on a read-only portion of the
workstations, these files are cached during the installation or
advertisement of a package, for use during subsequent on-demand
installations or maintenance installations of that package. Secured
transforms can be modified only by administrators.
• unsecured transforms — These files are the default transformation
files and are typically used by Corel software programs. Unsecured
transforms can be stored in the same folder as the MSI file (or almost
any other folder) and executed through the command line; however,
unsecured transforms cannot be combined in the same list as secured
transforms.
A discussion of embedded transforms and secured transforms is beyond
the scope of this guide. Any mention of MST files in this guide refers to
unsecured transforms.
The software supports the
automatic detection of
available patches. However, you can
choose whether to make this update
eature available on the workstations.
Corel Painter 12 does not provide any MST files, but you can apply MST
files of your own by specifying them in a command line. For
information, see “How do I apply MST files?” on page 28.
How do I register the software?
Registering Corel Painter 12 is important. Registration provides you
with timely access to the latest product updates, valuable information
about product releases, and access to free downloads, articles, tips and
tricks, and special offers.
For information specific to registering the software in a networked
environment, see “Can I deploy the software with a single registration?”
on page 48.
For general information about registering the software, please visit
www.corel.com/support/register.
How do I maintain the software?
Occasionally, you may find it necessary to repair your workstation
installations of the software. For more information, see Chapter 7.
Deployment Guide
Chapter 2: Understanding the software17
Page 21
Corel Corporation periodically releases Microsoft® patch (MSP) files, or
“patches,” for its products. These patches are made available through
the Corel Support Services website (www.corel.com/patches), and most
network administrators keep their installed software up-to-date by
monitoring this website. When a patch is made available, the network
administrator downloads and installs it to the server image and then
deploys the updated software to the workstations. For detailed
information on this process, see “How do I update the software?” on
page 36.
Finally, should you need to troubleshoot the installed software, try
consulting the frequently asked questions in Appendix B. You can also
consult the Corel Knowledge Base at www.corel.com/knowledgebase.
Deployment Guide
Chapter 2: Understanding the software18
Page 22
Chapter 3
N
k depl
Creating the server image
etwor
with creating an image of the
software on the server.
Be sure to consider the
capabilities and restrictions of
your network in planning the
deployment.
oyment begins
Deployment of Corel Painter 12 to the workstations begins with the
creation of a server image of the software. This step is mandatory if you
want to maintain all workstation installations from a central location.
This chapter answers the following questions:
• How can I best prepare for creating the server image?
• How do I create the server image?
• How do I finalize the image?
How can I best prepare for creating the server
image?
Before you create the server image, you need to plan your deployment
strategy. Careful planning ensures that you create the most suitable
server image possible.
This section answers the following questions:
• Which server operating systems are supported?
• What types of installations are available?
• What preliminary actions are required?
Which server operating systems are supported?
You can create an image of Corel Painter 12 on a server that has any of
the following operating systems installed:
• Windows Server 2008
• Windows Server 2003
What types of installations are available?
When creating a server image, you can specify which applications and
features to make available for installation. When using that server image
to install the software on the workstations, you can choose which of
those applications and features to install.
Deployment Guide
Chapter 3: Creating the server image19
Page 23
If you require help with using
a third-party technology to
create your own MST file, you must
refer to the documentation for that
technology.
In pull-installation scenarios (see Chapter 5), workstation users are
prompted to make such installation choices for themselves. However,
you can use the following method to standardize and enforce how
applications and features are installed:
• Use your own Microsoft transformation (MST) file to specify the desired installation settings. To do this, you must use a thirdparty product to create the file (see “What are MST files?” on
page 16); then, you must make it available for deployment through a
command line (see “How do I apply MST files?” on page 28). For
additional help with using MST files to deploy Corel software,
contact Corel Support Services (www.corel.com/support); please note
that charges will apply.
What preliminary actions are required?
You can copy the server image
to a CD or DVD. This
deployment method is useful for
installing to laptops, or to remote
workstations that are not connected to
the network.
To change the location of a
server image after you create
it, you must create a new image at a
new location. You cannot copy an
image from one location to another.
Before you begin creating the server image, follow these guidelines:
• Make sure that the network file systems are running an NTFS
partition. FAT and FAT32 systems are not supported.
• Make sure that you have administrator-level rights to the server and
workstations.
• Make sure that the server share has enough free disk space for the
server image. For more information, see “What are the system
requirements for the software?” on page 12.
• Make sure that the operating systems on the workstations have been
updated with the latest service packs and security patches.
• If you plan to use a push-installation scenario (see Chapter 6), make
sure that your push technology is up-to-date.
How do I create the server image?
As the administrator, you create the server image by running the
executable file Setup.exe.
Creating the server image can be a lengthy process. The setup must
check the rights on the server before copying over the files that make up
the server image — first the root files, and then the files in the MSI
table. A progress bar displays the status.
To create a server image on a Windows 7 or Windows Vista network
that contains a mix of workgroups and domains, you must have
appropriate permissions.
Deployment Guide
Chapter 3: Creating the server image20
Page 24
How do I create multiple server images?
If your workstations require different configurations of the software, you
can create a customized server image for each type of installation.
You must create both a 32-bit
server image and a 64-bit
server image if you want to deploy
both the 32-bit and 64-bit versions
of the software to your network.
When you install the software,
Microsoft Windows Installer
is automatically updated to
version 3.0.
If you do not specify whether to
create a 32-bit or 64-bit
server image, then by default, the
setup uses the format of the operating
system on that server.
For additional information on
customizing a command line,
see Chapter 4.
Proceed with extreme caution
when using the
/q switch to
create a server image. For best results,
it is strongly recommended that you
avoid using the switch altogether.
Similarly, if you want to support both 32-bit and 64-bit installations of
the software, you must create multiple server images: one for the 32-bit
installations, and one for the 64-bit installations.
You can customize a server image in several ways. Here are some
examples:
• Edit the MSI tables of the MSI files for the software. For
information, see “What is Setup.msi?” on page 14.
• Apply MST files to the setup. For information, see “What are MST
files?” on page 16.
To create a server image
1 Insert the Corel Painter 12 DVD into the disc drive.
If the Autorun opens, click Exit.
2 On the Windows taskbar, click Start `Run.
Type the following command line if you want to create a server image
for deploying the 32-bit version of Corel Painter 12.
X:\Setup.exe /a CREATE_WIN32_ADMIN=1
Type the following command line if you want to create a server image
for deploying the 64-bit version of Corel Painter 12.
X:\Setup.exe /a CREATE_X64_ADMIN=1
If you want additional control while creating the server image, you
can customize this command line with one or both of the following
switches:
•
/q — limits the amount of user interface encountered. Be careful
to avoid suppressing (or “silencing”) a required user-interface field
when introducing a
otherwise, you may fail to create a valid server image. For detailed
information on this switch, see “How much of the setup interface
do I want users to see?” on page 26.
•
/l — generates a log file of the results. For detailed information
on this switch, see “Do I want to create an installation log?” on
page 26.
If the Minimum system requirements dialog box appears, click
Continue to confirm that you are aware of the recommended
minimum system requirements for the software.
/q switch into your command line —
The setup cannot continue if
you do not accept the terms in
the license agreement.
3 Read the license agreement in its entirety. To agree to its terms and
continue the installation, enable the I accept the terms in the
license agreement check box, and click Next.
Deployment Guide
Chapter 3: Creating the server image21
Page 25
4 Type your user name and serial number (with or without hyphens) in
the boxes provided, and 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. If
you want to prevent users from changing the user name, you can
specify it from within the MSI table of your MSI file (see page 14) —
either by creating a customized MST file (see page 16), or by using
public properties in your command line (see page 29).
It is crucial that you limit
the installation path to
90 characters. Using more than
90 characters may cause the program
to function incorrectly.
For more information on
registering, see “How do I
register the software?” on page 17.
5 Specify a network location for the server image. To change the default
location, do one of the following:
•In the Folder box, type a Universal Naming Convention (UNC)
path.
•Click Change, and browse to a valid network location.
You can use an existing mapped drive unless you are creating the
server image from within a terminal-server session, as outlined by the
MSDN developer program.
6 If you want to allow workstations to detect and download product
updates, enable the Product updates check box.
7 Click Install now to begin copying the files to the server.
If you click Cancel, you are prompted whether to cancel creating the
server image. Cancelling “rolls back” the setup and undoes most of
the changes made; however, some manual cleanup may be required.
8 Click Finish.
9 Follow the directions given in “How do I finalize the image?” on
page 22.
10 Check for software updates, and apply them to the server image as
necessary. For information on this process, see “How do I update the
software?” on page 36.
How do I finalize the image?
Before you can begin deploying Corel Painter 12 to the workstations,
you must finalize the server image. To do this, you must verify the
network-access privileges and configure the registry settings that you
want to deploy.
• How do I verify network-access privileges?
• How do I edit registry settings?
Deployment Guide
Chapter 3: Creating the server image22
Page 26
It is recommended that you test
the user rights before deploying
the software to the workstations.
When you edit the MSI table
of the server image, it affects
everyone who uses that setup.
Therefore, to be safe, it is highly
recommended that you back up the
MSI table of the server image before
making any changes to it.
How do I verify network-access privileges?
As you finalize the server image and prepare to deploy the software to
the workstations, do the following:
• Make sure that you have and retain administrator-level rights to the
server and workstations.
• Make sure that workstation users have access to the server image.
• If you have customized the Setup.msi file, make sure that it is
available on your server share.
How do I edit registry settings?
After you create the server image, you may want to edit its registry
settings for deployment to the workstations. By doing so, you can avoid
having to manually configure the registry settings of each individual
workstation installation of the software.
To edit the registry settings of the server image, you must do one of the
following:
• Use a database editor such as Orca (a table-editing tool provided
with the Windows Installer SDK) to modify the registry entry in the
MSI table.
• Create a new registry (REG) file that contains the new settings.
The first of these methods is easier than the second. After you create the
server image, you can alter entries in the MSI tables of the server image.
The MSI file then transfers the MSI entries for the server to the registry
for the workstation when that workstation runs the setup from the
server image.
Deployment Guide
Chapter 3: Creating the server image23
Page 27
Chapter 4
f
s
Installing with command lines
As mentioned in Chapter 3, you use a command line to create a server
image.
Similarly, you use a command line to deploy the software to the
workstations from that server image. To do this, you assemble a
command line that specifies the installation settings that you want to
provide or enforce. In this way, you can control the installation type of
the software, the amount of interaction that users have with the setup,
the creation of log files, and other installation options.
Some network administrators
prefer to deploy a command line
to the workstations by using a “batch
ile.” However, for best results, it is
recommended that you pull or push the
oftware to the workstations.
After assembling your command line, you are ready to deploy the
software to the workstations. To do this, you can allow users to “pull”
the software by initiating the setup themselves (see Chapter 5), or you
can use a third-party technology to “push” the software to users’
workstations (see Chapter 6).
This chapter answers the following questions:
• How do I assemble a command line?
• How do I run my command line?
What else can I do with command lines?
You can also use command lines to automate the following tasks:
• repairing existing installations of the software (see page 34)
• updating the software on the workstations (see page 36)
• removing the software from the workstations (see page 39)
How do I assemble a command line?
There are three steps to assembling a command line:
• Step 1: Specify the executable file.
• Step 2: Define the deployment process with switches.
• Step 3: Refine the installation with public properties.
This section describes these three steps in detail.
Deployment Guide
Chapter 4: Installing with command lines24
Page 28
Step 1: Specify the executable file
s
f
All command lines in this
guide are designed to run the
Setup.exe file from its source
directory on a typical server image.
Your deployment scenario may
require you to specify a path to a
pecific Setup.exe file.
Switches signal installation
options.
Separate switches from other
command-line elements,
including other switches, with spaces.
The first item to specify in the command line is the executable file for
the software: Setup.exe. Therefore, the basic component of every
command line is as follows:
Setup.exe
All command lines in this guide are designed to run the Setup.exe file
from its source directory on a typical server image. Your deployment
scenario may require you to specify a path to a specific Setup.exe file —
for example, if you have created multiple server images (as outlined on
page 21). The syntax for specifying a path is as follows:
\\server\path\Setup.exe
If your path contains spaces, you must place quotation marks around it:
"\\server\path\Setup.exe"
Step 2: Define the deployment process with switches
To define the deployment process, you can use command-line switches,
which signal installation options.
The syntax for a switch consists of a forward slash (
followed by a character or string — for example,
space on both sides of a switch separates that switch from other
command-line elements. You can use one or more switches in a single
command line, but be sure to separate them with spaces as you would do
for any other command-line element.
/ ) immediately
/q or /quiet. Typing a
This guide displays parameters
in italics to distinguish them
rom switches.
Do not type a space between a
switch and its parameters or
between the parameters in one switch.
For a list of all command-line
switches for Microsoft
Windows Installer, see the Microsoft
website.
Some switches have parameters, which let you tweak the settings. In fact,
some switches let you use multiple parameters for the same switch. If
you do not specify any parameters, the switch uses its default settings.
To use a parameter, simply type the parameter immediately after the
switch. Do not type a space between a switch and its parameters or
between the parameters in one switch.
To customize a command line for installing the software, ask yourself the
following questions:
• How much of the setup interface do I want users to see?
• Do I want to create an installation log?
For a complete list of command-line switches available for the software,
see “What are the available command-line switches?” on page 42.
Deployment Guide
Chapter 4: Installing with command lines25
Page 29
f
ter installation with the /q
A
switch, it is normal for the
licensing agreement to appear the first
time that users run the application on
their workstations.
Errors are logged to the default
user’s temporary folder.
You can use the /quiet
switch as an alternative to
/qn.
You can use the /passive
switch as an alternative to
/qb.
How much of the setup interface do I want users to see?
The /q switch can be used to restrict the amount of the user interface
that appears during installation. You can use the switch to prevent users
from entering their own registration information, to help enforce specific
installation options, or even to perform silent installations, in which no
user interface is visible during the setup.
/q switch can be used in conjunction with one of the following
The
parameters:
n — The user does not see the user interface during installation.
•
Errors are recorded in a log file. (For more information, see “Do I
want to create an installation log?” on page 26.) This is the default
parameter.
•
b — The user sees only a progress bar and a Cancel button. If the
user pushes the Cancel button, the installation is rolled back.
b! — The user sees only a progress bar and cannot cancel the
•
installation.
•
b+ — The user sees only a progress bar and a Cancel button. If the
user pushes the Cancel button, the installation is immediately rolled
back. (The user is not prompted to confirm the cancellation request.)
r — The user sees a progress bar, along with a page containing
•
information about the installation. The user can choose to cancel the
installation.
•
f — The user sees the full user interface.
The /q switch can be used to
create a server image, but only
if you proceed with extreme caution.
When citing the path, do not
use an ending backslash (
\ ).
Here is a sample command line that suppresses the user interface during
installation and records any errors in a log file:
Setup.exe /qn
or
Setup.exe /quiet
Although you can use the /q switch to create a server image, you must
proceed with extreme caution to avoid suppressing any registration
prompts for the software. In this scenario, you can preset the destination
of the installation files by including the public property
TARGETDIR="<path>" in your command line. For information on
creating a server image, see Chapter 3.
Do I want to create an installation log?
Use the /l switch if you want to log general information about the
installation to a log file with the specified path and filename. If you do
not specify a path and filename, the log file is created in the current
user’s temporary (“Te m p ”) folder.
Deployment Guide
Chapter 4: Installing with command lines26
Page 30
You can use the
s
/log switch
as an alternative to
/l*.
The parameters available for the /l switch are as follows:
•
i — logs status messages
•
w — logs nonfatal warnings
•
e — logs all error messages
•
a — logs initiated actions
•
r — logs action-specific records
•
u — logs user requests
•
m — logs error messages about out-of-memory warnings or fatal
exits
o — logs error messages resulting from insufficient hard disk space
•
during installation to a server
•
p — logs terminal properties
•
v — logs very detailed information
•
* — applies all parameters except v and x, recording all information
in a single log file
Quotation marks ensure that
the path is read as a single
unit, particularly if it contains
paces.
The default parameters for the
command line that uses the
Setup.exe /l
/l switch are iwearmo. Here is a sample
/l switch with its default parameters:
If you want to specify a path for the log file, you must type a space after
/l switch followed by the path in quotation marks:
the
Setup.exe /l "<path>"
The following sample command line uses the default parameters of the
/l switch to log installation information to the file C:\install.txt during
installation:
Setup.exe /l "C:\install.txt"
You can use the /q and /l switches together. The following sample
command line uses the
installation and record errors in the log file specified by the
Setup.exe /qn /l "C:\Logs\My_Log.txt"
/q switch to suppress the user interface during
/l switch:
Step 3: Refine the installation with public properties
Finally, to refine the installation of the software on the workstations, you
can use public properties — command-line elements that are shared
outside the application. When you deploy software by using command
lines, you can use public properties to set the values of various
installation properties (such as the information found in the Customer information and Choose destination location dialog boxes).
Deployment Guide
Chapter 4: Installing with command lines27
Page 31
Be sure to use spaces to
p
separate public properties from
other command-line elements
(including other public properties).
Public properties are case-sensitive; they must be typed in capital letters,
and they cannot contain spaces. To use a public property in a command
line, you must type the name of the public property in capital letters,
followed directly by an equals sign ( = ), followed directly by the desired
value.
Use quotation marks around
any value that contains spaces
to ensure it is “read” as a single unit.
Additional information on the
use of public properties is
available from the MSDN developer
rogram.
Values are also case-sensitive, but they can contain both uppercase and
lowercase letters. A value can be a text string (such as a feature name) or
a number. It’s a good idea to use quotation marks around a value so that
it is “read” as a single unit, particularly if that value contains spaces.
By combining public properties, you can successfully customize the
installed software to accomplish various tasks.
•How do I apply MST files?
• How do I specify customer information?
• How do I customize the destination of the installation files?
• How do I specify whether to allow automatic updates?
• How do I specify whether to reboot after installation?
For an at-a-glance list of all available public properties, see “What are
the available public properties?” on page 43.
How do I apply MST files?
If you have used a third-party product to create a Microsoft
transformation (MST) file for customizing the software (see “What are
MST files?” on page 16), you must refer to the MST file from within
your command line. First, store the MST file on the server image. Then,
build a command line that pairs the
MST file, as demonstrated by the following syntax (where
TRANSFORMS property with that
<MST> is the
filename of the MST file):
Setup.exe TRANSFORMS="<MST>"
If the MST file is not in the same folder as Setup.exe, <MST> must
specify the full path and filename of the MST file.
By default, the MST file is applied to the Setup.msi file for the setup
(see “What is Setup.msi?” on page 14).
If you have trouble applying your MST file, do the following:
• Check the syntax of your command line, particularly the path to the
MST file.
• Check your permissions.
• Make sure that the MST file was created correctly.
• Check the associated MSI files.
For additional help with MST files, contact Corel Support Services
(www.corel.com/support); please note that charges will apply.
Deployment Guide
Chapter 4: Installing with command lines28
Page 32
You cannot use the
INSTALLDIR property when
creating a server image.
When citing the path, do not
use an ending backslash (
\ ).
How do I specify customer information?
To install the software, you must provide the setup with customer
information. You can use any of the following public properties to input
this information into the Customer information dialog box:
•
USERNAME="<user name>" — specifies the user name
•
SERIALNUMBER="<serial number>" — specifies the serial number
How do I customize the destination of the installation files?
When deploying software from the server image to the workstations,
you can set the destination of the installation files (as in the Choose destination location dialog box) by using the following public
property:
• INSTALLDIR="<path>"
For best results, do not end the path with a backslash ( \ ).
How do I specify whether to allow automatic updates?
The property for controlling whether to allow for automatic updates
(and in-product messaging) on the workstations is
ALLOW_PRODUCTUPDATES. You can use this property only when creating
the server image.
Allowing automatic updates
for workstations that do not
have access to the Internet is not
recommended.
To enable automatic updates (and in-product messaging), specify
ALLOW_PRODUCTUPDATES=1, as in the following example:
Setup.exe ALLOW_PRODUCTUPDATES=1
To turn off automatic updates, specify either
ALLOW_PRODUCTUPDATES=0 or nothing at all. (Remember: By default,
automatic updates are not enabled for workstations installed from a
server image.)
For additional information on updating the software, see “How do I
update the software?” on page 36.
How do I specify whether to reboot after installation?
The REBOOT property allows you to specify whether users are prompted
to reboot after installation. The
REBOOT property is used with one of the
following values:
Force (or F) — always prompts for a reboot after installation. If the
•
user interface has been suppressed, then the computer is
automatically rebooted after installation.
•
Suppress (or S)— reboots automatically after installation. If a
reboot is required during installation, the user is prompted to reboot
unless the user interface has been suppressed (in which case, the
computer is automatically rebooted).
•
ReallySuppress (or R)— suppresses all reboots and all reboot
prompts, both during and after installation
Deployment Guide
Chapter 4: Installing with command lines29
Page 33
You can also use the following switches as alternatives to the REBOOT
public property:
/forcerestart — same as REBOOT=Force
•
• /promptrestart — same as REBOOT=Suppress
• /norestart — same as REBOOT=ReallySuppress
How do I run my command line?
As you can imagine, your final command line could end up looking
quite complex.
So, now that you know how to assemble command lines, how do you use
them to deploy the software to the workstations? Some network
administrators choose to create a “batch file” that runs the command
line. However, for best results, it is recommended that you use your
command line to either pull (see Chapter 5) or push (see Chapter 6) the
software to the workstations.
Deployment Guide
Chapter 4: Installing with command lines30
Page 34
Chapter 5
r
t
b
n
r
w
c
t
u
M
w
Pulling the software to the workstations
After deploying the software to
the workstations, you can, at
any time, repair the installations (to
install missing files, shortcuts, and
registry entries, or to replace corrupted
items). For more information, see
Chapter 7.
Before you begin deploying the
software, verify the minimum
equirements and user-access rights of
he workstations. For workgroup-
ased (rather than domain-based)
etworks, it is also highly
ecommended that you map the
orkstations to the server image,
onfigure the workstations to log in to
he server location at startup, and
pgrade to the latest version of
icrosoft Windows Installer on all
orkstations.
After you create a server image of Corel Painter 12 that meets the needs
of your organization (see Chapter 3), you are ready to deploy the
software to the workstations.
This chapter shows you how to empower users to install (or “pull”) the
software to their own workstations. For information on using third-party
technologies to “push” the software to the workstations on the users’
behalf, see Chapter 6.
This chapter answers the following questions:
• How can I best prepare for pull installation?
• How do users pull the software?
How can I best prepare for pull installation?
Before users can pull the software to their workstations, you must do the
following:
• Make sure that each workstation meets the minimum requirements
for the software (see page 12).
• Make sure that each workstation user has administrator-level access
to the workstation and read-only access to the server image
(see page 12).
• Properly configure any Group Policy Objects that you want to use to
deploy the software (see page 47).
In addition, it is highly recommended that workstation users map to the
server image and set their workstations to log in to that server location
at startup. Performing this step ensures that users are always connected
to the server image.
It is also recommended that you verify that all workstations are running
the latest version of Microsoft Windows Installer.
Deployment Guide
Chapter 5: Pulling the software to the workstations31
Page 35
How do users pull the software?
Users pull the software to their workstations by initiating the setup for
the server image.
The following procedure
describes how to pull a default
installation to a workstation.
The setup cancels if you do not
accept the terms in the license
agreement.
The degree of user interaction required by the setup depends on how
you’ve customized the server image and the deployment process. The
following procedure describes how to pull a default installation to a
workstation.
To pull Corel Painter 12 to a workstation
1 Browse to the location of the server image.
2 Double-click Setup.exe.
If the Minimum system requirements dialog box appears, click
Continue to confirm that you are aware of the recommended
minimum system requirements for the product.
3 Read the license agreement in its entirety. To agree to its terms and
continue the installation, enable the I accept the terms in the
license agreement check box, and click Next.
4 Type your user name, and click Next.
5 Specify where to install the software. To change the default location,
click Change and browse to the desired location.
The destination path is limited to 90 characters.
6 Disable the Product updates check box if you do not want the
software to detect and download product updates and service packs.
7 Click Install now to begin copying the files to the workstation.
Deployment Guide
Chapter 5: Pulling the software to the workstations32
Page 36
Chapter 6
p
Pushing the software to the workstations
For best results with installing
the software, see “How can I
best prepare for pull installation?” on
age 31
For complete information on
using a third-party push
technology, please refer to the
manufacturer’s documentation.
For best results in deploying Corel Painter 12 to your workstations, it is
recommended that you have the users themselves install (or “pull”) the
software (as explained in Chapter 5).
However, it is possible to “push” the software from the server image to
the workstations. To do this, you use a command line (see Chapter 4) in
conjunction with one of the following:
• a batch file — a text file that can be scripted to run commands
automatically. For help with using batch files, please see the
Microsoft website.
• a Group Policy Object (or “GPO”) — an item, stored in a central
network location, that defines how the workstations are configured.
For basic help with using GPOs, see “Can I deploy the software by
using a Group Policy Object?” on page 47; for complete help, please
refer to your Group Policy Software Development Kit.
• a push technology — a third-party tool that is specially designed
for installing software automatically. For detailed help with using a
third-party push technology, please refer to the manufacturer’s
documentation.
For many administrators, using a third-party push technology is the
preferred push method.
Deployment Guide
Chapter 6: Pushing the software to the workstations33
Page 37
Chapter 7
Maintaining the software
To keep your network running in top shape, it’s important to know
how to repair and update your workstation installations of
Corel Painter 12.
When you need to upgrade to the next version of the software, you must
know how to cleanly remove the previous version from the network.
This chapter answers the following questions:
• How do I repair the software?
Some procedures in this chapter
require the use of command
lines. For detailed information on
using command lines, see Chapter 4.
• How do I update the software?
• How do I remove the software?
Some procedures in this chapter require the use of command lines. For
detailed information on using command lines, see Chapter 4.
How do I repair the software?
Repairing Corel Painter 12 lets you install missing files, shortcuts, and
registry entries, or replace corrupted items. You can repair a single
installation of the software by using the Windows Control Panel for the
workstation, or you can repair multiple installations simultaneously by
using a command line.
How do I repair the software by using
the Windows Control Panel?
You can use the Windows Control Panel to repair a single workstation
installation of Corel Painter 12.
To repair the software by using the Windows Control Panel
1 On the workstation, click Start `Control Panel on the Windows
taskbar.
2 Do one of the following:
• In Windows 7 and Windows Vista, click Programs | Uninstall a
program (or click Programs and features if you are using the
Classic view of the Control Panel).
• In Windows XP, double-click Add or remove programs.
Deployment Guide
Chapter 7: Maintaining the software34
Page 38
You cannot use the
p
p
/f switch
together with the
REINSTALL or REINSTALLMODE
ublic properties — or with any
other public property.
3 Choose Corel Painter 12 from the list, and then click Uninstall/
Change (for Windows 7 or Windows Vista) or Change/Remove (for
Windows XP).
4 Enable the Repair option, and then click Repair.
5 Follow the instructions that appear.
How do I repair the software by using a command line?
You can use a command line to repair multiple workstation installations
of Corel Painter 12 simultaneously.
For more information on using command lines, see Chapter 4.
What is the command-line syntax for repairing the software?
To repair multiple workstation installations of the software by using the
server image, you can build a command line that combines the
Setup.exe file with either the
REINSTALLMODE public properties.
The
/f switch uses the following command-line syntax:
Setup.exe /f
/f switch or the REINSTALL and
The default parameters for the
/f switch are oums.
Do not use the v parameter
for the first installation of an
application.
The default conditions for the
REINSTALLMODE public
roperty are oums.
The /f switch can be customized with the following parameters:
•
p — reinstalls any missing files
•
o — reinstalls any missing files, as well as any files for which an older
version is installed
•
e — reinstalls any missing files, as well as any files for which an equal
or older version is installed
d — reinstalls any missing files, as well as any files for which a
•
different version is installed
a — reinstalls all files
•
•
u — rewrites all required user-specific registry entries (that is, the
HKEY_CURRENT_USER and HKEY_USERS keys)
•
m — rewrites all required computer-specific registry entries (that is,
HKEY_LOCAL_MACHINE and HKEY_CLASSES_ROOT keys)
the
•
s — overwrites all existing shortcuts
•
v — runs from the source files and re-caches the local package
If you want greater control over how the software is repaired, you can
use the following public properties instead of the
•
REINSTALL=ALL — reinstalls all application features
•
REINSTALLMODE=<condition> — specifies the type of
/f switch:
reinstallation to perform. It is recommended that you use this
property in conjunction with
property are the same as the parameters for the
REINSTALL. The conditions for this
/f switch.
Deployment Guide
Chapter 7: Maintaining the software35
Page 39
The command-line syntax for these public properties is as follows:
p
f
Setup.exe REINSTALL=ALL REINSTALLMODE=<condition>
The following sample command line automatically reinstalls all features.
The use of the
button, and the use of the
/qb switch displays only a progress bar and a Cancel
The following sample command line specifies that the reinstallation run
from the source files and re-cache the local package, reinstall missing
and outdated files, rewrite all required user-specific and computerspecific registry entries, and overwrite all existing shortcuts. The use of
the
/qb switch displays only a progress bar and a Cancel button, and
/le switch logs all error messages to C:\Logs\repair.txt.
How do I update the software?
In this guide, “Pa tc h .e x e ”
refers to the name of the
executable file for the patch, although
the actual filename varies with each
atch.
Installing the update feature
to workstations that run
eatures from the network, or that do
not have access to the Internet, is not
recommended.
Corel periodically releases Microsoft patch (MSP) files, or “patches,” for
its products. Installing patches helps keep the software up-to-date.
A service pack is typically an executable file that combines multiple
patches to make a major update to the software. One MSP file is
included for each MSI file (see “What is Setup.msi?” on page 14) to be
updated.
In this guide, “Patch.exe” refers to the name of the executable file for
the patch, although the actual filename varies with each patch.
How do I locate available patches?
Many network administrators keep their software up-to-date
by monitoring the website for Corel Support Services
(www.corel.com/support). When a patch is made available, these
administrators download it and carry out the patching process
themselves (as documented in “How do I apply patches?” on page 37).
If you prefer, Corel Painter 12 can be configured to use an automaticupdate feature to detect when patches are available; however, you must
enable this update feature on the server image if you want to make it
available on the workstations that install from that server image. For
information on using a command line to customize whether the update
feature is made available to workstations, see “How do I specify whether
to allow automatic updates?” on page 29.
Deployment Guide
Chapter 7: Maintaining the software36
Page 40
How do I apply patches?
s
s
Be sure to download the patch
to an accessible location on the
erver.
The Readme file for the patch
explains which features
require updating.
After locating and downloading a patch, you can apply it to the server
image and then use the new server image to deploy the updated
software to the workstations.
To apply patches, you use command lines. For more information on
command lines, see Chapter 4.
From within the command line, you can access the basic help for the
patching process by using the following syntax:
Patch.exe /?
However, detailed instructions follow.
How do I apply a patch to the server image?
You can apply the patch directly to the server image, or you can control
the patching process by extracting the patch files before applying them.
To apply the patch directly to the server image, use a command line that
includes the executable file for the patch and the
/a switch. Follow the
instructions given in “To create a server image” on page 21, but change
Setup.exe to the filename for the patch:
Patch.exe /a
If desired, you can include the path to the server image:
If no target location is
specified, the patch files are
extracted to the Te m p folder.
For best results, apply all the
extracted patch files to the
erver image.
Patch.exe /a "<path to server image>"
To control the process of patching the server image, you can extract the
patch files before applying them. To extract the patch files to a target
location, use the following command-line syntax:
Patch.exe /extract_all "<path to target location>"
To apply the extracted patch files to the server image, use the following
command-line syntax:
Setup.exe /a
If desired, you can include the path to the server image:
Setup.exe /a "<path to server image>"
You can also include an /l switch (see page 26) if you want to create an
installation log.
If you choose to extract the patch files, it is important that you apply all
of them to the server image. Applying only some of the patch files may
cause the deployed software to function incorrectly.
Deployment Guide
Chapter 7: Maintaining the software37
Page 41
How do I deploy a patched server image to the workstations?
After applying the patch to the server image, you are ready to deploy the
patched server image to the workstations.
Setting the REINSTALL
public property to
ALL ensures
that all features are updated.
For applying a patch to the
workstations, the recommended
set of conditions for the
REINSTALLMODE public property is
vdm.
To update the workstations, use the following command-line syntax:
Setup.exe REINSTALL=ALL
You can include a /q switch (see “How much of the setup interface do I
want users to see?” on page 26) if you want to control how much of the
user interface is displayed.
You can include an
/l switch (see page 26) if you want to create an
installation log.
You can include the
REINSTALLMODE public property (see “What is the
command-line syntax for repairing the software?” on page 35) if you
want to specify one or more reinstallation conditions. The default
conditions for the
REINSTALLMODE property — oums — are used if the
property is not explicitly stated in the command line, or if no conditions
are specified for it.
Finally, you can include the
REBOOT public property (see page 29) if you
want to specify whether to reboot the workstation after applying the
patch to it.
The following sample command line patches the workstations, logging
all error messages to C:\Install Log\Patch Service Pack.txt:
Setup.exe /le "C:\Install Log\Patch Service Pack.txt"
REINSTALL=ALL REINSTALLMODE=vdm
The following sample command line patches the workstations,
displaying no user interface:
Setup.exe /qn REINSTALL=ALL REINSTALLMODE=vdm
The following sample command line patches the workstations,
displaying only a progress bar and a Cancel button:
Setup.exe /qb REINSTALL=ALL REINSTALLMODE=vdm
The following sample command line patches the workstations,
suppressing their reboot:
If desired, you can silently apply the patch to the server image and
silently deploy it to the workstations by using the following command
line:
Patch.exe /s
Deployment Guide
Chapter 7: Maintaining the software38
Page 42
However, for best results, it is recommended that you apply and deploy
f
the patch yourself, as previously described.
How do I remove the software?
You can remove Corel Painter 12 from your network. Cleanly
uninstalling the software is crucial when the time comes to upgrade to
the next version of the product.
You can remove a single installation of the software by using the
Windows Control Panel for the workstation, or you can remove multiple
installations simultaneously by using a command line.
How do I remove a server image of the software?
There is no application or functionality for automatically removing or
uninstalling a server image of the software. You must manually delete
the server image.
If you experience any
problems during
uninstallation, avoid removing user
iles.
This procedure also applies to
removing an installation from
a terminal server.
Before doing this, we recommend that you remove all network-based
workstation installations and make sure that the applications to be
removed — and their associated files — are not currently in use. Also, if
you are using Windows Terminal Server, make sure that all users are
logged off.
After the software image has been removed from the server, the only
way to get it back is to re-create it by following the procedures for
creating a server image (as explained in Chapter 3).
How do I remove the software by using
the Windows Control Panel?
You can use the Windows Control Panel to remove a single workstation
installation of Corel Painter 12.
To remove the software by using the Windows Control Panel
1 On the workstation, click Start `Control Panel on the Windows
taskbar.
2 Do one of the following:
• In Windows 7 and Windows Vista, click Programs | Uninstall a
program (or click Programs and features if you are using the
Classic view of the Control Panel).
• In Windows XP, double-click Add or remove programs.
3 Choose Corel Painter 12 from the list, and then click Uninstall/
Change (for Windows 7 or Windows Vista) or Change/Remove (for
Windows XP).
Deployment Guide
Chapter 7: Maintaining the software39
Page 43
4 Enable the Remove option.
5 By default, the Remove user files check box is enabled. If you do
not want to remove user files (such as presets, user-created fills, and
customized files), disable this check box.
6 Click Remove.
How do I remove the software by using
a command line?
You can use a command line to remove multiple workstation
installations of Corel Painter 12 simultaneously. You can use either the
switch or the /uninstall switch in this command line, as follows:
x
Setup.exe /x
or
Setup.exe /uninstall
The /x switch and the /uninstall switch perform a silent removal of
all software associated with Corel Painter 12.
If you want to customize the removal of the software, you cannot use the
/x switch or the /uninstall switch. Instead, you must use the
following public properties:
REMOVE=ALL — removes all features
•
•
REMOVEUSERFILES=<value> — specifies whether to remove user
files. A value of
remove them.
0 does not remove user files, while a value of 1 does
/
If you want, you can further refine the custom removal with the
switch (to suppress the user interface) and the
/l switch (to create an
/q
installation log).
The following sample command line removes workstation installations
and all user files, displays a progress bar and information about the
installation, and logs all error messages to C:\Install Log\uninstall.txt:
switches for Microsoft
Windows Installer, please see the
Microsoft website.
The following table lists the command-line switches that are compatible
with Corel Painter 12.
SwitchEffect
/aCreates or patches a server image. For more information,
see “How do I create the server image?” on page 20 or
“How do I apply patches?” on page 37.
/extract_allExtracts the files from a patch (or an electronic software
download, or “ESD”). For more information, see “How
do I apply a patch to the server image?” on page 37.
/fReinstalls the software. Its default parameters are oums.
For more information, see “What is the command-line
syntax for repairing the software?” on page 35.
/forcerestartWorks the same as the public property REBOOT=Force.
For information on this public property, see “How do I
specify whether to reboot after installation?” on page 29.
/helpSame as /?
/lLogs general information about the installation. The log
file is created in the current user’s temporary folder if a
path and filename are not specified. For more
information, see “Do I want to create an installation log?”
on page 26.
/logSame as /l*
/norestart
Works the same as the public property
REBOOT=ReallySuppress. For information on this
public property, see “How do I specify whether to reboot
after installation?” on page 29.
/passiveSame as /qb
/promptrestart
Works the same as the public property
REBOOT=Suppress. For information on this public
property, see “How do I specify whether to reboot after
installation?” on page 29.
/qSets the extent to which the user interface of the setup is
displayed. For more information, see “How much of the
setup interface do I want users to see?” on page 26.
/quietSame as /qn
/s
Silently applies and deploys a patch for the software. For
more information, see “How do I silently apply and
deploy a patch?” on page 38.
using command-line switches,
including the parameters that are
available for each switch, see “Step 2:
Define the deployment process with
switches” on page 25.
For a list of all public
properties for Microsoft
Windows Installer, please see the
Microsoft website.
Any public properties that are
visible from within the setup
but not listed in this table are
internal to the setup and cannot be
ccessed through a command line.
/x
/?Accesses help for the setup
Uninstalls the software from the workstation. For more
information, see “How do I remove the software by using
a command line?” on page 40.
Remember that you must separate switches from other command-line
elements with a space, but you must not separate a switch from its
parameters. For information on assembling command lines, see
Chapter 4.
What are the available public properties?
The following table lists the public properties that are compatible with
Corel Painter 12.
PropertyDescription and values
ALLOW_PRODUCTUPDATES
During server-image creation, specifies
whether to allow for automatic product
updates. Its value is
automatic updates, or
do I specify whether to allow automatic
updates?” on page 29.
Used with a value of 1 to specify the
creation of a 32-bit server image. See “To
create a server image” on page 21.
Used with a value of 1 to specify the
creation of a 64-bit server image. See “To
create a server image” on page 21.
Sets the destination of the installation files
on the workstations. Its value is the path;
for best results, do not use an ending
backslash (
value in quotation marks, in case it contains
spaces. See “How do I customize the
destination of the installation files?” on
page 29.
\ ). It’s a good idea to enter this
Page 47
PropertyDescription and values
REBOOT
REINSTALL
REINSTALLMODE
Specifies whether to reboot after
installation. Its value is
Force (always prompts for a reboot),
Suppress (reboots automatically),
ReallySuppress (suppresses all
or
reboots and all reboot prompts, both during
and after installation). See “How do I specify
whether to reboot after installation?” on
page 29.
Reinstalls all features by taking the value
ALL. See “What is the command-line syntax
for repairing the software?” on page 35, or
“How do I deploy a patched server image to
the workstations?” on page 38.
Specifies the type of reinstallation to
perform. Its values mirror those of the
/f
switch. See “What is the command-line
syntax for repairing the software?” on
page 35, or “How do I deploy a patched
server image to the workstations?” on
page 38.
REINSTALLMODE public property can
The
also be used when installing the software to
the workstations for the first time. However,
it cannot be used when creating a server
image.
REMOVE
Removes all features by taking the value
ALL. See “How do I remove the software by
using a command line?” on page 40.
REMOVEUSERFILES
During uninstallation, signals whether you
want to remove user files. Its value is
0 if you don’t want to remove user files,
1 if you do. See “How do I remove the
or
software by using a command line?” on
page 40.
SERIALNUMBER
Sets the serial number for the registration
process. Its value is the serial number. See
“How do I specify customer information?”
on page 29.
For detailed instructions on
using public properties, see
“Step 3: Refine the installation with
ublic properties” on page 27.
TARGETDIR
TRANSFORMS
USERNAME
Specifies the destination of the installation
files when creating a server image by using a
/q switch in the command line. Its value is
the path; for best results, do not use an
ending backslash (
enter this value in quotation marks, in case
it contains spaces. See page 26.
Specifies a Microsoft transformation (MST)
file to apply to the Setup.msi file. Its value
is the path and filename. It’s a good idea to
enter this value in quotation marks, in case
it contains spaces. See “How do I apply MST
files?” on page 28.
Sets the user name for the registration
process. Its value is the user name. It’s a
good idea to enter this value in quotation
marks, in case it contains spaces. See “How
do I specify customer information?” on
page 29.
\ ). It’s a good idea to
Remember that the correct syntax for a public property is the following:
<public property>=<value>
Because spaces are used to separate command-line elements from each
other, you must enter the value in quotation marks if it contains spaces.
For information on assembling command lines, see Chapter 4.
This appendix answers some of the most frequently asked questions
about Corel Painter 12:
• Can I deploy the software in a Windows 7 environment?
• Can I deploy the software in a Mac OS environment?
• Can I deploy the software by using a Group Policy Object?
• Can I deploy the software with a single registration?
• Can I create multiple server images?
• Can I make the extra content on the DVD available to workstation
users?
Can I deploy the software in a Windows 7
environment?
Yes! Corel Painter 12 is compatible with the Windows 7 operating
system.
To create a server image on a Windows 7 network that contains a mix of
workgroups and domains, you must have appropriate permissions.
Can I deploy the software in a Mac OS
environment?
Yes! Corel Painter 12 can be installed on Mac OS workstations that meet
the following minimum system requirements:
• Operating system with the latest revision: Mac OS X 10.5 or 10.6
• Intel® Core™ Duo processor
•1 GB of RAM
• 300 MB of hard-disk space for installation of program files
• Mouse or tablet
• 1200 × 800 (or greater) screen resolution
How do I install and maintain the Mac OS version of the software?
The Corel Painter 12 setup for Mac OS supports the following
command-line syntax for installing the software to the Mac OS X
workstations on your network:
To simplify the process of making Corel Painter 12 available to the
network, you can use the tools that are included with the
Mac OS X Server operating system. For example, you can use the
NetBoot service to manage Corel Painter 12 from a server image, or you
can use the NetInstall utility to install and maintain Corel Painter 12 on
the workstations. For detailed information on deploying software to a
Mac OS X network, please visit the manufacturer’s website for
Mac OS X Server.
How do I register the Mac OS version of the software?
The installation package for Corel Painter 12 supports the following
command-line syntax, which you can use to register the software after it
is installed:
prompts for all users, you
must use the specified syntax for each
individual user.
In addition, you can use the following command-line syntax to disable
the registration utility for a user and prevent that user from receiving
registration prompts:
% defaults write com.corel.register PF12.count 0
Can I deploy the software by using a Group
Policy Object?
Yes, if you have the following:
• a network domain that is based on Active Directory® directory
service
• domain controllers for Windows Server 2003 (or later)
• workstations that run Windows 7, Windows Vista or
Windows XP Professional.
For basic information on the access rights that are required for installing
the software, see page 12.
For help with using Group Policy Objects, please refer to your
Group Policy Software Development Kit.
For specific help with using Group Policy Objects to deploy Corel
software, contact Corel Support Services (www.corel.com/support).
Please note that charges will apply.
Can I deploy the software with a single
registration?
For information on
registering the software in a
Mac OS environment, see “Can I
deploy the software in a Mac OS
environment?” on page 46.
In fact, you must create
multiple server images if you
want to support both 32-bit and
64-bit installations of the software.
Yes. If you do not want the workstations to display a registration
request, be sure to enter all the required registration information when
you create the server image.
You can use a command line to suppress the user interface during the
installation of the software on the workstations. This technique
automatically applies the registration information that you provided for
the server image. For more information on this technique, see “How
much of the setup interface do I want users to see?” on page 26.
If your command line for deploying to the workstations uses the
switch (see page 26), the end-user license agreement (EULA) appears
the first time that Corel Painter 12 is started on a workstation. To
prevent the EULA from appearing again on that workstation, a user
with administrator-level rights must unlock the software by accepting
the terms of the EULA.
/q
Can I create multiple server images?
Yes. For details, see “How do I create multiple server images?” on
page 21.
Can I make the extra content on the DVD
available to workstation users?
Yes. If your version of Corel Painter 12 includes extras (such as
gradients, nozzles, patterns, stock photos, paper textures, and brushes),
you can make them available to workstation users by copying them to a
shared folder on the server (or at some other location on your network).
The person who makes sure that all software is deployed to the network. An administrator may be a project
manager, a network administrator, or a deployment specialist.
administrator image
See “server image.”
advertisement
A file used by Microsoft Systems Management Server to deploy software by deploying the information stored
in a package.
command line
A textual command. A command line lets you specify settings with switches and parameters when you create
a software image on the server and install an application to each workstation.
component
See “feature.”
deployment
The systematic and strategic distribution of software to a network.
feature
A set of files that makes up part of an installed product. For example, an application or the writing tools for a
language can make up a feature. Using a command line, you can specify how you want to install features.
“Parent features” govern “child features.”
Globally Unique Identifier (GUID)
A 128-bit (16-byte) integer that uniquely identifies a user-interface object, so that it is highly unlikely to be
duplicated.
Group Policy Object (GPO)
An item, stored in a central network location, that defines the common desktop and network configurations
used on a Windows-based workstation. Each Windows-based workstation uses Group Policy Objects to
automatically update or modify local registry settings when users log in to the network.
image
See “server image.”
Deployment Guide
Glossary49
Page 53
key
The place where application-configuration information is stored in the Windows registry. Keys are roughly
analogous to records in a database.
license
The permission to install a purchased application to one workstation.
Microsoft patch (MSP) file
A file used to update, or “patch,” the software.
Microsoft transformation (MST) file
A file that applies a group of customized settings to an installation. Some administrators choose to create their
own MST files to make the deployment process easier.
Microsoft Windows Installer (MSI) file
A file, provided by a product, that is used to create a server image of the product or deploy the product to a
network. An MSI file is a database file that contains all the setup features and all the keys for the Windows
registry required for the product; it also defines the folders and shortcuts that must be installed for the
product.
MSI file
See “Microsoft Windows Installer (MSI) file.”
MSI table
The information contained within a Microsoft Windows Installer (MSI) file. You can edit an MSI table to
customize the installation settings of the software.
MSP file
See “Microsoft patch (MSP) file.”
MST file
See “Microsoft transformation (MST) file.”
network
A configuration of two or more computers that are connected to each other to exchange information.
network administrator
A person who specializes in running a network and deploying software to it.
original equipment manufacturer (OEM)
Typically, a company that bundles the software of another company with its products. The OEM editions of a
software product typically include fewer features than their non-OEM editions.
package
A file used by Microsoft Systems Management Server to store the information necessary to deploy software.
Packages, also called “package definition files” or “SMS files,” are deployed by using advertisements.
Deployment Guide
Glossary50
Page 54
package definition (SMS) file
See “package.”
parameter
A command line element that can be invoked to refine the results of a switch.
patch
See “Microsoft patch (MSP) file.”
public property
An element in a command line that can be used to refine how the installation is carried out (for example,
which features are installed).
pull installation
A deployment scenario that allows users to execute the software installation themselves and perhaps even
choose their own installation options.
push installation
A deployment scenario that forces installation on the workstations without requiring any user interaction.
The user interface for the installation is typically suppressed. Silent switches are often used with third-party
push technologies.
push technology
A third-party tool that is used to initiate a push installation.
Readme file
A document, typically included with the software, that contains “release notes” or other important
information about the product.
registry
The Windows repository for application settings. A registry stores information in keys.
server
The network computer on which you create images of the software you want to deploy to the workstations,
and from which you manage the shared resources of the network.
server image
A set of uncompressed application files (created from a set of compressed files on the installation disc) used to
deploy the software to the workstations.
service pack
Typically, a set of Microsoft patch (MSP) files used to make a major update to the software.
setup
The installation wizard initiated by the Setup.exe file, which can be used to create a server image of the
software, prepare workstations for installation, deploy the software to a network, and (perhaps) maintain the
software.
Deployment Guide
Glossary51
Page 55
silent installation
A type of push installation in which no user interface is shown on the workstations.
SMS file
See “package.”
switch
A command line element that can be used to customize the installation scenario (for example, how much of
the user interface is visible or whether a log file is created).
system policy
See “Group Policy Object.”
transform
See “Microsoft transformation (MST) file.”
transformation file
See “Microsoft transformation (MST) file.”
value
A specification for a setting, such as for a registrykey or a public property.
workstation
A computer in the network from which a user works.
Product specifications, pricing, packaging, technical support and information (“specifications”) refer to the retail
English version only. The specifications for all other versions (including other language versions) may vary.
INFORMATION IS PROVIDED BY COREL ON AN "AS IS" BASIS, WITHOUT ANY OTHER
WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABLE QUALITY, SATISFACTORY QUALITY, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE, OR THOSE ARISING BY LAW, STATUTE, USAGE OF
TRADE, COURSE OF DEALING OR OTHERWISE. THE ENTIRE RISK AS TO THE RESULTS OF THE
INFORMATION PROVIDED OR ITS USE IS ASSUMED BY YOU. COREL SHALL HAVE NO LIABILITY
TO YOU OR ANY OTHER PERSON OR ENTITY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, OR
CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING, BUT NOT LIMITED TO, LOSS OF
REVENUE OR PROFIT, LOST OR DAMAGED DATA OR OTHER COMMERCIAL OR ECONOMIC LOSS,
EVEN IF COREL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR THEY ARE
FORESEEABLE. COREL IS ALSO NOT LIABLE FOR ANY CLAIMS MADE BY ANY THIRD PARTY.
COREL'S MAXIMUM AGGREGATE LIABILITY TO YOU SHALL NOT EXCEED THE COSTS PAID BY
YOU TO PURCHASE THE MATERIALS. SOME STATES/COUNTRIES DO NOT ALLOW EXCLUSIONS
OR LIMITATIONS OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE
ABOVE LIMITATIONS MAY NOT APPLY TO YOU.
Corel, the Corel logo, Corel DESIGNER, CorelDRAW, Digital Studio, Knowledge Base, Natural-Media,
PaintShop Photo, Painter, Video Studio, WinDVD, WinZip, and WordPerfect are trademarks or registered
trademarks of Corel Corporation and/or its subsidiaries in Canada, the U.S., and/or other countries. All other
product names and any registered and unregistered trademarks mentioned are used for identification purposes
only and remain the exclusive property of their respective owners.
106051
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.