mirror of
https://github.com/fleetdm/fleet
synced 2026-05-21 07:58:31 +00:00
- Update docs to reflect that, in order to use Autopilot, you must have one Intune license per host (from #fleetdm/confidential#6283) - Make "MDM setup" doc page cross platform - Cut content
151 lines
7.6 KiB
Markdown
151 lines
7.6 KiB
Markdown
# Windows MDM setup
|
||
|
||

|
||
|
||
To control OS settings, updates, and more on Windows hosts follow the manual enrollment instructions.
|
||
|
||
To use automatic enrollment (aka zero-touch) features on Windows, follow instructions to connect Fleet to Microsoft Azure Active Directory (aka Microsoft Entra). You can further customize zero-touch with Windows Autopilot.
|
||
|
||
## Manual enrollment
|
||
|
||
### Step 1: Generate your certificate and key
|
||
|
||
Fleet uses a certificate and key pair to authenticate and manage interactions between Fleet and Windows host.
|
||
|
||
> If you're already using Fleet's macOS MDM features, you already have a SCEP certificate and key. Skip to step 2 and reuse the SCEP certificate and key as your WSTEP certificate and key.
|
||
|
||
If you're not using macOS MDM features, run the following command to download three files and send an email to you with an attached CSR file.
|
||
|
||
```
|
||
fleetctl generate mdm-apple --email <email> --org <org>
|
||
```
|
||
|
||
Save the SCEP certificate and SCEP key. These are your certificate and key. You can ignore the downloaded APNs key and the APNs CSR that was sent to your email.
|
||
|
||
### Step 2: Configure Fleet with your certificate and key
|
||
|
||
In your Fleet server configuration, set the contents of the certificate and key in the following environment variables:
|
||
|
||
> Note: Any environment variable that ends in `_BYTES` expects the file's actual content to be passed in, not a path to the file. If you want to pass in a file path, remove the `_BYTES` suffix from the environment variable.
|
||
|
||
- [FLEET_MDM_WINDOWS_WSTEP_IDENTITY_CERT_BYTES](https://fleetdm.com/docs/deploying/configuration#mdm-windows-wstep-identity-cert-bytes)
|
||
- [FLEET_MDM_WINDOWS_WSTEP_IDENTITY_KEY_BYTES](https://fleetdm.com/docs/deploying/configuration#mdm-windows-wstep-identity-key-bytes)
|
||
|
||
Restart the Fleet server.
|
||
|
||
### Step 3: Turn on Windows MDM
|
||
|
||
1. Head to the **Settings > Integrations > Mobile device management (MDM) enrollment** page.
|
||
|
||
2. Next to **Turn on Windows MDM** select **Turn on** to navigate to the **Turn on Windows MDM** page.
|
||
|
||
3. Select **Turn on**.
|
||
|
||
### Step 4: Test manual enrollment
|
||
|
||
With Windows MDM turned on, enroll a Windows host to Fleet by installing [Fleet's agent (fleetd)](https://fleetdm.com/docs/using-fleet/enroll-hosts).
|
||
|
||
## Automatic enrollment
|
||
|
||
> Available in Fleet Premium
|
||
|
||
To automatically enroll Windows workstations when they’re first unboxed and set up by your end users, we will connect Fleet to Microsoft Azure Active Directory (Azure AD).
|
||
|
||
After you connect Fleet to Azure AD, you can customize the Windows setup experience with [Windows Autopilot](https://learn.microsoft.com/en-us/autopilot/windows-autopilot).
|
||
|
||
In order to connect Fleet to Azure AD, the IT admin (you) needs a Microsoft Enterprise Mobility + Security E3 license.
|
||
|
||
Each end user who automatically enrolls needs a Microsoft Intune license.
|
||
|
||
### Step 1: Buy Microsoft licenses
|
||
|
||
1. Sign in to [Microsoft 365 admin center](https://admin.microsoft.com/).
|
||
|
||
2. In the left-side bar select **Marketplace**.
|
||
|
||
3. On the **Marketplace** page, select **All products** and in the search bar below **All products** enter "Enterprise Mobility + Security E3".
|
||
|
||
4. Find **Enterprise Mobility + Security E3** and select **Details**
|
||
|
||
5. On the **Enterprise Mobility + Security E3** page, select **Buy** and follow instructions to purchase the license.
|
||
|
||
6. Find and buy an Intune license.
|
||
|
||
7. Sign in to [Azure portal](https://portal.azure.com).
|
||
|
||
8. At the top of the page search "Users" and select **Users**.
|
||
|
||
9. Select or create a test user and select **Licenses**.
|
||
|
||
10. Select **+ Assignments** and assign yourself the **Enterprise Mobility + Security E3**. Assign the test user the Intune licnese.
|
||
|
||
### Step 2: Connect Fleet to Azure AD
|
||
|
||
For instructions on how to connect Fleet to Azure AD, in the Fleet UI, select the avatar on the right side of the top navigation and select **Settings > Integrations > Automatic enrollment**. Then, next to **Windows automatic enrollment** select **Details**.
|
||
|
||
### Step 3: Test automatic enrollment
|
||
|
||
Testing automatic enrollment requires creating a test user in Azure AD and a freshly wiped or new Windows workstation.
|
||
|
||
1. Sign in to [Azure portal](https://portal.azure.com).
|
||
|
||
2. At the top of the page search "Users" and select **Users**.
|
||
|
||
3. Select **+ New user > Create new user**, fill out the details for your test user, and select **Review + Create > Create**.
|
||
|
||
4. Go back to **Users** and refresh the page to confirm that your test user was created.
|
||
|
||
5. Open your Windows workstation and follow the setup steps. When you reach the **How would you like to set up?** screen, select **Set up for an organization**. If your workstations has Windows 11, select **Set up for work or school**.
|
||
|
||
6. Sign in with your test user's credentials and finish the setup steps.
|
||
|
||
7. When you reach the desktop on your Windows workstation, confirm that your workstation was automatically enrolled to Fleet by selecting the carrot (^) in your taskbar and then selecting the Fleet icon. This will navigate you to this workstation's **My device** page.
|
||
|
||
8. On the **My device** page, below **My device** confirm that your workstation has a **Status** of "Online."
|
||
|
||
## Windows Autopilot
|
||
|
||
### Step 1: Create an Autopilot profile
|
||
|
||
1. Sign in to [Microsoft Intune](https://endpoint.microsoft.com/) using the Intune admin user from step 1.
|
||
|
||
2. In the left-side bar select **Devices > Enroll devices**. Under **Windows Autopilot Deployment Program** select **Deployment Profiles** to navigate to the **Windows Autopilot deployment profiles** page.
|
||
|
||
3. Select **+ Create profile > Windows PC** and follow steps to create an Autopilot profile. On the **Assignments** step, select **+ Add all devices**.
|
||
|
||
### Step 2: Register a test workstation
|
||
|
||
1. Open your test workstation and follow these [Microsoft instructions](https://learn.microsoft.com/en-us/autopilot/add-devices#desktop-hash-export) to export your workstations's device hash as a CSV. The CSV should look something like `DeviceHash_DESKTOP-2V08FUI.csv`
|
||
|
||
2. In Intune, in the left-side bar, select **Devices > Enroll devices**. Under **Windows Autopilot Deployment Program** select **Devices** to navigate to the **Windows Autopilot devices** page.
|
||
|
||
3. Select **Import** and import your CSV.
|
||
|
||
4. After Intune finishes the import, refresh the **Windows Autopilot devices** page several times to confirm that your workstation is registered with Autopilot.
|
||
|
||
### Step 3: Upload your organization's logo
|
||
|
||
1. Navigate to [Azure portal](https://portal.azure.com).
|
||
|
||
2. At the top of the page, search for "Microsoft Entra ID", select **Microsoft Entra ID**, and then select **Company branding**.
|
||
|
||
3. On the **Company Branding** page, select **Configure** or **Edit** under **Default sign-in experience**.
|
||
|
||
4. Select the **Sign-in form** tab and upload your logo to the **Square logo (light theme)** and **Square logo (dark theme)** fields.
|
||
|
||
5. In the bottom bar, select **Review + Save** and then **Save**.
|
||
|
||
### Step 4: Test Autopilot
|
||
|
||
1. Wipe your test workstation.
|
||
|
||
2. After it's been wiped, open your workstation and follow the setup steps. At screen in which you're asked to sign in, you should see the title "Welcome to [your organziation]!" next to the logo you uploaded in step 4.
|
||
|
||
|
||
<meta name="articleTitle" value="Windows MDM setup">
|
||
<meta name="authorFullName" value="Noah Talerman">
|
||
<meta name="authorGitHubUsername" value="noahtalerman">
|
||
<meta name="category" value="guides">
|
||
<meta name="publishedOn" value="2023-10-23">
|
||
<meta name="articleImageUrl" value="../website/assets/images/articles/windows-mdm-fleet-1600x900@2x.png">
|
||
<meta name="description" value="Configuring Windows MDM in Fleet.">
|