---
# source: src/content/solutions/en/omnissa/workspace-one/omnissa-dex.md
# route:  /en/solutions/omnissa/workspace-one/omnissa-dex/
title: Omnissa DEX
tags: [modern-workplace, monitoring, endpoint-security]
vendors: [omnissa]
summary: "Measures what the workplace is actually like to use: boot times, crashes, logon duration, network quality. One slow laptop is a ticket, forty is a cause."
photoNeed: "A Horizon or Workspace ONE session in use: a virtual desktop on a real screen, or a thin client on a real desk"
stub: false
draft: false
kind: product
addon: true
sourceNote: Omnissa, Omnissa Workspace ONE edition comparison, Workspace_ONE_Editions_Comparison_7-8-26.pdf, table Workspace ONE add-ons, read 2026-08-30
vendorName: Workspace ONE Experience Management
status: current
practice: >
  Draft, not yet reviewed. Telemetry from every endpoint is also a record of how individual people work. Who may see which view, and how long it is kept, is a data protection question and in some companies a works council one. We settle it before the agent is rolled out, not after somebody notices.
practiceReview: true
---

## What it is

DEX is the measurement half of the digital workplace. Devices, applications and connections
report continuously, and the result is an answer to a question most IT departments can only
guess at: what is it actually like to work here?

## What it measures

CPU and memory load, free disk, battery health, how often a machine restarts, application
crashes, logon duration, network quality and VPN failures. Individually these are numbers.
Grouped by device model, operating system version, application version, location or
department, they become a pattern.

## Why the pattern is the point

One person with a slow logon is a support ticket. Forty people on the same notebook model
with a slow logon is a cause, and it can be fixed once instead of forty times. The same
grouping answers the question after a rollout: did the update make anything better, and by
how much, measured rather than felt.

## What it does about it

Two things, and both reduce tickets rather than route them faster. Automatic remediation
handles the cases with a known fix: run a cleanup when the disk fills, reinstall or update
an application version that is crashing, restart a service that has stopped. Self-service
gives the same repertoire to the person at the keyboard, so reinstalling an application or
refreshing a VPN profile does not need a ticket at all.

## What to watch

The interesting number is not the experience score. It is the drift: logons that have
lengthened by four seconds a month, a battery cohort ageing faster than the others, a
driver that has started failing on one hardware generation. Those are visible before anyone
complains, and only if somebody is looking.
