Security Management Platform Global Settings Current - User Guide

Working with Security Management Platform Global Settings Overview of Security Management Platform Global Settings Signing up for Security Management Platform Global Settings Managing organizations and regions Adding users and groups to an organization Managing your Microsoft Entra tenants and on-premises domains Security Management Platform Home page Configuring settings Documentation roadmap Technical Support

On-premises agent system configuration requirements

The agent requires:

•
LDAP (TCP 389) connectivity to all domain controllers in the local domain.
•
SMB TCP port 445 open on the domain controllers.
•
The following Windows services running:
•
DNS client
•
Remote Procedure Call (RPC)
•
Windows event log

The agent uses:

•
The Windows (Internet Explorer) Proxy Server settings applied to the service account or computer where it is installed.
•
MQTT over WebSockets - TCP 443 for IoT Hub communication.
•
HTTPS - TCP 443 for upload/download of files.
•
The login account that you use to run the agent setup program must have the Windows (Internet Explorer) Proxy Server settings configured if your environment requires a Proxy Server to access the Internet.

The agent footprint:

•
Estimated hard disk space used: 160 MB + log size.
•
By default, up to 10 MB of log files are retained.
•
Estimated physical memory (RAM) used: 25 to 50 MB.

On-premises agent endpoint requirements

The agent must be able to access the following endpoints associated with the region where your Security Management Platform organization resides.

•
Australia:
•
Agent updates: odjrsauprodauiotinst--odjrsauprodauiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
Agent connection to Security Management Platform: odjrs-auprod-au-iothub.azure-devices.net
•
MQTT over WebSockets - TCP 443
•
Agent and package download: https://odjrsauprodaugrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
Agent data upload: https://odjrsauprodausto.blob.core.windows.net
•
HTTPS - TCP 443
•
Canada:
•
Agent updates: odjrscaprodcaiotinst--odjrscaprodcaiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
Agent connection to Security Management Platform: odjrs-caprod-ca-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
Agent and package download: https://odjrscaprodcagrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
Agent data upload: https://odjrscaprodcasto.blob.core.windows.net
•
HTTPS - TCP 443
•
Europe:
•
Agent updates: odjrseuprodeuiotinst--odjrseuprodeuiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
Agent connection to Security Management Platform: odjrs-euprod-eu-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
Agent and package download: https://odjrseuprodeugrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
Agent data upload: https://odjrseuprodeusto.blob.core.windows.net
•
HTTPS - TCP 443

 

•
UK:
•
Agent updates: odjrsukprodukiotinst--odjrsukprodukiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
Agent connection to Security Management Platform: odjrs-ukprod-uk-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
Agent and package download: https://odjrsukprodukgrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
Agent data upload: https://odjrsukproduksto.blob.core.windows.net
•
HTTPS - TCP 443
•
US:
•
Agent updates: odjrsusprodusiotinst--odjrsusprodusiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
Agent connection to Security Management Platform: odjrs-usprod-us-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
Agent and package download: https://odjrsusprodusgrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
Agent data uploads: https://odjrsusprodussto.blob.core.windows.net
•
HTTPS - TCP 443

Adding an on-premises agent

The following steps describe the general process for installing and configuring the Security Management Platform on-premises agent. For the detailed procedures, see To add an agent and To configure an agent.

For information about the permissions required to install an agent and the permissions needed by the agent service account, see On-premises agent prerequisites.

1
Generate a passphrase on the How to Add an Agent page. Take note of the passphrase.
2
Add the agent to Security Management Platform.
An agent package is generated with a unique key.
3
Download the agent package and copy it to the member server on which you want to run the agent.
4
Install the agent, specifying the required information including the passphrase.
Once the agent is installed it connects to the Security Management Platform organization.
5
Configure the agent specifying the actions it can perform and domains with which it works.
* 
NOTE: On-premises hybrid agent support

Installation platforms (x64) supported for the following versions:

•
Windows Server 2016
•
Windows Server 2019
•
Windows Server 2022
•
Windows Server 2025
To add an agent
1
Log in to Security Management Platform using the credentials you used to sign up for Security Management Platform.
2
In the navigation panel on the left, click Tenants.
3
Click Hybrid Agents.
4
Click Add Agent,
When you click Add Agent, the How to Add an Agent page is displayed. You must create a passphrase that will be used when you install the agent.
5
To create a passphrase, use one of the following options:
•
Click Generate New to get a new passphrase.
•
Enter a passphrase manually. The passphrase can be from 4 to 100 words (32 to 1024 characters long).
•
Edit a displayed passphrase to make it more complex (such as adding numbers or characters).
•
Enter a passphrase word count (from 4 to 100 words) and click Generate New to get a passphrase of the specified word count. NOTE: The passphrase must be from 32 to 1024 characters long.
6
When you decide to use the displayed passphrase, click Copy and Continue.
The passphrase is copied to your clipboard. Ideally, you should paste it into a Notepad or Word document to keep for future reference.
7
Once the installation package is ready, click Download.
The agent package with a unique key is downloaded to your computer.
 
* 
IMPORTANT: You must install the agent within 10 days or the unique key will expire. Also, you cannot re-use an agent package, even if you have removed the agent from a previous installation. You must download and install a separate agent on each server.
8
Copy the agent package to the server and double-click the AgentSetup.exe file.
The installer is packaged as a self-extracting executable. If you run the installer without arguments, it prompts you for the required installation parameters, including the folder where the agent should be installed. You also are asked for the passphrase that was copied to your clipboard.
For information about the available arguments, see Installing the agent using the command shell.
 
* 
IMPORTANT: The maximum number of agents is limited to 10 per organization. If you need a higher number of agents, contact Quest Support.
9
In the command line console, enter the following information in response to the prompts:
•
Agent installation path: The folder to which the agent files will be extracted. If you do not specify the path, the default path is set to C:\QuestAgent.
•
Enter Y when you are prompted to install Quest Security Management Platform On-Premises Agent.
•
Agent name - optional. If you do not specify an agent name, the NETBIOS name of the computer is used.
•
Secure LDAP - optional. Enter Y to use TLS encrypted LDAP. IMPORTANT: Domain controllers in the forest must be properly configured to enable this feature. See Secure LDAP configuration and deployment for more information.
•
Credentials (user name and password) of the account that is used to run the agent service. The account specified must have local administrator rights on the computer where the agent is being installed. Other required rights depend on the modules with which the agent will be used.
•
Passphrase - The generated passphrase that you generated on the How to Add an Agent page.

About agent installation

Depending on your browser and the download options that you configured, when you click Download, the AgentSetup.exe file is downloaded to the location you specify. In most cases the AgentSetup.exe file is downloaded to your Downloads folder.

The setup program is a console application. If you double-click the AgentSetup.exe file, a console window is opened and you are prompted for information such as installation folder and service user name and password. Optionally, you can open a command shell and manually execute the installer from the command line which allows you to specify arguments

The file name of the downloaded file is AgentSetup.exe. The installer is packaged as a self-extracting executable. If you run the installer without arguments, it prompts you for all required installation parameters, including the folder where the agent should be installed.

You can run the AgentSetup.exe from any directory (as long as you run the program on the computer on which it is to be installed). The self-extracting executable prompts you for the folder to which the agent files will be extracted. The self-extracting installation package extracts the files to the specified target folder and runs the setup program (Setup.exe) from the target folder.

Once an agent installation package is used to install the agent on a computer, you cannot use the same package to install the agent on another computer.

 
* 
IMPORTANT: The installation key included in the installer is a unique one-time key that cannot be used again to install the agent elsewhere, even if you uninstall the agent from the current computer.

After you have installed the agent, it is recommended that you delete the file containing the passphrase (if you saved it to a file) and the downloaded agent installation package. However, do not delete the AgentSetup.exe file that was extracted.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択