Corel Corel Designer Technical Suite - 2017 Deployment Guide

Download

Page 1

DEPLOYMENT GUIDE

Page 2

Introduction

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

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

Conventions Please note the following conventions used in this guide.

CorelDRAW® Technical Suite 2017 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 Corel® Beginner’s Guide to Network Deployment.

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

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

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

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

Wherever you see this You’ll find

italicized text A placeholder for user-specified

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 Co

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

rel® Support Services website:

www.corel.com/support

Microsoft® website



Deployment Guide Introduction 1

Page 3

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

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 2017 on a

server that meets the following requirements:

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

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

Deployment Guide Stage 1: Preparing for deployment 2

Page 4

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 2017 DVD or the ISO file provided by Corel to install the software on the server.

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

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

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

meet the following requirements:

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

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

• 2 GB of RAM

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

• Multi-touch screen, mouse or tablet

• 1280 x 720 screen resolution at 100% (96 dpi), 1920 x 1080 at 150%, and 2560 x 1440 at 200%

• DVD drive

• Microsoft® Internet Explorer® 11 (with the latest service pack) or later (Microsoft does not offer support and security updates for Internet Explorer prior to version 11)

• Microsoft® .NET Framework 4.6

• So users can view videos embedded in Help files, Adobe Flash Player must be installed on their system or the Adobe Flash Player plug-in must be enabled in their browser.

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

Lattice3D Studio Corel Edition is included and installed with CorelDRAW Technical Suite 2017. The Lattice3D Studio CAD AddOn 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 2017 Applications (DVD or ISO file)

available for download.

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

• Mount the ISO file as a virtual drive.

Deployment Guide Stage 1: Preparing for deployment 3

Page 5

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

Optionally, other content is available for download from a shared drive in the following folders:

• Extra Application — PhotoZoom Pro 4 (EXE file)

• Videos — videos that are available online can be downloaded and accessed through the product for offline workflows

• Extensions — extensions, such as Border and Grommet, Calendar Wizard, Convert All To Curves, Color Chart Creator, File Converter, and Prep and Stretch, that add features to the applications

• Content — clipart, fills, fonts, image lists, interactive frames, objects, photo frames, photos, templates

• eBooks — Corel DESIGNER 2017 User Guide, CorelDRAW 2017 User Guide and Corel PHOTO-PAINT 2017 User Guide published to the EPUB and MOBI file formats

For more information, see “Server setup” on page 4 and “Extensions” on page 41.

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

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.

Deployment Guide Stage 1: Preparing for deployment 4

Page 6

If you want to make extra content (such as clipart and videos) and extensions 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 18.2 GB.

Workstation setup Do the following:

• Make sure that the workstations have Microsoft .NET Framework

4.6 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

Page 7

Stage 2: Creating the server image

Highlights:

Initializing the setup . . . . .7

Setting up the server image7 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 administrator 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 core the email address you used to create account helps you 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.

l.com account, validating the email that is sent to

Deployment Guide Stage 2: Creating the server image 6

Page 8

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

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

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

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

server 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 userinterface field when introducing a — 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>

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.

A few notes on this process will suffice.

/q switch into your command line

\ ).

Deployment Guide Stage 2: Creating the server image 7

Page 9

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 assigned to the corel.com account used when creating the server image. For more information, see “Before

password, are required to access internet-based features, product updates, and the Content Exchange. Ensure your corel.com account password does not contain special characters.

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.

Content location If you have added extra content

to a network shared folder, type the full path to the content folder, or click Change to browse to the folder.

Product Updates (updated in

CorelDRAW Technical Suite

2017)

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 your email address and password.

Deployment Guide Stage 2: Creating the server image 8

Page 10

UI component Notes

Internet features This option allows workstations

to access Internet-based features such as the Content Exchange, and QR code. You can access this option only after entering your email address and password.

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 userinterface 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 the Content Exchange and QR codes.

• 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

Deployment Guide Stage 2: Creating the server image 9

Page 11

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 Internet-based features are disabled, the paths to the server image and extra content are 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> NETWORKINSTALLDIR=<PathToExtraContent> /L "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 43).

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

Page 12

Creating a customized image

If you require a more customized server image than offered by command-line 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 43.

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

workstations. See page 45.

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

Page 13

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

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

Page 14

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 2017 installation dialog boxes. You can modify this setting in Microsoft Internet Explorer so that text will appear by

3 Click Tools  Internet Options.

4 Click the Security tab.

5 Click the Custom level button.

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

scripting.

7 Click OK, and click OK again.

8 Close Microsoft Internet Explorer.

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

Deployment Guide Stage 3: Installing the software 13

Page 15

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

Deployment Guide Stage 3: Installing the software 14

Page 16

Parameter What it logs

Error messages for insufficient hard-disk space during server installation

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 (Temp ) 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

/qn, you can use /quiet.

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

/qb, you can use /passive.

NOTE: Alternatively to

Basic UI: only a progress bar. The user cannot cancel the 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

Page 17

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.

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"

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

The

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

Page 18

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.

Deployment Guide Stage 3: Installing the software 17

Page 19

For best results, do not end the path with a backslash ( \ ).

NETWORKINSTALLDIR Pointing installations to the extra content

You can place extra content and videos at a shared location on the server so that users can access them. See “Server setup” on page 4.

To point the installations to this location, use the following property:

NETWORKINSTALLDIR="path"

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

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.

PROFILEID value is a combination of letters and numbers. To

The access it, go to Your Account page on corel.com and click Product

Status in You r P rodu ct s 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

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

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

ProfileGuid=4797935F031C2DD2E0530D02140A2BE4

In addition, the ALLOW_INTERNETFEATURES property changes from 0 to

1 in the following hive directory: [HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel

DESIGNER\19.0]

Deployment Guide Stage 3: Installing the software 18

Page 20

This property cannot be combined with any other properties.

Do not manually edit the key. Use the the key.

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

REBOOT Handling reboots

REBOOT property is used with one of the following values to

The specify how the installation process handles any required reboots.

Value What it does

Force

(or F)

Suppress

(or S)

/s command to properly modify

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

/forcerestart switch.

REBOOT=Force,

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

REBOOT=Suppress, 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:.

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.

Deployment Guide Stage 3: Installing the software 19

Page 21

For best results, do not end the path with a backslash ( \ ).

Usernames cannot exceed 60 characters.

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.

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

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

You can create a package from scratch — or you can create one from the existing SMS files included with CorelDRAW Technical Suite 2017 (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 2017 and must therefore be used at your discretion.

Deployment Guide Stage 3: Installing the software 20

Page 22

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 the Content Exchange.

Users are automatically signed in to the corel.com account associated with your 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.

For purchases that include more than 10 licenses, you can choose to remove specific workstations from Your Account page on corel.com. To sign in wo provide account credentials.

rkstations that you previously signed out, you must

Deployment Guide Stage 3: Installing the software 21

Page 23

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

REINSTALLMODE properties instead of /f.

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

\\server\path\Setup.exe /f

REINSTALL and

Deployment Guide Stage 4: Maintaining the installations 22

Page 24

The /f switch has the following parameters.

Parameter What it does

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

Reinstalls all existing shortcuts

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

The default parameters for

/f are oums.

REINSTALL

and REINSTALLMODE

Advanced repair

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

REINSTALL and REINSTALLMODE public properties together.

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

Deployment Guide Stage 4: Maintaining the installations 23

Page 25

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

Page 26

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.

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, update. 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 pa

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.

Patch.exe is a placeholder for the filename of the

tching process themselves.

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

Corel will provide patches for any updates to Lattice3D Studio Corel Edition and Lattice3D Player, which are included with CorelDRAW Technical Suite 2017. However, the process of applying a Lattice3D 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 Lattice3D Studio Corel Edition and Lattice3D Player” on page 33.

Image patching You can apply an update to the server image. Optionally, you can begin

by extracting the patch files to a specified location.

Deployment Guide Stage 4: Maintaining the installations 25

Page 27

To extract the update files to a specified location

To extract the update files to a specified location (instead of the default Temp 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.

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

For details on REINSTALL (and REINSTALLMODE), see page 23.

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, begin by doing the following:

• Make sure that the programs to be removed — and their associated files — are not currently in use on the workstations.

• If you are using Windows Terminal Server, make sure that all users are logged off.

Deployment Guide Stage 4: Maintaining the installations 26

Page 28

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

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 remove the software:

\\server\path\Setup.exe /x

When you remove CorelDRAW Technical Suite 2017, Lattice3D Studio Corel Edition and Lattice3D Player are removed by default. If you want to silently remove CorelDRAW Technical Suite 2017 but not Lattice3D Studio Corel Edition and Lattice3D Player syntax:

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

, use the following

Deployment Guide Stage 4: Maintaining the installations 27

Page 29

Property

What it does

REMOVE=ALL

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

REMOVEUSERFILES=value

Specifies whether to remove user files:

0 — no

•

1 — yes REMOVE_GPL=1

REMOVE_SHELLEXT=1

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), an online repository of FAQs and articles.

Deployment Guide Stage 4: Maintaining the installations 28

Page 30

Appendix: 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

Customizing the setup fileset . . . . . . . . . . . . . . . . . . . . . . . . .43

Deploying customized installation settings . . . . . . . . . . . . . .46

Deploying specific features

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

ADDLOCAL=Feature

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

ADDLOCAL=Feature1,Feature2

ADDLOCAL property to specify

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 property 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 2017 components are organized into the following child features of

Software component ”MainApp” child feature

Corel DESIGNER

MainApp.

REMOVE public

ADDLOCAL=ALL:

Designer

Deployment Guide Appendix: Specialized deployment scenarios 29

Page 31

Software component ”MainApp” child feature

CorelDRAW®

Corel® PHOTO-PAINT®

Corel CAPTURE™

Corel® CONNECT™

Draw

Capture

Connect

Lattice3D Studio Corel Edition STUDIO

Lattice3D 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 available for download as an ISO file.

Corel CONNECT The

menu to the standalone Corel CONNECT application. All other files required to run the Connect docker and the standalone application are installed by default.

Utilities The utilities (feature name

features.

Utility “Utility” child feature

Duplex wizard (for two-sided print jobs)

Visual Basic® for Applications (VBA)

Specifying 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:

Deployment Guide Appendix: Specialized deployment scenarios 30

Connect feature adds or removes a shortcut on the Windows Start

Utility) include the following child

DupWiz

VBAFiles

Utility does not include its child features. You must

Page 32

• the node that references ShellExt.msi

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

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

Guide and the Corel® PHOTO-PAINT® 2017 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 (He

Deploying specific languages

When performing a basic or silent installation with the /q switch (see page 15), you may want to use the which 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 or writing tools.

lp  Product Help).

ADDLOCAL property to specify

Language codes are case-sensitive.

Specifying UI modules by language code

A language module includes both the software UI and the writing tools for that language. By installing multiple language modules, you can

enable dynamic language switching — the ability to change the

language of the software UI.

Lattice3D Studio Corel Edition and Lattice3D Player German (

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)

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

support only

Deployment Guide Appendix: Specialized deployment scenarios 31

Page 33

Language module Language code

Czech

Dutch

English

French

German

Italian

Japanese

Polish

Russian

Spanish

Turkish

Specifying writing tools by language code

Each set of writing tools includes Spell Checker and may include Thesaurus or Grammatik (or both). The available languages are as follows.

Language Code Spell Checker Thesaurus Grammatik

Afrikaans

Catalan

Czech

Danish

Dutch

English

French

Galician

German

Greek

Icelandic

Italian

Afrika

Catalan

Czech

Danish

Dutch

English

French

Galician

German

Greek

Iceland

Italian

TTT

Deployment Guide Appendix: Specialized deployment scenarios 32

Page 34

Language Code Spell Checker Thesaurus Grammatik

Norwegian

Polish

Portuguese

Russian

Slovak

Sotho

Spanish

Turkish

Tswana

Xhosa

Zulu

Norway

Polish

Portugue

Russian

Slovak

Sotho

Spanish

Turkish

Tswana

Xhosa

Zulu

TTT

In most cases, writing tools are automatically installed with their corresponding language module—and to match the installed keyboard languages of the operating system.

If you want to exclude writing tools from the installation, you must do one of the following:

• 32-bit — delete the Dbm node that references WT.msi from

setup.xml.

• 64-bit — delete the Dbm node that references WT_x64.msi from

setup.xml.

The parent feature for the writing tools is named specifying

WTools does not include its child features. You must

WTools. However,

individually specify each desired set of writing tools.

Deploying Lattice3D Studio Corel Edition and Lattice3D Player

A typical server image of CorelDRAW Technical Suite 2017 includes the files required to deploy Lattice3D

Player to the workstations.

Updating Corel Corporation will provide patches for any updates to

Lattice3D Studio Corel Edition included with CorelDRAW Technical Suite 2017. Any such patches

Deployment Guide Appendix: Specialized deployment scenarios 33

Lattice3D Studio Corel Edition

and

Lattice3D

Player, which are

and

Page 35

will update the server image of CorelDRAW Technical Suite 2017 with the latest files for The updated software can then be deployed to the workstations by manually repairing the installed software.

Lattice3D Studio Corel Edition

and

Lattice3D

Player.

Removing

Lattice3D Studio Corel Edition

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

Lattice3D Player

Lattice3D Player Pro (Ver. 9 or later) programs dialog box of the Windows Control Panel.

If you want to silently remove CorelDRAW Technical Suite 2017 but not

Lattice3D Studio Corel Edition

the following command line:

Setup.exe /x /qb DO_NOT_REMOVE_XVL=1

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 2017 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 2017\Designer\UIConfig folder. In addition, the following workspaces for Corel DESIGNER are installed in CorelDRAW Technical Suite 2017\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

• 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

can be removed by using the

entry in the Add or remove

and

Lattice3D

Lattice3D Player /

Player, you must use

Deployment Guide Appendix: Specialized deployment scenarios 34

Page 36

Installed CorelDRAW

workspaces

The default workspace of CorelDRAW 2017 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 2017\Draw\UIConfig folder.

Installed Corel PHOTO-

PAI NT workspaces

In addition, the following workspaces for CorelDRAW

are installed in

CorelDRAW Technical Suite 2017\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

• X6 Inspired.cdws — designed for users who are upgrading from

CorelDRAW X6

• 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 2017 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 2017\PHOTO-PAINT\UIConfig folder. In addition, the following workspaces for Corel PHOTO-PAINT are installed in the CorelDRAW Technical Suite 2017\PHOTO- PAINT\Workspace folder:

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

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

• X6 Inspired.cdws — designed for users who are upgrading from

Corel PHOTO-PAINT X6

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

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

Deployment Guide Appendix: Specialized deployment scenarios 35

Page 37

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 Copy the custom workspace files to the corresponding Workspace

folders, making sure not to delete any existing workspace files.

For 32-bit server images

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

msis\Program files\Corel\CorelDRAW Technical Suite 2017\Draw\Workspace

msis\Program files\Corel\CorelDRAW Technical Suite 2017\PHOTO-PAINT\Workspace

For 64-bit server images

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

msis\Program files 64\Corel\CorelDRAW Technical Suite 2017\Draw\Workspace

msis\Program files 64\Corel\CorelDRAW Technical Suite 2017\PHOTO-PAINT\Workspace

4 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 Technical Suite 2017 on a workstation, and log

in as a local user.

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 2017\Designer\Workspace

Deployment Guide Appendix: Specialized deployment scenarios 36

Page 38

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

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

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

installation” on page 36.

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 32-bit 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. Lattice3D Studio Corel Edition and Lattice3D support only German (DE), English (EN), French (FR) and Japanese (JP). However, some versions of CorelDRAW Technical Suite 2017 may include additional 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.

Deployment Guide Appendix: Specialized deployment scenarios 37

Page 39

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)

Turkish 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 CONNECT Connect.msi (32-bit), or 

Connect_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: Specialized deployment scenarios 38

Page 40

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 2017

DVD or in the msis folder of the server image. These files include the following.

Feature MSI file

Ghostscript general public license, for EPS and PostScript® import

Microsoft Visual Basic for Applications (VBA)

Microsoft Visual Studio Tools for Applications (VSTA)

Windows Shell Extension ShellExt.msi and 64BitKey.msi

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.

Ghostscript.msi

\msis\vba\vba71.msi (for both

32-bit and 64-bit)

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

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

Making extra content available

As previously discussed (see page 4), you can make extra content available to workstation users by copying it to the server share.

You can set the path to the server content by using the NETWORKINSTALLDIR public property (see page 18) — or, by editing the appropriate section in the following HKEY_LOCAL_MACHINE\Software\ registry key:

• 32-bit OS — Corel\Media\Corel Content\

NETWORKINSTALLDIR property

• 64-bit OS with (default) 64-bit build — 

Corel\Media\Corel Content\

NETWORKINSTALLDIR property

Deployment Guide Appendix: Specialized deployment scenarios 39

path specified by

Page 41

• 64-bit OS with 32-bit build — 

Wow6432Node\Corel\Media\Corel Content\

by NETWORKINSTALLDIR property

If you want to change the server path to the extra content and Corel CONNECT has been previously launched, you must update the Media registry key with the new path for the extra content and delete the file

C:\Users\<username>\AppData\Roaming\Corel\CorelDRAW Technical Suite 2017\Connect\Connect.config.

When you relaunch Corel CONNECT, a new Connect.config file will

be created containing the updated path.

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.

The extracted content is 18.2 GB.

Internet access is required once to access the download location.

To configure the content

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

workstations, create a main content folder and name it Content.

2 Extract the archive files from CorelDRAW Technical Suite 2017

extra content zip file into separate folders using a decompression tool to the folder created in step 1.

There are six main archive files: Extra applications, eBooks, Clipart, Content (which includes Extensions, Fills, Fonts, Templates, Image Lists, Objects, Photo Frames and Interactive Frames), Photos and Videos. For information about extensions, see “Extensions” on page 41.

path specified

3 Move the Content.db3 file from the extra content archive to the root

of the main content folder created in step 1.

4 Move the following folders from the extra content archive to the root

of the main content folder created in step 1.

•Extensions

• Fills

•Fonts

• Image Lists

• Interactive Frames

• Objects

•Photo Frames

• Templates

Deployment Guide Appendix: Specialized deployment scenarios 40

Page 42

When all zip files have been downloaded and decompressed, this should be the final structure:

Content\

• Content.db3

• Clipart folder

• Extensions folder

• Fills folder

• Fonts folder

• Image Lists folder

• Interactive Frames folder

• Languages folder

• Objects folder

• Photo Frames folder

• Photo folder

• Te mp lat es folder

To share the content folder to workstations

1 Using the Setup.exe /a command line, open the setup wizard.

2 On the last page of the wizard, type the UNC path for the main

content folder in the box in the Content Location area.

3 Click Install Now.

You can also set the path to the server content by using the NETWORKINSTALLDIR. For more information, see “Pointing installations to the extra content” on page 18.

Extensions

Extensions add features to the applications, and do not require installation. The Extra Content zip file, located in the Extensions folder on the shared drive, includes the following extensions: Border and Grommet, Calendar Wizard, Color Chart Creator, File Converter, and Prep and Stretch.

Once extracted, extensions must be copied to the following folder on the workstations:

X:\Users\[UserName]\Documents\Corel\Corel Content\Extensions

Users can then access the extensions from within the applications. For example, the Border and Grommet extension, which allows you to prepare banners for printing, appears under the To ol s menu in CorelDRAW. Downloaded macro extensions, such as Calendar Wizard and File Converter, appear in the Macro Manager docker.

The following extensions require Microsoft Visual Basic for

Applications (VBA):

Deployment Guide Appendix: Specialized deployment scenarios 41

Page 43

• Calendar Wizard

• Color Chart Creator

• File Wizard

• Convert All To Curves

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 31). 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 DESIG NER\19.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 three-letter 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

Japanese JPN

Deployment Guide Appendix: Specialized deployment scenarios 42

Page 44

Language Code

Polish PLK

Russian RUS

Spanish ESN

Turkish 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 Tools  Options  Global page

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

HKEY_CURRENT_USER\Software\Corel\Corel DESIGNER\19.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:

HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel DESIG NER\19.0\Languages

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.

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.

Deployment Guide Appendix: Specialized deployment scenarios 43

Page 45

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 where

GUID is the associated product code, and MSI is the path and

<Dbm/> node has the following structure,

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 and MSI files are in separate folders,

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

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 is the name of the MSI file and

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

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

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.

Deployment Guide Appendix: Specialized deployment scenarios 44

Page 46

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

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

• Remove the corresponding

<Dbm/> node for each removed MSI

file.

• Remove the corresponding

<Feature/> node and subnode for

each removed MSI file.

• Adjust any corresponding

<Property/> nodes by changing their

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

<Feature/> nodes for each removed language module. Next, you

must set each

$$ is a removed language module. The <Property/> node

where for

ShowApplicationLanguageSelector is automatically set to

a value of

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

<Dbm/> and

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:

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.

Deployment Guide Appendix: Specialized deployment scenarios 45

Page 47

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

For more information, see “ALLOW_PRODUCTUPDATES” on page 17.

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

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 point the installations to

the location of extra content and videos:

For more information, see “NETWORKINSTALLDIR” on page 18.

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

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:

Deployment Guide Appendix: Specialized deployment scenarios 46

Page 48

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

Deployment Guide Appendix: Specialized deployment scenarios 47

Page 49

Index

command lines

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

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

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

content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

deployment

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

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

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

dynamic language switching . . . . . . . . . . . . . . . . . 42

extra content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

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

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

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

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

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

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

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

MSI files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

networks

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

setting up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

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

Persist.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

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

server images

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

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

fileset, customizing . . . . . . . . . . . . . . . . . . . . . 43

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

servers

setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

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

setup

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

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

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

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

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

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

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

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

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

Deployment Guide Index 48

Page 50

UI language modules . . . . . . . . . . . . . . . . . . . . . . . . .31

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

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

workspaces, customizing . . . . . . . . . . . . . . . . . . . . 34

workstations

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

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

writing tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Deployment Guide Index 49

Page 51

CorelDRAW® Technical Suite 2017 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, CONNECT, 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

116067