Corel Painter 12 Network Deployment Guide Chapter 5 to Chapter 7


  • Chapter 5: Pulling the software to the workstations

    After you create a server image of Corel Painter 12 that meets the needs of your organization (see Chapter 3), you are ready to deploy the software to the workstations.

    This chapter shows you how to empower users to install (or pull ) the software to their own workstations. For information on using third-party technologies to push the software to the workstations on the users behalf, see Chapter 6.

    This chapter answers the following questions:

    • How can I best prepare for pull installation?
    • How do users pull the software?

    How can I best prepare for pull installation?

    Before users can pull the software to their workstations, you must do the following:

    Make sure that each workstation meets the minimum requirements for the software (seepage 12).

    Make sure that each workstation user has administrator-level access to the workstation and read-only access to the server image (see page 12).

    Properly configure any Group Policy Objects that you want to use to deploy the software (see page 47).

    In addition, it is highly recommended that workstation users map to the server image and set their workstations to log in to that server location at startup. Performing this step ensures that users are always connected to the server image.

    It is also recommended that you verify that all workstations are running the latest version of Microsoft Windows Installer.

    How do users pull the software?

    Users pull the software to their workstations by initiating the setup for 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. The following procedure describes how to pull a default installation to a workstation.

    To pull Corel Painter 12 to a workstation

    Browse to the location of the server image.


    Double-click Setup.exe


    If the Minimum system requirements dialog box appears, clickContinue to confirm that you are aware of the recommended minimum system requirements for the product.


    Read the license agreement in its entirety. To agree to its terms and continue the installation, enable the I accept the terms in the license agreement check box, and click Next


    Type your user name, and click Next.


    Specify where to install the software. To change the default location, click 


    Disable the Product updates check box if you do no want the software to detect and download product updates and service packs.


    Click Ito begin copying the files to the workstation.



    Chapter 6: Pushing the software to the workstations

    For best results in deploying Corel Painter 12 to your workstations, it is recommended that you have the users themselves install (or pull ) the software (as explained in Chapter 5).

    However, it is possible to push the software from the server image to the workstations. To do this, you use a command line (see Chapter 4) in conjunction with one of the following:

    a batch file a text file that can be scripted to run commands automatically. For help with using batch files, please see the Microsoft website.

    a Group Policy Object (or GPO anitem, stored in a central network location, that defines how the workstations are configured. For basic help with using GPOs, see Can I deploy the software by using a Group Policy Object? on page 47; for complete help, please refer to your Group Policy Software Development Kit.

    a push technology a third-party tool that is specially designed for installing software automatically. For detailed help with using a third-party push technology, please refer to the manufacturer s documentation.

    For many administrators, using a third-party push technology is the preferred push method.


    Chapter 7: Maintaining the software

    To keep your network running in top shape, it is important to know how to repair and update your workstation installations of Corel Painter 12.

    When you need to upgrade to the next version of the software, you must know how to cleanly remove the previous version from the network.

    This chapter answers the following questions:

    • How do I repair the software?
    • How do I update the software?
    • How do I remove the software?

    Some procedures in this chapter require the use of command lines. For detailed information on using command lines, see Chapter 4.

    How do I repair the software?

    Repairing Corel Painter 12 lets you install missing files, shortcuts, and registry entries, or replace corrupted items. You can repair a single installation of the software by using the Windows Control Panel for the workstation, or you can repair multiple installations simultaneously by using a command line.

    How do I repair the software by using the Windows Control Panel?

    You can use the Windows Control Panel to repair a single workstation installation of Corel Painter 12.

    To repair the software by using the Windows Control Panel:

    1. On the workstations, click Start >> Control Panel on the Windows taskbar.
    2. Do one of the following:
      • In Windows 7 and Windows Vista, click Programs Uninstall a program (or click Programs and features if you are using the Classic view of the Control Panel).
      • In Windows XP, double-click Add or remove programs.
    3. Choose Corel Painter 12 from the list, and then click Uninstall/ Change (for Windows 7 or Windows Vista) or Change/Remove (for Windows XP).
    4. Enable the Repair option, and then click Repair .
    5. Follow the instructions that appear.


    How do I repair the software by using a command line?

    You can use a command line to repair multiple workstation installations of Corel Painter 12 simultaneously.

    For more information on using command lines, see Chapter 4.

    What is the command-line syntax for repairing the software?

    To repair multiple workstation installations of the software by using the server image, you can build a command line that combines the Setup.exe file with either the /f switch or theREINSTALL and REINSTALLMODE public properties.

    The /f switch uses the following command-line syntax:

    Setup.exe /f

    The /f switch can be customized with the following parameters:

    reinstalls any missing files

    reinstalls any missing files, as well as any files for which an older version is installed

    reinstalls any missing files, as well as any files for which an equal or older version is installed

    reinstalls any missing files, as well as any files for which a different version is installed

    reinstalls all files

    rewrites all required user-specific registry entries (that is, the HKEY_CURRENT_USERand HKEY_USERS keys)

    rewrites all required computer-specific registry entries (that is, theHKEY_LOCAL_MACHINE and HKEY_CLASSES_ROOT keys)

    overwrites all existing shortcuts

    runs from the source files and re-caches the local package

    If you want greater control over how the software is repaired, you can use the following public properties instead of the /f switch:

    REINSTALL=ALL reinstalls all application features

    REINSTALLMODE= ''' specifies the type of reinstallation to perform. It is recommended that you use this property in conjunction with REINSTALL . The conditions for this property are the same as the parameters for the /f switch.


    The command-line syntax for these public properties is as follows: Setup.exe REINSTALL=ALL REINSTALLMODE= ''' The following sample command line automatically reinstalls all features. The use of the /q '''switch displays only a progress bar and a Cancel button, and the use of the /l '''switch logs all error messages to C:\ Logs\ repair.txt.Setup.exe REINSTALL=ALL /q '''b '''/l '''e '''"C: \ Logs\ repair.txt" The following sample command line specifies that the reinstallation run from the source files and re-cache the local package, reinstall missing and outdated files, rewrite all required user-specific and computer specific registry entries, and overwrite all existing shortcuts. The use of the /q '''switch displays only a progress bar and a Cancel button, and the use of the /l '''switch logs all error messages to C:\ Logs\ repair.txt.

    Setup.exe REINSTALL=ALLREINSTALLMODE= '''voums'''/q '''b '''/l '''e '''"C:\ Logs\repair.txt"

    How do I update the software?

    Corel periodically releases Microsoft patch (MSP) files, or patches, for its products. Installing patches helps keep the software up-to-date.

    A service pack is typically an executable file that combines multiple patches to make a major update to the software. One MSP file is included for each MSI file (see What is Setup.msi? on page 14) to be updated.

    In this guide, Patch.exe refers to the name of the executable file for the patch, although the actual filename varies with each patch.

    How do I locate available patches?

    Many network administrators keep their software up-to-date by monitoring the website for Corel Support Services (www.corel.com/support). When a patch is made available, these administrators download it and carry out the patching process themselves (as documented in How do I apply patches? on page 37).

    If you prefer, Corel Painter 12 can be configured to use an automatic update feature to detect when patches are available; however, you must enable this update feature on the server image if you want to make it available on the workstations that install from that server image. For information on using a command line to customize whether the update feature is made available to workstations, see How do I specify whether to allow automatic updates? on page 29.

    How do I apply patches?

    After locating and downloading a patch, you can apply it to the server image and then use the new server image to deploy the updated software to the workstations.

    To apply patches, you use command lines. For more information on command lines, see Chapter 4.

    From within the command line, you can access the basic help for the patching process by using the following syntax:

    Patch.exe /?

    However, detailed instructions follow.

    How do I apply a patch to the server image?

    You can apply the patch directly to the server image, or you can control the patching process by extracting the patch files before applying them.

    To apply the patch directly to the server image, use a command line that includes the executable file for the patch and the /a switch. Follow the instructions given in To create a server image on page 21, but change Setup.exe to the filename for the patch:

    Patch.exe /a

    If desired, you can include the path to the server image: Patch.exe /a "''' '''"

    To control the process of patching the server image, you can extract the patch files before applying them. To extract the patch files to a target location, use the following command-line syntax:

    Patch.exe /extract_all " ''' '''"

    To apply the extracted patch files to the server image, use the following command-line syntax:

    Setup.exe /a

    If desired, you can include the path to the server image: Setup.exe /a "''' '''"

    You can also include an /l switch (see page 26) if you want to create an installation log.

    If you choose to extract the patch files, it is important that you apply all of them to the server image. Applying only some of the patch files may cause the deployed software to function incorrectly.


    How do I deploy a patched server image to the workstations?

    After applying the patch to the server image, you are ready to deploy the patched server image to the workstations.

    To update the workstations, use the following command-line syntax:

    Setup.exe REINSTALL=ALL

    You can include a /q switch (see How much of the setup interface do I want users to see? on page 26)if you want to control how much of the user interface is displayed.

    You can include an /l switch (see page 26) if you want to create an installation log.

    You can include the REINSTALLMODE public property (see What is the command-line syntax for repairing the software? on page 35) if you want to specify one or more reinstallation conditions. The default conditions for the REINSTALLMODE property oumsare used if the property is not explicitly stated in the command line, or if no conditions are specified for it.

    Finally, you can include the REBOOT public property (see page 29) if you want to specify whether to reboot the workstation after applying the patch to it.

    The following sample command line patches the workstations, logging all error messages to C:\ Install Log\ Patch ServicePack.txt:

    Setup.exe /l '''e '''"C:\ Install Log\ Patch Service Pack.txt" REINSTALL=ALL REINSTALLMODE= '''vdm

    The following sample command line patches the workstations, displaying no user interface:

    Setup.exe /q '''n '''REINSTALL=ALL REINSTALLMODE= '''vdm

    The following sample command line patches the workstations, displaying only a progress bar and a Cancel button:

    Setup.exe /q '''b '''REINSTALL=ALL REINSTALLMODE= '''vdm

    The following sample command line patches the workstations, suppressing their reboot:

    Setup.exe REINSTALL=ALL REINSTALLMODE= '''vdm '''REBOOT=ReallySuppress

    How do I silently apply and deploy a patch?

    If desired, you can silently apply the patch to the server image and silently deploy it to the workstations by using the following command line:

    Patch.exe /s

    However, for best results, it is recommended that you apply and deploy the patch yourself, as previously described.

    How do I remove the software?

    You can remove Corel Painter 12 from your network. Cleanly uninstalling the software is crucial when the time comes to upgrade to the next version of the product.

    You can remove a single installation of the software by using the Windows Control Panel for the workstation, or you can remove multiple installations simultaneously by using a command-line.

    How do I remove a server image of the software?

    There is no application or functionality for automatically removing or uninstalling a server image of the software. You must manually delete the server image.

    Before doing this, we recommend that you remove all network-based workstation installations and make sure that the applications to be removed and their associated files are not currently in use. Also, if you are using Windows Terminal Server, make sure that all users are logged off.

    After the software image has been removed from the server, the only way to get it back is to re-create it by following the procedures for creating a server image (as explained in Chapter 3).

    How do I remove the software by using the Windows Control Panel?

    You can use the Windows Control Panel to remove a single workstation installation of Corel Painter 12.

    To remove the software by using the Windows Control Panel

    On the workstation, click' S'tart >> Control Panel on the Windows taskbar.


    Do one of the following:


    In Windows 7 and Windows Vista, click Programs >>Uninstall a program (or click Programs and features if you are using the Classic view of the Control Panel).


    In Windows XP,double-click Add or remove programs .


    Choose Corel Painter 12 from the list, and then click Uninstall/ Change(for Windows 7 or Windows Vista)or Change/Remove (for Windows XP).


    Enable the Remove option.


    By default, the Remove user files check box is enabled.If you do not want to remove user files (such as presets, user-created fills, and customized files), disable this check box.


    Click Remove .


    How do I remove the software by using a command line?

    You can use a command line to remove multiple workstation installations of Corel Painter 12 simultaneously. You can use either the / x switch or the /uninstall switch in this command line, as follows:

    Setup.exe /x or

    Setup.exe /uninstall

    The /x switch and the /uninstall switch perform a silent removal of all software associated with Corel Painter 12.

    If you want to customize the removal of the software, you cannot use the /x switch or the/uninstall switch. Instead, you must use the following public properties:

    REMOVE=ALL removes all features

    REMOVEUSERFILES= ''' specifies whether to remove user files. A value of does not remove user files, while a value of does remove them.

    If you want, you can further refine the custom removal with the /q switch (to suppress the user interface) and the /l switch (to create an installation log).

    The following sample command line removes workstation installations and all user files, displays a progress bar and information about the installation, and logs all error messages to C:'\ 'Install Log \ uninstall.txt :

    Setup.exe REMOVE=ALL REMOVEUSERFILES=1 /q '''r '''/l '''e

    "C: \ Install Log \ uninstall.txt"

    For more information on using command lines, see Chapter 4.
     



    Go to Knowledgebase

    Suggested Products: