Sensors

Overview

Sensors in DEX Manager Plus allow IT administrators to define and collect custom device metrics that go beyond standard performance indicators. These script-based data collectors enable organizations to capture real-time, environment-specific data—such as registry values, hardware compatibility, event information, and application-specific details (antivirus status, and so on)—to enhance visibility and drive automated decision-making.

Sensors are highly flexible and can be used to power workflows, generate reports, and surface meaningful insights tailored to your unique endpoint environment.

Why Use Sensors?

Accessing the Sensors Module

Navigate to Sensors from the left-hand pane of the DEX tab. The main view lists all created sensors with their names, types, and usage status. Use the Add Sensor button to create new ones.

Generating Sensors Using Ask Zia

DEX Manager Plus integrates Ask Zia — an AI-powered virtual assistant — directly within the Sensors module. IT professionals can generate custom sensors instantly by describing their monitoring requirements in natural language, eliminating the need to create sensor scripts manually from scratch.

Powered by OpenAI technology, Ask Zia understands your endpoint monitoring requirements and generates ready-to-use sensor scripts in seconds. This enables your team to quickly create sensors, monitor device health and configurations, and automate endpoint management with minimal effort.

Steps to Generate a Sensor Using Ask Zia

1. Navigate to DEX > Sensors.

2. Click the Ask Zia button available next to Add Sensor or within the Add Sensor view.

   

3. A chat panel opens on the right side of the screen.

4. Select a suggested prompt or enter your own requirement. For example:

   • "Create a sensor to check the available disk space on the C: drive"

   • "Generate a sensor to verify whether Google Chrome is installed"

   

5. Based on your requirement, Zia generates a sensor script compatible with Windows, macOS, or both platforms.

   

6. Review the generated sensor script, make any necessary modifications, and save the sensor.

Creating a Sensor

Step 1: Define Sensor Details

• Sensor Name: Enter a unique, descriptive name.
• Description (optional): Summarize the sensor’s purpose or logic.

Step 2: Declare Fields

Use Add Field to define input/output variables. These fields act as data carriers between the sensor and the script. You can define field type (string, number, and so on) and optionally flag fields as PII for compliance.

Step 3: Write the Script

Use the built-in Script Writer to compose your PowerShell script. Fields defined above are available as variables. The script must output structured values that match the declared fields.

Step 4: Set Run History Retention

Define how many execution records should be stored per deployment execution. Minimum: 1, Maximum: 5. This helps track trends over time and enables post-event analysis.

Step 5: Save

Click Save to add the sensor to your repository. The sensor is now available to deploy for data collection on targeted endpoints.

Deploying a Sensor

A saved sensor collects data only after it is deployed to devices. You can deploy a sensor from two places, and both create the same deployment:

• From the sensor’s own Deployment tab — convenient when you are already working on that sensor.
• From the Deployments module — convenient when you are setting up several deployments together.

Sensors support Immediate and Schedule deployment modes. For full details on deployment, targeting, and monitoring, see Deployments.

Deploy from the Sensor’s Deployment Tab

1. Open the sensor, then select the Deployment tab.
2. Click Create Deployment.
3. Enter a Deployment Name and an optional description.
4. Select one or more Custom Groups to define the scope. Use the include / exclude options for finer targeting.
5. Set the Deployment Mode to Immediate or Schedule. If you choose Schedule, set the frequency, active period, and run time.
6. Click Deploy.

Deploy from the Deployments Module

Set the Type to Sensor when creating the deployment. For the full procedure, see Creating a Deployment.

Best Practices