Editable intrinsic properties for servers


Intrinsic properties are always associated with managed servers. You can edit many intrinsic properties.

The following is a list of editable intrinsic properties. For more information about editing property values, see Setting-values-for-system-object-properties.

Note

For properties associated with virtual environments, see Generating-reports-for-virtualization.

Property

Meaning

AGENTLESS_MANAGED_OBJECT_ICON_FILE

Identifies the file used to store icons representing agentless devices and their contents.

AGENTLESS_MANAGED_OBJECT_PROXY_HOST

Indicates this server is used to manage agentless devices.

CUSTOM_OBJECTS_ENVIRONMENT

Lets you set JVM parameters when you are running a Java custom configuration object.

DEPLOY_ALLOW_NFS_DURING_SUM

Indicates that, during a Deploy Job, an agent on a target server running in single user mode can mount a source location using NFS. By default this property is set to False. For more information, see Using NFS to mount a location while running single-user mode.

IS_DEPLOYABLE

Designates a server as not being subject to a Deploy Job. For more information, see Designating servers that cannot be targeted by Deploy Jobs.

{{id name="Editableintrinsicpropertiesforservers-is_online"/}}

IS_ONLINE

Indicates that the server is available for use within the system.

A status of false means that the server is offline for an Update Server Properties Job.

IS_SOLARIS_LIVE_UPGRADE

Indicates an Oracle Solaris server should be remediated using Live Upgrade. By default this is set to False.

MS_OFFICE_INSTALL_LOCATION

Provides the path used to access installation media for Microsoft Office. The path must be provided in UNC format. For more information, see Defining-the-location-of-Microsoft-Windows-installation-media-for-Microsoft-Office-patch-deployment.

MS_OFFICE_INSTALL_USERNAME

Provides the user name that should be used to access the installation media for Microsoft Office. For more information, see Defining-the-location-of-Microsoft-Windows-installation-media-for-Microsoft-Office-patch-deployment.

MS_OFFICE_INSTALL_PWD

Provides the password for a user name that is needed when installing Microsoft Office. For more information, see Defining-the-location-of-Microsoft-Windows-installation-media-for-Microsoft-Office-patch-deployment.

PUSH_ACL_NO_USERS_FLAG

Restricts server access to only those users listed in the server's users file. See Agent ACL description.

REPEATER_MAX_CACHE_SIZE

Specifies the maximum size for the cache on repeaters where BLPackages and software is stored until it is deployed. See Configuring-servers-to-use-repeaters-during-deployments.

REPEATER_NAME

The host name of a BMC Server Automation repeater used to stage a deployment to this server. This option is only provided for compatibility with earlier releases. For information about using repeaters, see Configuring-servers-to-use-repeaters-during-deployments.

REPEATER_STAGING_DIR

The repeater's staging directory. This option is only provided for compatibility with earlier releases. For information about using repeaters, see Configuring-servers-to-use-repeaters-during-deployments.

SOLARIS_ALTERNATIVE_BOOT_ENV

Identifies the Alternate Boot Environment present on the server. This property should only be used when IS_SOLARIS_LIVE_UPGRADE is set to True.

STAGING_DIR

A local path that identifies a location on this server to store the following:

  • Packages until they are applied during a deployment.
  • Network Shell scripts until they are run during a Network Shell Script Job.

The default directory is /C/Temp/stage on Windows platforms and /var/tmp/stage on UNIX platforms.

TRANSACTION_DIR

A local path that identifies a location that stores rollback and log information for Deploy Jobs. For more information, see Configuring-the-location-of-the-transactions-directory.

 

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