Welcome
BigFix Workspace - US Federal
BigFix Digital Employee Experience (DEX)
Administrating DEX
DEX Installation
This topic provides a detailed sequence of steps required to install all BigFix DEX components. The installation must follow this order: Data services (MSSQL, ClickHouse, NATS JetStream: any order) > DEX Server > (DEX FillDB + Root Server DEX Plugin: any order) > Configure DEX in BFUI → Scanner DEX Plugin on endpoints.
Installation process
The below sections describe each installation step in detail.
Configure DEX in BFUI
To configure the BigFix UI to show the DEX application to the users with 'DEX dashboard' privileges, use the BigFix UI command line to configure DEX.

BigFix Documentation Homepage
BigFix Workspace
BigFix Workspace+
BigFix Workspace - US Federal
- BigFix Platform
- BigFix Lifecycle
- BigFix Remediate
- BigFix Compliance
- BigFix Inventory
- CISA KEV Content Pack
- Windows ESU
- RHEL ESU
- PCI DSS
- BigFix Digital Employee Experience (DEX)
  - Using DEX
    Welcome to the BigFix DEX documentation, where you can find information about how to install and configure BigFix DEX (Digital Employee Experience). DEX is a endpoint experience management application that provides simplified view of your IT environment and make well-informed decisions to increase the productivity of employees.
  - Administrating DEX
    - DEX Installation
      This topic provides a detailed sequence of steps required to install all BigFix DEX components. The installation must follow this order: Data services (MSSQL, ClickHouse, NATS JetStream: any order) > DEX Server > (DEX FillDB + Root Server DEX Plugin: any order) > Configure DEX in BFUI → Scanner DEX Plugin on endpoints.
      - Prerequisites
        Before installing DEX, the following set of prerequisites must be met.
      - System support and requirements
        This topic provides information about the system requirements for DEX.
      - Firewalls configuration
        This section provide info on the Firewall rules needed to consent DEX data flow.
      - Capacity Plan
        Capacity Planning is the proactive practice of checking your IT environments' current endpoint usage and forecast when they will run out of resources. The main objective is to prevent performance drops or system crashes before they happen.
      - Installation process
        The below sections describe each installation step in detail.
        Installing MS SQL
        BigFix DEX relies on an enterprise database backend to aggregate, process, and retain metrics. For this purpose, the architecture requires Microsoft SQL Server to be installed to manage and store logs and scores.
        Installing ClickHouse
        The ClickHouse DB installation sets specialized database built to handle large amounts of data in BigFix DEX.
        Installing NATS JetStream
        NATS JetStream is a messaging system that stores, queues, and delivers data across BigFix DEX components.
        Installing DEX Server
        This is the central component responsible for orchestrating data ingestion and communication between MSSQL, ClickHouse, and NATS JetStream. It must be deployed only once per DEX environment.
        Installing DEX FillDB
        The DEX FillDB is responsible for collecting data from BigFix-managed endpoints and pushing them into the database.
        Installing Root Server DEX Plugin
        This plugin integrates the BigFix Root Server with DEX components for data forwarding and management.
        Configure DEX in BFUI
        To configure the BigFix UI to show the DEX application to the users with 'DEX dashboard' privileges, use the BigFix UI command line to configure DEX.
        Installing Scanner DEX Plugin
        This is an endpoint component. This is a plugin for the BigFix Scanner that enables all DEX use cases. Therefore, it is critical that the BigFix Scanner is already deployed on all endpoints that are intended to be DEX-enabled, as the plugin depends on the scanner’s presence to work correctly.
      - Fixlets
        In this section all the install fixlets details are showed.
      - Analyses
        In this section all the analyses details are showed.
      - BigFix Self-Service Application
        The BigFix Self-Service Application (SSA) is a client-side interface that empowers endpoint users to install software, accept administrative actions, and review deployments without requiring local administrator privileges.
    - Configuration
      BigFix DEX provides four configuration Fixlets, one for each DEX component, to support post-installation configuration and reconfiguration.
    - Upgrade
      The upgrade Fixlets are available for each of the four DEX components, which internally refers to the same directory path where the installation was previously performed.
  - Integrations available with DEX
    The Service Now, Remote Control and Historical data integration are available using the APIs. For information on the respective areas, refer to their documentations.
  - Troubleshooting DEX Application Issues
    This section provides information about the types of issues and the ways to solve it.
- BigFix Resolve

Configure DEX in BFUI

To configure the BigFix UI to show the DEX application to the users with 'DEX dashboard' privileges, use the BigFix UI command line to configure DEX.

Command-line settings and configuration

After the initial setup, when the BigFix UI is not running, start the application with the BFUI.exe --configure-dex flag.

The user must enter the following set of parameters:

The BFUI Instance Admin user created during BFUI installation.
The DEX Server IP address is the address of the system where the DEX Server is running.
The Basic Auth Port (default is 8081) is the port used for communication to initialize the mTLS certificate exchange. If you use the ServiceNow integration, port 8081 must also stay open after the exchange; see Creating Basic Auth for ServiceNow Integration in DEX.
mTLS port (default is 9443) is the port used to communicate with the DEX Server for mTLS requests.
The DEX Instance Admin username is the instance administrator of the DEX Server created during the DEX server installation (local user defined on DEX Server).
BigFix Operator is the master operator that is used by BigFix UI to retrieve data from the BigFix Server.
The SANs can be inserted in a comma-separated list; the first one must match the DEX Server IP address. Others are optional.
The custom site has to be filled with one custom site that has already been created from the Console. This site has to be owned by the BigFix Operator (see above).