Welcome
Installation and Configuration
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.

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.
Overview
This section guides you through BigFix Modern Client Management (MCM) and BigFix Mobile to understand the MCM concepts, terminologies, features, and functionality.
Guides in PDF format
This section contains links to PDF versions of all the MCM and BigFix Mobile manuals.
Installation and Configuration
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.
- Identity service configuration
  Starting from UEM3.0, MCM extends the capability to identify and manage devices based on users. The users can be identified based on their associated attributes including names, roles, group memberships, distribution list memberships, or physical locations. The devices identified based on users can then be targeted and managed through various configurations to provide conditional access and ensure compliance, endpoint security, and App protection.
- 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.
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.

Installation and Configuration

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.

Mandatory Credentials for Secure Communication within BigFix MDM Servers

To ensure secure and seamless communication within BigFix MDM (Mobile Device Management) servers, the following credentials are mandatory:

TLS Certificate signed by a trusted Certificate Authority (CA): Essential for establishing secure connections over the Transport Layer Security (TLS) protocol.
Apple Push Notification Service (APNS) Certificate: Required for sending push notifications to iOS and macOS devices. Integration with Apple APNS enables our platform to securely communicate with Apple's servers and deliver notifications to your users' devices.
Google credentials: Necessary for integrating with Google services, particularly for Android devices. This token allows our platform to authenticate and interact with Google's servers, facilitating the delivery of notifications and access to other Google services as needed.
Windows Notification Service (WNS) Credentials: Essential for sending push notifications to Windows devices. These credentials enable communication with Microsoft's servers, ensuring the delivery of notifications to Windows-based devices.

For initial MDM server installation, follow the instructions at On-premises deployment setup.

After the initial MDM server installation, to configure the environment to support additional features, read the following topics.

Important: While both Windows Notification Service (WNS) and Azure Active Directory (Azure AD) require a Microsoft account for setup, they are separate services and do not share data or have a direct link between them.

Windows Notification Service (WNS): WNS provides push notification services for Windows applications. This is primarily for sending real-time notifications to Windows-based devices.
Azure Active Directory (Azure AD): Azure AD is an identity and access management service used for secure authentication, often for managing user access to applications and services within Microsoft’s cloud ecosystem.

To add feedback about this topic, select the following checkbox:

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners Four, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site. Personal data should not be shared in this comment box. See our Privacy Statement to understand how personal data is used.