Endpoint Integration Guide › Endpoint Deployment › Snapshot Operations › Follow-up Snapshot Installations

Follow-up Snapshot Installations

If required, you can deploy follow-up snapshot images to machines already running CA DataMinder. For example, if you initially chose not to deploy the Application Integration feature to client machines, you could configure a follow-up snapshot to have the additive, or cumulative, effect of installing Application Integration on top of existing CA DataMinder installations. The procedure is summarized opposite:

The basic idea is straightforward: On your source machine, you rerun the CA DataMinder installation wizard on your source machine and choose any new features you want; you then create and deploy a follow‑up CA DataMinder snapshot. In detail, you must:

1. Specify the follow-up baseline image

   Using your preferred snapshot tool, start creating a new snapshot image. First, specify the baseline image.

   To ensure the follow-up snapshot only contains the latest modifications by the CA DataMinder installation wizard, you must generate the snapshot from a baseline image of your source machine immediately after the original CA DataMinder installation. This is why we recommend that you create and save a follow-up baseline image directly after creating the original snapshot. However, if you need to recreate this baseline, you must:

   1. Rebuild your source machine.
   2. Rerun the original CA DataMinder installation (step 5, If you want to customize the CA DataMinder installation, (for example, omitting the CA DataMinder consoles), do so in the Custom Setup screen; see step 3 in Manual installations (setup.exe).).
   3. Create a new baseline image.
2. Modify the original CA DataMinder installation

   Rerun the installation wizard and choose the new features you want to add (or the features you want to uninstall).

3. Create a follow-up snapshot

   Using your preferred snapshot tool, create a snapshot image of the changes made by the CA DataMinder installation wizard.

   Unlike the original snapshot, this time you do not need to edit startup.properties.

4. Deploy the follow-up snapshot

   Now deploy the snapshot to your target client machines, using any method that best suits your organization.