You must perform the following steps to be able to use Empirum-PatchManagement:

1. Enter the respective license key under Licensing.
2. Install the Empirum Activation Service.

You can only see Empirum-PatchManagement and configure it accordingly when these two steps have been completed.

Use the Empirum-PatchManagement service to integrate approved patches of various vendors into the Matrix42 structure. This window can be used to set the respective behavior, i.e., when, how often and where synchronization should be performed.

• Matrix42-PatchManagement
  • Use a Proxy server: The data is integrated into the Matrix42 structure via the common proxy server.
  • Root Directory: Specifies the path, where the downloaded patches are to be stored within the Empirum structure.
    

    This path should not be changed, because the PMClient software package is linked to it.

  • Synchronize with: Specifies the name of the server from which the patch definitions are retrieved.
  • Definition Version: Specifies the internal version of the patch definition.
  • Last Run Date: Shows the date of the last execution.
  • Definition Date: Shows the date of the last patch definition.
  • Automatic Synchronization: In the default setting, a connection is made to the Microsoft server daily, at 03:00, and the newest available patches are included into the Empirum structure and displayed.
  • Synchronize Now: This button makes immediately a connection to the patch server and the newest available patches are included into the Matrix42 structure and displayed. This can take several minutes.
  • Cloud only (No local patch download): There are two scenarios for running patch management with this option:
    • The client computers primarily download the patches from the Internet.
      • The MX42_PATCHMANAGEMENT.DOWNLOAD_ORDER variable must be set to the value "Vendor,Infrastructure" for all client computers. This happens automatically by activating the "Cloud only" option via forced inheritance of the variable on the "Configuration groups" object.
      • In this constellation, all patches/service packs from the vendor are always downloaded directly from the client.
    • The client computers primarily copy the patches from the depot server. The Depot Server downloads the patches from the Internet.
      • The variable MX42_PATCHMANAGEMENT.DOWNLOAD_ORDER must be set to the value "Infrastructure,Vendor" for all client computers. To do this, the value on the "Configuration Groups" object must be changed.
      • UEM Depot Management must be set up and running. This is described in the UEM Agent help file (PDF) located in the "Help" directory of the Matrix42 UEM Agent package.
      • For the use of patches from the cloud it is important that the UEM_DEPOT_MANAGEMENT variable SYNC_PATCHES_SOURCE for the depots is set to the value "Vendor". Only then all patches/service packs are always downloaded from the vendor directly to the depot server.

In both scenarios, no physical patches are downloaded to the patch repository on the Empirum master server. Manually added patches are still downloaded by the client from the assigned Empirum server and must be manually placed there by the administrator beforehand.