Adding a hotfix to the Depot

Adding a hotfix to the Depot adds all files necessary to perform an unattended installation of that hotfix.

When you initiate the process of adding a hotfix to the Depot by running a Snapshot or Audit Job, the system automatically provides all information required by the Add Depot Software wizard. Source files are downloaded to the Depot from repositories maintained by trusted organizations. You do not have to provide install and uninstall commands as you do when adding other types of software to the Depot.

Alternatively, when adding a hotfix to the Depot, you have the option of specifying a source file rather than using the pre-identified source files as you do when browsing server objects or running a Snapshot or Audit Job. If you specify a source file, you may have to manually enter information that the Add Depot Software wizard requires.

To add all types of software to the Depot other than hotfixes — including custom software — you can use a similar procedure. See Adding-software-to-the-Depot-from-snapshot-results.

After adding a hotfix to the Depot, you can deploy it using a Deploy Job. For a description of this procedure, see Creating-a-Deploy-Job.

Adding a hotfix to the Depot

  1. Perform one of the following actions to open the Add Depot Software wizard:
    • Using the Depot folder, right-click the depot folder where you want to add the software package. From the pop-up menu, select New > Software > Hotfix.
    • Using the results of a Snapshot Job, select the hotfixes that should be added to the Depot. For more information, see Adding-software-to-the-Depot-from-snapshot-results.
    • Using the Select Matching Software window, you can add hotfixes to the Depot, as described in Matching-software-with-depot-items. The Select Matching Software window appears in many contexts throughout the TrueSight Server Automation Console.
  2. In the Select Installable Sources dialog box, select the installable file.
    The Select Installable Source dialog box provides options for accessing the installable file. Use the hierarchical tree to browse to the location where the installable file is saved and select the file.You can browse and select the source file from the following locations:
    • Servers
    • Local Computer
    • Web Repositories New
    Alternatively, you can manually enter the path to the installable file by using the Source Location field. The file paths can include parameters. You can enter parameters manually or click Select Propertyg_V95_SelectPropertyIcon.gif, see Inserting-a-parameter for more information.Depending on how you want to access the installable file, select either of the following option buttons:
    Field
    Descriptions
    Upload source to File Server
    Select this option if you want to copy the installable file to the file server. When you select this option, you cannot edit the contents of the Source Location field.
    Refer to source at its current location
    Select this option if you want the installable file to reside at network location until deployment. When you select this option, you cannot use the hierarchical tree to select the source files. Under Refer to source at its current location, select one of the following options:
    • Copy to Agent at staging — The Application Server copies the installable file to a staging directory on the agent during the staging phase of a Deploy Job.
       To use this option, the Source Location field must provide a URL that complies with TrueSight Server Automation requirements for network data transmission, including a data transmission protocol of RSCD, NFS, or SMB. For details about the required syntax, see URL-syntax-for-network-data-transmission.
    • Agent mounts source for direct use at deployment (no local copy) — The Deploy Job instructs an agent to mount or map the device specified in the URL and deploy the software package directly to the agent. When you select this option, the agent uses the data transmission protocol specified in the URL to access the specified source files. The installable file is not copied to a staging area on the agent, so no local copy of the source file is created.
       To use this option, the Source Location field must provide a URL that complies with TrueSight Server Automation requirements for network data transmission, including a data transmission protocol: either NFS or SMB. For details information about the required syntax, see URL-syntax-for-network-data-transmission.
      Note(Only for Windows 2012 targets) Before you enable the Agent mounts source for direct use at deployment (no local copy) option, you need to add the mounted device in the security zone of the target. This can be done by making the following changes to the registry of the target.
      1.  Under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscRanges\, create a key with the name Range1. If key Range1 already exists, create a key with the next available number (for example Range2, Range3, Range4 and so on).
      2. Create the following values under the Range1 key:
        Value Name
        Value Data
        :Range
        <mountedDeviceIPAddress>
        file
        1 hexadecimal

  3. Provide information for the wizard, as described in the following sections:

  4. After completing the last step of the wizard, click Finish.
    A background process saves the patch or hotfix to the Depot. Depending on how you have specified behavior for background processes, either a dialog box opens or the Show background operations icon appears in the lower right corner of the console. Both indicate an operation is running in the background.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*