Working with BMC Helix Client Management master

If you are using BMC Helix Client Management, the master server cannot be used in the console. The master server cannot be a patch manager and hence cannot download the patches. Any device, being a direct child (relay or not) of the master, directly downloads the patches from the internet (or retrieve them in patch repository) instead of using the Filestore mechanism. You must ensure that the relay that is directly under the master and downloading the patches is connected to the internet. 


Related topics

Cloud-architecture

You should consider the following recommendations when setting up the BMC Helix Client Management master.

  • We highly recommend to have at least one and possibly only one L1 relay directly connected to the master. It will reduce the number of devices that download the patches.
  • Do not have any device other than the L1 relay under the helix master.
  • If you have more than one L1 relay as a direct child, it should not exceed 500 devices. If the master has more direct children, it affects the master's efficiency.
  • Patches are stored on the L1 relay as a consequence and not on the master.
  • We recommend to publish the packages to the L1 relay (and to any other relay that could be a direct child of the master) and not to the master.
  • It implies that the L1 relay or any device directly under the master must have a lot of disk space.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*