Corel Corel Draw Technical Suite - X7 Deployment Guide

Deployment Guide

Last updated: March 18, 2015

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

Stage 4: Maintaining the installations . . . . . . . . . . . . . . . . . .19

Appendix: Specialized deployment scenarios . . . . . . . . . . . . .26

Wherever you see this You’ll find

italicized text A placeholder for user-specified

information, such as a path or filename

bold monospace text A reference to programming

syntax

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

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

Corel Beginner’s Guide to Network Deployment

Corel® website: www.corel.com

website: www.corel.com/support

Microsoft® website

Deployment Guide Introduction 1

Stage 1: Preparing for deployment

Highlights:

Server requirements. . . . . .2

Workstation requirements .3

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

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.

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

server that meets the following requirements:

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

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

• Microsoft Windows Installer 4.5

Deployment Guide Stage 1: Preparing for deployment 2

Windows® Terminal Server (2008, 2008 R2, or 2012 R2) is supported, but please note the following:

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

• Windows Media® Player is required if you want workstation users to have access to the Hints docker and the Video Browser.

• 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 X7 on workstations that

meet the following requirements:

• Operating system with the latest service pack and critical updates: 32-bit or 64-bit version of Windows® 8/8.1 or Windows® 7

• Intel Core 2 Duo or AMD Athlon 64

• 2 GB of RAM

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

• Mouse or tablet

• 1280 x 768 screen resolution or greater

• DVD drive

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

• Microsoft® .NET Framework 4.5

• Microsoft Windows Installer 4.5

• Windows Media Player 10 or later (for Hints docker and Video Browser)

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

Software The software includes the following components:

• CorelDRAW Technical Suite X7 Applications (DVD or ISO file)

• Corel Website Creator (ISO file)

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 third-party software.

Optionally, you can download the extra content and videos that are available online and can be accessed through the product. For more information, see “Server setup” on page 4.

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.

Deployment Guide Stage 1: Preparing for deployment 3

To access the Readme file on the installation disc

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

X:\x86\Lang\EN\Readme.html X:\x64\Lang\EN\Readme.html

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

• X:\x86\Lang\DE\Readme.html or X:\x64\Lang\DE\Readme.html

• X:\x86\Lang\FR\Readme.html or X:\x64\Lang\FR\Readme.html

• X:\x86\Lang\JP\Readme.html or X:\x64\Lang\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.

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

• Download the content from the Downloads For Members and Subscribers page in your corel.com account. The download consists of two Zip files that you must extract to the shared network location by using WinZip® or another compression tool.

The extracted content is 9 GB.

Workstation setup Do the following:

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

Deployment Guide Stage 1: Preparing for deployment 4

• Make sure that you have — and anyone else who will be installing the software has — read access to the server-image location.

• Make sure that the workstations have Microsoft .NET Framework

4.5 installed.

• Make sure that the workstations have Windows Installer 4.5 installed.

To run Bitstream® Font Navigator®, workstation users require administrator-level privileges.

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.

Deployment Guide Stage 1: Preparing for deployment 5

Stage 2: Creating the server image

Highlights:

Initializing the setup . . . . .6

Setting up the server image7 Finalizing the server image9

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

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.

Creating a customized image . . . . . . . . . . . . . . . . . . . . . . . . . .9

Creating multiple images . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

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.

In this section Initializing the setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

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

Finalizing the server image. . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Initializing the setup

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

To initialize the setup for creating a server image, 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

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

Deployment Guide Stage 2: Creating the server image 6

X: is the disc drive):

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

creating a server image, include the For details on this process, see “Limited setup UI” on page 8.

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 may need to include the following public property 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 (

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 in your command line.

/q switch into your command line

\ ).

UI component Notes

Email address and password Your corel.com account

information such as email address and password is required to access premium features, product updates, and the Content Exchange.

End-User License Agreement (EULA)

To create the server image, you must accept — on behalf of your organization — the terms in the license agreement. Installations deployed from the image will not prompt users to review the license agreement.

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

Deployment Guide Stage 2: Creating the server image 7

UI component Notes

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 Enabling this option

automatically downloads product updates to the workstations and prompts users to install them. You can access this option only after entering your email address and password.

Internet features This option allows workstations

to access Internet-based features such as the Content Exchange, QR code and ConceptShare. 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 term of service. In addition, when you enter your email and password when online, a PROFILEID is generated that allows users to be signed in automatically. For more information, see “PROFILEID” on page 16.

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

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 may need to 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 (

•

ALLOW_PRODUCTUPDATES=0 — to disable automatic updates (and

\ ).

in-product messaging) on the workstations. By default, automatic updates are enabled for workstations installed from a server image.

•

ALLOW_INTERNETFEATURES=0 — to disable access to internet-

based features such as the Content Exchange, ConceptShare and product updates.

Deployment Guide Stage 2: Creating the server image 8

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

In the following example, there is no setup UI, automatic product updates and access to Internet-based features is disabled, the paths to the server image and extra content are set, and any errors are recorded in the specified log file:

\\server\path\Setup.exe /qn SERIALNUMBER=<SerialNumber> PROFILEID=<ProfileIDDigit> ALLOW_PRODUCTUPDATES=0 ALLOW_INTERNETFEATURES=0 TARGETDIR=<PathToAdminImage> NETWORKINSTALLDIR=<PathToExtraContent> /l D:\Log\MYlog.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 32).

• Customize the setup fileset (see page 34).

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

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.

Creating a customized image

If you require a more customized server image than offered by command-line switches (see page 13) and public properties (see page 15), you may want to consider the specialized scenarios discussed in the Appendix.

MSI files You can modify the Microsoft Windows Installer (MSI) files used to

install the software. See page 31.

Deployment Guide Stage 2: Creating the server image 9

MST files You can apply Microsoft® transformation (MST) files to the setup. See

page 31.

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

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

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

workstations. See page 37.

Creating multiple images

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

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

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 10

Stage 3: Installing the software

Highlights:

Using switches. . . . . . . . .13

Using public properties . .15

In this stage Pulling the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

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

Pushing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

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

Carrying out a pull installation . . . . . . . . . . . . . . . . . . . . . . . .11

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

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 11

+ 28 hidden pages