Corel Corel Designer Technical Suite - X5 Deployment Guide

DEPLOYMENT GUIDE

Contents

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

About Corel DESIGNER Technical Suite X5 . . . . . . . . . . . . . . . . . . . . 1

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

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 DESIGNER Technical Suite X5? . . . . . . . . 11

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

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

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

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

What is Setup.exe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

What is Setup.msi? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

What is Setup.xml? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

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

What are SMS files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

What are MST files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

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

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

Chapter 3

Creating the server image. . . . . . . . . . . . . . . . . . . . . 20

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

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

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

What preliminary actions are required? . . . . . . . . . . . . . . . . . . . . . . . .21

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

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

Corel DESIGNER Technical Suite X5 Deployment Guide i

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

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

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

How do I create customized workspaces? . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 4

Installing with command lines . . . . . . . . . . . . . . . . . 30

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

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

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

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

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

Chapter 5

Pulling the software to the workstations . . . . . . . . . 41

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

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

Chapter 6

Pushing the software to the workstations . . . . . . . . 44

How do I deploy the software

with Microsoft System Center Configuration Manager? . . . . . . . . . 44

How do I deploy the software

with Microsoft Systems Management Server?. . . . . . . . . . . . . . . . . 45

How do I create a package

with Microsoft Systems Management Server? . . . . . . . . . . . . . . . . . . . 45

How do I create an advertisement? . . . . . . . . . . . . . . . . . . . . . . . . . . .47

How do I deploy the software with IntelliMirror? . . . . . . . . . . . . . . 47

How do I deploy the software

with Novell ZENworks Desktop Management? . . . . . . . . . . . . . . . . 48

Chapter 7

Maintaining the software . . . . . . . . . . . . . . . . . . . . . 49

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

How do I repair the software by using

the Windows Control Panel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

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

How do I modify the software?. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

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

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

How do I apply patches? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

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

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

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

Contents ii

Appendix A

Quick-reference topics . . . . . . . . . . . . . . . . . . . . . . . 57

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

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

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

What are the available features?. . . . . . . . . . . . . . . . . . . . . . . . . . . 63

What are the features for the main applications? . . . . . . . . . . . . . . . .63

What are the features for the language modules? . . . . . . . . . . . . . . . .66

What are the features for the writing tools? . . . . . . . . . . . . . . . . . . . .67

Appendix B

Frequently asked questions . . . . . . . . . . . . . . . . . . . 69

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

Can I deploy the software by using the msiexec.exe file? . . . . . . . 69

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

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

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

Can I customize the setup fileset on the server image?. . . . . . . . . . 72

What information is contained in the Setup.xml file? . . . . . . . . . . . . .73

Can I customize the installation settings on the server image? . . . . 75

Can I create run-from-network installations? . . . . . . . . . . . . . . . . . 75

Can I make the extra content on the DVD

available to workstation users? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Can I make the Bitstream Font Navigator software

available to workstations users? . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

How do I deploy and maintain

the Right Hemisphere Deep Exploration software? . . . . . . . . . . . . . 77

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Contents iii

Introduction

This guide was developed as a step-by-step resource for deploying Corel DESIGNER® Technical Suite X5 to your network.

In this introductory section, you’ll learn a bit about the software, this guide, and Corel Corporation.

• About Corel DESIGNER Technical Suite X5

• About this guide

• About Corel

About Corel DESIGNER Technical Suite X5

Corel DESIGNER Technical Suite X5 offers the following powerful applications for creating technical illustrations:

• Corel DESIGNER® — a precision graphics application that is created to meet the demands of technical illustrators

• Right Hemisphere® Deep Exploration™ — an application for authoring and publishing a wide range of two-dimensional (2D) and three-dimensional (3D) graphics

In addition, Corel DESIGNER Technical Suite X5 includes CorelDRAW Graphics Suite X5, trusted illustration and design software that offers the following applications:

• CorelDRAW® — an intuitive and versatile graphics application for creating high-quality vector illustrations, logo designs, and page layouts

• Corel® PHOTO-PAINT™ — a complete image-editing application for retouching and enhancing photos

• Corel CAPTURE™ — an application for capturing images from your computer screen

• Corel® CONNECT — an application for finding content on your computer, local network, the Corel® content DVD, or online

This software is an excellent choice for networked environments because it offers a robust deployment process for easy installation and maintainance.

Corel DESIGNER Technical Suite X5 Deployment Guide 1

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.

• Chapter 2: Understanding the software lists the system requirements and technical specifications for Corel DESIGNER Technical Suite X5.

• 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, modify, 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.

Introduction 2

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.

The documentation conventions that are used 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

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.

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 guides at the following location (where X: is the drive where the software is installed):

Introduction 3

X:\Program Files\Corel\Corel DESIGNER Technical Suite X5\ Languages\<language>\Help

For even more information about the software, please see the following online resources.

Resource Description and URL

Corel DESIGNER Technical Suite website

Corel® Support Services website Provides prompt and accurate

® Knowledge Base™ Provides a repository of articles, written

Corel

Corel DESIGNER Technical Suite online community

Provides the latest news, tips and tricks, and information about upgrades

www.corel.com/designer

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

www.corel.com/support

by the Corel® Technical Support Services team in response to questions by users, that you can search by keyword

www.corel.com/knowledgebase

Provides interaction with other users through sharing experiences, asking questions, and receiving help and suggestions

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

Introduction 4

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 the recently released 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.

Introduction 5

Chapter 1

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

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

Corel DESIGNER Technical Suite X5 Deployment Guide 6

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 mp ut er s t hat 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 a second for the more advanced version.) Be sure to use a naming convention that lets you remember what each server image contains.

Chapter 1: Getting started 7

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, IntelliMirror® management technologies, or Novell® ZENworks® Desktop Management.

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.

Chapter 1: Getting started 8

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.

Chapter 1: Getting started 9

A service pack typically

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.

Chapter 1: Getting started 10

Chapter 2 Understanding the software

This chapter provides the system requirements and technical specifications for Corel DESIGNER Technical Suite X5. 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 DESIGNER Technical Suite X5?

• 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 DESIGNER Technical Suite X5?

Workstations already using

CorelDRAW Graphics Suite X5 must be either upgraded to Corel DESIGNER Technical Suite X5 or left as is.

The CorelTRACE®

application, which offered bitmap-to-vector conversion in earlier editions of the software, has been directly integrated into Corel DESIGNER and CorelDRAW as the Corel® PowerTRACE™ feature.

Corel DESIGNER Technical Suite X5 includes the following:

• Corel DESIGNER X5

• Right Hemisphere Deep Exploration

• CorelDRAW Graphics Suite X5

Workstations already using CorelDRAW Graphics Suite X5 must be either upgraded to Corel DESIGNER Technical Suite X5 or left as is. Corel DESIGNER Technical Suite X5 offers all the features of CorelDRAW Graphics Suite X5, plus additional features specific to creating technical illustrations. If you want to help workstation users transition between the two software suites, you can customize the Windows Start menu with only Corel DESIGNER Technical Suite X5 shortcuts, only CorelDRAW Graphics Suite X5 shortcuts, or both sets of shortcuts; for information, see page 35.

CorelDRAW Graphics Suite X5 includes the following:

•CorelDRAW X5

• Corel PHOTO-PAINT X5

•Corel CAPTURE X5

Corel DESIGNER Technical Suite X5 Deployment Guide 11

• Corel CONNECT

• Bitstream® Font Navigator®

• Microsoft® Visual Basic® for Applications 6.4

• Microsoft® Visual Studio® Tools for Applications 2.0

To run Bitstream Font

Navigator, workstation users require elevated access privileges.

For information on making the

clipart available on workstations, see “How do I provide access to extra content?” on page 25.

Please note that workstation users require elevated access privileges to run Bitstream Font Navigator. The required user-access level depends on the operating system:

• Windows 7 — administrator-level privileges

• Windows Vista® — administrator-level privileges

• Windows XP — “Power User” privileges

What’s on the DVD?

The Corel DESIGNER Technical Suite X5 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 DESIGNER Technical Suite X5 DVD also contains the following extra content:

• professional clipart images and templates

• photos and objects

•fonts

• video tutorials for CorelDRAW and Corel PHOTO-PAINT (require Windows Media® Player 10)

For information on using

Windows Terminal Server, see “Which server operating systems are supported?” on page 20.

What are the system requirements for the software?

To allow the installation of Corel DESIGNER Technical Suite X5, 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

• Pentium® 4, AMD Athlon™ 64, or AMD Opteron™

•1 GB of RAM

• 1.4 GB of hard-disk space (1.6 GB for a typical installation without extra content; up to 6.7 GB with extra content)

• Mouse or tablet

• 1024 × 768 or greater screen resolution (768 × 1024 on a tablet PC)

• Microsoft® Internet Explorer® 7.0 or later

Chapter 2: Understanding the software 12

You can also access the Readme

file from the Release notes

button on the AutoRun screen.

Where is the Readme file for the software?

The Corel DESIGNER Technical Suite X5 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 DESIGNER Technical Suite X5 DVD into the DVD

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:\English\Readme.html, where X: is the DVD drive.

Readme files for other languages can be accessed from their respective language folders on the DVD, as in the following examples:

•

X:\French\Lisez-moi.html — for the French-language

Readme file

X:\German\Infodatei.html — for the German-language

• Readme file

Group Policy Objects, sometimes called “system

olicies,” reside in a central location on a Windows-based network and define how each workstation is configured.

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

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.

Chapter 2: Understanding the software 13

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\

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 successfully install the software during a terminal (or “remote desktop”) session, users require the following system policy to be enabled:

• Computer Configuration\Administrative Templates\

Windows Components\Windows Installer\ Allow admin to install from Terminal Services session

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.

To allow the successful patching of the installed software, users who have limited access rights require the following system policy to be enabled:

• Computer Configuration\Administrative Templates\

Windows Components\Windows Installer\ Enable user to patch elevated products

For help with using Group Policy Objects with Corel software, contact Corel Support Services (www.corel.com/support). Please note that charges will apply.

What files are required by the setup?

The Setup folder on the Corel DESIGNER Technical Suite X5 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

Chapter 2: Understanding the software 14

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

What is Setup.exe?

In this guide, “Setup.exe”

refers to the Setup.exe file for Corel DESIGNER Technical Suite X5, 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 Setup folder, 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, modify, 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 DESIGNER Technical Suite X5, unless otherwise noted.

What is Setup.msi?

Located at Setup\CGS15, 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 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.

Various components of the software are stored in additional MSI files. Some of these MSI files are required by the setup, while others represent optional features of the software. The setup uses these additional MSI files to carry out the installation, based on the specified installation settings.

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:

Chapter 2: Understanding the software 15

• Setup\ICA.msi

• Setup\CGS15\64BitKey.msi

• Setup\CGS15\ShellExt.msi

You can combine languages

from multiple versions of the software to create a customized setup. For more information, see “Can I customize the setup fileset on the server image?” on page 72.

The $$_Des.msi files provide

language support for Corel DESIGNER, while the $$.msi files provide language support

or CorelDRAW Graphics Suite X5. Also note that Right Hemisphere Deep Exploration always installs in English, French, and German.

In addition, the setup requires at least one language module, MSI files for which are stored at Setup\CGS15. The language modules that are available vary with each edition of the software.

• BR.msi — installs the Brazilian Portuguese language module

• CS.msi — installs the Chinese (Simplified) language module

• CT.msi — installs the Chinese (Traditional) language module

• CZ.msi — installs the Czech language module

• DE.msi, along with DE_Des.msi — installs the German language

module

• EN.msi, along with EN_Des.msi — installs the English language

module

• ES.msi — installs the Spanish language module

• FR.msi, along with FR_Des.msi — installs the French language

module

• IT.msi — installs the Italian language module

• JP.msi — installs the Japanese language module

• KR.msi — installs the Korean language module

• MA.msi — installs the Hungarian language module

• NL.msi — installs the Dutch language module

• PL.msi — installs the Polish language module

• RU.msi — installs the Russian language module

• SU.msi — installs the Finnish language module

• SV.msi — installs the Swedish language module

• TR.msi — installs the Turkish language module

What additional MSI files are used by the setup?

To install the applications that are included with the software, the setup uses the following MSI files (stored at Setup\CGS15):

• Capture.msi — installs Corel CAPTURE

• Designer.msi — installs Corel DESIGNER

• Draw.msi — installs CorelDRAW

• FontNav.msi — installs Bitstream Font Navigator

• PHOTO-PAINT.msi — installs Corel PHOTO-PAINT

To install the Right Hemisphere Deep Exploration software, the setup uses the following MSI file (stored at Setup\CGS15):

• DeepExploration.msi

To install the various components of the software, the setup uses additional MSI files (stored at Setup\CGS15), such as the following:

Chapter 2: Understanding the software 16

• Ghostscript.msi — installs the general public license (GPL) for

Ghostscript, a technology that enhances support for importing EPS files and PostScript® files

• VBA.msi — with the files in the VBA subfolder, installs the

Microsoft Visual Basic for Applications 6.4 feature

• CGS_VSTA.msi — with the files in the VSTA subfolder, installs the

Microsoft Visual Studio Tools for Applications 2.0 feature

To create a customized server

image with a reduced fileset, see “Can I customize the setup fileset on the server image?” on page 72.

If you want, you can exclude any of these MSI files from the setup by creating a customized server image. Excluding an MSI file prevents the corresponding feature from being installed. For more information, see “Can I customize the setup fileset on the server image?” on page 72.

What is Setup.xml?

Located at the root of the Setup folder, 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. If you want to customize the setup fileset on the server image, you must edit the Setup.xml file to reflect any changes made to the fileset. For more information on this procedure and on the contents of the Setup.xml file, see “Can I customize the setup fileset on the server image?” on page 72.

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

SMS files are used in

push-installation scenarios, as explained in Chapter 6.

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.

SMS files are available on the Corel DESIGNER Technical Suite X5 DVD at Setup\CGS15\Administrator. Copies are stored on the server image at cgs15\administrator.

For more information on using SMS files, see “How do I deploy the software with Microsoft Systems Management Server?” on page 45.

Chapter 2: Understanding the software 17

You can also use a command

line to specify how features are installed. For information, see

age 36.

You can also use a command

line to specify the default location of installation files. For information, see page 35.

For information about other

methods of editing registry entries, see page 24.

Public properties are

command-line elements that are used to customize the software. For information on the available

ublic properties, see page 59.

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, which are set to run from the network, 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 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.

Chapter 2: Understanding the software 18

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 DESIGNER Technical Suite X5 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 34.

How do I register the software?

Registering Corel DESIGNER Technical Suite X5 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 72.

For general information about registering the software, please visit

www.corel.com/support/register.

The software supports the

automatic detection of available patches. However, you can choose whether to make this update

eature available on the workstations. For information, see “How do I specify whether to allow automatic updates?” on page 39.

How do I maintain the software?

Occasionally, you may find it necessary to repair or modify 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 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 52.

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.

Chapter 2: Understanding the software 19

Chapter 3

k depl

r a

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 DESIGNER Technical Suite X5 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?

If you open the Autorun on Windows Server, you may

eceive a script error on close. To

void this error, right-click the

utorun entry on the taskbar, and

hoose Close.

You can create an image of Corel DESIGNER Technical Suite X5 on a server that has any of the following operating systems installed:

• Windows Server 2008

• Windows Server 2003

• Windows Server 2003, Advanced Server

Is Windows Terminal Server supported?

Yes, you can use Corel DESIGNER Technical Suite X5 with Windows Terminal Server. However, please keep in mind the following:

• You must use the Corel DESIGNER Technical Suite X5 DVD to install the software on the server.

• You must be in Install mode to install the software.

Corel DESIGNER Technical Suite X5 Deployment Guide 20

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.

• Corel Corporation does not provide technical support for the installation functionality of any third-party software on its installation discs.

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 — and whether to install them locally or run from the network. In pull-installation scenarios (see Chapter 5), workstation users are prompted to make such installation choices for themselves. However, you can use any of the following methods to standardize and enforce how applications and features are installed:

• Use command-line public properties to specify the desired installation settings. For information, see “How do I specify how features are installed?” on page 36.

• Change the fileset for the setup. For information, see “Can I customize the setup fileset on the server image?” on page 72.

• 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 18); then, you must make it available for deployment through a command line (see “How do I apply MST files?” on page 34). 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.

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.

Workstations running the

Dutch version of Windows Vista with .NET SP1 require a

atch from the Microsoft website.

What preliminary actions are required?

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.

Chapter 3: Creating the server image 21

How do I create the server image?

As the administrator, you create the server image by running the executable file Setup.exe.

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.

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.

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

• Apply MST files to the setup. For information, see “What are MST

files?” on page 18.

• Change the fileset for the setup. For information, see “Can I

customize the setup fileset on the server image?” on page 72.

When you install the software,

Microsoft Windows Installer is automatically updated to version 3.0.

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.

To create a server image

1 Insert the Corel DESIGNER Technical Suite X5 DVD into the DVD

drive. If the Autorun opens, click Exit.

2 On the Windows taskbar, click Start ` Run. 3 Type the following command line, where X: is the DVD drive.

X:\Setup\Setup.exe /a

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

/q switch into your command line —

Chapter 3: Creating the server image 22

The setup cannot continue if

you do not accept the terms in the license agreement.

• /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 32.

If prompted, choose the installation language from the list box. 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.

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

5 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 15) — either by creating a customized MST file (see page 18), or by using public properties in your command line (see page 35).

It is crucial that you limit

the installation path to 70 characters. Using more than 70 characters may cause the applications to function incorrectly.

Workstations that run from the network cannot be

configured to detect and download

roduct updates.

For more information on registering, see “How do I

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

7 If you want to allow workstations to detect and download product

updates, enable the Product updates check box.

Workstations that run from the network cannot be configured to detect and download product updates.

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

9 Follow the prompts to register the software immediately.

10 Click Finish.

11 Follow the directions given in “How do I finalize the image?” on

page 24.

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

Chapter 3: Creating the server image 23

It is recommended that you test the user rights before deploying

the software to the workstations.

How do I finalize the image?

Before you can begin deploying Corel DESIGNER Technical Suite X5 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. If you want, you can also create customized workspaces that can be deployed to the workstations.

• How do I verify network-access privileges?

• How do I edit registry settings?

• How do I create customized workspaces?

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.

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

• How do I provide access to extra content?

• How do I provide dynamic language switching?

Chapter 3: Creating the server image 24

+ 63 hidden pages