Skip to main content

Category filter

Enroll Windows 11 devices with Google Workspace when OOBE shows invalid_client

TL;DR

Windows 11 OOBE may return an invalid_client error when a Google Workspace account is entered at the Work or School account sign-in step. This occurs because Windows routes that prompt through Microsoft Entra ID (Azure AD), which expects a Microsoft-managed identity. To enroll the device with Hexnode using Google Workspace, bypass the OOBE cloud sign-in, create a Local Offline Account, reach the Windows desktop, and install the Hexnode Agent from the enrollment URL. For the highest level of automation, use a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment.

Executive Summary

Windows 11 OOBE does not accept Google Workspace credentials through the native Work or School account cloud sign-in flow when Microsoft Entra ID is expecting a Microsoft-managed account. The resulting invalid_client error is a Microsoft Entra ID restriction, not a Hexnode enrollment failure.

There are two supported enrollment paths depending on the deployment requirement:

  • Manual enrollment workaround: Bypass OOBE cloud sign-in, create a local offline Windows account, then install and enroll the Hexnode Agent from the desktop using Google Workspace authentication.
  • Automated deployment: Use a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment to reduce or eliminate user-driven installation steps.

Why the invalid_client error appears during Windows 11 OOBE

During Windows 11 OOBE, the Work or School account option expects an identity that Microsoft Entra ID can validate. If a Google Workspace account is entered in this prompt, Windows attempts to route the sign-in through Microsoft Entra ID. Microsoft Entra ID can reject the sign-in with invalid_client when the account is not a Microsoft-managed identity or does not have a matching Microsoft license.

Note:


The invalid_client response at the Windows OOBE Work or School account screen is caused by the Microsoft sign-in flow. It does not indicate that the Hexnode Agent or Hexnode enrollment URL is unavailable.

Choose the correct enrollment workflow

Requirement Recommended workflow
Enroll a Windows 11 device immediately using Google Workspace credentials Bypass OOBE cloud sign-in, create a Local Offline Account, then enroll with the Hexnode Installer from the desktop.
Minimize end-user actions during setup Use a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment.

Manually enroll the device after bypassing OOBE cloud sign-in

Use this workflow when a Windows 11 device must be enrolled with Google Workspace credentials but the OOBE Work or School account sign-in fails with invalid_client.

Prerequisites

  • Access to the device during Windows 11 OOBE.
  • The Hexnode enrollment URL for the portal.
  • Administrator permission to run the Hexnode Installer setup file on the Windows device.
  • The required Google Workspace domain must be available in the Hexnode authentication Domain dropdown during enrollment.

Step 1: Bypass the Microsoft cloud sign-in prompt

  1. Return to the Windows 11 OOBE account login page from the error screen.
  2. Temporarily disconnect the device from the internet by unplugging Ethernet or disconnecting from Wi-Fi.
  3. If Windows forces online setup, enter a dummy blocked email address in the sign-in field and enter any random password.
  4. When Windows displays Something went wrong, select Next.
  5. Create a Local Offline Account.
  6. Complete the remaining OOBE setup steps until the Windows desktop is available.
  7. Reconnect the device to the internet.

Step 2: Install and enroll the Hexnode Agent using Google Workspace authentication

  1. Open a web browser on the Windows device.
  2. Go to the Hexnode enrollment URL for the portal.
  3. Select Download to download the Hexnode Installer setup file.
  4. Run the installer wizard.
  5. Grant administrator permissions when prompted.
  6. Select Agree and Enroll.
  7. In the Hexnode authentication window, change the Domain dropdown from Local to the required Google Workspace domain.
  8. Enter the user’s Google Workspace email address and password.
  9. Select Authenticate to complete enrollment.
Note:


Do not use the Windows 11 OOBE Work or School account prompt for Google Workspace authentication. Use the Hexnode Agent enrollment flow from the Windows desktop instead.

Use a Windows Provisioning Package for automated enrollment

For deployments where the Hexnode Agent should be installed and enrollment should occur with minimal user action, use a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment.

This approach is recommended when the Windows 11 OOBE Microsoft cloud sign-in flow blocks Google Workspace credentials, but the deployment still requires a more automated onboarding experience than manual desktop enrollment.

  • The provisioning package is used to preconfigure the Windows device during setup.
  • Hexnode Open Enrollment is used with the provisioning workflow to enroll devices without relying on the OOBE Work or School account sign-in prompt.
  • This workflow is suitable for larger deployments where manual download and enrollment of the Hexnode Agent is not preferred.

Troubleshooting

Windows 11 shows invalid_client at the Work or School account step

This indicates that Microsoft Entra ID rejected the Google Workspace account in the native Windows OOBE sign-in flow. Bypass the cloud sign-in prompt and enroll from the desktop using the Hexnode Agent, or deploy through a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment.

The user is asked to authenticate with Local instead of Google Workspace

In the Hexnode authentication window, change the Domain dropdown from Local to the required Google Workspace domain before entering the user’s credentials.

Manual installation is not acceptable for the deployment

Use a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment instead of the desktop installer workflow. This is the recommended path when the goal is to reduce end-user actions during Windows device setup.

Frequently Asked Questions

Can Google Workspace credentials be used directly in the Windows 11 OOBE Work or School account screen?

No. The Windows 11 OOBE Work or School account flow expects Microsoft Entra ID to validate the identity. Google Workspace credentials can be rejected with invalid_client in that flow.

Is invalid_client a Hexnode Agent error?

No. In this scenario, invalid_client is generated by the Microsoft Entra ID sign-in flow during Windows OOBE. The device can still be enrolled in Hexnode after reaching the Windows desktop or by using a provisioning package workflow.

What is the fastest workaround for a single device?

Create a Local Offline Account during OOBE, reach the Windows desktop, download the Hexnode Installer from the enrollment URL, and authenticate with the Google Workspace domain in the Hexnode enrollment window.

What is the recommended method for large-scale deployment?

Use a Windows Provisioning Package (.ppkg) with Hexnode Open Enrollment to automate enrollment and avoid depending on the Windows OOBE Microsoft cloud sign-in prompt.

Troubleshooting Guides