Quantcast
Viewing all articles
Browse latest Browse all 1056

How to pre-stage Distribution Packages Through the Management Gateway

Staging Files


LDMS 9.6

  1. Schedule your Distribution Task.
  2. Right Click on the task and select Properties.
  3. Go to the Task Setting page, and select the following options.
    1. Task Type: Policy OR Policy Supported Push
    2. Download Options: Pre-cache
  4. Save the task settings.
  5. Add targets and run task.

 

LDMS 9.5

  1. In the Management Suite Console go to: Tools - Distribution - Delivery Methods.
  2. In the Delivery Methods tool, expand My Delivery Methods.
  3. Right click on Policy, and select New Delivery Method.
  4. On the Network Usage page of the settings, under "File Transfer/Source Download Options" select Pre-cache.
  5. Other setting can be set as desired. Save the settings once complete.
  6. Schedule the distribution package.
  7. Right click the scheduled task, select Properties.
  8. On the Delivery Method page, select Policy, and select your new Pre-cache method from the list of available delivery methods.
  9. Save the task.
  10. Add targets and run task.


Legacy Delivery Methods


When using the Management Gateway on Legacy versions of LDMS 9.0 and older, only Policy-based Delivery Methods can be used.  Such Delivery Methods do not allow for pre-staging a file but always run the primary file of the Distribution Package.

 

Workaround

 

In order to pre-stage a Distribution Package create a copy of the Distribution Package and move the current Primary File to be an additional file and replace the Primary File with a blank batch file.  Even though the Primary File will always run, it now does not matter because a blank batch will of course do nothing and will always run successfully.

 

Note:

 

This is also very useful to pre-stage files in environments where Multicast is either not desired or not functional.


Viewing all articles
Browse latest Browse all 1056

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>