Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuration files

By default BMC Server Automation automatically recognizes standard configuration files for all supported OSs.

For BMC Server Automation to read a configuration file correctly, it must adhere to configuration file standards for the relevant operating system. BMC Server Automation can also treat most types of XML files as configuration files.

Parsing configuration files

BMC Server Automation uses a system of grammar files to parse configuration files. Typically the BMC Server Automation grammars examine each line in a configuration file, and if the line matches rules set up in the grammar, the grammar generates a configuration file record. When defining a grammar file, an option exists for creating configuration file records from multiple lines, which is required for some types of configuration files.

After configuration file records are created, you can browse, snapshot, audit, run compliance on, and deploy them like other server objects. Using these standard procedures, you can manipulate the contents of configuration files with great precision, down to their individual lines. In this way you can monitor configuration files on servers throughout your system and if necessary correct inconsistencies. For more information, see:


For information about a special issue and workaround in deploying the grub configuration file, see Password in grub configuration file does not deploy properly.

Configuration files available in BMC Server Automation

Following configuration files are available in BMC Server Automation for respective operating systems:

Operating SystemConfiguration files







Oracle™ Solaris™














































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