Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.7 Administrator Guide > Monitor with Orion agents in SAM > Mass deploy a Windows agent for SAM

Mass deploy a Windows agent for SAM

Updated: 3-9-2017

If you are already using a mass-deployment technology, this deployment method is an easy way to get agents on a large number of computers.

Polling engine selection is important. When you download the MST file, the file includes the polling engine IP address and other vital information. When you deploy the agent using the MSI file, along with the MST file on the managed node, the agent will be installed and pointed to the correct polling engine.

What is an MST file?

A Microsoft Transform (MST) file is a collection of specified changes applied to a base Windows Installer package file at the time of deployment. It is an overlay on top of an existing MSI??file that defines what specific components or features of an application get installed. The MST file modifies the Microsoft Installer package.

After the software you want to install is packaged in the Windows Installer package format, you can use MST files to customize the software for your organization, such as installing only specific features. The modular design of Windows Installer packages simplifies deployment. When you apply transforms to an MSI file, Windows Installer can dynamically add or modify data in the installation database to customize the installation of the application. Additional information on creating MST files can be found on

Generate and download the MST file

  1. Click Settings > All Settings in the menu bar.
  2. Under Product Specific Settings, click Agent Settings > Download Agent Software.
  3. Click Windows, and click Next.
  4. Click Mass Deploy to Multiple Machines, and click Next.
  5. Select the agent communication mode.
    • For agent-initiated communication, enter the polling engine you want the agent to use. You may need to manually enter the polling engine information if the IP address is different from what the Orion server reports. This happens when the monitored host is behind a NAT or proxy device. In these cases, enter the IP address of the Orion server or the additional polling engine as it is accessible from the host where the agent will be installed.
      1. To use an existing polling engine, select Use Connection Details from Polling Engine, and then select a polling engine from the list.
      2. To manually enter the polling engine IP address, select Enter Connection Details Manually, and then enter the host name and IP address. The IP address is required. Use the host name and IP address of the polling engine that you can access from the client.
    • For server-initiated communications, enter your agent communication port number. The default port is 17790.
  6. Click Download .MSI, and save the file.
  7. Click Download .MST, and save the file.

Add the MST??file to a Group Policy

  1. Share a folder containing the MST and MSI files with proper permissions.
  2. In Active Directory, locate the container where you want to advertise the application, and then access the container properties.

    A container is a site, domain, or organizational unit (OU).

  3. Create a Group Policy object.
  4. In Advanced Options, add the Software installation policy. Select the network path for the agent MSI and MST files.

The agent is deployed at login and is registered by Orion (if auto-registration is enabled).

Last modified