Contents of the Live node

The contents of the Live node vary by operating system.

Virtual environments contain specialized Live node children, which are described in Browsing virtual inventory.

OS

Server Objects

IBM AIX

  • BLPackages
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Packages
  • Patches
  • Processes
  • System Info
  • UNIX Groups
  • UNIX Users

HP-UX

  • BLPackages
  • Bundles
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Patches
  • Processes
  • Products
  • System Info
  • UNIX Groups
  • UNIX Users

Linux

  • BLPackages
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Processes
  • RPMs
  • System Info
  • UNIX Groups
  • UNIX Users

Oracle Solaris

  • BLPackages
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Packages
  • Patches
  • Processes
  • System Info
  • UNIX Groups
  • UNIX Users

Microsoft Windows

  • .NET Global Assemblies
  • Active Directory
  • Applications
  • BLPackages
  • Complus
  • Components
  • Configuration
  • Event Logs
  • Extended Objects
  • File System

    Note

    For Windows directories, the size of the directories is not displayed.

  • Hardware Information
  • Hotfixes
  • Local Groups (shows no data if server is domain controller)
  • Local Users (shows no data if server is domain controller)
  • Metabase (if Microsoft IIS is installed)
  • Registry
  • Security Settings

  • Services
  • System Info

The following list provides additional information about nodes that are children of the Live node:

  • Active Directory — Provides a hierarchical listing of the groups, shared folders, and users associated with Active Directory domains and sub-domains on a Windows server.
  • Applications — Shows the applications installed on the server.

    Note

    Applications that cannot be uninstalled are not presented under the Applications node. To identify applications that cannot be uninstalled, browse to the Registry node and then to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ApplicationName or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ApplicationName. If the application cannot be installed, the UninstallString value is missing at this location.

  • BLPackages — Shows all BLPackages that have been deployed to a server. For more information about using this object, see Tracking BLPackage deployments.
  • Components — Shows components associated with a server. Components are objects representing a higher level of abstraction than server objects. Using a component, you can manage an application rather than the server objects that make up the application. For more information, see Components and component templates.
  • Configuration — Lists files that present the contents of configuration files for the operating systems BMC Server Automation supports. To deliver this information in a standard format, BMC Server Automation parses the contents of those files using grammar files. (In this respect, configuration file objects are similar to extended objects.) If necessary, you can identify additional configuration files. For more information, see Identifying additional configuration files and Configuration files.
  • Extended Objects — Shows custom objects that consist of information after it is parsed by a BMC Server Automation grammar file (see Grammar files supported by BMC Server Automation) so it can be presented in a standard format. Extended objects can deliver information not included in a standard BMC Server Automation installation, such as local user account data or network settings. For more information, see Creating an extended object.
  • File System — Provides a hierarchical listing of the server's files and directories. When browsing a file system, you can traverse symbolic links to files and directories.
  • Hardware Information — Provides information about a server's hardware configuration.

    Note

    Different operating systems, especially in virtual environments, expose different levels of details relating to hardware information. The level of detail provided by the hardware information object typically varies for different platforms.

    If, under Hardware Information on Microsoft Windows 2003, the number of cores and number of logical processors appear incorrectly as 0, you must apply a Microsoft hotfix, as discussed in http://support.microsoft.com/kb/932370.

    For an IBM AIX server, the CPU count under the Hardware Information node represents, by default, the active CPU from the physical host computer. If your AIX server is a logical partition (LPAR) and you prefer to receive information about the entitled capacity of the LPAR, perform the following configuration task: 

    1. Within the RSCD installation directory, navigate to the /nativetool/config/ subdirectory, and locate the mcsysinfo.cfg configuration file.
    2. In the mcsysinfo.cfg file, set the CpuCountPhysLparEntitled option to a value of yes:
      CpuCountPhysLparEntitled=yes

    You do not need to restart the RSCD Agent for changes in the mcsysinfo.cfg file to take effect.
    If at any later time you want to revert to the default of CPU from the physical host computer, change the value of this setting to no, or delete this setting from the mcsysinfo.cfg file. 

  • Hotfixes — Provides a list of Windows Security Patches installed on the target server based on patch metadata from Shavlik. The first time that you click this branch, BMC Server Automation retrieves the Shavlik metadata and populates the list. If the Shavlik file needs to be downloaded through a proxy, ensure that the proxy settings in Patch Global Configuration (which are used for this download) are up-to-date.
  • Security Settings — Windows security policy settings. Note the following special issues:
    • Some limitations apply to the deployment of security settings within BLPackages based on Windows security settings. These limitations are discussed in Creating a Deploy Job.
    • Settings for policies that are present in the Advanced Audit Policy Configuration for Not Defined and No Auditing values on the target are displayed as Not Defined on the console.Remediation for Advanced Audit Policy does not persist after system reboot or after running the gpupdate /force command.

    • When live browsing the Security Settings of a localized server, policy properties that were defined using CJK (Chinese, Japanese, or Korean) characters are not retrieved and are displayed as Not Defined. Furthermore, such policy properties are not available for use in jobs (such as Compliance Jobs).

      As a workaround, you can implement an extended object with translations of policy setting values. For guidance, contact BMC Support.

Was this page helpful? Yes No Submitting... Thank you

Comments