Resources

At Library > Resources, you can manage Resources. Resources can contain any file that is needed to perform a certain Task, such as MSI files, setup files, patches, hotfixes, etc.

For example, if you want to install a certain application or security update on an Agent by using a Task Perform Unattended Installation, you first need to store the necessary files as a Resource before you can use them in the Task.

Resources can be stored in the following formats:

  • Stored in Datastore: This storage method may take a bit longer at the first upload, but the Resource can be used repeatedly without requiring additional credentials. This storage method supports single files only.
  • Located on fileshare: Although this is the fastest storage method, it can severely affect network traffic: Agents will download the Resource directly from the file share; it is not downloaded by the Dispatchers first. This storage method requires credentials to access the share each time the Task is run and the availability of the Resource also depends on the availability of the share. Choose this method if the Resource is too large to be stored in the Datastore or cached on Dispatchers. This storage method supports single files only.
  • Located at URL: Similar to Resources stored at a fileshare, this type of Resource makes it possible to refer to Resources that are stored at a certain Internet location. However, it can severely affect network traffic: Agents will download the Resource directly from the URL: it is not downloaded and cached by the Dispatchers first. The availability of the Resource depends on the availability of the Internet site. The functionality also supports URL redirection. This storage method can be used for Agents using Windows, Apple macOS and Linux (only RedHat, Suse, Ubuntu). For all Agents, except the Windows Agents, applies that a LibCurl library must be installed.

  • Use the Name field to specify a name for the Resource. The filename of the Resource is used as a back-up. When the filename cannot be retrieved from the URL header, it will use the filename from the Resource.

  • In the Download location field, URLs must start with "http://" or "https://" (not "file:// or ftp://).
  • Ivanti Automation Resource Package: Use this storage method if a Resource consists of a set of files (for example, a Microsoft Office installation). All files are stored in the Datastore.

Configuration

  • Use the Folders tab to group Resources into folders. Grouping Resources in folders can be useful in large environments and multi-tenant Ivanti Automation sites to easily locate any Resources you have created and also to create folders for various needs. You can use Resource folders for example to:
  • Use the Resources tab to view a alphabetical list of all Resources, without the folder structure.
  • To save an existing Resource to an external location (for example, a share or a USB drive), select it in the list and click Save Save Resource in the command bar. This functionality is only available for Resources that are stored in the Datastore and Resource packages (Resources stored on a file share are already stored on an external location).
  • To scan for unused Resources, right-click either the Folders tab or the Resources tab and choose Scan for unused Resources. You can safely delete all Resources that were never used. If a Resource has previously been used in a Job, you should probably not delete it: you will need it again to reschedule that Job or to reapply the Job History of the Agent. Information about the latest timestamp of a job containing the Resource and how many times the Resource was part of a job can be found in the Console, using the Resources view and not the Folders view. Please refer to “Last Run (UTC)” and “Run Count” columns in order to better appreciate if the Resources should be removed or not.
  • To convert an existing Resource from Stored in Datastore to Located on fileshare or the other way round, right-click a Resource and choose Convert. Resources cannot be converted to or from the Ivanti Automation Resource Package format. The conversion and its settings are only applied to Resources to which they are applicable. For example, special actions are only set for Resources of the relevant storage method and file type.
  • When saving changes to the Resource, the Version Control window will be opened. This window makes it possible to configure the versioning of changes to the Resource. The availability of this window depends on the global setting Use silent versioning.

When configuring a Resource:

  • Use the Resource tab to select the file(s) that should be stored as a Resource.
  • Use the Properties tab to view the properties of the selected file. This tab is only available for Resources that are stored in the Datastore or that are located on a file share.
  • Use the Contents tab to configure the contents of the Resource package. This tab is only available for Resources that are stored as Ivanti Automation Resource Packages.
  • Use the Usage tab to view in which Modules, Projects, and/or Run Books the Resource is used.
  • Use the Versioning tab to view a list of changes made to the Run Book, including all known versions of the Run Book.
  • Use the Trusts tab to define trusted Agents and Teams for the Resource. This tab is only shown if Trusts Security has been enabled.
  • Use the Permissions tab to view the level of access that Console users have to the Resource.

  • The Edit button allows you to edit any file type, as long as an editor is associated with it. This option is available for Resources stored in the Datastore or on a file share.

  • You can disable a Resource. If a Resource is disabled, you can no longer add it to a Task. However, it is still enabled in existing Tasks.