This document will explain you about the following:
The Downloaded Patches view provides the details of the patches that are downloaded by Desktop Central MSP, along with their Deployment Status.
To view the list of the downloaded patches, click the Downloaded Patches link under the Patch Mgmt tab. You can filter the view based on the Language(s) that are present in your network.
You can export the Downloaded Patches details in PDF and CSV file formats..
The details of the downloaded patches shown in the tabular format include:
Patch ID: A unique reference ID in Desktop Central MSP for every patch
Bulletin ID: A Unique ID, that represents the Patch as per the update
Patch Description: A short description on the Patch
Language: This gives you information about the language in which the patch got downloaded, say English, Japanese, etc.
Size ( in KB): Refers to the size of the Downloaded Patches.
Download Status: The Download Status attribute displays whether the patch download was successful or not.
Approve Status: Status of the Patch, as Approved or Declined for deployment purposes
Superseded By: Latest version of the patch that has been released, which Supersedes the previous versions of the patch
Download Time: Time, when the Patch has been downloaded
Remarks: Remarks/ comments can be specified about the patch
Platform: Specifies the Operating System of the Patch
Patch Name: The name of the patch. Clicking this link, will lead you to the Patch Details view, which provides more details about the patch.
Release Date: Date, when the patch has been released
Administrators can configure a specific limit of space for Patch Repository. When the Patch Repository size exceeds the specified limit, a mail notification will be sent to the administrators if required. This provides them a feasibility to verify that the Patch Repository does not run out of free disk space. If a Patch Repository runs out of free space, then the latest patches cannot be downloaded. However, the space limit specified above is used only for notification purposes. Assume, if you have configured the Repository size as 10 GB, where as the available free space in the same drive is 40 GB, then the patch downloads will not be affected even if the size exceeds the specified limit of 10 GB.
In case the existing patch store has limited space available, you can modify the location details using the Change Patch Store Location option available on the top right corner of the Downloaded Patches page. You should copy the patches from the previous directory to this new location and restart Desktop Central MSP Server for the changes to take effect. The steps to restart the Desktop Central Server are as follows:
Administrators can configure patch cleanup settings to increase the free disk space on the Patch Repository. There are two significant ways to increase the free disk space, they are explained below:
Using "Cleanup Settings", you can remove superseded Patches. When a new version of a patch has been released, the older version of the patch is no longer required in the network. So these patches can be removed as and when a latest version is supported. You can automate this process of removing the superseded patches by configuring the cleanup policy. This will result in increasing you free disk space, by removing unwanted patches.
Patches once downloaded, are retained in your patch repository. Administrators needs to periodically check for the patches which are not missing on any of the computers and which are old enough to be removed. Though it is a time consuming process, you can remove a lot of unwanted patches and increase your disk space. Desktop Central has now automated this process of removing patches which are older than a specific period of time. You can specify a time interval, after which the patches will be removed if it is not missing in any of the managed computers.
You can follow the steps mentioned below to configure Patch Cleanup Policy:
You have successfully configured the patch cleanup policy. Superseded patches and patches that are older than the specified time limit will be removed from the patch repository, which means the available free disk space in the Desktop Central server will be increased. These changes will also impact the Distribution Server. Distribution server synchronizes the patch details with the Desktop Central server in such a way, that when a patch is removed from the Desktop Central server, it will also be removed from the Distribution Server during the subsequent replication interval. So whenever the patch repository is cleaned up, the unwanted patches will also be removed from the Distribution Server.