Corel Corel Draw Technical Suite - 2019 Deployment Guide

Deployment Guide

CorelDRAW® Technical Suite 2019 Introduction

Welcome! This guide is intended to support you, the administrator, in deploying

CorelDRAW® Technical Suite 2019 to your network.

Are you new to network deployment? For a nontechnical introduction to the concepts and processes discussed in this guide, please see the companion

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

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

Stage 3: Installing the software . . . . . . . . . . . . . . . . . . . . . . .12

Stage 4: Maintaining the installations . . . . . . . . . . . . . . . . . .22

Appendix A: Specialized deployment scenarios . . . . . . . . . . .29

Appendix B: Authenticating the software. . . . . . . . . . . . . . . .47

Conventions Please note the following conventions used in this guide.

Wherever you see this You’ll find

italicized text A placeholder for user-specified

Corel® Beginner’s Guide to Network Deployment.

information, such as a path or filename

bold monospace text

For more information The following resources offer additional support.

For information on See the following resource

deploying Corel® software: concepts and processes, general advice and best practices

Corel Corporation, or a specific Corel software product

support for Corel software Corel® Support Services website: 

the Microsoft® Windows® Installer (MSI) technology, which is used to install Corel software

A reference to programming syntax

Corel® Beginner’s Guide to Network Deployment

Corel® website: 

www.corel.com

www.corel.com/support

Microsoft® website

Deployment Guide CorelDRAW® Technical Suite 2019 Introduction 1

Stage 1: Preparing for deployment

Highlights:

Server requirements. . . . . . . 2

Workstation requirements . .3

Before beginning the deployment, take the time to familiarize yourself with your network and the software you want to deploy to it. Doing so can help your administrative duties run as smoothly as possible.

In this stage Getting to know your network. . . . . . . . . . . . . . . . . . . . . . . . . 2

Getting to know the software . . . . . . . . . . . . . . . . . . . . . . . . .2

Setting up your network accordingly . . . . . . . . . . . . . . . . . . . .5

Getting to know your network

Make sure to consider your network requirements for the deployment.

Administrative factors Does your organization (or do you, as administrator) have any particular

requirements for deploying and maintaining software?

Server factors Does your server have any special characteristics or constraints?

Workstation factors Do your workstations have any special characteristics or constraints?

User factors Do your workstation users have any special workflows?

For more information For general guidance on assessing your deployment needs, please refer to

“Processes: Stage 1” in the Corel® Beginner’s Guide to Network Deployment

Getting to know the software

Make sure that your server and workstations are eligible for the software.

Server requirements You can create an image of CorelDRAW Technical Suite 2019 on a server

that meets the following requirements:

• Operating system with the latest service pack and critical updates:  Windows Server® 2012 R2, Windows Server® 2016, or Windows Server, Version 1709

• 3 GB of server space (for a typical installation without extra content)

Deployment Guide Stage 1: Preparing for deployment 2

The supported server operating systems support Remote Desktop Services (RDS) (previously known as Windows® Terminal Server), but please note the following:

• You must use the CorelDRAW Technical Suite 2019 DVD or the ISO file provided by Corel to install the software on the server.

• Corel Corporation does not provide technical support for installing thirdparty software included with the product.

• When you use remote desktop virtualization and deploy CorelDRAW Technical Suite on a server, note the following: When you access the suite as an administrator, the security settings of Internet Explorer on the server may not allow you to use the Welcome book. By default, Internet Explorer has its Enhanced Security Configuration setting enabled. You must disable it for the Welcome book to work normally.

• When workstations have Windows 7, and a Remote Desktop Client is used to connect to Remote Desktop Services, the display must be set to Highest Quality (32 bit) before connecting. Otherwise, the applications may stop responding when text is added to documents.

For details on server permissions, see “Server setup” on page 5.

Workstation requirements You can install CorelDRAW Technical Suite 2019 on workstations that

meet the following requirements:

• Windows 7, Windows 8.1 or Windows 10*, in 32-bit or 64-bit, all with latest Updates and Service Packs.

• Intel Core i3/5/7/9 or AMD Athlon 64

• 2 GB of RAM

• 10.7 GB of hard-disk space (for a typical installation)

• Multi-touch screen, mouse or tablet

• 1280 x 720 screen resolution at 100% (96 dpi)

• CD drive optional (for box installation) Installation from CD requires a download of up to 1.82 GB

• Microsoft® Internet Explorer® 11 (with the latest service pack) or later

• Microsoft® .NET Framework 4.7.2

• Internet connection is required to install and authenticate CorelDRAW Technical Suite and access some of the included software components, online features and content.

* CorelDRAW Technical Suite 2019 supports Windows 10, version 1803, 1809 and later versions being released during the lifecycle of CorelDRAW Technical Suite 2019.

For details on workstation permissions, see “Workstation setup” on page 5.

Workstations that have Windows 7 must have their monitors set to True Color (32 bit) for the software to function normally. Otherwise, the applications may stop responding when text is added to documents.

Deployment Guide Stage 1: Preparing for deployment 3

XVL Studio Corel Edition is included and installed with CorelDRAW Technical Suite 2019. The XVL Studio 3D CAD Corel Edition Add-On product unlocks additional functionality for the integrated application. For processing 3D CAD assembly data we recommend:

• Microsoft Windows 10, Windows 8.1 or Windows 7 (64-bit editions) with the latest updates and service pack installed

• 8 GB RAM or more

• 1280 x 800 or higher screen resolution

Software CorelDRAW Technical Suite 2019 Applications are available on DVD or as

an ISO file that you can download.

To use an ISO file, you can use one of the following options:

• Mount the ISO file as a virtual drive.

• Extract the ISO file contents by using WinZip or other third-party software.

Optionally, other content is available for download from a shared drive. This content includes applications — BenVista PhotoZoom Pro (EXE file) and Corel® AfterShot™ HDR — images (vector files and photos), fills, fonts, and templates. Please note that the default installation of CorelDRAW Technical Suite offers a limited number of fills and transparencies so it is important to download and install the fill packs included in the Fills folder.

For more information, see “Server setup” on page 5 and “Extensions” on page 42.

Note that training videos are not available for download. You can access short What’s New videos

and Hints videos online, on the CorelDRAW YouTube channels, or from the Welcome screen in CorelDRAW, Corel DESIGNER, and Corel PHOTO-PAINT.

For more information For important notes on installing and using the software, it’s a good idea to

review the Readme file for the software.

To access the Readme file on the installation disc

• Run the following command line (where X: is the disc drive):

X:\ReadMe\EN\Readme.html

Readme files for other languages can be accessed from their respective language folders on the DVD. Examples:

• X:\ReadMe\DE\Readme.html

• X:\ReadMe\FR\Readme.html

• X:\ReadMe\JP\Readme.html

Deployment Guide Stage 1: Preparing for deployment 4

Setting up your network accordingly

After familiarizing yourself with your network and the software you want to deploy to it, you can set up your network accordingly.

Server setup Do the following:

• Make sure that you are either a local administrator or an administrator

for the domains and workgroups that you are managing.

• Create a shared network location for the server image, and make sure

that you have read/write access to that location.

If you want to make extra content (such as clipart, photos, and fills) available to workstation users in an offline network environment, do the following:

• Set up a shared network location, and make sure that users have access

to that location.

• You will receive a confirmation Proof of Entitlement Certificate email

containing a URL linking to a shared drive containing the extra content, which you can download. Some of the downloadable content consists of Zip files that you must extract to the shared network location by using WinZip® or another compression tool.

The extracted content is 5.65 GB.

Workstation setup Do the following:

• Make sure that the workstations have Microsoft .NET Framework 4.7.2

installed.

• Make sure that you are — and anyone else who will be installing the

software is — either a local administrator or an administrator for the domains and workgroups that you are managing.

• Make sure that you have — and anyone else who will be installing the

software has — read access to the server-image location.

GPOs

To more easily manage the access rights of workstation users — especially for pull-installation scenarios — you may want to consider using Group Policy Objects (GPOs). The Corel Beginner’s Guide to Network Deployment offers basic information on GPOs. For more advanced information, please refer to the Software Development Kit (SDK) for Group Policy, which is available from Microsoft.

Deployment Guide Stage 1: Preparing for deployment 5

Stage 2: Creating the server image

Highlights:

Initializing the setup . . . . . .7

Setting up the server image . 7 Finalizing the server image 10

After preparing for deployment, you’re ready to create the server image.

To create a basic image, you run a standard command line. To create a customized image, you can modify this command line — or you can modify certain aspects of the server image or its setup. If you want to support multiple installation types, you can create multiple server images.

In this stage Creating a basic image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Creating a customized image. . . . . . . . . . . . . . . . . . . . . . . . .11

Creating multiple images . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Before creating a server image

You must have a corel.com account before running the administrative installation. If you don’t have a corel.com account, go to the corel.com sign-in page, click Create an Account, and follow the steps.

When creating a corel.com account, validate the email that is sent to the email address you used to create the account to avoid service disruption.

The account credentials (email address and password) used when first signing in to create a server image are the only account credentials that will be recognized for future sign-ins. Make note of the first credentials used.

It is recommended that you use an IT department email address as Corel.com account name.

Customers will receive a Proof of Entitlement Certificate email. It serves as proof of purchase and provides direct access to the software download and serial numbers for perpetual licenses. It also contains instructions for importing subscription licenses into the Corel.com customer account.

Creating a basic image

To create a basic server image, you must initialize the setup. After setting up the image and tweaking it as necessary, you can use it for deployment.

Deployment Guide Stage 2: Creating the server image 6

In this section Initializing the setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Initializing the setup

Event logging If you want to create a log file of installation events, include the /L switch

Limited setup UI If you want to limit the amount of UI encountered when creating a server

Setting up the server image . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Finalizing the server image. . . . . . . . . . . . . . . . . . . . . . . . . . .10

To initialize the setup for creating a server image using a limited amount of user interface (UI), you use a command line. You can create either a 32-bit server image or a 64-bit image.

The following command line lets you create a basic 32-bit server image from the installation disc (where

X:\x86\Setup.exe /a

X: is the disc drive):

The following command line lets you create a basic 64-bit server image:

X:\x64\Setup.exe /a

in your command line. For details on this switch, see page 14.

image, include the

/q switch in your command line. For details on this

process, see “Limited setup UI” on page 9.

Be careful to avoid suppressing (or “silencing”) a required user-interface field when introducing a you may fail to create a valid server image. You must include the following public properties in your command line:

•

TARGETDIR="path" — to specify the desired location of the server

image. For best results, do not end the path with a backslash (

•

SERIALNUMBER=<SerialNumber>

Setting up the server image

If your /a command line succeeds, the setup initializes in one of two ways:

• with full UI — for the standard command line

• with limited (or no) UI — for a command line customized to include

Full setup UI The setup UI takes you step-by-step through the process of setting up the

server image.

/q switch into your command line — otherwise,

\ ).

Deployment Guide Stage 2: Creating the server image 7

UI component Notes

End-User License Agreement (EULA) and Terms of Service

To create the server image, you must accept — on behalf of your organization — the End-User License Agreement and Terms of Service. Installations deployed from the image will not prompt users to review the license agreement.

Serial number, email address and password

A valid serial number and your corel.com account information, such as email address and

The Proof of Entitlement Certificate email contains the required serial number, which is

password, are required to access internet-based features and product updates.

assigned to the corel.com account used when creating the server image. For more information, see “Before creating a server image” on page 6.

Image Location Type the full (UNC) path in the

box provided, or click Change to browse to that location. To prevent installation problems, limit the path to 89 characters.

Product Updates You can choose to:

• automatically update the product

• check for updates and let the user choose when to install them

• never check for updates.

You can access these options only after entering the corel.com account user credentials.

Internet features This option allows workstations to

access internet-based features such as QR codes. You can access this option only after entering the corel.com account user credentials.

Deployment Guide Stage 2: Creating the server image 8

UI component Notes

Welcome screen You can choose to allow

workstations to access the Welcome screen in offline or online mode. When the Welcome screen is in offline mode, users cannot download and purchase items.

To create and deploy the server image, you must use a serial number that begins with the prefix DE21C22 (for perpetual licenses) or DE21S22 (for subscriptions) and has 37 characters (including dashes). If your serial number has fewer characters, it is not a valid serial number for software deployment.

You must be online when creating the server image so that you can accept the terms of service. In addition, when you enter your email address and password when online, a PROFILEID is generated that allows users to be signed in automatically. For more information, see “PROFILEID” on page 18.

If you’re offline, you can still deploy a server image without using credentials, but workstations will not have access to internet features or product updates. However, you can convert an offline workstation to online. For more information, see “Converting workstations from offline to online after deployment using /s” on page 18.

Limited setup UI If you want to limit the amount of user interface (UI) encountered when

creating a server image, include the

/q switch in your command line. For

details on this switch, see page 15.

Be careful to avoid suppressing (or “silencing”) a required user-interface field when introducing a

/q switch into your command line — otherwise,

you may fail to create a valid server image. You must include the following public properties in your command line:

•

TARGETDIR="path" — to specify the desired location of the server

image. For best results, do not end the path with a backslash (

• SERIALNUMBER=<SerialNumber>

\ ).

• ALLOW_PRODUCTUPDATES=2 — to disable automatic updates (and in-

product messaging) on the workstations. By default, if the administrator signs in or specifies a PROFILEID at the command line, automatic updates are enabled for workstations installed from a server image. For more information on the PROFILEID property, see “PROFILEID” on page 18.

•

ALLOW_INTERNETFEATURES=0 — to disable access to internet-based

features, such as QR codes.

Deployment Guide Stage 2: Creating the server image 9

• additional installation properties supported by the setup. For details, see “Using public properties” on page 16.

In the following example, the administrator has signed in with account credentials (email address and password), there is no setup UI, the serial number and PROFILEID properties are specified (for more information on the PROFILEID property, see “PROFILEID” on page 18), automatic product updates and access to internet-based features are enabled, the path to the server image is set, and any errors are recorded in the specified log file:

\\mountedISOpath\Setup.exe /a /qn SERIALNUMBER=<SerialNumber> PROFILEID=<ProfileIDDigit> ALLOW_PRODUCTUPDATES=1 ALLOW_INTERNETFEATURES=1 TARGETDIR=<PathToAdminImage> /L "C:\Logs\My_Log.txt"

In the following example, the administrator has not signed in with account credentials (email address and password), there is no setup UI, the serial number is specified, automatic product updates and access to internetbased features are disabled, the path to the server image is set, and any errors are recorded in the specified log file:

\\mountedISOpath\Setup.exe /a /qn SERIALNUMBER=<SerialNumber>  ALLOW_PRODUCTUPDATES=2  ALLOW_INTERNETFEATURES=0 TARGETDIR=<PathToAdminImage> "C:\Logs\My_Log.txt"

Finalizing the server image

This section describes recommended steps to take before deploying from the server image.

Optionally, you can finalize the image in the following ways:

• Customize the registry settings you want to deploy (see page 39).

• Customize the setup fileset (see page 42).

To avoid deploying the software twice, you may want to check for software updates and apply them to the image as necessary. For details, see page 25.

Testing the image You may want to test your finalized image with a small subset of

workstations before rolling it out to your entire organization.

Moving the image To change the location of a server image after you create it, you can copy

the image to a new location. However, after the software has been deployed to the workstations, the image cannot be moved.

Deployment Guide Stage 2: Creating the server image 10

Creating a customized image

If you require a more customized server image than offered by commandline switches (see page 14) and public properties (see page 16), you may want to consider the specialized scenarios discussed in the Appendix.

Registry keys You can edit the registry settings for the server image. See page 39.

Setup fileset You can customize the setup fileset. See page 42.

Installation settings You can customize the settings used to install the software on the

workstations. See page 44.

Creating multiple images

If your workstations require different configurations of the software, you can create one server image for each installation type.

If you want to support both 32-bit and 64-bit installations of the software, you must create two server images: one for the 32-bit installations, and one for the 64-bit installations. Make sure to place each server image in a separate folder.

You can install either the 32-bit or 64-bit version of the software to a workstation, but not both.

Product updates When a product update becomes available, you will need to apply it to each

server image. For details on image patching, see page 25.

Naming convention Use a naming convention that makes it easy to distinguish the server

images from one other.

Deployment Guide Stage 2: Creating the server image 11

Stage 3: Installing the software

Highlights:

Using switches . . . . . . . . . 14

Using public properties . . .16

After creating the server image, you can use it to install the software on the workstations in one of two ways:

• manually, by having users “pull” the software to their own workstations

• automatically, by “pushing” the software to the workstations on their users’ behalf

In this stage Pulling the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Pushing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Pulling the software

If users have both access to the server and administrator-level rights to their workstations, they can install (or “pull”) the software themselves. To do this, they run the setup from the server image.

In this section Preparing for pull installation. . . . . . . . . . . . . . . . . . . . . . . . .12

Carrying out a pull installation . . . . . . . . . . . . . . . . . . . . . . . .12

Preparing for pull installation

To ensure that the pull-installation process runs as smoothly as possible, take the time to prepare for it.

Requirements • Confirm that each workstation meets the minimum requirements for the

software (see “Workstation requirements” on page 3).

• Confirm that each workstation user has read-only access to the server image and administrator-level access to the workstation (see also “Workstation setup” on page 5).

Recommendation Map the workstations to the server image, and set the workstations to log

in to that server location at startup. Doing so ensures that users are always connected to the server image.

Carrying out a pull installation

Users pull the software to their workstations by running the setup from the server image.

The degree of user interaction required by the setup depends on how you’ve customized the server image and the deployment process.

Deployment Guide Stage 3: Installing the software 12

If you prefer to restrict user customization, you may want to offer multiple server images — one per set of installation options. For details, see page 11.

To pull the software to a workstation

1 Browse to the location of the server image, and double-click Setup.exe.

2 Carry out the installation, specifying any desired options, by following

the on-screen instructions.

To prevent installation problems, limit the installation path to 50 characters.

Pushing the software

To “push” the software from the server image to the workstations,  you must write a command line that includes the following:

• the filename of the setup you want to use

• any desired switches, to control how the setup runs

• any desired public properties, to specify installation settings

Using this command line, you can install the software on the workstations by using any supported push method.

When pushing a server image to workstations, the setup must be run with administrator-level privileges.

If the Security level for this zone setting is set to High in Microsoft Internet Explorer, no text will appear in the CorelDRAW Technical Suite 2019 installation dialog boxes. You can modify this setting in Microsoft Internet Explorer so that text will appear by following the procedure below.

To modify security settings in Internet Explorer

1 Click To o l s  Internet Options.

2 Click the Security tab.

3 Click the Custom level button.

4 In the Scripting list of options, enable the Enable option for Active

scripting.

5 Click OK, and click OK again.

6 Close Microsoft Internet Explorer.

If you plan to push the software silently, first make sure that each workstation has Microsoft .NET Framework 4.7.2 installed.

Deployment Guide Stage 3: Installing the software 13

In this section Specifying the setup file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Specifying the setup file

Using switches

Using switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Using public properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Running your command line . . . . . . . . . . . . . . . . . . . . . . . . .20

The most important item to specify in your command line is the executable file for the setup: the Setup.exe file on the server image you want to use:

•

\\server\path\x86\Setup.exe — to push the 32-bit version of

the software to 32-bit or 64-bit operating systems

•

\\server\path\x64\Setup.exe — to push the 64-bit version of

the software to 64-bit operating systems

You cannot use the 64-bit version of the software on 32-bit operating systems.

By using switches in your command line, you can control the setup process. Listed in this section are the switches most commonly used when installing the software.

For general information on switches, along with details on switch syntax, please see “Switches” in the Corel® Beginner’s Guide to Network Deployment

For a list of all command-line switches for Microsoft Windows Installer, please see the Microsoft website.

/L Event logging

Use

/L to log installation events.

Parameter What it logs

Status messages

Nonfatal warnings

All error messages

Initiated actions

Action-specific records

User requests

Error messages for out-of-memory warnings or fatal exits

Error messages for insufficient hard-disk space during server installation

Deployment Guide Stage 3: Installing the software 14

Parameter What it logs

Terminal properties

All of the above, in a single log file NOTE: Alternatively to

/L*, you can use /log.

Very detailed information

The default parameters for /L are iwearmo.

If you want to specify a path for the log file, use the following syntax:

/L "C:\Logs\My_Log.txt"

If you do not specify a path and filename, the log file is created in the current user’s temporary (Te m p ) folder.

In the following example, the

/L switch (with default parameters) is used

to log installation events in the specified file:

\\server\path\Setup.exe /L "C:\Logs\My_Log.txt"

/q Limited setup UI

Use

/q to limit the amount of setup UI encountered during installation.

You can use

/q to prevent users from entering their own registration

information, to help enforce specific installation options, or even to perform silent installations (in which no setup UI is visible whatsoever).

Parameter What the user sees during installation

No UI whatsoever. Errors are logged in a file that you can control by using

/L (see page 14). This is the default

parameter. NOTE: Alternatively to

Basic UI: a progress bar and a Cancel button. If the user

/qn, you can use /quiet.

pushes the Cancel button, the installation is rolled back upon confirmation.

NOTE: Alternatively to

Basic UI: only a progress bar. The user cannot cancel the

/qb, you can use /passive.

installation.

Basic UI: a progress bar and a Cancel button. If the user pushes the Cancel button, the installation is rolled back (without first prompting for confirmation).

Deployment Guide Stage 3: Installing the software 15

Parameter What the user sees during installation

/? Help

Using public properties

Reduced UI: A progress bar, along with a page containing information about the installation. The user can cancel the installation. Note: When run on a workstation, a command line with this parameter automatically installs any needed components. For example, it will install .NET 4.7.2 if the workstation doesn’t have the required version of .NET.

Full UI

The default parameter for /q is n.

In the following example, all setup UI is suppressed, and any errors are recorded in the specified log file:

\\server\path\Setup.exe /q /L "C:\Logs\My_Log.txt"

The

/? switch (or /help) displays Help for the setup.

By using public properties in your command line, you can specify installation settings. Listed alphabetically in this section are the properties most commonly used during software installation.

For general information on public properties, along with details on property syntax, please see the Corel Beginner’s Guide to Network Deployment.

For a list of all command-line properties for Microsoft Windows Installer, please see the Microsoft website.

ADDLOCAL Installing specific components

For details on this scenario, see the following topics in the appendix:

• “Deploying specific features” on page 29

• “Deploying specific languages” on page 31

ALLOW_INTERNETFEATURES Specifying settings for internet-based features

You can opt out of internet-based features by using the following property:

ALLOW_INTERNETFEATURES=0

You can allow access to internet-based features by using the following property:

ALLOW_INTERNETFEATURES=1

Deployment Guide Stage 3: Installing the software 16

ALLOW_PRODUCTUPDATES Specifying settings for product updates

You can check for updates and let the user choose when to install by using the following property:

ALLOW_PRODUCTUPDATES=0

You can keep the product automatically updated (and allow in-product messaging) by using the following property:

ALLOW_PRODUCTUPDATES=1

You can opt out of automatic updates (and in-product messaging) by using the following property:

ALLOW_PRODUCTUPDATES=2

There are default settings for product updates based on whether the administrator signs in with credentials.

• If the administrator does not sign in,

ALLOW_PRODUCTUPDATES=2 is

the default, and cannot be modified later.

• If the administrator enters credentials before creating the basic server image or specifies a PROFILEID at the command line,

ALLOW_PRODUCTUPDATES=1 is the default, but can be modified later.

DESKTOPSHORTCUTS Specifying settings for desktop shortcuts

You can prevent the installation of desktop shortcuts by using the following property:

DESKTOPSHORTCUTS=0

You can allow the installation of desktop shortcuts by using the following property:

DESKTOPSHORTCUTS=1

If nothing is specified, DESKTOPSHORTCUTS=1 is the default.

EXCLUDE_VSTA Opting out of installing Microsoft Visual Studio Tools for

Applications (VSTA)

You can opt out of installing VSTA by using the following property:

EXCLUDE_VSTA=1

INSTALLDIR Customizing the installation path

When deploying from the server image, use the following public property to customize the

INSTALLDIR="path"

workstation

installation path of the software:

This property can only be used during a workstation installation. For best results, do not end the path with a backslash ( \ ).

Deployment Guide Stage 3: Installing the software 17

PROFILEID Converting workstations from offline to online after

deployment using /s

PROFILEID property is used to push down account credentials to the

The workstations and sign in all users to the account. This property enables users to use their product privileges, such as content and updates, without knowing the email address and password associated with the account. Users must be online to access content and updates.

If the administrator deployed from the server image without signing in, workstations can only use the software offline. After deployment, administrators can give workstations online privileges, such as access to content and internet features, using the “

/s PROFILEID =” switch and

property.

The

PROFILEID value is a combination of letters and numbers. To access

it, go to Your Account page on corel.com and click Product Status Products section (Support > Your Account > Product Status). The Profile ID is in the lower-left corner of the page.

The following is an example of converting an offline workstation to online. You cannot convert multiple workstations simultaneously. Each workstation must be converted individually.

Example: Setup.exe /s PROFILEID=E9BBBZC091F861590331B12D63CA923

in Yo u r

The /s command line creates a key in the following hive directory:

HKEY_USERS\.DEFAULT\Software\Corel\Corel DESIGNER\21.0\IPM_CDTS\PremiumFeatures

ProfileGuid=4797935F031C2DD2E0530D02140A2BE4

The ALLOW_INTERNETFEATURES property changes from 0 to 1 in the following hive directory:

[HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel DESIGNER\21.0]

In addition, the WELCOMESCREENONLINE property changes to on in the following hive directory:

[HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel DESIGNER\21.0]

The PROFILEID property cannot be combined with any other properties.

This property can be used to convert workstations from offline to online after deployment but not vice versa.

Do not manually edit the key. Use the

/s command to properly modify the

key.

This property is not required if you have entered the email address and password when creating the server image.

Deployment Guide Stage 3: Installing the software 18

REBOOT Handling reboots

The

REBOOT property is used with one of the following values to specify

how the installation process handles any required reboots.

Value What it does

Force

(or F)

Prompts for reboot after installation. If the setup UI is suppressed, the computer is automatically rebooted after installation. NOTE: Alternatively to can use the

Suppress

(or S)

Prompts for reboot during installation (if required), but reboots automatically after installation. If the setup UI is suppressed, all required reboots are automatic. NOTE: Alternatively to you can use the 

/promptrestart switch.

ReallySuppress

(or R)

Suppresses all reboots and all reboot prompts, both during and after installation. NOTE: Alternatively to

REBOOT=ReallySuppress, you can use the /norestart switch.

SERIALNUMBER Specifying the serial number

The

SERIALNUMBER property is used to specify the serial number for the

installation:

REBOOT=Force, you

/forcerestart switch.

REBOOT=Suppress,

SERIALNUMBER=<SerialNumber>

TARGETDIR Specifying the location of the server image

The

TARGETDIR property is used to specify the desired location of the

server image.

TARGETDIR=<PathToAdminImage>

This property can only be used during server image installations. For best results, do not end the path with a backslash ( \ ).

Usernames cannot exceed 60 characters.

Deployment Guide Stage 3: Installing the software 19

WELCOMESCREENONLINE Setting the Welcome screen in offline or online mode

This property lets you set the Welcome screen in offline or online mode. When the Welcome screen is in offline mode, users cannot download and purchase items. To set the Welcome screen in offline mode, use the following syntax:

WELCOMESCREENONLINE=off

If WELCOMESCREENONLINE is not set to off or is any other value different from off, the Welcome screen is in online mode. Users can download and purchase items.

If the administrator does not sign in and deploys the software offline, this property is irrelevant for the workstation installations.

WELCOMESCREENONLINE is automatically set to off.

When the use of internet-based features (ALLOW_INTERNETFEATURES=1) is allowed,

WELCOMESCREENONLINE is set to on. When the use of internet-based

features (ALLOW_INTERNETFEATURES=0) is not allowed,

WELCOMESCREENONLINE is set to off.

You can change the value of file, stored at the root of the server image. For more information about customizing the installation settings, see “Deploying customized installation settings” on page 44.

Running your command line

Your command line can be used to push the software to the workstations through any of the following:

• a batch file — see the Microsoft website for details

• a GPO — see the Group Policy SDK for details

• a third-party push technology — see the manufacturer’s documentation for details

For many administrators, using a third-party push technology is the preferred push method. This section offers general guidelines on using a few such technologies.

SCCM At the time of this writing, Corel has verified support for Microsoft®

System Center Configuration Manager (SCCM) only insofar as its Microsoft Systems Management Server (SMS) components.

For complete information on using SCCM, please see the Microsoft website.

WELCOMESCREENONLINE in the persist.xml

SMS For deployment to the workstations on a “per-system” basis using package

definition files (or “packages”), CorelDRAW Technical Suite 2019 supports the use of Microsoft Systems Management Server (SMS).

Deployment Guide Stage 3: Installing the software 20

You can create a package from scratch — or you can create one from the existing SMS files included with CorelDRAW Technical Suite 2019 (in the Administrator folder on the installation disc or the server image).

For complete information on using SMS files, please refer to your resource kit for Microsoft Systems Management Server.

The recommendations posted on the Microsoft website have not been tested with CorelDRAW Technical Suite 2019 and must therefore be used at your discretion.

Using product privileges

To take advantage of product privileges, such as content and updates, after deployment, workstations must have internet access the first time they launch the applications. Users can then work offline, but they won’t have access to internet-based features.

Users are automatically signed in to the corel.com account associated with your volume license purchase provided you included account credentials (email address and password) during the creation of the server image. This ensures that they can use their product privileges.

You can choose to remove specific workstations from Yo u r A c c ou n t

page on corel.com. To sign in workstations that you previously signed out, you must provide account credentials. Alternatively, you can run the

command with PROFILEID again to restore the sign-in of signed out

setup.exe /

workstations. For more information, see “PROFILEID” on page 18.

Deployment Guide Stage 3: Installing the software 21

Stage 4: Maintaining the installations

An important part of administering a network is maintaining the software installed on its workstations.

In this stage Repairing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Modifying the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Updating the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Removing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Troubleshooting the software . . . . . . . . . . . . . . . . . . . . . . . .28

Repairing the software

Repairing the software lets you install (or reinstall) missing (or corrupted) components. You can repair a single installation of the software by using the Windows Control Panel on that workstation, or you can repair multiple workstation installations by using a command line.

Repairing a single installation

You can use the Windows Control Panel to repair a single installation.

To repair an installation with the Windows Control Panel

1 In the Windows Control Panel, display the list of currently installed

programs, and choose the program from the list.

2 Click Uninstall/Change.

3 Enable the Repair option, and then click Repair.

4 Follow the on-screen instructions.

Repairing multiple installations

You can use a command line to repair multiple installations at a time.

/f Basic repair

Use the

You cannot use the /f switch with public properties. For greater control over the repair process, use the properties instead of

/f switch with the Setup.exe file on the server image:

\\server\path\Setup.exe /f

REINSTALL and REINSTALLMODE

/f.

Deployment Guide Stage 4: Maintaining the installations 22

The /f switch has the following parameters.

Parameter What it does

REINSTALL

and REINSTALLMODE

Reinstalls missing files

Reinstalls missing files and files older than current version

Reinstalls missing files and files equal to or older than current version

Reinstalls missing files and files different from current version

Reinstalls all files

Reinstalls all required user-specific registry keys: HKEY_CURRENT_USER, HKEY_USERS

Reinstalls all required computer-specific registry keys: HKEY_LOCAL_MACHINE, HKEY_CLASSES_ROOT

The default parameters for

Reinstalls all existing shortcuts

Runs from the source files and re-caches the local package

/f are oums.

Advanced repair

For greater control over how the software is repaired, use the and

REINSTALLMODE public properties together.

REINSTALL

Property What it does

REINSTALL=ALL

Reinstalls all program features. If you prefer to reinstall only specific features (see page 29 for a list), use the following syntax:

REINSTALL=Feature

REINSTALLMODE=type

Specifies the type of reinstallation to perform. The values for this property are the same as the parameters for the switch, so its default values are

Deployment Guide Stage 4: Maintaining the installations 23

oums.

Modifying the software

Modifying the software lets you change which program features are installed. You can modify a single installation of the software by using the Windows Control Panel on that workstation, or you can modify multiple workstation installations by using a command line.

Modifying a single installation

You can use the Windows Control Panel to modify a single installation.

To modify an installation with the Windows Control Panel

1 In the Windows Control Panel, display the list of currently installed

programs, and choose the program from the list.

2 Click Uninstall/Change.

3 Enable the Modify option, and then click Next.

4 Follow the instructions that appear.

Modifying multiple installations

You can use a command line to modify multiple installations at a time.

ADDLOCAL Adding features

You can use the

ADDLOCAL=Feature

ADDLOCAL public property to add program features:

For more than one feature, use a comma-separated list, with no spaces between the comma and the feature name:

ADDLOCAL=Feature1,Feature2

For a list of available features, see page 29.

REMOVE Removing features

You can use the

REMOVE=Feature

REMOVE public property to remove a program feature:

For more than one feature, use a comma-separated list, with no spaces between the comma and the feature name:

REMOVE=Feature1,Feature2

For a list of available features, see page 29.

Deployment Guide Stage 4: Maintaining the installations 24

If you want to add nearly all features and remove only a couple of features, you can use the ADDLOCAL public property in conjunction with the REMOVE public property. For more information, see “Deploying specific features” on page 29.

Application languages are considered as features as well. You can use the ADDLOCAL public property and the REMOVE public property to add and remove application languages. For more information, see “Deploying specific languages” on page 31.

Updating the software

Corel periodically releases Microsoft patch (MSP) files — also known as “patches” or “updates” — for its products. Installing updates helps keep the software up-to-date.

Locating updates

Applying updates

In this guide, The actual filename varies with each update.

Many network administrators keep their software up-to-date by monitoring the Corel Support Services website (www.corel.com/support When an update is made available, these administrators download it and carry out the patching process themselves.

In this guide, location and filename of the downloaded patch.

If you prefer to have workstation users patch the software for themselves, you can set up the server image to enable the automatic detection of available patches. For details, see “Setting up the server image” on page 7.

After locating and downloading an update, you can apply it to the server image and then use the updated image to patch the installed software.

Corel will provide patches for any updates to XVL Studio Corel Edition and XVL Player, which are included with CorelDRAW Technical Suite 2019. However, the process of applying a XVL Studio Corel Edition patch to the server image may differ from the process described here. For guidance, please refer to the patch notes. For more information, see “Deploying XVL Studio Corel Edition and XVL Player” on page 33.

Patch.exe is a placeholder for the filename of the update.

\\server\path\Patch.exe is a placeholder for the

Image patching You can apply an update to the server image. You must begin by extracting

the patch files to a specified location.

Deployment Guide Stage 4: Maintaining the installations 25

To extract the update files to a specified location

To extract the update files to a specified location (instead of the default Te m p folder), use the following command-line syntax:

\server\path\Patch.exe /extract_all "C:\Extracted"

Be sure to apply all extracted update files to the server image. Applying only some of the update files may cause the installations to function incorrectly.

To apply the update files to the server image

Use a command line that includes the executable file for the update and the

/a switch:

\\server\path\Patch.exe /a

Workstation patching After updating the server image, you can deploy the update to the

workstations.

To silently update the workstations

Use the following command line:

\\server\path\Setup.exe REINSTALL=ALL REINSTALLMODE=vdm /qn

Removing the software

You can remove the software from your network. Uninstalling the software cleanly is crucial when the time comes to upgrade to a newer version.

Image removal You cannot automate the removal of a server image. Instead, you must

manually delete the image from the server.

For best results with deleting an image, make sure that the programs to be removed — and their associated files — are not currently in use on the workstations.

The only way to recover a deleted server image is to re-create it by rerunning the setup.

Don’t delete the server image if there are still workstations that use the image. Otherwise, users won’t be able to maintain and modify the installations.

Deployment Guide Stage 4: Maintaining the installations 26

Removing the software

from a server

If Remote Desktop Services (formerly known as Windows Terminal Server) are used so that users can run the applications from a server, make sure that all users are logged off before you remove the software.

Workstation removal You can remove a single installation of the software by using the Windows

Control Panel on that workstation, or you can remove multiple workstation installations by using a command line.

Removing a single installation

You can use the Windows Control Panel to remove a single installation.

To remove an installation with the Windows Control Panel

1 In the Windows Control Panel, display the list of currently installed

programs, and choose the program from the list.

2 Click Uninstall/Change.

3 Enable the Remove option.

4 If you want to remove user files (such as presets, user-created fills, and

customized files), enable the Remove user files check box.

5 Click Remove.

Repeat for Corel Graphics - Window Shell Extension and Ghostscript GPL.

Removing multiple installations

You can use a command line to remove multiple installations at a time.

/x Basic removal

You can use the the software:

\\server\path\Setup.exe /x

When you remove CorelDRAW Technical Suite 2019, XVL Studio Corel Edition and XVL Player are removed by default. If you want to silently remove CorelDRAW Technical Suite 2019 but not XVL Studio Corel Edition and XVL Player

\\server\path\Setup.exe /x /qb DO_NOT_REMOVE_XVL=1

You must use the b parameter with the q switch(/qb). Using either the n

(/qn) or r parameter (/qr) will not work.

REMOVE

and REMOVEUSERFILES

Advanced removal

If you want more control over the removal process, use the following public properties.

/x switch (or the /uninstall switch) to silently remove

, use the following syntax:

Deployment Guide Stage 4: Maintaining the installations 27

Property

What it does

REMOVE=ALL

Removes all features (except GPL Ghostscript and Windows Shell Extension)

REMOVEUSERFILES=value

REMOVE_GPL=1

REMOVE_SHELLEXT=1

Specifies whether to remove user files:

•

0 — no

•

1 — yes

Removes GPL Ghostscript

Removes Windows Shell Extension

For example, if you want to uninstall both GPL Ghostscript and Windows Shell Extension, you can use the following command:

\\server\path\Setup.exe /x REMOVE_SHELLEXT=1 REMOVE_GPL=1

You can also use a msiexec command to uninstall both GPL Ghostscript and Windows Shell Extension.

For 64-bit installations:

msiexec /i \\server\path\msis\Setup_x64.msi REMOVE=ALL CHAINER_CMD="/qb REMOVE_SHELLEXT=1 REMOVE_GPL=1"

For 32-bit installations:

msiexec /i \\server\path\msis\Setup.msi REMOVE=ALL CHAINER_CMD="/qb REMOVE_SHELLEXT=1 REMOVE_GPL=1"

Troubleshooting the software

For help troubleshooting any issues with the software, please visit the Corel® Knowledge Base (www.corel.com/knowledgebase), repository of FAQs and articles.

an online

Deployment Guide Stage 4: Maintaining the installations 28

Appendix A: Specialized deployment scenarios

If you require a more specialized deployment scenario, the supplementary topics in this appendix may be of interest to you.

In this appendix Deploying specific features. . . . . . . . . . . . . . . . . . . . . . . . . . .29

Deploying specific languages . . . . . . . . . . . . . . . . . . . . . . . . .31

Working with registry keys. . . . . . . . . . . . . . . . . . . . . . . . . . .39

Configuring content for offline availability. . . . . . . . . . . . . . .40

Customizing the setup fileset . . . . . . . . . . . . . . . . . . . . . . . . .42

Deploying customized installation settings . . . . . . . . . . . . . .44

Deploying specific features

When performing a basic or silent installation with the /q switch (see page 15), you may want to use the software features to install. You can specify a single feature:

ADDLOCAL=Feature

Or you can specify a comma-separated list of components:

ADDLOCAL property to specify which

ADDLOCAL=Feature1,Feature2

You can even specify all features:

ADDLOCAL=ALL

If you want to install nearly all features, naming them individually would be quite tedious. In this scenario, you can use the to specify the features to subtract from

ADDLOCAL=ALL REMOVE=Feature1,Feature2

For example, if you want to install all CorelDRAW Technical Suite features except CorelDRAW and Corel Capture:

ADDLOCAL=ALL REMOVE=Draw,Capture

Feature names are case-sensitive.

Specifying software features by feature name

CorelDRAW Technical Suite 2019 components are organized into the following child features of

Software component ”MainApp” child feature

Corel DESIGNER

MainApp.

REMOVE public property

ADDLOCAL=ALL:

Designer

Deployment Guide Appendix A: Specialized deployment scenarios 29

Software component ”MainApp” child feature

CorelDRAW®

Corel® PHOTO-PAINT®

Corel CAPTURE™

Draw

Capture

XVL Studio Corel Edition STUDIO

XVL Player PLAYER

Corel Font Manager™

Utilities

Import/export filters

FontManager

Utility

Filters

Some editions of the software do not include certain features listed in this section.

When you specify a parent feature (such as

MainApp) for programs other

than Corel DESIGNER, only program files are included. To add other child features, you must specify them individually. And remember: Feature names are case-sensitive.

Corel PHOTO-PAINT The Corel PHOTO-PAINT component used to include the child feature

Photozoom, a photo-enlarger plug-in. The plug-in has been updated to PhotoZoom Pro 4 and is now included with the content that is available for download.

Utilities The utilities (feature name

Utility “Utility” child feature

Duplex wizard (for two-sided print jobs)

Visual Basic® for Applications (VBA)

Specifying

Utility does not include its child features. You must

Utility) include the following child features.

DupWiz

VBAFiles

individually specify each desired utility.

Windows Shell Extension cannot be added or excluded by specifying the child feature name when using the ADDLOCAL public property. To exclude Windows Shell Extension, you must delete the following Dbm nodes from setup.xml:

• the node that references ShellExt.msi

• the node that references 32BitKey.msi or 64BitKey.msi

Corel AfterShot 3 HDR Corel AfterShot 3 HDR is available with the extra content available for

download. You can also download Corel AfterShot 3 HDR from within CorelDRAW, Corel DESIGNER, and Corel PHOTO-PAINT.

Deployment Guide Appendix A: Specialized deployment scenarios 30

Corel AfterShot 3 HDR is a professional-grade photo editing applications that lets you make easy corrections and enhancements to your RAW or JPEG photos, and apply adjustments to one or thousands of photos at once with batch processing tools. This application includes a High Dynamic Range (HDR) Merge module that can be accessed directly from the Camera RAW Lab in Corel PHOTO-PAINT 2019 to combine two or more photos of the same scene that were taken with different exposure settings. Using the HDR module, you can achieve a broader tonal range to create images that can be breathtaking.

Local Help Local Help for Corel DESIGNER, CorelDRAW, Corel PHOTO-PAINT,

Corel Font Manager, Corel Capture, and Corel Barcode is included on the CorelDRAW Technical Suite 2019 Applications ISO file, in MSI files. For more information, see “Local Help” on page 38.

User guides The Corel DESIGNER® 2019 User Guide, CorelDRAW® 2019 User

Guide

and the Corel® PHOTO-PAINT® 2019 User Guide contain comprehensive information about product features and tools. They are PDF versions of the Help that are available online and can be accessed from the Help Home pages (Help  Product Help).

SharePoint Integration Corel DESIGNER and CorelDRAW give users direct access to your

organization’s document management system (DMS), such as Microsoft SharePoint, to quickly retrieve and store documents from within Corel DESIGNER and CorelDRAW. To use the organization’s DMS with Corel DESIGNER and CorelDRAW, users must log in to SharePoint by using their SharePoint credentials, not their Corel.com account credentials.

When users are working offline, they can still use the document management feature provided they have intranet access and the SharePoint server is installed on a local network.

Deploying specific languages

When performing a basic or silent installation with the /q switch (see page 15), you may want to use the software languages to support. You can specify a single language:

ADDLOCAL=LanguageCode

Or you can specify a comma-separated list of languages:

ADDLOCAL=Feature1,LanguageCode1,LanguageCode2

Using language codes, you can specify language modules.

Deployment Guide Appendix A: Specialized deployment scenarios 31

ADDLOCAL property to specify which

Language codes are case-sensitive.

Specifying UI modules by language code

A language module includes the software UI. By installing multiple language modules, you can enable dynamic language switching — the ability to change the language of the software UI.

XVL Studio Corel Edition and XVL Player English (

EN), French (FR), and Japanese (JP).

support only German (DE),

The following table lists the available language modules for the software, along with their corresponding language codes.

Language module Language code

Brazilian Portuguese

Chinese (Simplified)

Chinese (Traditional)

Czech

Dutch

English

French

German

Italian

Japanese

Polish

Russian

Spanish

Tu r k i s h

By default, writing tools are automatically installed for all available languages.

Deployment Guide Appendix A: Specialized deployment scenarios 32

Deploying XVL Studio Corel Edition and XVL Player

A typical server image of CorelDRAW Technical Suite 2019 includes the files required to deploy workstations.

Updating Corel Corporation will provide patches for any updates to

XVL Studio Corel Edition CorelDRAW Technical Suite 2019. Any such patches will update the server image of CorelDRAW Technical Suite 2019 with the latest files for XVL Studio Corel Edition be deployed to the workstations by manually repairing the installed software.

XVL Studio Corel Edition

and

XVL

Player, which are included with

and

XVL

Player. The updated software can then

and

XVL

Player to the

Removing

XVL Studio Corel Edition XVL Studio Corel Edition entry in the Add or remove programs dialog box of the Windows Control Panel.

XVL Player

Pro (Ver. 9 or later)

the Windows Control Panel.

If you want to silently remove CorelDRAW Technical Suite 2019 but not XVL Studio Corel Edition command line:

Setup.exe /x /qb DO_NOT_REMOVE_XVL=1

can be removed by using the

Understanding workspaces

The software installs a selection of workspaces for use in Corel DESIGNER, CorelDRAW, and Corel PHOTO-PAINT.

Installed Corel DESIGNER

workspaces

The default workspace of Corel DESIGNER 2019 is designed to provide a more intuitive placement of tools and controls. The default settings are included in DrawUi.xml, which is located in the CorelDRAW Technical Suite 2019\Designer\UIConfig folder. In addition, the following workspaces for Corel DESIGNER are installed in CorelDRAW Technical Suite 2019\Designer\Workspace:

• lite.cdws — ideal for new users who are getting started

• Micrografx Designer.cdws — ideal for users who prefer the look and

feel of Micrografx Designer 9

• Default(TM).cdws — has a streamlined user interface (UI) that

displays only the tools and commands that users are most likely to use when using a tablet

can be removed by using the

XVL Player / Lattice3D Player

entry in the Add or remove programs dialog box of

and

XVL

Player, you must use the following

Deployment Guide Appendix A: Specialized deployment scenarios 33

• Technical Illustration.cdws — optimized for users who create

technical manuals and catalogs of interactive parts

• Diagramming.cdws — features tools and a layout that are essential for

creating diagrams

• CorelDRAW X7.cdws — designed to help users transition easily from

CorelDRAW to Corel DESIGNER

• Adobe Illustrator.cdws — simulates the Adobe Illustrator workspace

by positioning the Corel DESIGNER features where you would find the equivalent feature in Adobe Illustrator

Installed CorelDRAW

workspaces

Installed Corel PHOTO-

PAI NT workspaces

The default workspace of CorelDRAW 2019 is designed to provide a more intuitive placement of tools and controls. The default settings are included in DrawUI.xml, which is located in the CorelDRAW Technical Suite 2019\Draw\UIConfig folder.

In addition, the following workspaces for CorelDRAW are installed in CorelDRAW Technical Suite 2019\Draw\Workspace:

• illustration.cdws — designed for creating book cover designs,

magazine adds, storyboards, and other types of illustration

• illustrator.cdws — designed for Adobe® Illustrator® users

• lite.cdws — ideal for new users who are getting started

• pagelayout.cdws — optimized for users who are creating layouts for

business cards, branding materials, product packaging, or multipage documents

• Default(TM).cdws — has a streamlined user interface (UI) that

displays only the tools and commands that users are most likely to use when using a tablet

The default workspace of Corel PHOTO-PAINT 2019 is designed to provide a more intuitive placement of tools and controls. The default settings are included in PHOTO-PAINTUI.xml, which is located in the CorelDRAW Technical Suite 2019\PHOTO-PAINT\UIConfig folder. In addition, the following workspaces for Corel PHOTO-PAINT are installed in the CorelDRAW Technical Suite 2019\PHOTO- PAINT\Workspace folder:

• lite.cdws — ideal for new users who are getting started

• photoshop.cdws — designed for Adobe® Photoshop® users

• Default(TM).cdws — has a streamlined user interface (UI) that

displays only the tools and commands that users are most likely to use when using a tablet

Custom workspaces You can customize all available workspaces by modifying the CDWS

(CorelDRAW Workspace) files. You can also create a custom workspace from within Corel DESIGNER, CorelDRAW or Corel PHOTO-PAINT, and you can customize the default workspace.

Deployment Guide Appendix A: Specialized deployment scenarios 34

With CorelDRAW Technical Suite 2019, you can deploy customized workspaces and any new workspaces you create with the installation. You can also deploy custom default workspaces.

To deploy custom workspaces with the installation

1 Create the server image. For more information, see “Stage 2: Creating

the server image” on page 6.

2 Create the custom workspaces you want to add to the server image.

To create a custom workspace, you must start Corel DESIGNER as a local user. For information about how to create and export workspaces, see the Help topic “Creating workspaces” (Help > Product Help).

3 Install CorelDRAW Te c h n i c a l Suite 2019 on a workstation, and log in

as a local user.

4 Copy the custom workspace files to the corresponding Wo r ks p a ce

folders in the server image, making sure not to delete any existing workspace files.

For 32-bit server images

msis\Program files\Corel\CorelDRAW Technical Suite 2019\Designer\Workspace

MSIs\Program files\Corel\CorelDRAW Technical Suite 2019\Draw\Workspace

MSIs\Program files\Corel\CorelDRAW Technical Suite 2019\PHOTO-PAINT\Workspace

For 64-bit server images

msis\Program files 64\Corel\CorelDRAW Technical Suite 2019\Designer\Workspace

MSIs\Program files 64\Corel\CorelDRAW Technical Suite 2019\Draw\Workspace

MSIs\Program files 64\Corel\CorelDRAW Technical Suite 2019\PHOTO-PAINT\Workspace

5 Deploy the server image. For more information, see “Stage 3: Installing

the software” on page 12.

Users can access the custom workspaces after they start the applications.

To deploy custom default workspaces with the installation

The default workspace files of Corel DESIGNER, CorelDRAW and Corel PHOTO-PAINT _default.cdws are created when the applications are launched for the first time. You can customize the default workspaces, and then you can deploy them similarly to the way you can deploy other custom workspaces.

1 Install CorelDRAW Te c h n i c a l Suite 2019 on a workstation, and log in

as a local user.

Deployment Guide Appendix A: Specialized deployment scenarios 35

2 Start Corel DESIGNER, CorelDRAW or Corel PHOTO-PAINT, and

customize the workspace.

3 Copy the _default.cdws file from the respective user folder.

C:\Users\[User Name]\AppData\Roaming\Corel\CorelDRAW Technical Suite 2019\Designer\Workspace

C:\Users\[User Name]\AppData\Roaming\Corel\CorelDRAW Technical Suite 2019\Draw\Workspace

C:\Users\[User Name]\AppData\Roaming\Corel\CorelDRAW Technical Suite 2019\PHOTO-PAINT\Workspace

4 Follow steps 3 and 4 from “To deploy custom workspaces with the

installation” on page 35.

If you want to add custom workspaces after the software has been deployed, you must repair each workstation installation using the following command line:

<AdminImagePath>\Setup.exe REINSTALL=ALL REINSTALLMODE=oums /qn

To access the new custom workspaces, users must restart the applications while holding down F8.

Working with MSI files

Stored in the Setup folder on the installation disc, the main Microsoft Windows Installer (MSI) file for the setup — \x86\msis\Setup.msi (for 32bit installations) or \x64\msis\Setup_x64.msi (for 64-bit installations) — contains a database of main features, registry keys, folders, and shortcuts for the software.

The server image contains a copy of the main setup MSI file — the MSI tables within which you can modify for deployment to the workstations.

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.

Setup files Besides Setup.msi, the setup requires and additional MSI files to carry out

the installation:

• x86\ICA.msi or x64\ICA_x64.msi

Language modules The setup requires at least one language module, MSI files for which are

stored at x86\msis (32-bit) or x64\msis (64-bit) on the installation disc. XVL Studio Corel Edition and XVL Studio 3D CAD Corel Edition support only German (DE), English (EN), French (FR) and Japanese (JP). However, some versions of CorelDRAW Technical Suite 2019 may include additional

Deployment Guide Appendix A: Specialized deployment scenarios 36

language modules for the remaining components (CorelDRAW, Corel PHOTO-PAINT, and Corel CONNECT). The following table lists all language modules that the software may contain.

Language module MSI file

Brazilian Portuguese BR.msi (32-bit) or BR_x64.msi (64-bit)

Chinese (Simplified) CS.msi (32-bit) or CS_x64.msi (64-bit)

Chinese (Traditional) CT.msi (32-bit) or CT_x64.msi (64-bit)

Czech CZ.msi (32-bit) or CZ_x64.msi (64-bit)

Dutch NL.msi (32-bit) or NL_x64.msi (64-bit)

English EN_Des.msi and EN_Des_x64.msi

French FR_Des.msi and FR_Des_x64.msi

German DE_Des.msi and DE_Des_x64.msi

Italian IT.msi (32-bit) or IT_x64.msi (64-bit)

Japanese JP.msi (32-bit) or JP_x64.msi (64-bit)

Polish PL.msi (32-bit) or PL_x64.msi (64-bit)

Russian RU.msi (32-bit) or RU_x64.msi (64-bit)

Spanish ES.msi (32-bit) or ES_x64.msi (64-bit)

Tu r k i s h TR.msi (32-bit) or TR_x64.msi (64-bit)

Programs To install the programs included with the software, the setup uses the

following MSI files at X:\x86\MSIs (32-bit) or X:\x64\MSIs (64-bit) on the installation disc.

Program MSI file

Corel CAPTURE Capture.msi (32-bit), or 

Capture_x64.msi (64-bit)

Corel DESIGNER Designer.msi (32-bit), or 

Designer_x64.msi (64-bit)

Corel Font Manager FontManager.msi (32-bit), or 

FontManager_x64.msi (64-bit)

CorelDRAW Draw.msi (32-bit), or 

Draw_x64.msi (64-bit)

Corel PHOTO-PAINT PHOTO-PAINT.msi (32-bit), or 

PHOTO-PAINT_x64.msi (64-bit)

Deployment Guide Appendix A: Specialized deployment scenarios 37

Features To install the various components of the software, the setup uses additional

MSI files stored at Setup\x86\msis (32-bit) or Setup\x64\msis (64-bit) on the CorelDRAW Technical Suite 2019 DVD, the software ISO file, or in the MSIs folder of the server image. These files include the following.

Feature MSI file

Ghostscript general public license,

Ghostscript.msi

for EPS and PostScript® import

Microsoft Visual Basic for Applications (VBA)

Microsoft Visual Studio Tools for Applications (VSTA)

\msis\vba\vba71.msi (for both 32bit and 64-bit)

\msis\vsta_setup.exe (for both 32bit and 64-bit)

Windows Shell Extension ShellExt.msi and 64BitKey.msi

(32-bit) or ShellExt.msi and 32BitKey.msi (64-bit)

Local Help To install local Help for Corel DESIGNER, CorelDRAW, Corel PHOTO-

PAINT, Corel Font Manager, Corel Capture, and Corel Barcode, the setup uses the following the following MSI files stored at Setup\x86\msis (32bit) or Setup\x64\msis (64-bit) on the CorelDRAW Technical Suite 2019 DVD, the software ISO file, or in the MSIs folder of the server image:

• documentation.msi and documentation2.msi — for 32-bit

installations

• documentation_x64.msi and documentation2_x64.msi — for 64-bit

installations

Local Help is installed to the following folders on the workstations, where XX stands for the language of the Help (for example, EN for English, DE for German, FR for French):

(64-bit installations) X:\Program Files\Corel\CorelDRAW Technical

Suite 2019\Languages\XX\Help

(32-bit installations) X:\Program Files(x86)\Corel\CorelDRAW Technical Suite 2019\Languages\XX\Help

In addition, a Help folder is installed that contains most of the images referenced in the local Help. This folder is installed to:

(64-bit installations) X:\Program Files\Corel\CorelDRAW Technical

Suite 2019

(32-bit installations) X:\Program Files(x86)\Corel\\CorelDRAW Technical Suite 2019

Deployment Guide Appendix A: Specialized deployment scenarios 38

Working with registry keys

After creating the server image, you may want to edit its registry keys for deployment to the workstations. By doing so, you can avoid having to manually configure the registry keys of each individual workstation installation of the software.

Setting up dynamic language switching

Dynamic language switching allows the language of the user interface to be changed, both during and after installation. This feature requires the installation of multiple language modules for the software — one for each desired user-interface language (see page 32). The selection of languages you can implement depends on the license you have purchased.

Two sets of registry settings are required for dynamic language switching:

• workstation settings

• current user settings

Workstation settings Workstation settings affect all users. The registry setting for each

workstation is as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel DESIGNER\

21.0\ Languages

Inside this key are language keys — three-letter codes that represent the available languages. These language keys are put in place by the setup, so no intervention is required. Shown here (for reference only) are the threeletter codes for the available languages for the remaining components.

Language Code

Brazilian Portuguese PTB

Chinese (Simplified) CHS

Chinese (Traditional) CHT

Czech CSY

Dutch NLD

English ENU

French FRA

German DEU

Italian ITA

Deployment Guide Appendix A: Specialized deployment scenarios 39

Language Code

Japanese JPN

Polish PLK

Russian RUS

Spanish ESN

Tu r k i s h TRK

Under each language key are the following registry settings:

• DirName — specifies the name of the folder for the language-specific

files, relative to InstallationPath\Languages

• UIName — specifies the name to show in the startup dialog box and on

the To o l s  Options  Global page

Current user settings The registry setting for each current user is as follows:

HKEY_CURRENT_USER\Software\Corel\Corel DESIGNER\21.0

The UILang setting is not initialized by the setup because the setup cannot determine which user will run the applications. After the user has run the application once, this setting changes to the three-letter code that corresponds to the user-specified language key at the following location:



Configuring content for offline availability

The Proof of Entitlement Certificate email will contain a URL linking to a shared drive containing the extra content, which you can download. After you unzip the extra content to the location you want, you can create aliases to the various content folders from within Corel DESIGNER or CorelDRAW. When you create aliases, a database file is created. To make it easier for users to find and search the extra content, you must deploy this database file to the workstations.

The extracted content is 13.7 GB.

Internet access is required to access the download location.

To unzip the content

1 On the server that you are going to make available to all workstations,

create a main content folder and name it Corel Content.

2 Follow the content URL provided on your Proof of Entitlement

Certificate email. There are five main archive files: Applications, Fills,

Deployment Guide Appendix A: Specialized deployment scenarios 40

Fonts, Images, and Templates. The Images folder includes clipart and photos that are organized by theme in separate folders.

3 Extract the archive files into separate folders using a decompression tool

to the folder created in step 1.

When all zip files have been downloaded and decompressed, you should see the following folders:

• Applications

• Fills

•Fonts

•Images

• Templates

Once the content is available on the server, users can create aliases to the folders so that they can access the content from within the CONNECT Content docker, the Fill and Transparency pickers, and the New from Template dialog box in Corel DESIGNER or CorelDRAW. However, we recommend that you create the aliases yourself so that it is easier for users to access extra content.

To create aliases to the subfolders in the Images folder

1 Do any of the following:

• In Corel DESIGNER, click Window  CONNECT Content.

•In CorelDRAW, click Window  Dockers  CONNECT Content.

2 In the CONNECT Content docker, open the Choose content source

list box, and click Add new.

3 Click Create alias.

4 In the Locate content library dialog box, browse to a subfolder in the

Images folder located on the server.

5 Click Select Folder.

Repeat steps 2 to 5 to create aliases to other subfolders in the Images folder.

You can create an alias to the Images folder as well. Note, however, that it takes a long time to generate the thumbnails of all images. That’s why we recommend that you create aliases to the subfolders.

To create an alias to the Fills folder

1 In Corel DESIGNER or CorelDRAW, open the Fill picker or the

Transparency picker in the Fill or Transparency section of the Properties docker (Corel DESIGNER: Window  Properties; CorelDRAW: Window  Dockers  Properties).

2 In the Locate fills library dialog box, open the Choose content source

list box, and click Add new.

Deployment Guide Appendix A: Specialized deployment scenarios 41

3 Click Create alias.

4 In the Locate fills library dialog box, browse to the Fills folder located

on the server.

5 Click Select folder.

Repeat steps 2 to 5 to create aliases to the subfolders in the Fills folder.

To create an alias to the Templates folder

1 In Corel DESIGNER or CorelDRAW, click File  New from Template.

2 In the New from Template dialog box, open the Choose content

source list box, and click Add new.

3 Click Create alias.

4 In the Locate template library dialog box, browse to Te m p l a t e s folder,

located on the server.

5 Click Select folder.

Repeat steps 2 to 5 to create aliases to the subfolders in the Te m p l a t e s folder.

To share content (fills, templates, and images) created by your company with the workstations, you can use the same method of creating aliases to network folders from within Corel DESIGNER or CorelDRAW.

Deploy the content database file

When you create aliases, a simple database file is generated. This file is called UserCollections.db and resides in one of the following locations:

• (Windows) AppData\Roaming\Corel\Databases\Assets V1.0

After you deploy the content database file to the workstations, users will be able to search and use content from the alias folders.

Extensions

Extensions, which were available for download in previous versions, have been integrated as regular features in the product. They no longer need to be downloaded and extracted.

Customizing the setup fileset

The main configuration file Setup.xml, located in the x86 or x64 folder, lists all features included in the setup.

When you create a server image, a copy of the Setup.xml file is included. If you want to customize the setup fileset on the server image, you must edit the Setup.xml file to reflect your desired changes.

Deployment Guide Appendix A: Specialized deployment scenarios 42

Understanding Setup.xml

The Setup.xml file contains four main types of nodes. With an understanding of these four nodes, you can modify the Setup.xml file to create a customized server image.

<Msi/> nodes Each

<Msi/> node specifies a main setup file, such an executable (EXE)

file, a self-extracting ZIP file, or an MSI file that bundles (or “chains”) other MSI files.

For example, you can exclude Ghostscript from the installation by making the following modification.

<Dbm/> nodes Each <Dbm/> node specifies a component of a <Msi/> node — typically,

an MSI file. A associated product code, and

<Dbm/> node has the following structure, where GUID is the

MSI is the path and filename of the MSI file:

Some <Dbm/> nodes also require a condition.

If you want to apply an MST file to the specified MSI file, you can use the following syntax (in cases where the MST and MSI files are in the same folder,

MST is the filename of the MST file; in cases where the MST and

MSI files are in separate folders,

MST is the path and filename of the MST

file):

<Feature/> nodes Each <Feature/> node specifies a feature that is associated with an MSI

file. A

<Feature/> node has the following format, where name is the

name of the MSI file and

feature is the name of the associated feature:

Some <Feature/> nodes have subnodes.

For a list of the available features, see page 29.

<Property/> nodes Each

<Property/> node specifies a property. A <Property/> node has

the following structure, where property and

Deployment Guide Appendix A: Specialized deployment scenarios 43

value is its value:

property is the name of the public

For a list of available public properties, see page 16.

Creating a server image with a customized fileset

You can use Setup.xml to create a server image with a customized fileset.

To create a server image with a customized fileset

1 Copy the server image to a new location.

2 Add any desired language-module MSI files to the server image.

3 Edit Setup.xml to reflect the additions you’ve made to the fileset:

•Add an

•Add a

•Add the following

module MSI file, where

4 Edit Setup.xml to reflect the removals you’ve made from the fileset:

• Remove the corresponding

removed MSI file.

• Adjust any corresponding

value.

For example, let’s say that you’re creating a single-language setup from a multi-language setup. To record the fileset changes in the Setup.xml file, you must remove the corresponding nodes for each removed language module. Next, you must set each

<Property/> node for Include.$$ to a value of 0, where $$ is a

removed language module. The

ShowApplicationLanguageSelector is automatically set to a

value of

<Msi/> node for each new setup file.

<Dbm/> node for each new language-module MSI file.

<Property/> node for each new language-

$$ is the language:

<Msi/> node for each removed setup file. <Dbm/> node for each removed MSI file. <Feature/> node and subnode for each

<Property/> nodes by changing their

<Property/> node for

Deploying customized installation settings

To modify the settings used to install the software on the workstations, you can use the Persist.xml file stored at the root of the server image.

Each entry in Persist.xml corresponds to a public property for the software (see page 16). The syntax of each entry is as follows:

Deployment Guide Appendix A: Specialized deployment scenarios 44

By modifying the value of an existing entry in Persist.xml — or by adding a new entry — you can customize the installation settings deployed from that server image. This deployment method offers an excellent alternative to creating a different server image or customizing a command line.

You must modify Persist.xml before installing the software on the workstations for the changes to take effect.

Example 1 You can use the following Persist.xml entry to specify that access to

internet features are enabled:

The administrator must either be signed in or specify a value for the PROFILEID.

Example 2 You can use the following Persist.xml entry to specify that automatic

software updates are enabled:

By changing the value of this entry from "1" to "2" (and saving this change to Persist.xml), you can disable automatic updates for the workstation installations.

By changing the value of this entry from

"1" to "0" (and saving this

change to Persist.xml), you can check for updates and let the user choose when to install the update.

ALLOW_PRODUCTUPDATES must be set to "2" if the administrator does

not sign in or specify a value for the PROFILEID, and uses the following Persist.xml entry:

For more information, see “ALLOW_INTERNETFEATURES” on page 16, “ALLOW_PRODUCTUPDATES” on page 17, and “PROFILEID” on page 18.

Example 3 You can use the following Persist.xml entry to specify the PROFILEID

and add account credentials to the server image:

Specifying a value for the PROFILEID will ensure that all workstations are automatically signed in to the account after installation. For more information, see “PROFILEID” on page 18.

Example 4 You can use the following Persist.xml entry to allow users to take

advantage of Welcome screen features:

Deployment Guide Appendix A: Specialized deployment scenarios 45

Note that the Welcome screen cannot be used without enabling internet features and providing account credentials. For information about enabling internet features, see “Example 1” on page 45. For information about adding account credentials, see “Example 3” on page 45.

Example 5 You can use the following Persist.xml entry to specify the serial number

for the installation:

By changing the "SN"value, you can specify a different serial number for the workstation installations.

For more information, see “SERIALNUMBER” on page 19.

Deployment Guide Appendix A: Specialized deployment scenarios 46

Appendix B: Authenticating the software

If you signed in by providing account credentials when creating the server image, all users are automatically signed in and have access to internet based features. This is made possible by a software authentication mechanism. In this appendix, you will learn about what information is exchanged during software authentication and what is required for successful authentication.

In this appendix Exchanging information during authentication . . . . . . . . . . .47

Requirements for authentication . . . . . . . . . . . . . . . . . . . . . .47

Exchanging information during authentication

Each time a CorelDRAW Technical Suite application is launched, the following information is sent to the Corel server that authenticates the software:

• Information that identifies the corel.com account, which can be either the email address and password or the PROFILEID. For more information about PROFILEID, see “PROFILEID” on page 18.

• Information that identifies the workstation on which the application is launched such as computer and hardware signature and name.

• Product identifiers that specify the product family (such as CDGS for CorelDRAW Graphics Suite or CDTS for CorelDRAW Technical Suite), product version, language as well as the product serial number.

• Information about the license state.

The Corel server returns feature identifiers that enable online features such as QR codes.

Requirements for authentication

For successful software authentication in a corporate network, you must allow access to https://iws.corel.com, which is the address of the Corel authentication server. The port number is 443, with the following specific endpoint:

• https://iws.corel.com/ipmws/services/Subscription

To allow access to the Corel authentication server, you may need to modify the security settings in your proxy or firewall software.

Deployment Guide Appendix B: Authenticating the software 47

Index

account credentials . . . . . . . . . . . . . . . . . . . . . . . . . . 6

authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

command lines

public properties . . . . . . . . . . . . . . . . . . . . . . . . . . 16

running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

deployment

preparing for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

specialized scenarios . . . . . . . . . . . . . . . . . . . . . . . . 29

desktop shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

dynamic language switching . . . . . . . . . . . . . . . . . 39

features, deploying . . . . . . . . . . . . . . . . . . . . . . . . . 29

fileset customization . . . . . . . . . . . . . . . . . . . . . . . . 42

installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

installation settings . . . . . . . . . . . . . . . . . . . . . . . . . 44

installing software . . . . . . . . . . . . . . . . . . . . . . . . . . 12

internet features, specifying settings . . . . . . . . . . 16

languages, deploying . . . . . . . . . . . . . . . . . . . . . . . 31

maintaining software . . . . . . . . . . . . . . . . . . . . . . . 22

modifying software . . . . . . . . . . . . . . . . . . . . . . . . . 24

MSI files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

networks

requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

setting up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

patching software . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Persist.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

product updates, specifying settings . . . . . . . . . .17

public properties . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

pull installations . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

push installations . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Readme file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

reboots, handling . . . . . . . . . . . . . . . . . . . . . . . . . . .19

registry keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

removing software . . . . . . . . . . . . . . . . . . . . . . . . . .26

repairing software . . . . . . . . . . . . . . . . . . . . . . . . . .22

SCCM support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

serial number

acquiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

server images

basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

customized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

fileset, customizing . . . . . . . . . . . . . . . . . . . . . . . . .44

multiple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

servers

setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

software requirements . . . . . . . . . . . . . . . . . . . . . . . .2

setup

logging events . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

suppressing UI . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Setup.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

shortcuts, desktop . . . . . . . . . . . . . . . . . . . . . . . . . .17

silent installations . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Deployment Guide Index 48

SMS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

software requirements . . . . . . . . . . . . . . . . . . . . . . . 2

switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

troubleshooting software . . . . . . . . . . . . . . . . . . . . 28

UI language modules . . . . . . . . . . . . . . . . . . . . . . . . 32

uninstalling software . . . . . . . . . . . . . . . . . . . . . . . . 26

updating software . . . . . . . . . . . . . . . . . . . . . . . . . . 25

user name, inputting . . . . . . . . . . . . . . . . . . . . . . . . 20

videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

workspaces, customizing . . . . . . . . . . . . . . . . . . . . 33

workstations

converting offline to online . . . . . . . . . . . . . . . . . . . 18

setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

software requirements . . . . . . . . . . . . . . . . . . . . . . . 3

XVL Studio Corel Edition, deploying . . . . . . . . . . . 33

Deployment Guide Index 49

CorelDRAW® Technical Suite 2019 Deployment Guide

Product specifications, pricing, packaging, technical support and information (“specifications”) refer to the retail English version only. The specifications for all other versions (including other language versions) may vary.

Information is provided by Corel on an “as is” basis, without any other warranties or conditions, express or implied, including, but not limited to, warranties of merchantable quality, satisfactory quality, merchantability or fitness for a particular purpose, or those arising by law, statute, usage of trade, course of dealing or otherwise. The entire risk as to the results of the information provided or its use is assumed by you. Corel shall have no liability to you or any other person or entity for any indirect, incidental, special, or consequential damages whatsoever, including, but not limited to, loss of revenue or profit, lost or damaged data or other commercial or economic loss, even if Corel has been advised of the possibility of such damages, or they are foreseeable. Corel is also not liable for any claims made by any third party. Corel's maximum aggregate liability to you shall not exceed the costs paid by you to purchase the materials. Some states/countries do not allow exclusions or limitations of liability for consequential or incidental damages, so the above limitations may not apply to you.

Corel, the Corel logo, the Corel balloon logo, CorelDRAW, the CorelDRAW balloon logo, Corel Font Manager, CAPTURE, LiveSketch, and PHOTO-PAINT are trademarks or registered trademarks of Corel Corporation and/or its subsidiaries in Canada, the U.S. and/or other countries. Other product, font and company names and logos may be trademarks or registered trademarks of their respective companies.

Patents: www.corel.com/patent

111069

Corel Corel Draw Technical Suite - 2019 Deployment Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Stage 1: Preparing for deployment

Getting to know your network

Getting to know the software

Setting up your network accordingly

Stage 2: Creating the server image

Before creating a server image

Creating a basic image

Initializing the setup

Setting up the server image

Finalizing the server image

Creating a customized image

Creating multiple images

Stage 3: Installing the software

Pulling the software

Preparing for pull installation

Carrying out a pull installation

Pushing the software

Specifying the setup file

Using switches

Using public properties

Running your command line

Using product privileges

Stage 4: Maintaining the installations

Repairing the software

Repairing a single installation

Repairing multiple installations

Modifying the software

Modifying a single installation

Modifying multiple installations

Updating the software

Locating updates

Applying updates

Removing the software

Removing a single installation

Removing multiple installations

Troubleshooting the software

Appendix A: Specialized deployment scenarios

Deploying specific features

Specifying software features by feature name

Deploying specific languages

Specifying UI modules by language code

Deploying XVL Studio Corel Edition and XVL Player

Understanding workspaces

Working with MSI files

Working with registry keys

Setting up dynamic language switching

Configuring content for offline availability

Customizing the setup fileset

Understanding Setup.xml

Creating a server image with a customized fileset

Deploying customized installation settings

Appendix B: Authenticating the software

Exchanging information during authentication

Requirements for authentication

Index