Why does the Check/ Update Failed error occurs in Patch KB Configuration?



How to locally update the Patch Manager's KB if proxy is configured?
 

This kind of issue is most of the time due to Proxy or Network configuration that prevent BCM to download files from "https://content.ivanti.com".
Verify with the IT team to review Proxy system log files or Firewall configuration in order to check the requests from the BCM Patch Manager are accepted and correctly transferred to "https://content.ivanti.com".

BMC Client Management (BCM) Patch Manager device must be able to resolve and connect to "content.ivanti.com" over internet. 

In case a Proxy system is configured be sure it is correctly set in BCM Console > Patch Management > Patch Manager > Configuration > Proxy options node.

Here is a test procedure for system with and without Proxy that will help to identify the cause of this incident:

1 - On the BCM Patch Manager device, open a Command Prompt window as an Administrator
2 - Change Drive to BCM Installation path  (default patch C:\Program Files\BMC Software\Client Management\<Master or Client>)
3 - Change Drive to the \bin directory  (cd bin)
4 - Create the patch directory (mkdir patch)
5 - Execute following command:

mtxpatch.exe [--proxy=xxx] -update  --outdir=./patch --tmpdir=./patch --manifest=https://content.ivanti.com/data/oem/BMC-Numara/data/925/manifest/partner.manifest.xml

Here is syntax information for the proxy parameter : 

--proxy=[http://][base64(user:password)@]proxy_host[:proxy_port]
--proxy=[http://][base64(enc(user:password))@]proxy_host[:proxy_port]
--proxy=http://login:password@hostname

6 - Verify that file \bin\patch\update.bin is present. If it is present, this means Patch KB update is successfully downloaded.
If this test fails, \bin\patch\update.log file can be provided to the support team and a screenshot of command line result for analysis.
If the mtxpatch fails with a "COULDNT_RESOLVE_HOST" error then review network configuration with IT or Security team as the Patch Manager Server must be able to resolve and connect to content.ivanti.com. and it is currently not able to do so.

7 - If previous test is successful then delete \bin\patch\* files
8 - Later, execute following command (this one has an additional workspace parameter that will help support to know if issue is due to files that are already present on system) :    

mtxpatch.exe [--proxy=xxx] -update  --outdir=./patch --tmpdir=./patch --workspace=./../data/PatchManagementPremium/workspace/ --manifest=https://content.ivanti.com/data/oem/BMC-Numara/data/925/manifest/partner.manifest.xml

9 - Verify that file \bin\patch\update.bin is present.
If it is present, this means Patch KB update is successfully downloaded. Patch KB can be updated from BCM Console now. 
If this test fails, then delete the contents of following directory (be careful some files are hidden) then execute step 8 command line one more time:
==========================================================================================
C:\Program Files\BMC Software\Client Management\<Master or Client>/data/PatchManagementPremium/workspace/
==========================================================================================