Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Global Settings Current - User Guide

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

Removing a tenant

By removing a tenant, you are beginning the process of disabling all module functions related to the tenant. When you remove a tenant, you are removing the tenant from the On Demand organization for all users and this action cannot be undone.

All module operations will stop after 30 days. At that point, the following operations are halted:

•
Active backups and provisioning actions will be cancelled.
•
Migration project and status information will be lost.
•
Audit event data will no longer be collected.
•
License and cost data will no longer be collected.
•
Assessment data will no longer be collected.
 
* 
NOTE: If a tenant was inadvertently removed, it might be possible to restore a tenant and all the associated On Demand configuration for up to 30 days after it was removed from On Demand. In this situation, contact Technical Support.

You must provide the tenant name, your organization ID, and the tenant region.

To remove a tenant
1
Click Tenants in the navigation panel on the left.
2
On the tenant tile for the tenant you want to remove, click Remove.
3
Review the list of results from the remove action and select each check box.
4
Click Remove Tenant.

When you previously added the tenant, a Service Principal was created in your tenant, under Enterprise applications, for each consent that you granted for this tenant. To permanently remove the consents, log in to the Microsoft Azure portal and go to the Microsoft Entra Admin Center. Browse to Enterprise Applications, search for Quest on Demand, and delete all the application records that you do not need.

Managing your on-premises domains

Managing your on-premises domains

In addition to managing your Microsoft Entra tenants, On Demand provides support for connecting to on-premises domains in hybrid environments to perform data collection and management activities.

By installing an agent with a unique key and specifying domains to which the agent is connected, you can review information and perform actions in your hybrid environment. You start the process to install and configure an agent by selecting Tenants in the left navigation bar and selecting Hybrid Agents.

You can add on-premises domains to On Demand selecting Tenants in the left navigation bar and selecting Active Directory Domains. You can also add domains as part of the agent configuration process.

Agent prerequisites

You must meet the following prerequisites to download and install an agent for on-premises data collection from specified domains:

•
You must have the On Demand Organization Admin role and specifically must have the Can Configure Agents (core.configureAgents) permission.
•
You must have a passphrase, which you create on the How to Add an Agent page, that you enter when installing the agent.
•
You must have a valid paid subscription for the On Demand module with which you are using the agent.
•
The login account that you use to run the agent setup program must have local administrator rights.

The agent setup program will prompt you for service account credentials (username and password) that are used to run the agent service. The agent service account must be a domain account and must have local administrator rights on the computer on which the agent is being installed. Also, for License Management, the service account must have Write Members permissions on the directory group objects.

Agent requirements
Table 1.  
On-premises hybrid agent requirement
Details

Operating System

Installation platforms (x64) supported for the following versions:

•
Windows Server 2016
•
Windows Server 2019
•
Windows Server 2022

System configuration

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 must be able to access the following endpoints associated with the region where your On Demand organization resides.

•
Australia:
•
odjrsauprodauiotinst--odjrsauprodauiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
odjrs-auprod-au-iothub.azure-devices.net
•
MQTT over WebSockets - TCP 443
•
https://odjrsauprodaugrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
https://odjrsauprodausto.blob.core.windows.net
•
HTTPS - TCP 443
•
Canada:
•
odjrscaprodcaiotinst--odjrscaprodcaiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
odjrs-caprod-ca-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
https://odjrscaprodcagrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
https://odjrscaprodcasto.blob.core.windows.net
•
HTTPS - TCP 443

 

 

 
•
Europe:
•
odjrseuprodeuiotinst--odjrseuprodeuiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
odjrs-euprod-eu-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
https://odjrseuprodeugrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
https://odjrseuprodeusto.blob.core.windows.net
•
HTTPS - TCP 443
•
UK:
•
odjrsukprodukiotinst--odjrsukprodukiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
odjrs-ukprod-uk-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
https://odjrsukprodukgrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
https://odjrsukproduksto.blob.core.windows.net
•
HTTPS - TCP 443
•
US:
•
odjrsusprodusiotinst--odjrsusprodusiotacct.b.nlu.dl.adu.microsoft.com
•
HTTP - TCP 80
•
odjrs-usprod-us-iothub.azure-devices.net
•
MQTT over WebSockets (TCP 443)
•
https://odjrsusprodusgrssto.blob.core.windows.net
•
HTTPS - TCP 443
•
https://odjrsusprodussto.blob.core.windows.net
•
HTTPS - TCP 443

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.

Adding an on-premises agent

The following steps describe the general process for installing and configuring the On Demand 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 Agent prerequisites .

1
Generate a passphrase on the How to Add an Agent page. Take note of the passphrase.
2
Add the agent to On Demand.
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 agent is installed it connects to the On Demand 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
To add an agent
1
Log in to On Demand using the credentials you used to sign up for On Demand.
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 On Demand On-Premises Agent.
•
Agent name - optional. If you do not specify an agent name, the NETBIOS name of the computer is used.
•
Credentials (user name and password) of the account that is used to run the agent service. The account specified must be a domain account and 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.

Installing the agent using the command shell

If you open a command shell, you must open it with elevated permissions (such as “Run as administrator”). The setup program requires admin rights.

You can provide the parameters for agent installation through command line switches. This method allows the agent to be installed without any prompts. The supported switches are as follows:

--outdir <output_directory>

Provides the target directory where the agent files will be extracted. This is the only switch that is handled directly by the self-extracting executable. All other switches are forwarded to the agent setup program that is executed after the files are extracted.

--quiet

Prevents prompting. When you use this switch, you must also specify all parameters that do not have default values through the command line. If any parameters are missing, the installation will fail.

--name <name>

The name used to identify the agent. The agent name is displayed in the On Demand Agent configuration page once the agent installation is completed. If no name is provided, the NETBIOS name of the computer is used as a default value.

--user <username>

The Windows user account under which the agent service is run. This is a required parameter. The user account specified must be a domain account and must have local administrator rights on the computer where the agent is being installed. The local administrator rights are needed to allow the agent to perform an auto-update when new versions of the agent become available.
Additional permissions depend on the workload being performed by the agent. Refer to the documentation for the specific On Demand module for more information. For example, to manage on-premises groups in License Management, the agent service account must have Write Members rights on the group object in Active Directory.
The account is granted Log On As Service rights on the local system during installation.

--password <password>

The password of the Windows user account under which the agent service is run. It is a required parameter. This password is not stored anywhere within On Demand. The password is only used to configure the startup properties of the Windows service.

--passphrase “<passphrase>”

The generated passphrase that was created on the How to Add an Agent page. The passphrase is required to install the agent. Since the passphrase will contain spaces, you must use quotation marks to enclose the passphrase.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation