Manually Updating the Knowledge Base - Local Update
Automatically updating the Patch Knowledge Base requires a permanent Internet connection. If your master is not connected to the Internet, you can still keep the Patch Knowledge Base up-to-date. This process consists of downloading the files on another device, putting them on the master and updating the Patch Knowledge Base with these files. To do so, proceed as follows:
- Access another device with an agent installed on it and has access to the internet.
- Use the command line to access the
bin
folder of the agent or master. By default, the agent is located in:${ProgramFiles}\BMC Software\Client Management\Client
- or for a master, in
${ProgramFiles}\BMC Software\Client Management\Master
- Create a
patch
folder in thebin
folder. Enter:mkdir patch
From the
bin
folder, launch the command line and enter the following command:mtxpatch.exe -u --outdir=./patch --tmpdir=./patch --manifest=https://content.ivanti.com/data/oem/BMC-Numara/data/925/manifest/partner.manifest.xml
If the manifest has been retrieved manually and put into c:/Temp, run the following command:mtxpatch.exe -u --outdir=./patch --tmpdir=./patch --manifest=file://c:/Temp/partner.manifest.xml
- In the
patch
folder, a new file is created,update.bin.
- On the master server, copy the
update.bin
file to thedata\Vision64Database\pmupdates\pending
folder. - Remove the
patch
folder from thebin
folder of the agent. - Restart the master server. The knowledge base is updated and sent to all devices.
You manually updated the Patch Knowledge Base of Patch Manager with files on your local device. To update the Patch Knowledge Base again, simply repeat the procedure.
To update the knowledge base with or without proxy
Sometimes proxy or network configuration settings prevent BMC Client Management to download the files from the network. You need to review the proxy system log files or firewall configuration to verify that requests from the Patch Manager are accepted and correctly transferred.
If you have a proxy system, ensure that it is correctly configured at Patch Management > Patch Manager > Your Patch Manager > Configuration > Proxy Options.
- On the patch manager device, launch a command prompt as an administrator.
- Change the directory to the BMC Client Management installation directory (C:\Program Files\BMC Software\Client Management\<Master or Client>).
- Change the directory to the \bin directory.
- Create a patch directory.
Run the 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
If the manifest has been retrieved manually and put into c:/Temp, run the following command:
mtxpatch.exe [--proxy=xxx] -update --outdir=./patch --tmpdir=./patch --manifest=file://c:/Temp/partner.manifest.xml
The following is the 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
To verify the download, check if the \bin\patch\update.bin file is present. If this file present, you have successfully updated the Patch Knowledge Base of the patch manager. If this file is absent, contact the BMC support team.
Comments
As Written this process will generate an error:
Directory does not exist (./patch/)
To correct this step 5 needs to be updated to read:
5. From the bin folder run the following command:
mtxpatch.exe -u --outdir=./Temp --tmpdir=./Temp --Manifest=https://content.ivanti.com/data/oem/BMC-Numara/data/925/manifest/partner.manifest.xml
Log in or register to comment.