Configuring after OnDemand installation


This section contains information about activities that you must perform after you install BMC Client Management and before you roll out the relay and client agents in your network.

  • Antivirus exclusions
  • Far-Eastern language support

Antivirus exclusions

BMC recommends that you set in place some prerequisites to avoid false positive virus detections. This applies to all devices on which a CM agent is installed, including the master device.

Exceptions should be made for the following two objects:

  • The entire CM agent folder
  • CM agent files and file types

CM agent folder

If the agents's .sqlite and .log files are set to verbose mode, the CM agent is very talkative. To avoid this you must set an exclusion for the *..\client* folder on the clients and the *..\master* folder on the master.

Note:

If the device is an OSD Manager, do not forget to also set an exclusion for the ..\PXETFTP folder.

CM agent files and file types

You should also consider setting exceptions on the following files:

  • chilli.exe
  • comerr64.dll et comerr32.dll
  • dtengine64.dll et dtengine32.dll
  • IntelvPro.dll
  • InteVProRC.dll
  • k5sprt64.dll et k5sprt32.dll
  • krb5_64.dll et krb5_32.dll
  • krbcc64.dll et krbcc32.dll
  • libeay32.dll
  • libMtx.dll
  • libMtxChilli.dll
  • libMtxDtSearch.dll
  • libMtxHchl.dll
  • libMtxXslt.dll
  • libRemoteControl.dll
  • libssh.dll
  • Microsoft.VC80.CRT.manifest
  • msvcm80.dll
  • msvcp80.dll
  • msvcr80.dll
  • msvcr71.dll
  • mtxagent.exe
  • mtxcert.exe
  • mtxproxy.exe
  • mtxrproxy.exe
  • mtxset.exe
  • mtxsetup.exe
  • mtxsfx.exe
  • Nmap.zip
  • patchwrapper.exe
  • pdh.dll
  • pkgview.exe
  • psapi.dll
  • SafeReboot.locale
  • sas.dll
  • ssleay32.dll
  • stConvertXML.dll
  • stPackager.dll
  • stUpdateManager.dll
  • update.chl
  • wshelp64.dll et wshelp32.dll
  • *.sqlite
  • *.table

Far-Eastern language support

The console and the tool generating the reports in Client Management are both Java applications. For font management, Java relies on its own fonts, as well as those installed on the operating system of the device. As Java up to now does not include support for Far-Eastern languages, the devices on which the console and the master are installed must be correctly configured to be able to display reports in any of these languages, such as Japanese.

Ensuring support for Far-Eastern languages on Windows

The following procedure is an example for Windows 7, It is the same for other Windows versions but the names of the windows and options might vary slightly:

  1. Download the language pack for the Far-Eastern languages via Windows Update .
  2. Open the Start menu and select Control Panel .
  3. In the Control Panel select select Region and Language .
  4. In the Region and Language window, select the Keyboards and Languages tab.
  5. Click Install/uninstall languages .
  6. In the Install or uninstall display languages window select Install display languages .
  7. Browse to the location where you stored the language pack and select it from the list box.
  8. Click Next and then follow the remaining steps.

    If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

    Note:

    The Display language section of the Region and Language window is visible only if you have already installed a Language Interface Pack or if your edition of Windows supports a language pack. Language packs are available only in Windows 7 Ultimate and Windows 7 Enterprise.

Ensuring support for Far-Eastern languages on Linux

Under Linux, the fonts must be added in the Java JRE. To do so, proceed as follows:

  1. Locate the Java Run Time installation directory.
  2. Go to the $JAVA_HOME/jre/lib/fonts directory.
  3. Create a subdirectory called fallback .
  4. Copy the Asian fonts into this subdirectory.

    You can find the sazanami-mincho.ttf font, which is required for Japanese language support, in the BMC Client Management installation archive in the /root/BMC/support/fonts directory.

 

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