WordPerfect Office - X8
Table of contents
Loading...
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.
WordPerfect Office X8 to your network.
Stage 2: Copying the DVD or extracting the ESD to the server .6
Stage 3: Installing the software . . . . . . . . . . . . . . . . . . . . . . . .8
Stage 4: Maintaining the installations . . . . . . . . . . . . . . . . . .19
Appendix: Specialized deployment scenarios . . . . . . . . . . . . .26
Deploying Paradox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
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 & processes,
general advice & 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
A reference to programming
syntax
Corel Windows’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
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?
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 copy or extract WordPerfect Office X8 to a server that meets
the following requirements:
• Operating system with the latest service pack and critical updates:
indows Server® 2012 R2, Windows Server 2012, Windows Server
W
R2
2008
• 1.5 GB of server space (for a typical installation without extra
conten
t)
Remote Desktop Services are supported on the server operating
systems listed above.
For details on server permissions, see “Server setup” on page 3.
To function properly, Corel ScreenCap requires Windows
Media Player.
Deployment Guide
Stage 1: Preparing for deployment 2
Workstation requirements You can install WordPerfect Office X8 on workstations that meet the
following minimum system requirements:
• Windows® 10, Windows 8.1, Windows 7 (32-bit or 64-bit version)
with latest updates and service packs
• 1 GHz or faster (x86) or AMD64 processor
• 1 GB of RAM (x86); 2 GB of RAM (AMD64)
• 1.5 GB of hard-disk space for minimum installation (Paradox, i
in
cluded, requires an additional 215 MB of hard-disk space.)
• Mouse or tablet
• 1024 × 768 monitor resolution
•
DVD drive (required for box installation)
• Microsoft® Internet Explorer® 11 or later
Some features also require Microsoft® Outlook®.
f
For details on workstat
page 4.
DMS requirements WordPerfect Office X8 offers support for the WordPerfect® Office
(WPD, WPT, WP, QPW) formats on the following documentmanagement systems:
• Microsoft® SharePoint® Server 2013
• Microsoft SharePoint Server 2010
• Microsoft SharePoint Server 2007 with
• SharePoint Portal S
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.htm
ion permissions, see “Workstation setup” on
SP1
erver 2003
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 l
administrator for the domains an
managing.
Deployment Guide
Stage 1: Preparing for deployment 3
ocal administrator or an
d workgroups that you are
• Create a shared network location for the media you are copying or
extracting to the server
cess to that location.
ac
, and make sure that you have read/writ
e
If you want to make extra content (such as clipart and videos) available
to workstation users, do the following:
• Set up a shared network location, and make
cess to that location.
ac
• Use the program DVD to install o
r copy the content to the shared
sure that users have
location.
Workstation setup Do
the following:
• Make sure that you are — and anyone
software is —
either a local administrator or an administrator for the
else who will be installing the
domains and workgroups that you are managing.
• Make sure that you have — and anyone else who will be i
nstalling
the software has — read access to the location where you copied or
extracted media.
SharePoint setup WordPerfect Office IFilter is installed automatically when you install
WordPerfect Office X8. If you want WordPerfect Office IFilter as a
standalone application, you can download it from here
. To speed
searches, install WordPerfect Office IFilter on all servers that will be
hosting WordPerfect files. Detailed instructions on installing
WordPerfect Office IFilter on Microsoft SharePoint 2013, Microsoft
SharePoint 2010, and Microsoft SharePoint 2007 servers are available
on officecommunity.com
.
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 Office IFilter & SharePoint
Resources
On your SharePoint server, run the appropriate WordPerfect Office
IFilter executable file, which you can download from here
. The setup
installs the WordPerfect Office IFilter (for detecting and indexing
stored WordPerfect documents), along with various other
enhancements. Detailed installation instructions are available on
officecommunity.com
.
Step 3: Deploy SharePoint support
Workstations automatically receive SharePoint integration (and the
WordPerfect Office IFilter) when WordPerfect Office X8 is installed.
Deployment Guide
Stage 1: Preparing for deployment 4
If desired, you can deploy the following customized settings:
• disabling of WordPerfect toggle for displaying files in Internet
Explorer: Use the WPDVIEWLOCK public property (see page 17).
• home page for the Open File d
Use the HomePageUR
L registry key (see page 33).
ialog box:
To extend the SharePoint functions of WordPerfect — for example, to
automate multiple check-ins, mul
tiple 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 documentmanagement UI
Specify command arguments
(macro-specific values)
Specify document properties
DocMgmtCheckin
DocMgmtCheckout
DocSetWorkingFolder
DocMgmtUndoCheckout
DocMgmtCheckinDlg
DocMgmtCheckoutDlg
DocMgmtDocHistoryDlg
DocMgmtDocPropertiesDlg
DocMgmtUndoCheckoutDlg
DocMgmtVersionCompareDlg
DocMgmtGetResultCode
DocMgmtGetResultDesc
DocMgmtSetArg
DocPropertyGetCount
DocPropertyGetName
DocPropertyGetType
DocPropertyGetValue
DocPropertyRemove
DocPropertyRemoveAll
DocPropertySet
Deployment Guide
Stage 1: Preparing for deployment 5
Stage 2: Copying the DVD or extracting the ESD to the server
After preparing for deployment, you’re ready to copy (DVD) or extract
(ESD) media to the server.
You can modify certain aspects of the media you copied or extracted to
the server or its setup. If you want to support multiple installation
types, you can create multiple versions of the media you copied or
extracted to the server.
Finalizing media on the server
This section describes recommended steps to take before deploying
from the media copied to the server.
Optionally, you can finalize the media you copied or extracted to the
server in the following ways:
• Customize the registry settings you want to deploy (see page 32).
Applying patches To avoid deploying the software twice, you may want to check for
software updates and apply them as necessary. For details, see page 21.
Supporting OOXML You can deploy support for saving to Office Open XML (OOXML)
format from within WordPerfect Office X8.
To deploy support for saving to OOXML
1 After copying the DVD or extracting the ESD content to the server,
o
pen the <Language> folder.
2 Create a new folder, and name it MSPack.
3 In your browser, navigate to http://apps.corel.com/redirect/
command.asp?_redirect=command&function=download&app=CH
O&subfunction=ffc&lang=en and download the Microsoft Office
Compatibility Pack.
4 Save FileFormatConverters.exe to the MSPack folder.
All future workstation installations from this location will
automatically allow users to save to the Microsoft 2007-2016 format.
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.
Deployment Guide
Stage 2: Copying the DVD or extracting the ESD to the server 6
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 You may want to test on a small subset of workstations before rolling it
out to your entire organization.
Deployment Guide
Stage 2: Copying the DVD or extracting the ESD to the server 7
Stage 3: Installing the software
Highlights:
Using switches. . . . . . . . .10
Using public properties . .12
After copying the contents of the DVD or extracting the ESD to the
server, 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
work
stations
• automatically, by “pushing” the software to the workstations on
ers’ behalf
us
In this stage Pulling the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Pushing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
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 media you copied or extracted to
the server.
their
In this section Preparing for pull installation. . . . . . . . . . . . . . . . . . . . . . . . . .8
Carrying out a pull installation . . . . . . . . . . . . . . . . . . . . . . . . .9
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 software (see “Workstation requirements” on page 3).
• Confirm that each workstation user has read-only access to the m
you copied or extracted to the server and administrator-level access
to the workstation (see also “Workstation setup” on page 4).
Recommendations • Map the workstations to the media yo
server, and set the workstations to log in to that server location at
startup. Doing so ensures that users are always connected this
content.
• Confirm that all workstations are running the latest version o
Micros
process.
the minimum requirements for
edia
u copied or extracted to the
f
oft Windows Installer. Doing so simplifies the installation
Deployment Guide
Stage 3: Installing the software 8
Carrying out a pull installation
Users pull the software to their workstations by running the setup from
the media you copied or extracted to the server.
The degree of user interaction required by the setup depends on how
you’ve customized the media you copied or extracted to the server and
the deployment process.
If you prefer to restrict user customization, you may want to offer
multiple versions of the media you copied or extracted to the server —
one per set of installation options.
To pull the software to a workstation
1 Browse to the location of the media you copied or extracted to the
server, 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 media you copied or extracted to the
server 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.
In this section Specifying the setup file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Using switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Using public properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Running your command line . . . . . . . . . . . . . . . . . . . . . . . . .17
Specifying the setup file
The most important item to specify in your command line is the
executable file for the setup: the Setup.exe file on the server you want
to use:
\\server\path\Setup.exe
Deployment Guide
Stage 3: Installing the software 9
Using switches
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 35.
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 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
i
w
e
a
r
u
m
Status messages
Nonfatal warnings
All error messages
Initiated actions
Action-specific records
User requests
Error messages for out-of-memory warnings or fatal
exits
o
Error messages for insufficient hard-disk space during
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
Logs.txt").
/l*, you can use /log.
/l are iwearmo (/liwearmo "c:\install
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 (Temp ) folder.
Deployment Guide
Stage 3: Installing the software 10
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"
/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
n
No UI whatsoever. Errors are logged in a file that you
can control by using
/l (see page 10). This is the
default parameter.
NOTE: Alternatively to
b
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.
b!
NOTE: Alternatively to
Basic UI: only a progress bar. The user cannot cancel
the 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.
f
The default parameter for
Full UI
/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"
/? Help
The
/? switch (or /help) displays Help for the setup.
Deployment Guide
Stage 3: Installing the software 11
Using public properties
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 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
ASSOCIATE_DOC_FILES Associate DOC files with WordPerfect
You can associate all Microsoft® Word (DOC and DOCX) files with
WordPerfect by using the following property:
ASSOCIATE_DOC_FILES=1
ASSOCIATE_PPT_FILES Associate PPT files with Presentations
You can associate all Microsoft® PowerPoint® (PPT and PPTX) 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 and XLSX) 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
Deployment Guide
Stage 3: Installing the software 12
FORCENOSHOWLIC Suppressing the EULA prompt
If the software is installed silently (see page 11), 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
If you choose to suppress the EULA prompt on the workstations, you
are accepting the terms of the EULA on behalf of your organization and
all users. Deployed installations will not prompt users to review the
license agreement.
INSTALL_APP Installing only specified programs
By default, WordPerfect Office X8 installs WordPerfect, Quattro Pro,
and Presentations™. To install only one (or two) of these programs, use
INSTALL_APP property with one of the following values (or two
the
comma-separated values).
Value What it installs
presentations
quattropro
wordperfect
Presentations
Quattro Pro
WordPerfect
In the following example, only WordPerfect is installed:
Setup.exe INSTALL_APP=wordperfect
In the following example, only WordPerfect and Quattro Pro are
installed:
Setup.exe INSTALL_APP=wordperfect,quattropro
You can also install specific program features. For details, see page 26.
INST
ALLDIR Customizing the installation path
When deploying from the media you copied or extracted to the server,
use the following public property to customize the installation path of
the software:
INSTALLDIR="C:\Directory one\Directory two"
For best results, do not end the path with a backslash ( \ ).
Deployment Guide
Stage 3: Installing the software 13
Loading...