Corel Painter 12 User guide

Brand: Corel

Model: Painter 12

Category: Software manuals

Type: User guide

Deployment Guide

Contents

Deployment Guide

Contents i

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About Corel Painter 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About Corel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1: Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

What is a network? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

How is a network managed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

How is software deployed to a network? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

How is a server image created? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

How is a server image used to deploy software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

What is the best way to prepare for deployment? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

How is installed software best maintained? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2: Understanding the software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

What is included in Corel Painter 12? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

What are the system requirements for the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Where is the Readme file for the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What access rights are required for installing the software?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What files are required by the setup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

What is Setup.exe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

What is Setup.msi? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

What is Setup.xml? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

What types of files can interact with the setup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

What are SMS files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

What are MST files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

How do I register the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

How do I maintain the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3: Creating the server image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

How can I best prepare for creating the server image? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Which server operating systems are supported? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

What types of installations are available? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

What preliminary actions are required? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

How do I create the server image? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

How do I create multiple server images? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

How do I finalize the image? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

How do I verify network-access privileges? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

How do I edit registry settings? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Deployment Guide

Contents ii

Chapter 4: Installing with command lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

How do I assemble a command line? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Step 1: Specify the executable file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Step 2: Define the deployment process with switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Step 3: Refine the installation with public properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

How do I run my command line? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 5: Pulling the software to the workstations. . . . . . . . . . . . . . . . . . . . . . 31

How can I best prepare for pull installation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

How do users pull the software?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 6: Pushing the software to the workstations . . . . . . . . . . . . . . . . . . . . . 33

Chapter 7: Maintaining the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

How do I repair the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

How do I repair the software by using the Windows Control Panel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

How do I repair the software by using a command line? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

How do I update the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

How do I locate available patches? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

How do I apply patches? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

How do I remove the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

How do I remove the software by using the Windows Control Panel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

How do I remove the software by using a command line? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Appendix A: Quick-reference topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

What is the process for deploying the software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

What are the available command-line switches?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

What are the available public properties? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Appendix B: Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Can I deploy the software in a Windows 7 environment? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Can I deploy the software in a Mac OS environment?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Can I deploy the software by using a Group Policy Object? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Can I deploy the software with a single registration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Can I create multiple server images?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Can I make the extra content on the DVD available to workstation users? . . . . . . . . . . . . . . . . . . . . . . 48

Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Introduction

Deployment Guide

Introduction 1

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 software is an excellent choice for networked environments because

it offers a robust deployment process for easy installation and

maint

enance.

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.

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.

Deployment Guide

Introduction 2

• 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

Introduction 3

The documentation conventions that are used in this guide are explained

in the following table.

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

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

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 programming syntax.

For clarity, some programming

elements are further distinguished by

italics.

Deployment Guide

Introduction 4

For even more information about the software, please see the following

online resources.

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

Resource Description and URL

Corel Painter website Provides the latest news, tips and

tricks, and information about upgrades

www.corel.com/painter

Corel® Support Services website 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

Corel Painter online community Provides interaction with other users

through sharing experiences, asking

questions, and receiving help and

suggestions

www.painterfactory.com

Deployment Guide

Introduction 5

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

Chapter 1: Getting started 6

Chapter 1

Getting started

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?

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.

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.

A networ

is ma

e up o

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.”

Deployment Guide

Chapter 1: Getting started 7

How is a network managed?

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

way. Obviously, t h e more compu ters th 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.

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 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.

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.

Deployment Guide

Chapter 1: Getting started 8

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.

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.

Corel Corporation cannot

guarantee that all available

third-party push technologies work

with all Corel software products

Deployment Guide

Chapter 1: Getting started 9

What is the best way to prepare for 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.

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.

A Readme file contains

“release notes” or other

important information about the

roduct. Always consult the Readme

ile before deployment.

The registry is the Windows

repository for application

settings. The registry stores

information in keys.

Deployment Guide

Chapter 1: Getting started 10

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.

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.

A service pack typically

contains a set of patches that

combine to make a major update to

the software.

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.

Deployment Guide

Chapter 2: Understanding the software 11

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?

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.

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.

Deployment Guide

Chapter 2: Understanding the software 12

What are the system requirements

for the software?

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

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

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.

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.

Deployment Guide

Chapter 2: Understanding the software 13

To deploy the software to the workstations, you must

• be either a local administrator or an administrator for the domain

that you are managing

• have read access to the server location

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:

• Computer Configuration\Administrative Templates\