As mentioned in Chapter 3, you use a command line to create a server image.

Similarly, you use a command line to deploy the software to the workstations from that server image. To do this, you assemble a command line that specifies the installation settings that you want to provide or enforce. In this way, you can control the installation type of the software, the amount of interaction that users have with the setup, the creation of log files, and other installation options.

After assembling your command line, you are ready to deploy the software to the workstations. To do this, you can allow users to pull the software by initiating the setup themselves (see Chapter 5), or you can use a third-party technology to push the software to users workstations (see Chapter 6).

This chapter answers the following questions:

How do I assemble a command line?

How do I run my command line?

What else can I do with command lines?

You can also use command lines to automate the following tasks:

repairing existing installations of the software (see page 45)

updating the software on the workstations (see page 48)

removing the software from the workstations (see page 51)

How do I assemble a command line?

There are three steps to assembling a command line:

Step 1: Specify the executable file.

Step 2: Define the deployment process with switches.

Step 3: Refine the installation with public properties. This section describes these three steps in detail.

Step1: Specify the executable file

The first item to specify in the command line is the executable file for the software: Setup.exe. Therefore, the basic component of every command line is as follows:

Setup.exe

All command lines in this guide are designed to run the Setup.exe file from its source directory on a typical server image. Your deployment scenario may require you to specify a path to a specific Setup.exe file for example, if you have created multiple server images (as outlined on page 21).The syntax for specifying a path is as follows:

server\path\Setup.exe

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

\server\path\Setup.exe"

Alternatively to using the Setup.exe file to deploy the software, CorelDRAW Graphics Suite X5 supports using the msiexec.exe file. For information, see Can I deploy the software by using the msiexec.exe file? on page 63.

Step 2: Define the deployment process with switches

To define the deployment process, you can use command-line switches, which signal installation options.

The syntax for a switch consists of a forward slash ( / ) immediately followed by a character or string for example, /q or /quiet. Typing a space on both sides of a switch separates that switch from other command-line elements. You can use one or more switches in a single command line, but be sure to separate them with spaces as you would do for any other command-line element.

Some switches have parameters , which let you tweak the settings. In fact, witches let you use multiple parameters for the same switch. If you do not specify any parameters, the switch uses its default settings.

To use a parameter, simply type the parameter immediately after the switch. Do not type a space between a switch and its parameters or between the parameters in one switch.

To customize a command line for installing the software, ask yourself the following questions:

How much of the setup interface do I want users to see?

Do I want to create an installation log?

For a complete list of command-line switches available for the software, see What are the available command-line switches? on page 54.

How much of the setup interface do I want users to see?

switch can be used to restrict the amount of the user interface that appears during installation. You can use the switch to prevent users from entering their own registration information, to help enforce specific installation options, or even to perform silent installations , in which no user interface is visible during the setup.

The /q switch can be used in conjunction with one of the following parameters:

n The user does not see the user interface during installation. Errors are recorded in a log file. (For more information, see Do I want to create an installation log? on page 30.)

b The user sees only a progress bar and a Cancel button. If the user pushes the Cancelbutton, the installation is rolled back.

b! The user sees only a progress bar and cannot cancel the installation.

b+ The user sees only a progress bar and a Cancel button. If the user pushes the Cancelbutton, the installation is immediately rolled back. (The user is not prompted to confirm the cancellation request.)

r The user sees a progress bar, along with a page containing information about the installation. The user can choose to cancel the installation.

f The user sees the full user interface.

Here is a sample command line that suppresses the user interface during installation and records any errors in a log file:

Setup.exe /qn

or

Setup.exe /quiet

Although you can use the /q switch to create a server image, you must proceed with extreme caution to avoid suppressing any registration prompts for the software. In this scenario, you can preset the destination of the installation files by including the public property TARGETDIR=in your command line. For information on creating a server image, see Chapter 3.

Do I want to create an installation log?

Use the /l switch if you want to log general information about the installation to a log file with the specified path and filename. If you do not specify a path and filename, the log file is created in the current user s temporary( Temp) folder.

• applies all parameters except v and x, recording all information in a single log file

The default parameters for the /l switch are iwearmo. Here is a sample command line that uses the /l switch with its default parameters:

Setup.exe /l

If you want to specify a Deployment of CorelDRAW graphics Suite X5 to the workstations begins with the creation of a server image of the software. This chapter answers the following questions:

How can I best prepare for creating the server image?How do I create the server image?

How do I finalize the image?

Setup.exe /l "< path>"

The following sample command line uses the default parameters of the /l switch to log installation information to the file C:\ install.txt during installation:

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

You can use the /q and /l switches together. The following sample command line uses the /q switch to suppress the user interface during installation and record errors in the log file specified by the /l switch:

Setup.exe /qn /l "C: \Logs\My_Log.txt"

Step3: Refine the installation with public properties

Finally, to refine the installation of the software on the workstations, you can use public properties command-line elements that are shared outside the application. When you deploy software by using command lines, you can use public properties to set the values of various installation properties (such as the information found in the Customer information and Choose destination location dialog boxes). You can also use public properties to specify the installation type and the features to be installed.

Public properties are case-sensitive; they must be typed in capital letters, and they cannot contain spaces. To use a public property in a command line, you must type the name of the public property in capital letters, followed directly by an equals sign ( = ), followed directly by the desired value.

Values are also case-sensitive, but they can contain both uppercase and lowercase letters. A value can be a text string (such as a feature name) or a number. It s a good idea to use quotation marks around a value so that it is read as a single unit, particularly if that value contains spaces. By combining public properties, you can successfully customize the installed software to accomplish various tasks.

How do I prevent the setup from checking the system requirements?How do I apply MST files?How do I specify customer information?How do I customize the destination of the installation files?How do I specify where extra content is located on the server?How do I specify how features are installed?How do I specify whether to allow automatic updates?How do I specify whether to reboot after installation?

For an at-a-glance list of all available public properties, see What are the available public properties? on page 55.

How do I prevent the setup from checking the system requirements?

By default, the setup checks whether the workstations meet the minimum system requirements for the software (as listed on page 11). If you want to suppress this check, use the following public property:

IGNORE_LAUNCH_CONDITIONS=1

How do I apply MST files?

If you have used a third-party product to create a Microsoft transformation(MST)file for customizing the software(see What are MST files? on page 16), you must refer to the MST file from within your command line. First, store the MST file on the server image. Then, build a command line that pairs the TRANSFORMS property with that MST file, as demonstrated by the following syntax(where is the filename of the MST file):

Setup.exe TRANSFORMS=<"MST>"

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

By default, the MST file is applied to the Setup.msi file for the setup (see What is Setup.msi? on page 14). If you want to apply an MST file to a different MSI file, you must use the following syntax (where is the filename of the MSI file, not including its extension; and where is the filename of the MST file, including its extension):

Setup.exe TRANSFORMS_=""

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

For example, to apply my_draw.mst to Draw.msi (in the same folder), you would use the following syntax:

Setup.exe TRANSFORMS_Draw="my_draw.mst"

To apply MyTransform.mst to Pexp_EN.msi (in the same folder), you would use the following syntax:

Setup.exe TRANSFORMS_PP="MyTransform.mst"

If you have trouble applying your MST file, do the following:

Check the syntax of your command line, particularly the path to the MST file.

Check your permissions.

Make sure that the MST file was created correctly. Check the associated MSI files.

For additional help with MST files, contact Corel Support Services (www.corel.com/support); please note that charges will apply.

How do I specify customer information?

To install the software, you must provide the setup with customer information. You can use any of the following public properties to input this information into the Customer informationdialogbox:

USERNAME=" " specifies the user name

SERIALNUMBER=" " specifies the serial number

How do I customize the destination of the installation files?

When deploying software from the server image to the workstations, you can set the destination of the installation files (as in the Choose destination location dialog box) by using the following public property:

• INSTALLDIR=""

How do I specify where extra content is located on the server?

You can give users access to the extra content from the

CorelDRAW Graphics SuiteX5 DVD by copying the content files to a shared location on the server.For important details, see How do I provide access to extra content? on page 24.

To configure CorelDRAW and Corel PHOTO-PAINT to access this server location, you can edit the associated registry settings (also described on page 23), or you can use the following public property:

CLIPARTSOURCEDIR="" specifies the server location of the content files

How do I specify how features are installed?

When performing a basic installation (by using the /qb switch) or a silent installation (by using the /qn switch) as discussed on page 29, you may want to specify how some or all features are installed. To do this, you specify each desired feature as a value of the appropriate public property. If you want to combine features in a single value, separate them with commas (but no spaces).

For a list of the features that are available to the software, see What are the available features? on page 58.

Please note that some parent features have child features that are stored under them. Specifying a parent feature does not include its child features; you must individually specify each desired feature.

Here are the public properties that you can use to specify how features are installed:

ADDLOCAL= installs the feature to the workstation. To install all features to the workstation, use ADDLOCAL=ALL.

ADDSOURCE= sets the feature to run from the network. To set all features to run from the network, use ADDSOURCE=ALL.

By using these public properties, you can specify how you want to install individual features. Unspecified features are installed only if they are required.

Please note that not all features can be set to run from the network. For details on each available feature, see What are the available features? on page 58.

Lets say, for example, that you want to locally install only the files that are required to run CorelDRAW and Corel PHOTO-PAINT. In this case, you d use the following syntax:

ADDLOCAL=DRAW,PP

or

ADDLOCAL=DrPFiles,PPPFiles

To instead set CorelDRAW and Corel PHOTO-PAINT to run from the network, you d use the following syntax:

ADDSOURCE=DRAW,PP

or

ADDSOURCE=DrPFiles,PPPFiles

You can combine the ADDLOCAL and ADDSOURCE public properties in the same command line. This technique lets you simultaneously set some specific features to install locally and other specific features to run from the network.

For example, let s say that you want to locally install only the files that are required to run CorelDRAW and Corel PHOTO-PAINT, and that you want set the user guide to run from the network. In this case, you d use the following syntax:

ADDLOCAL=DRAW,PP ADDSOURCE=UseGuide

or

ADDLOCAL=DrPFiles,PPPFiles ADDSOURCE=UseGuide

Please note, however, that applications are always installed to the same location. If you specify some applications to install locally and others to run from the network, the first public property specified is the one that determines the location of all installed applications.

For example, the following syntax sets both CorelDRAW and Corel PHOTO-PAINT to install locally, because the local installation is specified first:

ADDLOCAL=DRAWADDSOURCE=PP or

ADDLOCAL=DrPFiles ADDSOURCE=PPPFiles

However, the following syntax sets both CorelDRAW and Corel PHOTO-PAINT to run from the network, because the run-from-network installation is specified first:

ADDSOURCE=DRAWADDLOCAL=PP

or

ADDSOURCE=DrPFiles ADDLOCAL=PPPFiles

You can also specify the language of the user interface for the software. (If you don t specify a language, then the language of the operating system becomes the default user-interface language of the software.) If you want to provide multiple user-interface languages, you can set up dynamic language switching.

To make a user-interface language available, you must install the feature for that language module:

CZ displays a check box for installing the Czech user interface at startup, and installs the Czech writing tools

DE displays a check box for installing the German user interface at startup, and installs the German writing tools

EN displays a check box for installing the English user interface at startup, and installs the English writing tools

ES displays a check box for installing the Spanish user interface at startup, and installs the Spanish writing tools

FR displays a check box for installing the French user interface at startup, and installs the French writing tools

IT displays a check box for installing the Italian user interface at startup, and installs the Italian writing tools

KR displays a check box for installing the Korean user interface at startup

JP displays a check box for installing the Japanese user interface at startup

MA displays a check box for installing the Hungarian user interface at startup

NL displays a check box for installing the Dutch user interface at startup, and installs the Dutch writing tools

PL displays a check box for installing the Polish user interface at startup, and installs the Polish writing tools

RU displays a check box for installing the Russian user interface at startup, and installs the Russian writing tools

SU displays a check box for installing the Finnish user interface at startup, and installs the Finnish writing tools

SV displays a check box for installing the Swedish user interface at startup, and installs the Swedish writing tools

So, for example, let s say that you want to locally install only the files that are required to run CorelDRAW and Corel PHOTO-PAINT; the writing tools; and the language modules for English, French, and German. In this case, you d use the following syntax:

ADDLOCAL=DRAW,PP,WTools,EN,FR,DE

or

ADDLOCAL=DrPFiles,PPPFiles,WTools,EN,FR,DE

How do I specify whether to allow automatic updates?

The property for controlling whether to allow for automatic updates (and in-product messaging) is ALLOW_PRODUCTUPDATES. You can use this property when installing from the server image or the installation disc. By default, automatic updates are enabled when installing from the installation disc but not from the server image.

To enable automatic updates (and in-product messaging), specify ALLOW_PRODUCTUPDATES=1 , as in the following example:

Setup.exe ALLOW_PRODUCTUPDATES=1

To turn off automatic updates (but not in-product messaging), specify either ALLOW_PRODUCTUPDATES=0 or nothing at all. (Remember: By default, automatic updates are not enabled for workstations installed from a server image.) For additional information on updating the software, see How do I update the software? on page 48.

How do I specify whether to reboot after installation?

The REBOOT property allows you to specify whether users are prompted to reboot after installation. The REBOOT property is used with one of the following values:

Force (or F ) always prompts for a reboot after installation. If the user interface has been suppressed, then the computer is automatically rebooted after installation.

Suppress(or S ) reboots automatically after installation. If a reboot is required during installation, the user is prompted to reboot unless the user interface has been suppressed (in which case, the computer is automatically rebooted).

ReallySuppress (or R ) suppresses all reboots and all reboot prompts, both during and after installation

You can also use the following switches as alternatives to the REBOOT public property:

/forcerestart same as REBOOT=Force /promptrestart same as REBOOT=Suppress /norestart same as REBOOT=ReallySuppress

How do I run my command line?

As you can imagine, your final command line could end up looking quite complex.

So, now that you know how to assemble command lines, how do you use them to deploy the software to the workstations? Some network administrators choose to create a batch file that runs the command line. However, for best results, it is recommended that you use your command line to either pull (see Chapter 5) or push (see Chapter 6) the software to the workstations.