Corel Painter - 11 Deployment Guide
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About Corel Painter 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About Corel Corporation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 1
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What is a network? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How is a network managed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
How is software deployed to a network? . . . . . . . . . . . . . . . . . . . . . 6
How is a server image created? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
How is a server image used to deploy software? . . . . . . . . . . . . . . . . . .7
What is the best way to prepare for deployment? . . . . . . . . . . . . . . . . .8
How is installed software best maintained? . . . . . . . . . . . . . . . . . . . 8
Chapter 2
Understanding the software. . . . . . . . . . . . . . . . . . . 10
What is included in Corel Painter 11? . . . . . . . . . . . . . . . . . . . . . . . 10
What are the system requirements for the software? . . . . . . . . . . . 11
Where is the Readme file for the software? . . . . . . . . . . . . . . . . . . 11
What security rights are required for installing the software?. . . . . 11
What security rights are required for using
a Group Policy object to deploy the software? . . . . . . . . . . . . . . . . . . .12
What files are required by the setup? . . . . . . . . . . . . . . . . . . . . . . . 13
What is Setup.exe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What is Setup.msi? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
What is Setup.xml? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
What types of files can interact with the setup? . . . . . . . . . . . . . . . 14
What are SMS files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
What are MST files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
How do I register the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
How do I maintain the software? . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 3
Creating the server image. . . . . . . . . . . . . . . . . . . . . 18
How can I best prepare for creating the server image? . . . . . . . . . . 18
Which server operating systems are supported? . . . . . . . . . . . . . . . . .18
What types of installations are available? . . . . . . . . . . . . . . . . . . . . . .18
What preliminary actions are required? . . . . . . . . . . . . . . . . . . . . . . . .19
How do I create the server image? . . . . . . . . . . . . . . . . . . . . . . . . . 19
How do I create multiple server images? . . . . . . . . . . . . . . . . . . . . . . . 19
Corel Painter 11 Deployment Guide i
How do I finalize the image? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
How do I verify network-access privileges? . . . . . . . . . . . . . . . . . . . . .21
How do I edit registry settings? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Chapter 4
Installing with command lines . . . . . . . . . . . . . . . . . 23
How do I assemble a command line? . . . . . . . . . . . . . . . . . . . . . . . 23
Step 1: Specify the executable file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Step 2: Define the deployment process with switches . . . . . . . . . . . . .24
Step 3: Refine the installation with public properties . . . . . . . . . . . . . . 26
How do I run my command line? . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 5
Pulling the software to the workstations . . . . . . . . . 30
How can I best prepare for pull installation?. . . . . . . . . . . . . . . . . . 30
How do users pull the software?. . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 6
Pushing the software to the workstations . . . . . . . . 32
How do I deploy the software
with Microsoft Systems Management Server?. . . . . . . . . . . . . . . . . 32
How do I create a package
with Microsoft Systems Management Server? . . . . . . . . . . . . . . . . . . . 33
How do I create an advertisement? . . . . . . . . . . . . . . . . . . . . . . . . . . .34
How do I deploy the software with IntelliMirror? . . . . . . . . . . . . . . 34
How do I deploy the software
with Novell ZENworks Desktop Management? . . . . . . . . . . . . . . . . 34
Chapter 7
Maintaining the software . . . . . . . . . . . . . . . . . . . . . 36
How do I repair the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
How do I manually repair the software? . . . . . . . . . . . . . . . . . . . . . . .36
How do I automatically repair the software? . . . . . . . . . . . . . . . . . . . .37
How do I update the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
How do I locate available patches? . . . . . . . . . . . . . . . . . . . . . . . . . . .38
How do I apply patches? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
How do I remove the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
How do I manually remove the software? . . . . . . . . . . . . . . . . . . . . . .41
How do I automatically remove the software? . . . . . . . . . . . . . . . . . . . 42
Appendix A
Quick-reference topics . . . . . . . . . . . . . . . . . . . . . . . 43
What is the process for deploying the software? . . . . . . . . . . . . . . 43
What are the available command-line switches?. . . . . . . . . . . . . . . 44
What are the available public properties? . . . . . . . . . . . . . . . . . . . . 45
Contents ii
Appendix B
Frequently asked questions . . . . . . . . . . . . . . . . . . . 48
Can I deploy the software in a Windows Vista environment? . . . . . 48
Can I deploy the software in a Mac OS environment?. . . . . . . . . . . 48
Can I deploy the software with a single registration? . . . . . . . . . . . 49
Can I deploy the software by using a Group Policy object?. . . . . . . 50
Can I create multiple server images?. . . . . . . . . . . . . . . . . . . . . . . . 50
Can I create run-from-network installations? . . . . . . . . . . . . . . . . . 50
Can I make the extra content on the CD
available to workstation users? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Contents iii
Introduction
s
p
This guide focuses on the
Windows®-based version of
Corel Painter 11. For information
pecific to the Mac OS®–based
version, see “Can I deploy the software
in a Mac OS environment?” on
age 48.
This guide was developed as a step-by-step resource for deploying
Corel® Painter™ 11 to your network.
This introductory section describes the software suite and summarizes
what you’ll find in each chapter of this guide. You’ll also find an
explanation of the documentation conventions used and some helpful
links to additional information.
About Corel Painter 11
Corel Painter 11 is the ultimate digital art studio. Its inventive drawing
tools, realistic brushes, and customizable features let you expand your
creative output in exciting new ways. When you use the pressuresensitive 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 takes you far beyond what’s possible in a traditional art
environment.
Corel Painter 11 is an excellent choice for networked environments,
offering a robust process for easily installing and maintaining the
software.
About this guide
This guide applies to all
editions of Corel Painter 11.
The features described are available
in all editions, unless otherwise noted.
This guide contains the following chapters:
• Chapter 1: Getting started gives you an overview of how to deploy
Corel® software to your network and explains the necessary
terminology. If you’re new to software deployment, you’ll find that
this chapter walks you through the basics; if you’re an “old pro,” feel
free to skip this chapter entirely.
• Chapter 2: Understanding the software introduces you to
Corel Painter 11.
• Chapter 3: Creating the server image explains how to create the
software image for Corel Painter 11 on the server.
Corel Painter 11 Deployment Guide 1
• Chapter 4: Installing with command lines explains how to use a
command line to deploy the software to the workstations with the
settings you choose.
• Chapter 5: Pulling the software to the workstations explains how
users themselves can install the software on their workstations.
• Chapter 6: Pushing the software to the workstations explains
how to use third-party push technologies for automatic deployment
of Corel Painter 11 to the workstations.
• Chapter 7: Maintaining the software explains how to repair and
update your network installations of Corel Painter 11.
The appendixes provide useful supplementary information:
• Appendix A provides 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
about deploying Corel Painter 11.
You’ll also find a glossary, which defines the terms used in this guide.
Documentation conventions
As you work through this guide, you’ll find that the right column
of the 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.
The documentation conventions followed in this guide are explained in
the following table.
Wherever you see this You’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 text Information that is emphasized for
clarity, such as the name of a control or
other element on the user interface
Introduction 2
Wherever you see this You’ll find
italicized text The 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 text A reference to coding. For clarity, some
coding elements are further
distinguished by
For more information
italics.
Corel Painter 11 provides resources with helpful information about the
software.
For comprehensive information about the features in Corel Painter 11,
you can consult the product documentation.
By default, the Corel Painter 11 User Guide is installed to the following
location (where X: is the drive where the software is installed):
X:\Program Files\Corel\Corel Painter 11\Resources\<language>\
Help
You can access the Help system from within an application by clicking
Help ` Help topics.
For more information about Corel Painter 11, see the following online
resources.
Resource Description and URL
Corel Painter 11 Web site Provides the latest news, tips and
tricks, and information about upgrades
www.corel.com/painter
Corel® Support Services™ Web site Provides prompt and accurate
information about product features,
specifications, pricing, availability,
services, and technical support
www.corel.com/support
Corel
® Knowledge Base™ Provides a repository of articles, written
by the Corel Technical Support Services
team in response to questions by users,
that you can search by keyword
www.corel.com/knowledgebase
Introduction 3
Resource Description and URL
Corel Painter online community Provides interaction with other users
through sharing experiences, asking
questions, and receiving help and
suggestions
www.painterfactory.com
If you have any comments or suggestions regarding this deployment
guide or Corel Painter 11, please submit them by using the contact
information provided at www.corel.com/contact.
For help with the Microsoft® Windows® Installer technology, which is
used to install Corel Painter 11, please refer to information on the
Microsoft Web site.
About Corel Corporation
Corel Corporation 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 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® Paint Shop Pro® Photo,
Corel® Painter™, VideoStudio®, WinDVD®, Corel®
WordPerfect® Office, and WinZip®. Our global headquarters are in
Ottawa, Canada, and our 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.
Introduction 4
Chapter 1
y
y
A
Getting started
This chapter gives you an
overview of how to deploy
Corel software to your network, and
it explains the necessary terminology.
If you’re new to software deployment,
ou’ll find that this chapter walks
ou through the basics; if you’re an
“old pro,” feel free to skip this chapter
entirely.
For an at-a-glance overview of
the deployment process, see
ppendix A. For an overview of the
terminology used in this guide, see the
Glossary.
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 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?
This chapter also introduces much of the terminology that is used
throughout the guide.
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
Novell® operating system or the Windows Server® operating system.
Corel Painter 11 Deployment Guide 5
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. O bv io us ly, t he mo re co mpu te rs 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.
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 a second for the more advanced
version.) Be sure to use a naming convention that lets you remember
what each server image contains.
For detailed information on creating a server image, see Chapter 3.
Chapter 1: Getting started 6
How is a server image used to deploy software?
To deploy software from a server image, you must assemble a command
line that specifies which options and features you want to make available
to your users. For detailed information on command lines, see
Chapter 4.
After assembling your command line, you are ready to use it with the
server image to deploy software to the workstations. Deployment 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 thirdparty tool (or “push technology”) to install, or “push,” the software to
each workstation from the server image.
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.
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 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?
Third-party push technologies (such as Microsoft Systems Management
Server, IntelliMirror® management technologies, or Novell®
ZENworks® Desktop Management) let you push the software to the
workstations on the users’ behalf, so that the users themselves do not
participate in the installation. Corel Corporation cannot guarantee that
all available third-party push technologies work with all Corel products;
however, Chapter 6 provides tips on choosing a push technology that is
suitable for deploying Corel software, as well as basic guidelines on
push-installation scenarios that have been tested by the Corel team.
For detailed information on any push technology, please refer to the
manufacturer’s documentation.
Chapter 1: Getting started 7
What is the best way to prepare for deployment?
p
f
A Readme file is an
installation file that contains
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 for the software and with any
special installation instructions associated with 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:
• 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.
A service pack typically
contains a set of patches that
combine to make a major update to
the software.
You can help keep the workstations in top shape by installing missing
files and by replacing any files, shortcuts, and registry entries (or “keys”)
that have become corrupt in the software. In addition, 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. For more
information on repairing or updating the software, see Chapter 7.
Chapter 1: Getting started 8
It’s always a good idea to upgrade to the latest version of the software.
f
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 removing the software, 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.
Chapter 1: Getting started 9
Chapter 2
s
Understanding the software
This chapter describes the system requirements and technical
specifications for Corel Painter 11. 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 11?
• What are the system requirements for the software?
• Where is the Readme file for the software?
• What security 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 11?
This guide focuses on the
Window s ver sion of
Corel Painter 11. For information
pecific to the Mac OS version, see
“Can I deploy the software in a
Mac OS environment?” on page 48.
For information on making the
clipart available on
workstations, see “Can I make the
extra content on the CD available to
workstation users?” on page 50.
Corel Painter 11 includes the Corel Painter application in both Windows
and Mac OS versions. Although this guide focuses on the Windows
version of Corel Painter 11, information specific to the Mac OS version is
provided on page 48.
What’s on the CD?
The Corel Painter 11 CD 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 13.
The Corel Painter 11 CD also includes a folder of extra content, which
contains libraries of unique gradients, nozzles, patterns, stock photos,
paper textures, and brushes.
Corel Painter 11 Deployment Guide 10
What are the system requirements for the software?
For information on using
Windows Terminal Server, see
“Which server operating systems are
supported?” on page 18.
To allow the installation of Corel Painter 11, workstations must include
the following:
• Operating system with the latest service pack and critical updates:
Windows Vista® (32-bit or 64-bit edition) or Windows XP (Home,
Professional, Media Center, Professional x64, or Tablet PC edition)
• Pentium® IV (700 MHz)
•1 GB of RAM
• Mouse or tablet
• SVG display with 1024 × 768 or greater screen resolution
(768 × 1024 on a tablet PC)
•CD drive
• 500 MB of hard-disk space
• Microsoft® Internet Explorer® 7.0
Where is the Readme file for the software?
The Corel Painter 11 CD 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.
You can also access the Readme
file from the AutoRun screen.
To access the Readme file
1 Insert the Corel Painter 11 CD into the CD drive.
2 On the Windows taskbar, do one of the following:
• In Windows Vista, click the Start button, and then click
All programs ` Accessories ` Run.
•In Windows XP, click Start ` Run.
3 Ty p e X:\Readme.htm, where X: is the CD drive.
What security rights are required for installing the software?
The setup is designed so that only users with administrator-level rights
can install the software. To create the server image or to deploy software
to the workstations, you must be either a local administrator or an
administrator for the domain that you are managing, and you must have
read/write access to the server location.
Chapter 2: Understanding the software 11
What security rights are required for using
p
a Group Policy object to deploy the software?
A Group Policy object,
sometimes called a “system
olicy,” defines the common desktop
and network configurations used on a
Windows-based workstation, and it
resides in a central network location.
Each Windows-based workstation
uses a Group Policy object to
automatically update or modify local
registry settings when users log in to
the network.
A Group Policy object is created by using the Microsoft Management
Console (MMC) or the Microsoft Group Policy Management Console
(GPMC, Windows Server 2003 only). To deploy the software by using a
Group Policy object, you must have a network domain that is based on
Active Directory® directory service, domain controllers for
Windows Server 2003, and workstations that run Windows Vista or
Windows XP Professional. For help with the MMC or GPMC, refer to
your Group Policy Software Development Kit.
To use a Group Policy object with Corel Painter 11, you must grant
workstation users the appropriate access. To do this, you must access the
editor for Group Policy objects:
• In Windows Vista, click the Start button, click All programs `
Accessories ` Run, and then run the file gpedit.msc.
• In Windows XP, click Start ` Run, and then run the file
gpedit.msc.
To successfully install software to the workstations, you must enable user
access to the following three policies:
• Computer Configuration\Administrative Templates\
Windows Components\Windows Installer\
Always install with elevated privileges
• Computer Configuration\Administrative Templates\
Windows Components\Windows Installer\
Enable user control over installs
• User Configuration\Administrative Templates\
Windows Components\Windows Installer\
Always install with elevated privileges
To allow the successful patching of an existing product by users with
limited security rights, enable the following policy:
• Computer Configuration\Administrative Templates\
Windows Components\Windows Installer\
Enable user to patch elevated products
To allow users to install software during a terminal (or “remote
desktop”) session, enable the following policy:
• Computer Configuration\Administrative Templates\
Windows Components\Windows Installer\
Allow admin to install from Terminal Services session
For help with Corel Painter 11 deployment issues related to Group
Policy objects, contact Corel® Support Services™
(www.corel.com/support). Please note that charges will apply.
Chapter 2: Understanding the software 12
Windows Installer technology
p
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.
What files are required by the setup?
The Corel Painter 11 CD contains all the files used by the setup.
The setup requires three main files:
• 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 14.
What is Setup.exe?
In this guide, “Setup.exe”
refers to the Setup.exe file for
Corel Painter 11, unless otherwise
noted.
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.
Stored at the root of the Corel Painter 11 CD, 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 11, unless otherwise noted.
What is Setup.msi?
Located in the Painter folder on the Corel Painter 11 CD, the
Setup.msi file is a Microsoft Windows Installer (MSI) file that contains a
database of all the setup features and registry keys 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
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.
Chapter 2: Understanding the software 13
What other MSI files are required by the setup?
The setup requires the following MSI files:
• ICA.msi
• Painter\Content.msi
• Painter\IconHandler 32 bit.msi
• Painter\IconHandler 64 bit.msi
• Painter\IPM.msi
In addition, the setup requires at least one of the language-module MSI
files stored in the Painter folder on the Corel Painter 11 CD. The
language modules provided depend on your version of the software.
• Chinese (Simplified) — CS.msi
• Chinese (Traditional) — CT.msi
•English — EN.msi
•French — FR.msi
•German — DE.msi
•Italian — IT.msi
• Japanese — JP.msi
•Korean — KR.msi
SMS files are used in
push-installation scenarios, as
explained in Chapter 6.
What is Setup.xml?
Located at the root of the Corel Painter 11 CD, Setup.xml is a text file
that lists all the features 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, 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.
For more information on using SMS files, see “How do I deploy the
software with Microsoft Systems Management Server?” on page 32.
Chapter 2: Understanding the software 14
You can also use a command
p
line to specify the default
location of installation files. For
information, see page 28.
For information about other
methods of editing registry
entries, see page 21.
Public properties are
command-line elements that
are used to customize the software.
For information on the available
ublic properties, see page 45.
Advertisements are used in
push-installation scenarios, as
explained in Chapter 6.
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.
• Specify values for any available public properties. Yo u ca 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 applications. 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.
Chapter 2: Understanding the software 15
You can use a proxy server to
register the software online.
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.
Corel Painter 11 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 27.
How do I register the software?
Registering 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.
You are prompted to register at the end of the process for creating a
server image of Corel Painter 11.
You can register by using one of the following methods:
• online — If you are connected to the Internet when you create the
server image, you can launch online registration. If no Internet
connection is detected, a list of options appears in a dialog box.
• by phone — If you are not connected to the Internet when you
create the server image, you can register by calling the Corel
Customer Service Center nearest you. For contact information, visit
www.corel.com/support.
Corel Painter 11 supports the
automatic detection of
available patches. However, this
update feature is not available on
workstations installed from a server
image.
Detailed registration procedures are included within the appropriate
sections in this guide. For more information about registering the
software, 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.
Corel Corporation periodically releases Microsoft patch (MSP) files, or
“patches,” for its products. These patches are made available through
the Corel Support Services Web site (www.corel.com/patches), and most
network administrators keep their installed software up-to-date by
monitoring this Web site. 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 38.
Chapter 2: Understanding the software 16
Loading...