Installing the Client on Solaris 10
In a Solaris zones environment, consider that non-global zones are entities separated from the global one. For example, if you set up two non-global zones, you will see three instances of the client computers in the BigFix console. Because the BigFix client is identified by the host name, ensure that you use descriptive unique host names when creating the zones.
Install the BigFix client first in the global zone. Depending on the Solaris OS version, the client could be automatically installed also in the managed non-global zones. Verify and install the client in the non-global zones, if required.
In any case, you must save the masthead actionsite.afxm
file in the
/etc/opt/BESClient/
directory of all Solaris zones with the BigFix client installed.
To install the client, perform the following steps:
- Download the corresponding BigFix client package file to the Solaris computer.
- Copy your actionsite masthead to the Solaris BigFix client computer (the masthead contains
configuration, license, and security information). The action site masthead
(
actionsite.afxm
) can be found in your BigFix Installation folders (by default they are placed underC:\Program Files (x86)\BigFix Enterprise\BES Installers\Client
on Windows and/var/opt/BESInstallers/Client/
on Linux). If the masthead is not namedactionsite.afxm
, rename it toactionsite.afxm
and place it on the computer at the following location:/etc/opt/BESClient/actionsite.afxm
. The masthead file for any BigFix server can also be downloaded athttp://servername:port/masthead/masthead.afxm
(example:http://bes.BigFix.com:52311/masthead/masthead.afxm
).Note: You might need to create the directory/etc/opt/BESClient/
if it does not already exist. - Install the PKG by running the
command:
pkgadd -d <path to BigFix Client package file>
- The BigFix Client is started
automatically by the Service Manager, on older versions run the
command:
/etc/init.d/besclient start
To install the BigFix client in the
local zone, after you have copied the masthead into the /etc/opt/BESClient/
local
zone folder, ensure that the svcs BESClient
service is online in the local zone by
completing the following steps:
- Check the status of the
BESClient
service:
If it is online, no additional action is needed.svcs -x BESClient
- If the service is in maintenance, stop the
BESClient
:/etc/init.d/besclient stop
- Enable the
BESClient
svc service:svcadm clear BESClient
- Check if the service is online and that the client is started:
svcs -x BESClient
svcs -p BESClient