×
×
×
×

Frequently Asked Questions | DEX Manager Plus

Last Updated On 22 Aug 2025 |
13 minutes read |

Introduction

This page provides answers to frequently asked questions (FAQs) about DEX Manager Plus. Expand the accordions under each section to view detailed answers.

Scope of Management (SoM)

What is Scope of Management (SoM)?
Scope of Management is a feature that is used to specify which computers you can manage using DEX Manager Plus. You can add and manage computers that are from an Active Directory, a workgroup or any other directory service like Novell eDirectory. The computers can either be in the same Local Area Network (LAN) or in a remote location connected through a Virtual Private Network (VPN) connection or through the Internet. For more information, see Defining the Scope of Management.
What will happen if the agents are unable to reach the server to report the status after performing any task?
Agents will report the status to the DEX Manager Plus server after performing every task. In case the server is not reachable, then the agents will update the status during their subsequent refresh interval.
How will the agent reach the Distribution Server if the port number used for their communication has been changed?
When the agents of the remote location are unable to contact the Distribution Server, they contact the DEX Manager Plus Server directly during the next 90 minutes refresh interval. They receive the modified port numbers of the Distribution Server and communicate with it henceforth.
What is IP Scope and what are its advantages?
DEX Manager Plus has different agents for different locations, for example a local office agent will not be the same as the remote office agent. Similarly every remote office has different agents as well. When you are managing computers in one or more remote locations, you can have a defined set of IP ranges for different offices. This enables the product server to identify the agents with respect to the IP range. So whenever a computer is moved from a local office to a remote location, IP scope is used to automatically detect and deploy the respective WAN agent. DEX Manager Plus will check for the change in the IP address periodically and will deploy the appropriate agents whenever a change is detected.
How to remove a computer from the Scope of Management (SoM)?
To remove a computer that has been taken offline, navigate to Admin >> Scope of Management >> Computers, select the computers that have been taken offline, and click on "Remove Computer(s)".
What are the various methods of agent installation?
DEX Manager Plus agents can be installed using multiple methods including: manual installation using the agent package, Active Directory Group Policy Object (GPO) deployment, using a GPO startup script, through the lightweight GPO tool, by configuring the GPO Scheduler, installing agents on cloud instances such as Microsoft Azure, or deploying directly via the product console.
How to add computers to be managed in LAN? / How to define the Scope of Management (SoM)?
Navigate to Admin >> Scope of Management and select the option to add computers. You can add systems from Active Directory, workgroups, or by specifying IP ranges. Computers added here will automatically be included for management by DEX Manager Plus.
How to add details of remote offices?
To add a remote office, go to Admin >> Scope of Management >> Remote Offices and provide details such as office name, IP range, WAN agent type, and the communication port. You can also configure distribution servers for bandwidth optimization.
How to manage roaming users' desktops?
Roaming users can be managed by configuring the agents to communicate with the DEX Manager Plus server over the internet. When the user moves outside the LAN, the agent continues to check in with the server using HTTPS communication. VPN or public IP configurations may also be applied.
How to add a device to the SoM, but exclude it from being managed?
Add the device to the Scope of Management and then mark it as "excluded" from management in the settings. This ensures the device is inventoried but will not receive configurations or deployments.
How to install/uninstall agents using various methods?
Agents can be installed via the console, GPO, GPO Scheduler, or manually using setup files. To uninstall, go to Admin >> SoM >> Computers, select the computer, and choose Uninstall Agent. End users can also uninstall if enabled in Add/Remove Programs.
How to use "Waiting for Approval" after agent installation?
Enable the "Waiting for Approval" option in Admin >> SoM settings. Newly installed agents will remain inactive until approved by an administrator. This ensures only trusted machines are managed.

Inventory

How to set up inventory scanning

Prerequisites: Ensure the DEX Manager Plus agent is installed and communicating with the server.

Set up inventory scanning

  1. Go to Inventory > Settings (or Admin > Inventory).
  2. Open Scan Settings and choose the scan frequency (e.g., daily/weekly) and scan window.
  3. Enable Hardware and Software inventory collection as needed (include Product Keys, Installed Apps, License where applicable).
  4. Click Save. Devices will scan on their next refresh interval; to scan immediately, select devices in Inventory > Computers and click Scan Now.
Note
Inventory collection also occurs during the agent's 90-minute refresh cycle and at user logon/logoff if configured.

Reports

Enable user logon tracking

Enable user logon tracking so reports show who used each device and when.

  1. Navigate to Admin > Agent > User Logon Settings.
  2. Enable Track user logon/logoff events.
  3. Choose when to collect data: on every logon/logoff and/or during the agent’s refresh interval.
  4. Apply the setting to the required groups or all computers and Save.
  5. View reports under Reports > User Logon Reports (or Inventory > Users in some builds).
Tip
If a device is shared, enable both logon and logoff capture to get accurate session durations.
How often will the logged on User names be refreshed?
The list of user names will be updated in three scenarios as specified below.
  • During 90 minutes refresh interval while the agent communicates with the server.
  • During every user log on if it is configured in the User Logon Settings.
  • During every user logoff.

Digital Employee Experience

Create sensors

Create sensors to collect custom endpoint metrics for DEX Manager Plus Endpoint Analytics.

  1. Go to Sensors and click Add Sensor.
  2. Enter a Name and optionally add a Description.
  3. Under Configure Script, click Add Field to define input parameters for the script:
    • Display Name and Field Name (required).
    • Select a Data Type (String, Integer, Long, Double).
    • Optionally set a Default Value, Description, and mark the field as PII Column if it contains sensitive data.
  4. Write or paste your script in the PowerShell Script Writer area. (Note: Fields must be created first—predefined "Write Out" sections are auto-generated for you.)
  5. If required, specify Script Argument(s) (space-separated and enclosed in double quotes for multiple values).
  6. In Execution Settings, set the Run history retention limit to define how many runs’ data should be retained.
  7. Click Save to add the sensor.

Examples

Windows — Last Boot Time

PowerShell:

(Get-CimInstance Win32_OperatingSystem).LastBootUpTime

Output type: Text

Windows — System Drive Free %

PowerShell:

$d = Get-WmiObject Win32_LogicalDisk -Filter "DeviceID='C:'"; [math]::Round(($d.FreeSpace/$d.Size)*100,2)

Output type: Number

macOS/Linux — Average Load (1 min)

Shell:

uptime | awk -F'load averages?: ' '{print }' | awk -F, '{print }'

Output type: Number

Note
Run scripts with least privileges needed. Validate output formats so dashboards and thresholds work as expected.
Create a workflow

Use workflows to automate routine endpoint tasks in DEX Manager Plus.

  1. Open DEX > workflowsand click Create Workflow.
  2. Choose a trigger: manual, schedule, event/threshold (e.g., sensor value, alert), or device state.
  3. Add blocks:
    • Conditions (if/else based on device, user, sensor output).
    • Actions (run Remote Action/script, notify via email/ITSM, move to group, enforce policy, etc.).
  4. Select the scope (devices/groups) and publish the workflow.
  5. Run on demand or attach a schedule. Monitor executions under Workflow Runs.
Tip
Start with a pilot group and add a dry-run notification step before remediation to validate logic.
Was this document helpful?
Yes
No