Administer > SA Provisioning > SA provisioning administration > SA provisioning components

SA Provisioning components

During an SA Core installation, you have the option to install the SA Provisioning components. The following sections describe those components.

SA Agent

During SA Provisioning, the SA Agent provides multiple services:

  • As an SA Agent that runs on the production OS. This SA Agent continues to run on the managed server after it is provisioned.
  • The SA Agent in Maintenance Mode runs in the service OS.

    The SA Agent that provides monitoring. Similar to the SA Agent used in the service OS, this instance of the SA Agent is configured to run while an OS is installed, monitors progress and allows Build Plan steps to be run after the system is installed (but before the first time the system is booted). Special care is taken so that the SA Agent does not interfere with the OS install.

    Not all platforms have a monitoring SA Agent.

The Build Plan content

Build Plan content, which is installed by default during a fresh installation or upgrade, includes a number of baseline Build Plans that can, by default, perform many common provisioning tasks. This content includes program and web extensions as well as scripts which are used to implement Build Plans. You can view this content in the SA Client Library.

All SA content is updated during SA Core upgrade. Mixed version content is not supported, and will likely not work if present. Build Plans that fail with import errors or errors suggesting incorrect or non existing method calls often are a sign that there is a version mismatch.

The Boot server

Provides a set of tools that are pre-installed with the SA Core to support a wide set of network booting capabilities. The Boot Sever requires no administration. The SA Core installation process handles all the complexities of installing and configuring the boot server.

For a high level summary of all SA Core Components, see the SA Key Concepts Guide.