Welcome
Installing and Configuring BigFix Mobile and MCM
Read this guide to learn about the requirements and available installation scenarios to ensure that the deployment of BigFix MCM and BigFix Mobile goes smoothly in your environment.
MCM and BigFix Mobile server and components installation
This guide provides instructions for installing the MCM and BigFix Mobile server along with its components, ensuring proper setup and configuration.
Troubleshooting
This section is intended to help you solve problems that might occur when installing BigFix MCM and BigFix Mobile.
Installation Failure with Exit Code 1
When the installation fails with `Exit Code 1`, there could be several possible causes related to Docker, Docker Compose, or system configuration. This document outlines the most common symptoms, how to troubleshoot and debug the issue, and provides possible causes with solutions for each case.
Docker client version too old (API Version 1.22 Not Supported)
This issue occurs because the installed Docker version is too recent to support the YAML configuration referencing an older Docker client version (1.22). Minimum supported API version is 1.24 suggests that the configuration file (docker-compose.yml) is using an outdated syntax or version (e.g., version: "2.0") that is no longer compatible with the updated Docker installation.

BigFix Documentation Homepage
Modern Client Management and BigFix Mobile
Welcome to the Modern Client Management and BigFix Mobile documentation, where you can find information about how to install, maintain, and use Modern Client Management and BigFix Mobile.
BigFix Mobile and MCM Overview
Discover how BigFix Mobile and Modern Client Management (MCM) extend unified endpoint management to mobile devices and modern OS platforms like iOS, Android, and Windows 10+, all from a single console.
Guides in PDF format
This section contains links to PDF versions of all the MCM and BigFix Mobile manuals.
Installing and Configuring BigFix Mobile and MCM
Read this guide to learn about the requirements and available installation scenarios to ensure that the deployment of BigFix MCM and BigFix Mobile goes smoothly in your environment.
- MCM and BigFix Mobile server and components installation
  This guide provides instructions for installing the MCM and BigFix Mobile server along with its components, ensuring proper setup and configuration.
  - Audience
    This guide is for administrators and IT managers who want to install and configure BigFix MCM and BigFix Mobile. It details prerequisites for each of the scenario and provides installation instructions that allow you to deploy the program in your environment. It also includes information about configuring and maintaining BigFix MCM and BigFix Mobile components.
  - Planning the installation
    Read this section before you begin to install or update any of the BigFix MCM or BigFix Mobile product features. Effective planning and an understanding of the key aspects of the installation process can help ensure a successful installation.
  - On-premises deployment setup
    Understand the prerequisites and preparation required to install the BigFix MDM server and BigFix PlugIn Portal on-premise.
  - On-Premises Upgrade
    Upgrade your on-prem BigFix Mobile and MCM setup to the latest version for improved security, new features, and better support for Apple, Android, and Windows devices. Learn how to update the MDM Server and Plugin, meet key prerequisites like Plugin Portal and Podman, and complete the upgrade with minimal disruption.
  - Configuring BigFix MCM and BigFix Mobile
    After the MCM components are set up, there are additional configuration options available to enable features like Bulk Enrollment for Windows, DEP policies for macOS, or prestage installers for Windows and MacOS MDM endpoints.
  - Reference Information
    This section contains more detailed information about some of the essential installation aspects.
  - Troubleshooting
    This section is intended to help you solve problems that might occur when installing BigFix MCM and BigFix Mobile.
    - Prerequisite & Connectivity Scan
      This document provides help and recommendations for all system prerequisite, port, and connectivity checks relevant to RHEL 8 and RHEL 9 installation servers.
    - Logging
      The MCM component generates log files which can provide extra information when you troubleshoot an issue.
    - Windows error codes
      The following includes commonly encountered error messages and related information.
    - Installing Docker CE and Docker compose on RHEL 8 or RHEL 9
      Starting from BigFix MCM v3.3, Podman is the default container runtime for RHEL 8 and later. Docker CE is no longer required for container management. This page remains available for reference, but it applies only to older releases where Docker CE was supported.
    - Troubleshooting LDAPS connection
    - Troubleshooting Azure connection
    - DEP troubleshooting
      You can find DEP enrollment troubleshooting information in this section.
    - MDM debug tool
      This command-line tool can be used to set log levels for individual/group/all MDM modules, execute commands and update policy settings on the MDM enrolled devices using REST APIs. This will be helpful to quickly debug production issues when there is a communication failure at different MDM layers and to trace the execution work flows, requests, responses from/to end points.
    - Ignore MDM server vulnerability due to TLS 1.0
      Read this section to address MDM Server security exposure.
    - Error while reinstalling MDM server
      Read this page to troubleshoot the error while reinstalling an MDM server after uninstalling the same.
    - Installation Failure with Exit Code 1
      When the installation fails with `Exit Code 1`, there could be several possible causes related to Docker, Docker Compose, or system configuration. This document outlines the most common symptoms, how to troubleshoot and debug the issue, and provides possible causes with solutions for each case.
      - Docker Compose installed but not found in system path
        Even though docker compose is installed, as confirmed by running docker-compose -v (which correctly displays the version), running one of the following commands might return empty output, indicating that the system cannot find the binary in expected path.
      - Docker client version too old (API Version 1.22 Not Supported)
        This issue occurs because the installed Docker version is too recent to support the YAML configuration referencing an older Docker client version (1.22). Minimum supported API version is 1.24 suggests that the configuration file (docker-compose.yml) is using an outdated syntax or version (e.g., version: "2.0") that is no longer compatible with the updated Docker installation.
      - Docker Daemon Not Running
        The Docker daemon is a background service that manages Docker containers on the host system. When the Docker daemon is not running, attempts to start docker containers will fail. Common indications of this symptom include error messages when attempting to execute Docker commands, such as docker images or docker ps, which may state that the daemon is unreachable or that the Docker command cannot connect to the Docker socket.
    - Clean Installation for MDM Server & Plugin
      Recommended steps for performing a clean reinstallation of the MDM Server and MDM Plugin when there are no enrollments or other configurations.
- Identity Service Configuration
  Configure identity services for BigFix Mobile and MCM to enable secure authentication and seamless user access. Learn how to integrate with identity providers and streamline user management across Apple, Android, and Windows devices.
- Simple Certificate Enrollment Protocol (SCEP) configuration
  BigFix MCM supports certificate management and certificate-based authentication through Simple Certificate Enrollment Protocol (SCEP). SCEP is the fastest and most secure way to provision certificates to all your MCM-managed devices. With SCEP, IT Admins can automate issuing certificates to the endpoints to provide access to corporate Wi-Fi, VPN, and secure e-mail through encryption.
- Domain join installation and configuration
  Read this section to learn the prerequisites and the tasks to install ODJ service to set up your environment to enroll Windows devices and join Active Directory domain or both Active Directory and Azure AD domain.
- SAML-authentication configuration
  MCM and BigFix Mobile supports Security Assertion Markup Language (SAML) authentication to enroll devices to protect sensitive data and ensure secure access to corporate resources.
- Remote Access
  The Remote Access feature in BigFix Modern Client Management (MCM) allows administrators to view the screen of managed mobile devices through the BigFix WebUI for troubleshooting and support purposes.
Deployment Guide
This document provides guidance for deploying the certificate enrollment infrastructure required for BigFix Mobile Configuration Management (MCM). It describes how to integrate BigFix MCM with Microsoft certificate services to enable device certificate enrollment using the Simple Certificate Enrollment Protocol (SCEP).
How-to guide
This section provides step-by-step instructions for setting up a BigFix environment, focusing on integration with third-party prerequisites such as Apple Business Manager and Google Play. It guides users through the necessary configuration steps to ensure seamless interoperability with these external services.
Quick Start
This quick start guide gets you up and running with your BigFix MCM and BigFix Mobile solution. It helps you secure, configure, and manage your mobile devices quickly and efficiently.
User Guide
Administrator Guide
Read this guide to learn about enrolling, administering, and troubleshooting endpoints through BigFix MCM and BigFix Mobile.
Glossary
This glossary provides terms and definitions for the BigFix software and products.

Docker client version too old (API Version 1.22 Not Supported)

This issue occurs because the installed Docker version is too recent to support the YAML configuration referencing an older Docker client version (1.22). Minimum supported API version is 1.24 suggests that the configuration file (docker-compose.yml) is using an outdated syntax or version (e.g., version: "2.0") that is no longer compatible with the updated Docker installation.

Steps to Identify the Symptom

Execute the following command on the MCM server to trigger the error:
```
/opt/BESUEM/service-mdm.sh restart
```
Check the installed Docker version by running:
```
docker --version
```
If the Docker version is greater than 1.24, this symptom may occur due to the incompatibility between the Docker Compose YAML configuration and the newer Docker version.

Possible Cause

The issue is caused by an unsupported Docker version being installed that does not align with the version specified in the Docker Compose configuration file.

Solution

To resolve this issue, install MCM using a fixlet with version number 3.2.0.x, which will update the Docker Compose YAML configuration to use a compatible client API with the installed Docker version.