This section covers the general procedure for snapshot installations. The basic procedure is the same, regardless of which third-party tool you use. However, the exact procedure for generating the snapshot image will naturally vary depending on the tool.
Note: The snapshot image used when testing these instructions was a RapidInstall Package (RIP), created with Altiris RapidInstall 3.1. You may find other third-party tools to be equally effective but these have not been tested.
Some pre-configuration of the source machine is necessary to ensure that the final snapshot image contains the correct CA DataMinder installation information.
Find this script in the \Support folder of the CA DataMinder distribution image.
The transform prevents CA DataMinder starting automatically after installation. This is necessary to prevent your source machine starting the CA DataMinder service automatically after step 5.
msiexec /i <path to client.msi> TRANSFORMS=<path to DisableAutostart.mst>
Where client.msi is your administrative source image for client machines. Find a copy of client.msi in the \Windows folder in your CA DataMinder distribution image>.
For details about DisableAutostart.mst and the TRANSFORMS property in Msiexec.exe commands, see the references at the end of this section.
Using your preferred snapshot tool, create a baseline image of your source machine. This is an image of the machine before CA DataMinder has been installed.
For example, if you are using RapidInstall 3.1, you can now set a baseline using the Altiris RIP creation wizard. Proceed to the Installing Applications screen, then stop and create a baseline image.
This launches the CA DataMinder client installation wizard in a separate window.
Alternatively, if you want a generic snapshot that can be easily customized and reused to install clients to different parent servers, you can enter a ‘placeholder’ IP address and select the Bypass Validation check box. This approach allows you to deploy several versions of the snapshot (for example, one for each department in your organization), with each version specifying a different gateway as the parent server.
Note: The placeholder address can be the address of any real machine that is not a CMS or gateway server. You must specify a real machine, otherwise the installation will fail and the snapshot will be incomplete.
Create a snapshot image of the changes made by the CA DataMinder installation wizard.
For example, if you are using RapidInstall 3.1, you can resume the Altiris RIP creation wizard and proceed to the Build RIP screen.
Typically, third-party tools let you configure the snapshot image, for example, to automatically reboot the target system after installation. Now is the time to configure the snapshot to meet your deployment requirements.
If you anticipate a future need for follow-up snapshot images (for example, to install CA DataMinder features omitted from the original snapshot), we recommend you now create and save a follow-up baseline image at this stage. This is an image of the source machine after CA DataMinder has been installed. You can then retrieve and use this baseline to generate future follow-up snapshots.
To deploy the snapshot to your target client machines, choose any method that best suits your organization. For example, you can attach the snapshot to an e‑mail and send it to your users; you can save the snapshot to a shared network location; or you can include it in a login script. However:
default.parent=<placeholder parent>
Where <placeholder parent> is the name of the machine whose IP address you specified in step 2. Now change this line to:
default.parent=<actual parent>
Where <actual parent> is the name or IP address of your CMS or a gateway server. See the previous column for an example file extract.
|
Copyright © 2014 CA.
All rights reserved.
|
|