Stage 3: Installing the software
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 workstations on their users’ behalf.
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.
Preparing for pull installation
To ensure that the pull-installation process runs as smoothly as possible, take the time to prepare for it.
- Confirm that each workstation meets the minimum requirements for the software
- Confirm that each workstation user has read-only access to the server image and administrator-level access to the workstation
- Map the workstations to the server image, and set the workstations to log in to that server location at startup. Doing so ensures that users are always connected to the server image.
- Confirm that all workstations are running the latest version of Microsoft Windows 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.
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.
To pull the software to a workstation
- Browse to the location of the server image, and double-click Setup.exe.
- Carry out the installation, specifying any desired options, by following the on-screen instructions.
To prevent installation problems, limit the installation path to 50 characters.
If you experience a scripting error, cancel the setup and try again. Doing so will resolve the error by installing required components of the Microsoft .NET Framework.
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
Using this command line, you can install the software on the workstations by using any supported push method.
Specifying the setup file
The most important item to specify in your command line is the executable file for the setup: theSetup.exe file on the server image you want to use:
- \\server\path'''\x86\Setup.exe — to push the 32-bit version of the software to 32-bit or 64-bit operating systems
- \\server\path'''\x64\Setup.exe — to push the 64-bit version of the software to 64-bit operating systems
You cannot use the 64-bit version of the software on 32-bit operating systems. If your path contains spaces, you must place quotation marks around it: "\\server\path containing spaces\Setup.exe"
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 see “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
Use /l to log installation events.
Parameter What it logs
i Status messages
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 server installation
p Terminal properties
* All of the above, in a single log file
NOTE: Alternatively to /l*, you can use /log.
v Very detailed information
The default parameters for /l are iwearmo (/liwearmo "c:\install 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 (Temp) 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"
/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).
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 /qn, you can use /quiet.
Basic UI: a progress bar and a Cancel button. If the user pushes the Cancel button, the installation is rolled back upon confirmation.
NOTE: Alternatively to /qb, you can use /passive.
Basic UI: only a progress bar. The user cannot cancel the installation.
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).
Reduced UI: A progress bar, along with a page containing information about the installation. The user can cancel the installation.
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.
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 general information on public properties, along with details on property syntax, please see theCorel Beginner’s Guide to Network Deployment.
For a list of all command-line properties for Microsoft Windows Installer, please see the Microsoft website.
Pointing installations to the extra content
You can give users access to the extra content installed from the program DVD, along with the videos downloaded from the FTP site, by placing it at a shared location on the server. To point the installations to this location, use the following property: ="path"
For best results, do not end path with a backslash ( \ ).
Opting out of desktop shortcuts
You can prevent the installation of desktop shortcuts by using the following property:DESKTOPSHORTCUTS=0
Suppressing the software-requirements check
By default, the setup checks whether the computer meets the minimum software requirements before proceeding with the installation. To suppress this check, use the following property:
Suppressing the EULA prompt
If the software is installed silently, 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:
If you choose to suppress the EULA prompt on the workstations, you are accepting the terms of the EULA on behalf of all users on your network when you create the server image.
Customizing the installation path
When deploying from the server image, use the following public property to customize the installation path of the software:
For best results, do not end the path with a backslash ( \ ).
Handling reboots , The REBOOT property is used with one of the following values to specify how the installation process handles any required reboots.
Force (or F)
Prompts for reboot after installation. If the setup UI is suppressed, the computer is automatically rebooted after installation.
NOTE: Alternatively to REBOOT=Force, you can use the /forcerestart switch.
Suppress (or S)
Prompts for reboot during installation (if required), but reboots automatically after installation. If the setup UI is suppressed, all required reboots are automatic.
NOTE: Alternatively to REBOOT=Suppress, you can use the /promptrestart switch.
Suppresses all reboots and all reboot prompts, both during and after installation.
NOTE: Alternatively to REBOOT=ReallySuppress, you can use the /norestart switch.
Inputting the user name, To input the user name for the installation, use the following property:
Running your command line
Your command line can be used to push the software to the workstations through any of the following:
- a batch file — see the Microsoft website for details
- a GPO — see the Group Policy SDK for details
- a third-party push technology — see the manufacturer’s documentation for details
For many administrators, using a third-party push technology is the preferred push method. This section offers general guidelines on using a few such technologies.
At the time of this writing, Corel has verified support for Microsoft® System Center Configuration Manager (SCCM) only insofar as its Microsoft Systems Management Server (SMS) components.
For complete information on using SCCM, please see the Microsoft website.
For deployment to the workstations on a “per-system” basis using package definition files (or “packages”), CorelDRAW Technical Suite X6 supports the use of Microsoft Systems Management Server (SMS).
You can create a package from scratch — or you can create one from the existing SMS files included with CorelDRAW Technical Suite X6 (in the Administrator folder on the installation disc or the server image).
For complete information on using SMS files, please refer to your resource kit for Microsoft Systems Management Server.
The recommendations posted on the Microsoft website have not been tested with CorelDRAW Technical Suite X6 and must therefore be used at your discretion.
For deployment to the workstations, CorelDRAW Technical Suite X6 supports the use of the IntelliMirror technology, which is part of the Windows Server 2003, Windows Server 2008, and Windows Server 2008 R1 operating systems.
“Per-user” installations are not supported.
To make deployment with IntelliMirror as easy as possible, CorelDRAW Technical Suite X6 includes a ZAP file (in the Administrator folder on the installation disc or the server image).
For complete information on IntelliMirror, please see the Microsoft website.