WordPerfect Office X6 Deployment Guide - Corel
Deployment Guide
IntroductionWelcome! This guide is intended to support you, the administrator, in deployingCorel WordPerfect Office X6 to your network.Are you new to network deployment? For a nontechnical introduction tothe concepts and processes discussed in this guide, please see thecompanion Corel Beginner’s Guide to Network Deployment.Contents Stage 1: Preparing for deployment . . . . . . . . . . . . . . . . . . . . .2Stage 2: Creating the server image. . . . . . . . . . . . . . . . . . . . . .6Stage 3: Installing the software . . . . . . . . . . . . . . . . . . . . . . .10Stage 4: Maintaining the installations . . . . . . . . . . . . . . . . . .20Appendix: Specialized deployment scenarios . . . . . . . . . . . . .26Conventions Please note the following conventions used in this guide.Wherever you see thisYou’ll finditalicized textA placeholder for user-specifiedinformation, such as a path orfilenamebold monospace textA reference to programmingsyntaxFor more information The following resources offer additional support.For information onSee the following resourcedeploying Corel software:concepts & processes,general advice & best practicesCorel Beginner’s Guide to NetworkDeploymentCorel Corporation, or a specificCorel software productCorel website: www.corel.comsupport for Corel softwareCorel Support Services website: www.corel.com/supportthe Microsoft Windows Installer (MSI) technology, which isused to install Corel softwareMicrosoft websiteDeployment GuideIntroduction1
Stage 1: Preparing for deploymentHighlights:Server requirements. . . . . . . 2Workstation requirements . . 3Before beginning the deployment, take the time to familiarize yourself withyour network and the software you want to deploy to it. Doing so can helpyour administrative duties run as smoothly as possible.In this stage Getting to know your network. . . . . . . . . . . . . . . . . . . . . . . . .2Getting to know the software . . . . . . . . . . . . . . . . . . . . . . . . .2Setting up your network accordingly . . . . . . . . . . . . . . . . . . . .3Getting to know your networkMake sure to consider your network requirements for the deployment.Administrative factors Does your organization (or do you, as administrator) have any particularrequirements 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 softwareMake sure that your server and workstations are eligible for the software. Ifyour organization uses a document-management system (DMS), make surethat it is supported by the software.Server requirements You can create an image of WordPerfect Office X6 on a server that meetsthe following requirements: Operating system with the latest service pack and critical updates: Windows Server 2008 or Windows Server 2008 R1, or WindowsServer 2003 1 GB of server space (for a typical installation without extra content)Windows Terminal Server (2008 or 2008 R1, or 2003) is supported, butplease note the following:Deployment GuideStage 1: Preparing for deployment2
You must use the WordPerfect Office X6 DVD to install the software onthe server. Corel Corporation does not provide technical support for installing thirdparty software included with the product.For details on server permissions, see “Server setup” on page 3.Workstation requirements You can install WordPerfect Office X6 on workstations that meet thefollowing 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, ifincluded, 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 laterSome features also require Microsoft Outlook .For details on workstation permissions, see “Workstation setup” on page 4.DMS requirements WordPerfect Office X6 offers support for the WordPerfect (WPD) formaton the following document-management systems: Microsoft Office SharePoint Server 2007 with SP1 SharePoint Portal Server 2003For details on SharePoint setup, see page 4.For more information For important notes on installing and using the software, it’s a good idea toreview 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.htmlSetting up your network accordinglyAfter familiarizing yourself with your network and the software you wantto deploy to it, you can set up your network accordingly.Server setup Do the following:Deployment GuideStage 1: Preparing for deployment3
Make sure that you are either a local administrator or an administratorfor the domains and workgroups that you are managing. Create a shared network location for the server image, and make surethat you have read/write access to that location.If you want to make extra content (such as clipart and videos) available toworkstation users, do the following: Set up a shared network location, and make sure that users have accessto that location. Use the program DVD to install or copy the content to the sharedlocation.Workstation setup Do the following: Make sure that you are — and anyone else who will be installing thesoftware is — either a local administrator or an administrator for thedomains and workgroups that you are managing. Make sure that you have — and anyone else who will be installing thesoftware has — read access to the server-image location.GPOsTo more easily manage the access rights of workstation users — especiallyfor pull-installation scenarios — you may want to consider using GroupPolicy Objects (GPOs). The Corel Beginner’s Guide to Network Deploymentoffers basic information on GPOs. For more advanced information, pleaserefer to the Software Development Kit (SDK) for Group Policy.SharePoint setup As part of your SharePoint solution, Microsoft provides a tutorial on settingup a site-based SharePoint server for use with programs such asWordPerfect. Please refer to this tutorial for general guidance, and thentake the following steps for best results with WordPerfect integration.Step 1: Check your security settingsWordPerfect supports the SharePoint features for Windows Security. Besure to configure the local domain to allow password authentication foryour SharePoint server, which requires Hypertext Transfer Protocol overSecure Socket Layer (HTTPS/SSL) security.Step 2: Install WordPerfect IFilter & SharePoint ResourcesOn your SharePoint server, run one of the setups located in the WPRSPfolder on the WordPerfect Office X6 DVD: WPRSP.exe (32-bit) orWPRSP 64.exe (64-bit).This setup installs the WordPerfect IFilter (for detecting and indexingstored WordPerfect documents), along with various other enhancements.Deployment GuideStage 1: Preparing for deployment4
Step 3: Index your WordPerfect documentsFor best results, use the SharePoint-server option “Treat similar words withdiacritics as different words” when first indexing the stored WordPerfectdocuments. You can subsequently disable this option, if desired.Step 4: Deploy SharePoint supportWorkstations automatically receive SharePoint integration (and theWordPerfect 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 WPDVIEWLOCK public property (see page 18). home page for the Open File dialog box: Use the HomePageURL registry key (see page 40).To extend the SharePoint functions of WordPerfect — for example, toautomate multiple check-ins, multiple check-outs, or file-comparisonreports — 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 followingUse the following commandsDirectly access the documentmanagement engine directly,bypassing its DocMgmtUndoCheckoutAccess the fy command arguments(macro-specific MgmtSetArgSpecify document eDocPropertyRemoveAllDocPropertySetDeployment GuideStage 1: Preparing for deployment5
Stage 2: Creating the server imageAfter preparing for deployment, you’re ready to create the server image.Highlights:Initializing the setup . . . . . . 6Setting up the server image . 6Finalizing the server image . 7To create a basic image, you run a standard command line. To create acustomized image, you can modify this command line — or you can modifycertain aspects of the server image or its setup. If you want to supportmultiple installation types, you can create multiple server images.In this stage Creating a basic image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Creating a customized image . . . . . . . . . . . . . . . . . . . . . . . . . .8Creating multiple images . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Creating a basic imageTo create a basic server image, you must initialize the setup. After settingup the image and tweaking it as necessary, you can use it for deployment.In this section Initializing the setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Setting up the server image . . . . . . . . . . . . . . . . . . . . . . . . . . .6Finalizing the server image. . . . . . . . . . . . . . . . . . . . . . . . . . . .7Initializing the setupTo 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 theinstallation disc (where X: is the disc drive):X:\Setup\Setup.exe /aIf your deployment scenario requires using msiexec.exe instead ofSetup.exe, see page 43.Event logging If you want to create a log file of installation events, include the /l switchin 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 whencreating a server image, include the /q switch in your command line. Fordetails on this process, see “Limited setup UI” on page 7.Setting up the server imageIf 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 /qDeployment GuideStage 2: Creating the server image6
Full setup UI The setup UI takes you step-by-step through the process of setting up theserver image. A few notes on this process will suffice.UI componentNotesEnd-User License Agreement(EULA)To create the server image, youmust accept — on behalf of yourorganization — the terms in thelicense agreement. Installationsdeployed from the image will notprompt users to review the licenseagreement.Image LocationType the full (UNC) path in thebox provided, or click the Changebutton to browse to that location.For best results, limit the path to70 characters.Product UpdatesBy default, automatic updates aredisabled. However, you can chooseto have workstations detect anddownload product updates.Limited setup UI If you want to limit the amount of user interface (UI) encountered whencreating a server image, include the /q switch in your command line. Fordetails on this switch, see page 13.Be careful to avoid suppressing (or “silencing”) a required user-interfacefield when introducing a /q switch into your command line — otherwise,you may fail to create a valid server image. You may need to include thefollowing public properties in your command line: TARGETDIR "path" — to specify the desired location of the serverimage. For best results, do not end the path with a backslash ( \ ). ALLOW PRODUCTUPDATES 0 — to disable automatic updates (and inproduct messaging) on the workstations. By default, automatic updatesare enabled for workstations installed from a server image. additional installation properties supported by the setup. For details, see“Using public properties” on page 13.Finalizing the server imageThis section describes recommended steps to take before deploying fromthe 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 41).Deployment GuideStage 2: Creating the server image7
Patching the image To avoid deploying the software twice, you may want to check for softwareupdates 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 calledMSPack. By downloading the Microsoft Compatibility Pack from theMicrosoft website and saving its executable file (EXE) to this folder, youcan deploy support for saving to Office Open XML (OOXML) format fromwithin WordPerfect Office X6. (The installation of the MicrosoftCompatibility Pack will take place after the workstation successfully installsWordPerfect Office X6 from the server image.)Configuring BDE For WordPerfect and Quattro Pro to function properly, you must ensurethat 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 Engine1Log on to the server console as an administrator.2From the Windows Control Panel, open the BDE Administrator.3Click the Configuration tab.4Expand the Configuration tree, and navigate to the following:Drivers\Native\PARADOX5In the right pane, click the field to the right of the NET DIR entry.6Click ., and browse to the location of the desired network folder.All users must have write and delete permissions for this folder.7Click Object Apply.8Click OK to confirm the save, and then click OK again when you areprompted to restart all Borland Database Engine applications.Testing the image You may want to test your finalized image with a small subset ofworkstations 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 createa new image at a new location. You cannot copy an image from onelocation to another.Creating a customized imageIf you require a more customized server image than offered by commandline switches (see page 12) and public properties (see page 13), you maywant to consider the specialized scenarios discussed in the Appendix.Deployment GuideStage 2: Creating the server image8
MSI files You can modify the Microsoft Windows Installer (MSI) files used to installthe software. See page 37.MST files You can apply Microsoft transformation (MST) files to the setup. Seepage 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 theworkstations. See page 43.Creating multiple imagesIf your workstations require different configurations of the software, youcan create one server image for each installation type.Product updates When a product update becomes available, you will need to apply it to eachserver image. For details on image patching, see page 23.Naming convention Use a naming convention that makes it easy to distinguish the serverimages from one other.Deployment GuideStage 2: Creating the server image9
Stage 3: Installing the softwareHighlights:Using switches . . . . . . . . . 12Using public properties . . . 13After creating the server image, you can use it to install the software on theworkstations 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 theirusers’ behalfIn this stage Pulling the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Pushing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Pulling the softwareIf users have both access to the server and administrator-level rights to theirworkstations, they can install (or “pull”) the software themselves. To dothis, they run the setup from the server image.In this section Preparing for pull installation. . . . . . . . . . . . . . . . . . . . . . . . .10Carrying out a pull installation . . . . . . . . . . . . . . . . . . . . . . . .10Preparing for pull installationTo 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 thesoftware (see “Workstation requirements” on page 3). Confirm that each workstation user has read-only access to the serverimage and administrator-level access to the workstation (see also“Workstation setup” on page 4).Recommendations Map the workstations to the server image, and set the workstations tolog in to that server location at startup. Doing so ensures that users arealways connected to the server image. Confirm that all workstations are running the latest version of MicrosoftWindows Installer. Doing so simplifies the installation process.Carrying out a pull installationUsers pull the software to their workstations by running the setup from theserver image.Deployment GuideStage 3: Installing the software10
The degree of user interaction required by the setup depends on how you’vecustomized the server image and the deployment process.If you prefer to restrict user customization, you may want to offer multipleserver images — one per set of installation options. For details, see page 9.To pull the software to a workstation1Browse to the location of the server image, and double-click Setup.exe.2Carry out the installation, specifying any desired options, by followingthe on-screen instructions.For best results, limit the installation path to 70 characters.Pushing the softwareTo “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 settingsUsing this command line, you can install the software on the workstationsby using any supported push method.In this section Specifying the setup file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Using switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Using public properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Running your command line . . . . . . . . . . . . . . . . . . . . . . . . .18Specifying the setup fileThe most important item to specify in your command line is the executablefile for the setup: the Setup.exe file on the server image you want to use:\\server\path\Setup.exeIf 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 ofSetup.exe, see page 43.Deployment GuideStage 3: Installing the software11
Using switchesBy using switches in your command line, you can control the setup process.Listed in this section are the switches most commonly used when installingthe 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 loggingUse /l to log installation events.ParameterWhat it logsiStatus messageswNonfatal warningseAll error messagesaInitiated actionsrAction-specific recordsuUser requestsmError messages for out-of-memory warnings or fatal exitsoError messages for insufficient hard-disk space duringserver installationpTerminal properties*All of the above, in a single log fileNOTE: Alternatively to /l*, you can use /log.vVery detailed informationThe default parameters for /l are iwearmo (/liwearmo "c:\installLogs.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 thecurrent user’s temporary (Temp) folder.In the following example, the /l switch (with default parameters) is usedto log installation events in the specified file:\\server\path\Setup.exe /l "C:\install.txt"Deployment GuideStage 3: Installing the software12
/q Limited setup UIUse /q to limit the amount of setup UI encountered during installation.You can use /q to prevent users from entering their own registrationinformation, to help enforce specific installation options, or even to performsilent installations (in which no setup UI is visible whatsoever).ParameterWhat the user sees during installationnNo UI whatsoever. Errors are logged in a file that youcan control by using /l (see page 12). This is the defaultparameter.NOTE: Alternatively to /qn, you can use /quiet.bBasic UI: a progress bar and a Cancel button. If the userpushes the Cancel button, the installation is rolled backupon confirmation.NOTE: Alternatively to /qb, you can use /passive.b!Basic UI: only a progress bar. The user cannot cancel theinstallation.b Basic UI: a progress bar and a Cancel button. If the userpushes the Cancel button, the installation is rolled back(without first prompting for confirmation).rReduced UI: A progress bar, along with a pagecontaining information about the installation. The usercan cancel the installation.fFull UIThe default parameter for /q is n.In the following example, all setup UI is suppressed, and any errors arerecorded in the specified log file:\\server\path\Setup.exe /q /l "C:\Logs\My Log.txt"/? HelpThe /? switch (or /help) displays Help for the setup.Using public propertiesBy using public properties in your command line, you can specifyinstallation settings. Listed alphabetically in this section are the propertiesmost commonly used during software installation.For general information on public properties, along with details onproperty syntax, please see the Corel Beginner’s Guide to Network Deployment.Deployment GuideStage 3: Installing the software13
For a list of all command-line properties for Microsoft Windows Installer,please see the Microsoft website.ADDLOCAL Installing specific componentsFor details on this scenario, see the following topics in the appendix: “Deploying specific features” on page 26 “Deploying specific languages” on page 27ASSOCIATE DOC FILES Associate .doc files with WordPerfectYou can associate all Microsoft Word .doc files with WordPerfect by usingthe following property:ASSOCIATE DOC FILES 1ASSOCIATE PPT FILES Associate .ppt files with PresentationsYou can associate all Microsoft PowerPoint .ppt files with Presentationsby using the following property:ASSOCIATE PPT FILES 1ASSOCIATE XLS FILES Associate .xls files with Quattro ProYou can associate all Microsoft Excel .xls files with QuattroPro by usingthe following property:ASSOCIATE XLS FILES 1DESKTOPSHORTCUTS Opting out of desktop shortcutsYou can prevent the installation of desktop shortcuts by using the followingproperty:DESKTOPSHORTCUTS 0IGNORE LAUNCH Suppressing the software-requirements checkCONDITIONSBy default, the setup checks whether the computer meets the minimumsoftware requirements (see page 3) before proceeding with the installation.To suppress this check, use the following property:IGNORE LAUNCH CONDITIONS 1FORCENOSHOWLIC Suppressing the EULA promptIf the software is installed silently (see page 13), each workstation user willbe prompted to accept the End-User License Agreement (EULA) at firststart-up. To suppress the EULA prompt on the workstations, use thefollowing property:FORCENOSHOWLIC 1Deployment GuideStage 3: Installing the software14
If you choose to suppress the EULA prompt on the workstations, you areaccepting the terms of the EULA on behalf of all users on your networkwhen you create the server image.INSTALL APP Installing only specified programsBy default, WordPerfect Office X6 installs WordPerfect, Quattro Pro, andPresentations . To install only one (or two) of these programs, use theINSTALL APP property with one of the following values (or two commaseparated values).ValueWhat it o ProwordperfectWordPerfectIn the following example, only WordPerfect is installed:Setup.exe INSTALL APP wordperfectIn the following example, only WordPerfect and Quattro Pro are installed:Setup.exe INSTALL APP wordperfect,quattroproYou can also install specific program features. For details, see page 26. INSTALLDIR Customizing the installation pathWhen deploying from the server image, use the following public propertyto customize the installation path of the software:INSTALLDIR "path"For best results, do not end the path with a backslash ( \ ). INSTALL IFILTER Managing IFilter installationYou can prevent the installation of the WordPerfect IFilter by using thefollowing property:INSTALL IFILTER 0MIGRATE PRODUCT Migrating user settings during upgradeWhen upgrading from a previous version of WordPerfect Office, you canuse the MIGRATE PRODUCT property to migrate user settings. For detailson upgrading to WordPerfect Office X6, see page 16.REBOOT Handling rebootsThe REBOOT property is used with one of the following values to specifyhow the installation process handles any required reboots.Deployment GuideStage 3: Installing the software15
ValueWhat it doesForce Prompts for reboot after installation. If thesetup UI is suppressed, the computer isautomatically rebooted after installation.NOTE: Alternatively to REBOOT Force, youcan use the /forcerestart switch.(or F)Suppress (or S)Prompts for reboot during installation (ifrequired), but reboots automatically afterinstallation. If the setup UI is suppressed, allrequired 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 toREBOOT ReallySuppress, you can use the/norestart switch.SERIAL NUMBER Inputting your serial numberTo input your assigned serial number, use the following property:SERIALNUMBER serial numberYou must type the serial number without any spaces.SPLITTABLEROWS Splitting table rowsBy default, WordPerfect disables the setting for splitting table rows acrosspages (Table Format Row Divide row across pages) — in part, toensure that footnotes can be added within tables. To enable this setting onthe workstations, use the following property:SPLITTABLEROWS 1Enabling this setting corresponds to writing the registry keyWPTablesSpanRows, while disabling it corresponds to writingWPTablesSpanRows defaultOff. See page 39 for details on registrykeys.UPGRADE PRODUCT Upgrading to WordPerfect Office X6andUPGRADE PRODUCT To upgrade to WordPerfect Office X6 and migrate user settings from aDEFAULT previous version of WordPerfect Office, you must use several publicproperties together.First, you must use the following property to specify which version (orversions) of WordPerfect Office to search for:UPGRADE PRODUCT valueDeployment GuideStage 3: Installing the software16
The UPGRADE PRODUCT property is used with one (or more) of thefollowing (comma-separated) values:ValueWhat it searches forAllAny installed version of WordPerfect Office15WordPerfect Office X514WordPerfect Office X413WordPerfect Office X312WordPerfect Office 1211WordPerfect Office 11NOTE: You cannot upgrade from WordPerfect Office 11without first uninstalling Paradox (if included).NoneNothing — upgrade feature is disabledNext, you must use the following public property to specify whether toupgrade the previous version (or versions) of WordPerfect Office found:UPGRADE PRODUCT DEFAULT valueThe UPGRADE PRODUCT DEFAULT property is used with one of thefollowing values:ValueWhat it doesOnAutomatically upgrades all installed versions ofWordPerfect Office(or any other value)OffDoes not automatically upgrade any installedversion of WordPerfect OfficeTo upgrade to WordPerfect Office X6, you must use UPGRADE PRODUCTand UPGRADE PRODUCT DEFAULT together. Using only one propertycauses it to be ignored altogether.Finally, you can use the following public property to migrate user settingsfrom a previous version of WordPerfect Office:MIGRATE PRODUCT valueThe MIGRATE PRODUCT property is used with one of the followingvalues:ValueWhere it migrates settings fromLatestThe latest installed version of WordPerfect Office15WordPerfect Office X514WordPerfect Office X4Deployment GuideStage 3: Installing the software17
ValueWhere it migrates settings from13WordPerfect Office X312WordPerfect Office 1211WordPerfect Office 11NoneNowhere — the migration feature is disabledIn the following example, all installed versions of WordPerfect Office areautomatically upgraded to WordPerfect Office X6, and user settings aremigrated from the latest installed version of WordPerfect Office:UPGRADE PRODUCT All UPGRADE PRODUCT DEFAULT OnMIGRATE PRODUCT LatestIn the following example, only WordPerfect Office 12 and WordPerfect Office X3 are searched for — but they are not automaticallyupgraded to WordPerfect Office X6; in addition, user settings are migratedfrom WordPerfect Offi
Some features also require Microsoft Outlook . For 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 with SP1 SharePoint Portal .
Corel WordPerfect Office X4 also supplies an open architecture, support for accessibility technologies, and a familiar, ribbon-free user experience that doesn't require retraining. Legal Law offices, from solo practitioners to the largest firms, benefit from Corel WordPerfect Office X4 through the suite's advanced, intuitive formatting;
procedure for restarting the applicable indexing service. WordPerfect Office does not have to be installed on the SharePoint Server. Preparing to install WordPerfect Office IFilter . 1. Log in to the system hosting Microsoft SharePoint Server 2007/2010/2013/2016/2019 as an administrator or as a user with local administrative rights. 2.
Web resources — product information, support materials, social media, and more. See “Part Eight: Web Resources” on page 243. Not all documented features are availa ble in all versions of WordPerfect O ffi
Chancellor Robert G. Clark, III sheila.lewis@madison-co.com Word Chancellor Cynthia Brewer regina.ferguson@madison-co.com Word/WordPerfect Chancellor James Walker richerish.johnson@madison-co.com Word/WordPerfect . Chancellor Rhea Sheldon lmartin@co.marion.ms.us Word/WordPe
2 Agenda ACS Installation & Deployment Overview of Installation & Deployment strategy The philosophy behind our strategy Current deployment methods for containerised and non-containerised environment Where we are heading with regard to improving the installation and deployment experience Demo-Ansible installation Demo -Helm deployment
MaxCS Client Remote Deployment Guide October 2019 Page 1 of 13 MaxCS Release 8.6.1 Client Remote Deployment Guide . or above, Windows 7, Windows 8.1, or Windows 10. The general procedure for deployment is the same as with most remote deployment processes: create a distribution point, create a Group Policy Object (GPO), assign a package .
1 Reg Office: Cmd Line Reg Office: Cmd Line 2 Reg Office: Desktop v1 Reg Office: Desktop v1 3 Reg Office: Desktop v2 Reg Office: Web v1 4 Reg Office: Web v1 Reg Office: Web v2 5 Reg Office: Web v2 Reg Office: Desktop v2. Client-Side Web Programming: CSS . - book.py, database.py
using Scrum for agile software project management in a university environment. The paper is divided into three parts. In the first part an overview of the Scrum method is given. In the second part .
