Home
Administrator Guide
Read this guide to learn about enrolling, administering, and troubleshooting endpoints through BigFix MCM and BigFix Mobile.
BigFix MCM
Read this section to learn enrolling and managing Windows and macOS desktop and laptop devices.
Enrolling Windows devices
You can get Windows 10 and Windows 11 devices enrolled in BigFix MCM in many ways.
Autopilot enrollment with Offline Domain Join service
Read this page to learn the ODJ architecture in MCM and the high-level process flow for enrolling Autopilot enabled Windows devices with ODJ service.
Hybrid AD join verification
After a successful autopilot enrollment with Hybrid Azure AD join, verify the following:

Administrator Guide
Read this guide to learn about enrolling, administering, and troubleshooting endpoints through BigFix MCM and BigFix Mobile.
- Modern Client Management and BigFix Mobile
  This guide is intended for HCL BigFix Master Operators (MO) and those who administer BigFix deployments. If you are looking for information about using Modern Client Management (MCM) and BigFix Mobile, see the WebUI User's Guide.
- BigFix MCM
  Read this section to learn enrolling and managing Windows and macOS desktop and laptop devices.
  - Enrolling Windows devices
    You can get Windows 10 and Windows 11 devices enrolled in BigFix MCM in many ways.
    - Enrolling through enrollment URL - Windows
      Read this section to understand how the users can enroll Windows 10 and Windows 11 devices to MDM when the admin shares the enrollment URL.
    - Bulk enrollment - Windows
      Bulk enrollment is an efficient way to set up and enroll a huge number of Windows devices to BigFix MCM.
    - Autopilot enrollment - Windows
      BigFix MCM supports Windows Autopilot enrollment.
    - Autopilot enrollment with Offline Domain Join service
      Read this page to learn the ODJ architecture in MCM and the high-level process flow for enrolling Autopilot enabled Windows devices with ODJ service.
      - Hybrid AD join verification
        After a successful autopilot enrollment with Hybrid Azure AD join, verify the following:
    - Enrollment by non-admin device users
      BigFix MCM facilitates non-admin device users to enroll the domain-joined devices to MDM and manage them.
    - SCEP enrollment
      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.
  - Enrolling Apple devices
    You can get Apple devices enrolled in BigFix MCM in the following ways.
  - Full Disk Encryption
    With BigFix MCM, you can centrally manage the native full-disk encryption technologies from Windows (BitLocker) and macOS (FileVault2) to secure data at rest.
  - OS update
    MDM administrators can remotely manage software updates such as software patches, minor or major versions. This can help secure or enhance the current operating system.
- BigFix Mobile
  BigFix Mobile enables you to enroll and manage Android, iOS, and iPadOS devices.
- SCEP Certificate-based authentication
  BigFix MCM supports 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.
- SAML-authenticated enrolment flow
  When you configure SAML as the authentication method, when a user hits the enrollment URL and click Enroll, the user is first authenticated via the identity provider before proceeding with the enrollment process.
- Application management
  Application management in BigFix MCM enables IT admins to centrally control, distribute, and maintain Windows and macOS applications. It allows IT administrators to streamline the deployment, update, and security of apps on enrolled devices.
- Email configuration management
  With BigFix MCM and BigFix Mobile, you have the ability to install and set up email application that can connect to your email system. This allows users to easily connect, verify their identity, and synchronize their work email accounts on their devices.
- VPN management
  BigFix MCM and BigFix Mobile enable organizations to manage and configure Virtual Private Network (VPN) settings on enrolled Android, Apple, and Windows devices, ensuring secure remote access to corporate networks.
- Wi-Fi configuration management
  BigFix MCM and BigFix Mobile offer WiFi configuration management, where administrators can control and configure the wireless network settings on MCM-enrolled devices. This helps organizations to maintain a secure and reliable wireless network infrastructure while providing flexibility for users to connect to authorized networks.
- Known limitations
  Read this topic to get familiarized with MCM v3.0 known limitations.
- Troubleshooting
  This section is intended to help you solve problems that might occur when installing BigFix MCM and BigFix Mobile.
- Frequently Asked Questions
  Read this section for commonly asked questions and their answers to manage the MCM deployments better.

Hybrid AD join verification

After a successful autopilot enrollment with Hybrid Azure AD join, verify the following:

You can ensure if an enrolled Windows endpoint is Hybrid Azure AD joined by verifying the following:

Active Directory: Log in to the Active Directory as an Admin user, navigate to Active Directory Users and Computers > Autopilot Domain Join and verify if the enrolled computer name is listed under the specified organization unit.

Azure AD

Log in to Azure AD as an Admin user and verify if the Join Type of the device is "Hybrid Azure AD joined".

Note:

The domain joined device is synchronized to Azure AD portal only after successful login using on-premises domain credentials.
Azure AD connect synchronizes the on-premises object with Azure AD in every 30 minutes.
Therefore, wait for a maximum of 30 minutes for the device to get listed in the Azure AD portal.

Windows endpoint

Ensure if dual account is provisioned at the endpoint.
Note: If Azure Primary refresh token is not successfully updated, SSO connect is not established, and so, the Azure AD account does not get provisioned. As a workaround, device user can manually sign-in with Azure AD credentials to provision the account by clicking the MDM Sync option under the domain account. This action must be performed only after the device is listed as ‘Hybrid Azure AD joined’ under Azure AD portal.
Ensure if the On-premises MDM synchronization is successful.
Ensure the device registration status reflects "YES" for both AzureAdJoined and DomainJoined.
Under the SSO state section, Device registration status must reflect AzureAdPrt as ‘YES’ .

For further reference to verify if a Windows endpoint is dual joined, see https://learn.microsoft.com/en-us/azure/active-directory/devices/howto-hybrid-join-verify.