How do I register an MSP (Microsoft Patch) to an existing package in my software package library?

Document ID : KB000027875
Last Modified Date : 14/02/2018
Show Technical Document Details


As new fixes get release by vendors it may be come necessary to make sure that CA Client Automation Software packages have these latest fixes included so they do not have to create a separate job to upgrade the software. In the below example we will list the steps needed to add an install procedure to apply SP 3 to the existing Office package. 



How do I register an MSP (Microsoft Patch) to an existing package in my software package library?



CA Client Automation - All Versions 



As a prerequisite, you must be sure to have the "Administrative Full File" MSP and not the "Client Binary" MSP. For the purposes of this example, I already have an OFFICE XP package or later in my DSM software package library and I would like to add Service Pack 3 to it.

  1. In the DSM gui Software Package Library, locate the Office XP package and expand it's procedures. Right Click and select the option for 'New added procedure with new files'.

  2. In the General Tab

    1. Enter a name for the Pack 3.
    2. Change the task to configure.

    Figure 1

  3. In the Added Files Tab:

    1. Change the Type to "MSI File".
    2. Enter the path to the MSP file.
    3. Enter the name of the MSP file.
    4. In the 'General sub pane, change the 'MSI Method' depending on whether you wish to patch and administrative install point, or an existing intallation.

    Figure 2

  4. Click 'OK'.
  5. The Patch will then be copied to the Office XP Package in the Software Package Library and you will see an added procedure under it's procedures now called "Service Pack 3".
  6. To Patch and Administrative install point, you would need to create a new procedure using exactly the same steps, with the exception of that in the Added Files tab, you would want to change the MSI Method to 'Patch an Administrative Install point'.

    Figure 3