Follow

CorelDraw Technical Suite X6 Deployment Guide Appendix Part 3

 Previous: CorelDraw Technical Suite X6 Deployment Guide - Appendix Part 2

Working with registry keys
After creating the server image, you may want to edit its registry keys for deployment to the workstations. By doing so, you can avoid having to manually configure the registry keys of each individual workstation installation of the software.

Making extra content available
As previously discussed (see page 4), you can make extra content available to workstation users by copying it to the server share.
You can set the path to the server content by using the public property (see page 14) — or, by editing the appropriate section in the following HKEY_LOCAL_MACHINE\Software\ registry key:

  • 32-bit OS — Corel\Media\CorelDRAW Technical Suite X6
  • 64-bit OS with (default) 64-bit build — Corel\Media\CorelDRAW Technical Suite X6
  • 64-bit OS with 32-bit build — Wow6432Node\Corel\Media\ CorelDRAW Technical Suite X6

Setting up dynamic language switching
Dynamic language switching allows the language of the user interface to be changed, both during and after installation. This feature requires the installation of multiple language modules for the software — one for each desired user-interface language (see page 27). The selection of languages you can implement depends on the license you have purchased.
Two sets of registry settings are required for dynamic language switching:

  • Workstation settings
  • current user settings

Workstation settings
Workstation settings affect all users. The registry setting for each workstation is as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel DESIGNER\ 16.0\Languages

Inside this key are language keys — three-letter codes that represent the available languages. These language keys are put in place by the setup, so no intervention is required. Corel DESIGNER, XVL Studio 3 D Corel Edition, and XVL Player support only German, English, and French. However, some versions of CorelDRAW Technical Suite X6 may include additional language modules for the remaining components (CorelDRAW, Corel PHOTO-PAINT, and Corel CONNECT). Shown here (for reference only) are the three-letter codes for the available languages for the remaining components.

   

Language

Code
Brazilian Portuguese PTB
Chinese (Simplified) CHS
Chinese (Traditional) CHT
Czech CSY
Dutch NLD
English ENU
Finnish FIN
French FRA
German DEU
Hungarian HUN
Italian ITA
Japanese JPN
Polish PLK
Russian RUS
Spanish ESN
Swedish SVE
Turkish  
TRK

Under each language key are the following registry settings:

  • DirName — specifies the name of the folder for the language-specific files, relative toInstallationPath\Languages
  • UIName — specifies the name to show in the startup dialog box and on the Tools }Options } Global page


Current user settings
The registry setting for each current user is as follows:
HKEY_CURRENT_USER\Software\Corel\Corel DESIGNER\16.0
The UILang setting is not initialized by the setup because the setup cannot determine which user will run the applications. After the user has run the application once, this setting changes to the three-letter code that corresponds to the user-specified language key at the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Corel\Corel DESIGNER\ 16.0\Languages

Customizing the setup fileset
The main configuration file Setup.xml, located in the x86 or x64 folder, lists all features included in the setup.
When you create a server image, a copy of the Setup.xml file is included. If you want to customize the setup fileset on the server image, you must edit the Setup.xml file to reflect your desired changes.
Understanding Setup.xml
The Setup.xml file contains four main types of nodes. With an understanding of these four nodes, you can modify the Setup.xml file to create a customized server image.
<Msi/> nodes
Each <Msi/> node specifies a main setup file, such an executable (EXE) file, a self-extracting ZIP file, or an MSI file that bundles (or “chains”) other MSI files.

<Dbm/> nodes
Each node specifies a component of a <Msi/> node — typically, an MSI file. A node has the following structure, where GUID is the associated GUID, MSI is the path and filename of the MSI file, and name is a descriptive name for the MSI file:


Some nodes also require a condition.
If you want to apply an MST file to the specified MSI file, you can use the following syntax (whereMST is the path and filename of the MST file):
<Dbm productcode="{GUID}" file="MSI"
cmdline="TRANSFORMS=MST" progresstext="Str.ProgressText.name" />

nodes
Each node specifies a feature that is associated with an MSI file. A node has the following format, where name is the name of the MSI file and feature is the name of the associated feature:
.Feature.name"
desc="Str.Feature.name.Desc" property="feature">
Some nodes have subnodes.




nodes
Each node specifies a public property. A
node has the following structure, where property is the name of the public property and value is its value:

You can install the software faster by disabling log-file creation: Simply change the value of the ICA.LogOptions property to an empty string.

Creating a server image with a customized fileset
You can use Setup.xml to create a server image with a customized fileset.
To create a server image with a customized fileset

  1. Copy the server image to a new location.
  2. Add any desired language-module MSI files to the server image.
  3. Edit Setup.xml to reflect the additions you’ve made to the fileset:
    • Add an <Msi/> node for each new setup file.
    • Add a node for each new language-module MSI file.
    • Add the following node for each new languagemodule MSI file, where $$ is the language:

.$$" value="1" />

  1. Remove any unwanted MSI files from the server image. Some MSI files cannot be removed from the setup fileset.
  2. Edit Setup.xml to reflect the removals you’ve made from the fileset:
  • Remove the corresponding <Msi/> node for each removed setup file.
  • Remove the corresponding node for each removed MSI file.
  • Remove the corresponding node and subnode for each removed MSI file.
  • Adjust any corresponding nodes by changing their value.


For example, let’s say that you’re creating a single-language setup from a multi-language setup. To record the fileset changes in the Setup.xml file, you must remove the corresponding and nodes for each removed language module. Next, you must set each node for Include.$$ to a value of 0, where $$ is a removed language module. The node for
ShowApplicationLanguageSelector is automatically set to a value of 0.
Deploying customized installation settings
To modify the settings used to install the software on the workstations, you can use thePersist.xml file stored at the root of the server image.
Each entry in Persist.xml corresponds to a public property for the software ( see page 14). The syntax of each entry is as follows:

By modifying the value of an existing entry in Persist.xml — or by adding a new entry — you can customize the installation settings deployed from that server image. This deployment method offers an excellent alternative to creating a different server image or customizing a command line.
Example 1 The following Persist.xml entry specifies that automatic software updates are enabled:

By changing the value of this entry from "1" to "0" (and saving this change to Persist.xml), you can disable automatic updates for the workstation installations.
Example 2 The following Persist.xml entry specifies the serial number for the installation:

By changing the "SN"value, you can specify a different serial number for the workstation installations.
Deploying the software with msiexec.exe
Alternatively to using Setup.exe, you can deploy the software by using msiexec.exe — a Microsoft Windows Installer file provided by the Windows operating system. In fact, you must usemsiexec.exe if you want to interact directly with the MSI files, such as in the following scenarios:

  • if you want to use the Setup.msi file, rather than a start-up script, to install the software by using a Group Policy Object
  • if you want to use the Setup.msi file to create packages for use with Novell ZENworks Desktop Management

Command-line syntax
As with Setup.exe, you use msiexec.exe to create command lines that perform a setup-relatedfunction. A msiexec.exe command line requires the following items:

  • a switch that signals the desired action: creating a server image (/a); or installing (/i), repairing (/f), or removing (/x) the software
  • the location and name of the desired MSI file: typically, Setup.msi (located on the installation disc or on the server image).
  • any desired public properties
  • any desired switches, as specified by the CHAINER_CMD="switches" public property (multiple switches are separated by a space)


For example, the following msiexec.exe command line uses the file \\server\CDTS16\Setup.msi or Setup_x64.msi to install the software while displaying the full user interface:
msiexec.exe /i "\\server\CDTS16\Setup.msi"
ADDLOCAL="ALL" CHAINER_CMD="/qf"


MST files
As previously explained (see page 35), you can use the TRANSFORMS
public property to apply an MST file to the setup. By default, all MST files are applied to the Setup.msi file. If you want to apply an MST file to a different MSI file, you must use the following syntax (where MSI is the filename of the MSI file, not including its extension; and where MST is the filename of the MST file, including its extension):
TRANSFORMS_MSI="MST"

If the MST file is not in the same folder as the MSI file, MST must specify the full path and filename of the MST file.

For example, the following msiexec.exe command line uses the file \\server\CDTS16\Setup.msi or Setup_x64.msi to install the software silently, applies the transformation my_draw.mst to Draw.msi (in the same folder), and applies the transformation my_pp.mst to PHOTO_PAINT.msi (in the same folder):
msiexec.exe /i "\\server\CDTS16\Setup.msi"
ADDLOCAL="ALL" CHAINER_CMD="/qn"
TRANSFORMS_Draw="my_draw.mst"
TRANSFORMS_PP="my_pp.mst"

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.