Configuring clients in non-global zones

In a Solaris Zones environment, you must install the BigFix client in the global zone first before optionally installing it in the non-global zones. In general, you do not need to separately install the client in the non-global zones if it is already installed in the global zone. One exception to this is when the client binaries are not available in the non-global zones.

About this task

If the client binaries are available in the non-global zone, you just need to save the masthead actionsite.afxm file in the /etc/opt/BESClient/ directory of the non-global zone.

The non-global zone reports as a separate entity from the global zone. For example, if you have set up two non-global zones, you will see three instances of the machine in the console. The non-global zone endpoints will be identified by their hostname, so make sure that you use a descriptive name.