Use > Server Automation > Agent installation and upgrade utilities > Augment information for a managed server

Augment information for a managed server

Caution Use caution when you augment the discovery process for a managed server that is functioning in the operational environment. You might inadvertently install or uninstall software from the server. During the test remediate, verify what software will be uninstalled from the server before you perform the actual remediate operation.

To augment information for a managed server:

  1. Model the OS and other applications running on the server in Server Automation by defining the OS with the Prepare Operating System Wizard and by creating nodes and templates for applications running on the managed server.

    See the SA Administer section for more information about operating system definitions.
  2. Move the server to the appropriate nodes for the OS and installed applications.

    The server is tracked in the SA Client; however, the server operating system cannot be managed while the server is assigned to the generic operating system node. You must reassign the server to the operating system that was defined with the OS Provisioning feature.
  3. Remediate the server.
  4. If an IP range group was set up, servers are automatically associated with customers when users install an Agent on the servers. Otherwise, the servers are associated with the Not Assigned customer.
  5. To specify the server’s use, stage, and state, edit the server’s properties.

Discovery is complete. Server Automation assumes that the server should always be running the specific OS build it has been associated with. Any changes to the OS outside of Server Automation are not captured in the model.

Users can deploy and manage new applications on the server, just as if Server Automation initially provisioned the server. Users can also deploy OS level patches on the server, or rebuild the OS by using the OS build with which the server was associated.