Corel WordPerfect Office - X6 Deployment Guide

Deployment Guide

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.

Corel® WordPerfect® Office X6 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 . . . . . . . . . . . . . . . . . . . . . . .10

Stage 4: Maintaining the installations . . . . . . . . . . . . . . . . . .20

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 & processes, general advice & best practices

Corel Corporation, or a specific Corel software product

support for Corel software Corel® Support Services website: 

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

Corel Beginner’s Guide to Network Deployment

Corel® website:  www.corel.com

www.corel.com/support

Microsoft® website

Deployment Guide Introduction 1

Stage 1: Preparing for deployment

Highlights:

Server requirements. . . . . . . 2

Workstation requirements . .3

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

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

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

Setting up your network accordingly . . . . . . . . . . . . . . . . . . . .3

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. If your organization uses a document-management system (DMS), make sure that it is supported by the software.

Server requirements You can create an image of WordPerfect Office X6 on a server that meets

the following requirements:

• Operating system with the latest service pack and critical updates:  Windows Server® 2008 or Windows Server® 200 Server 2003

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

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

8 R1, or Windows

Deployment Guide Stage 1: Preparing for deployment 2

• You must use the WordPerfect Office X6 DVD to install the software on the server.

• Corel Corporation does not provide techni party software included with the product.

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

orkstation requirements You can install WordPerfect Office X6 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® 7, Windows Vista® or  Windows XP

• Pentium® III (466 MHz)

• 256 MB of RAM

• 660 MB of hard-disk space for minimum installation (Paradox, if inc

luded, requires an additional 215 MB of hard-disk space.)

• Mouse or tablet

• 800 × 600 (or greater) screen resolution; 1024 × 768 or greater recommended

• Microsoft® Internet Explorer® 6.0 or later

Some features also require Microsoft® Outlook®.

cal support for installing third-

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

DMS requirements WordPerfect Office X6 offers support for the WordPerfect® (WPD) format

on the following document-management systems:

• Microsoft® Office SharePoint® Server 2007

• SharePoint Portal Server 2003

For details on SharePoint setup, see 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.

To access the Readme file on the installation disc

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

X:\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.

with SP1

Server setup Do the following:

Deployment Guide Stage 1: Preparing for deployment 3

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

tation users, do the following:

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

• Use the program DVD to install or

cation.

copy the content to the shared

location.

Workstation setup Do

the following:

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

tware 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 sof

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

GPOs

o more easily manage the access rights of workstation users — especially

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

SharePoint setup As part of your SharePoint solution, Microsoft provides a tutorial on setting

up a site-based SharePoint server for use with programs such as WordPerfect. Please refer to this tutorial for general guidance, and then take the following steps for best results with WordPerfect integration.

Step 1: Check your security settings

WordPerfect supports the SharePoint features for Windows Security. Be sure to configure the local domain to allow password authentication for your SharePoint server, which requires Hypertext Transfer Protocol over Secure Socket Layer (HTTPS/SSL) security.

Step 2: Install WordPerfect IFilter & SharePoint Resources

On your SharePoint server, run one of the setups located in the WPRSP folder on the WordPerfect Office X6 DVD: WPRSP.exe (32-bit) or WPRSP_64.exe (64-bit).

This setup installs the WordPerfect IFilter (for detecting and indexing stored WordPerfect documents), along with various other enhancements.

Deployment Guide Stage 1: Preparing for deployment 4

Step 3: Index your WordPerfect documents

For best results, use the SharePoint-server option “Treat similar words with diacritics as different words” when first indexing the stored WordPerfect documents. You can subsequently disable this option, if desired.

Step 4: Deploy SharePoint support

Workstations automatically receive SharePoint integration (and the WordPerfect IFilter) when WordPerfect Office X6 is installed.

If desired, you can deploy the following customized settings:

• disabling of WordPerfect toggle for displaying files in Internet Explorer: Use the

• home page for the Open File dialog Use the Home

WPDVIEWLOCK public property (see page 18).

box:

PageURL registry key (see page 40).

To extend the SharePoint functions of

WordPerfect — for example, to automate multiple check-ins, multiple check-outs, or file-comparison reports — you can use PerfectScript™ macros. The following commands (fully detailed in the installed Macro Help file, psh.chm) will be of interest.

To do the following Use the following commands

Directly access the documentmanagement engine directly, bypassing its UI

Access the document-management UI

Specify command arguments (macro-specific values)

DocMgmtCheckin DocMgmtCheckout DocSetWorkingFolder DocMgmtUndoCheckout

DocMgmtCheckinDlg DocMgmtCheckoutDlg DocMgmtDocHistoryDlg DocMgmtDocPropertiesDlg DocMgmtUndoCheckoutDlg DocMgmtVersionCompareDlg

DocMgmtGetResultCode DocMgmtGetResultDesc DocMgmtSetArg

Specify document properties DocPropertyGetCount

DocPropertyGetName DocPropertyGetType DocPropertyGetValue DocPropertyRemove DocPropertyRemoveAll DocPropertySet

Deployment Guide Stage 1: Preparing for deployment 5

Stage 2: Creating the server image

Highlights:

Initializing the setup . . . . . .6

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

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

Creating multiple images . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

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

Finalizing the server image. . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Initializing the setup

To initialize the setup for creating a server image, you use a command line. The following command line lets you create a basic server image from the installation disc (where

X:\Setup\Setup.exe /a

If your deployment scenario requires using msiexec.exe instead of Setup.exe, see page 43.

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

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

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

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

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

X: is the disc drive):

/l switch

/q switch in your command line. For

Deployment Guide Stage 2: Creating the server image 6

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.

UI component Notes

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 the Change button to browse to that location. For best results, limit the path to 70 characters.

Product Updates By default, automatic updates are

disabled. However, you can choose to have workstations detect and download product updates.

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

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

/q switch into your command line — otherwise,

you may fail to create a valid server image. You 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.

• additional installation properties supported by the set

“Using public properties

” on page 13.

up. For details, see

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 wa

• Customize the setup fileset (see page 41).

Deployment Guide Stage 2: Creating the server image 7

nt to deploy (see page 39).

Patching the image 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.

Supporting OOXML A typical server image of WordPerfect Office X6 includes a folder called

MSPack. By downloading the Microsoft® Compatibility Pack from the Microsoft website and saving its executable file (EXE) to this folder, you can deploy support for saving to Office Open XML (OOXML) format from within WordPerfect Office X6. (The installation of the Microsoft Compatibility Pack will take place after the workstation successfully installs WordPerfect Office X6 from the server image.)

Configuring BDE For WordPerfect and Quattro Pro® to function properly, you must ensure

that the network folder settings for the Borland® Database Engine (BDE) point to a folder for which all users have write and delete permissions.

To adjust the Borland Database Engine

1 Log on to the server console as an administrator.

2 From the Windows Control Panel, open the BDE Administrator.

3 Click the Configuration tab.

4 Expand the Configuration tree, and navigate to the following:

Drivers\Native\PARADOX

5 In the right pane, click the field to the right of the NET DIR entry.

6 Click ..., and browse to the location of the desired network folder.

All users must have write and delete permissions for this folder.

7 Click Object  Apply.

8 Click OK to confirm the save, and then click OK again when you are

prompted to restart all Borland Database Engine applications.

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 must create

a new image at a new location. You cannot copy an image from one location to another.

Creating a customized image

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

Deployment Guide Stage 2: Creating the server image 8

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

the software. See page 37.

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

page 38.

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

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

workstations. See page 43.

Creating multiple images

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

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

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 9

Stage 3: Installing the software

Highlights:

Using switches . . . . . . . . . 12

Using public properties . . .13

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 wor

users’ behalf

In this stage Pulling the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Pushing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

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

Carrying out a pull installation . . . . . . . . . . . . . . . . . . . . . . . .10

kstations on their

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

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

• Confirm that each workstation user has read-only access to the server

and administrator-level access to the workstation (see also

image “Workstation setup” on page 4).

Recommendations • Map the workstations to the server image, and

• Confirm that all workstations are running the latest version of Microsoft

indows Installer. Doing so simplifies the installation process.

Carrying out a pull installation

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

for the

set the workstations to

Deployment Guide Stage 3: Installing the software 10

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

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

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.

For best results, limit the installation path to 70 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

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

Specifying the setup file

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

Using switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Using public properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Running your command line . . . . . . . . . . . . . . . . . . . . . . . . .18

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\Setup.exe

If your path contains spaces, you must place quotation marks around it:

"\\server\path containing spaces\Setup.exe"

If your network requires deployment via msiexec.exe instead of Setup.exe, see page 43.

Deployment Guide Stage 3: Installing the software 11

Using switches

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

/l to log installation events.

Use

Parameter What it logs

w Nonfatal warnings

e All error messages

a Initiated actions

r Action-specific records

u User requests

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

o Error messages for insufficient hard-disk space during

Status messages

server installation

p Terminal properties

* All of the above, in a single log file

NOTE: Alternatively to

v Very detailed information

The default parameters for

/l are iwearmo (/liwearmo "c:\install

/l*, you can use /log.

Logs.txt").

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

/l "path"

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

In the following example, the

/l switch (with default parameters) is used

to log installation events in the specified file:

\\server\path\Setup.exe /l "C:\install.txt"

Deployment Guide Stage 3: Installing the software 12

/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 12). This is the default

parameter. NOTE: Alternatively to

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

/qn, you can use /quiet.

pushes the Cancel button, the installation is rolled back upon confirmation. NOTE: Alternatively to

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

/qb, you can use /passive.

installation.

b+ 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).

r Reduced UI: A progress bar, along with a page

containing information about the installation. The user can cancel the installation.

/? Help

Using public properties

f Full UI

The default parameter for

/q is n.

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

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

The

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

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

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

Deployment Guide Stage 3: Installing the software 13

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 26

• “Deploying specific languages” on page 27

ASSOCIATE_DOC_FILES Associate .doc files with WordPerfect

ou can associate all Microsoft® Word .doc files with WordPerfect by using

Y the following property:

ASSOCIATE_DOC_FILES=1

ASSOCIATE_PPT_FILES Associate .ppt files with Presentations

You can associate all Microsoft® PowerPoint® .ppt files with Presentations by using the following property:

ASSOCIATE_PPT_FILES=1

ASSOCIATE_XLS_FILES Associate .xls files with Quattro Pro

You can associate all Microsoft® Excel® .xls files with QuattroPro by using the following property:

ASSOCIATE_XLS_FILES=1

DESKTOPSHORTCUTS Opting out of desktop shortcuts

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

DESKTOPSHORTCUTS=0

IGNORE_LAUNCH_

CONDITIONS

Suppressing the software-requirements check

By default, the setup checks whether the computer meets the minimum software requirements (see page 3) before proceeding with the installation. To suppress this check, use the following property:

IGNORE_LAUNCH_CONDITIONS=1

FORCENOSHOWLIC Suppressing the EULA prompt

If the software is installed silently (see page 13), each workstation user will be prompted to accept the End-User License Agreement (EULA) at first start-up. To suppress the EULA prompt on the workstations, use the following property:

FORCENOSHOWLIC=1

Deployment Guide Stage 3: Installing the software 14

+ 33 hidden pages