Microsoft Intune, coupled with Windows Autopilot, offers a modern, cloud-native approach to deploying and managing Windows 11 Enterprise images. This strategy moves away from traditional, time-intensive imaging solutions, addressing common hybrid workplace pain points such as inconsistent device configurations, manual software installations, and prolonged user onboarding times. Without a standardized, automated deployment pipeline, IT departments often face increased service desk tickets related to application compatibility, driver issues, and security baseline drift.
This guide outlines a robust methodology for deploying Windows 11 Enterprise images through Intune, ensuring a consistent, secure, and efficient endpoint experience across your organization.
Prerequisites & Environment Checklist
Before initiating Windows 11 Enterprise deployments via Intune, ensure your environment meets the following minimum requirements:
- Microsoft 365 Licensing:
- Microsoft 365 Business Premium: For organizations under 300 users. Includes Intune, Entra ID P1, and Windows 11 Pro (upgradeable to Enterprise via subscription activation if eligible).
- Microsoft 365 E3/E5 or Enterprise Mobility + Security E3/E5: For larger organizations. Includes Intune, Entra ID P1/P2, and Windows 11 Enterprise.
- Administrative Roles:
- Intune Administrator and/or Global Administrator roles in Entra ID.
- Sufficient permissions to manage device registrations and profiles.
- PowerShell Modules:
Microsoft.Graph.Intunemodule for advanced scripting and automation.WindowsAutoPilotIntunemodule for Autopilot device management.
- Network Connectivity:
- Devices must have internet access to reach Intune and Microsoft services during Autopilot enrollment.
- Ensure firewall rules permit access to necessary Microsoft endpoints.
- Device Types:
- New devices (Out-of-Box Experience / OOBE) for optimal Autopilot experience.
- Existing devices can be reset and re-enrolled, but a clean slate is recommended.
Step-by-Step Implementation: Windows 11 Enterprise Deployment
The deployment process leverages Intune for policy enforcement and Windows Autopilot for device provisioning.
Step 1: Configure Autopilot Deployment Profile
An Autopilot deployment profile dictates the user experience during OOBE, including skipping privacy settings, setting up local accounts, and applying branding.
- Navigate to Intune Admin Center:
- Go to Microsoft Intune admin center.
- Devices > Windows > Windows enrollment.
- Under Windows Autopilot Deployment Program, select Deployment profiles.
- Create a New Profile:
- Click Create profile > Windows PC.
- Name:
Windows 11 Enterprise Standard Deployment - Description:
Standard Autopilot profile for Windows 11 Enterprise devices. - Convert all targeted devices to Autopilot:
Yes(This automatically registers existing devices assigned to this profile with Autopilot). - Deployment mode:
User-driven(Most common for corporate devices). - Join to Entra ID as:
Entra ID joined. - Skip Entra ID setup:
No. - Configure other OOBE settings as per your organizational policy (e.g., skip privacy settings, disable local admin account creation).
- Assign the Profile:
- Assign the profile to an Entra ID security group containing your target devices or users.
Step 2: Create a Device Configuration Profile for Windows 11 Baseline
This profile enforces core security and operational settings.
- Navigate to Intune Admin Center:
- Devices > Windows > Configuration profiles.
- Click Create profile.
- Platform:
Windows 10 and later. - Profile type:
Settings catalog(Recommended for granular control).
- Name the Profile:
Windows 11 Enterprise Baseline Policy - Add Settings:
- Search for and add essential settings such as:
BitLocker(e.g.,Require Device Encryption).Windows Update(e.g.,Manage Preview Builds,Active Hours).Security Center(e.g.,Tamper Protection).Device Restrictions(e.g.,Allow Camera,Allow Cortana).
- Search for and add essential settings such as:
- Assign the Profile:
- Assign to the same Entra ID security group used for your Autopilot deployment profile.
Step 3: Package and Deploy Essential Applications
Deploy core business applications as Win32 apps via Intune.
- Prepare Win32 App:
- Use the
Microsoft Win32 Content Prep Toolto package your.exeor.msiinstallers into a.intunewinformat. - Example PowerShell for packaging:
- Use the
# Download the Win32 Content Prep Tool from GitHub
# https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool/releases
# Example: Package Notepad++
$SourceFolder = "C:\Apps\Notepad++" # Folder containing installer and any necessary scripts
$InstallerFile = "npp.8.5.8.Installer.x64.exe" # Your installer file
$SetupFile = "$SourceFolder$InstallerFile"
$OutputFolder = "C:\IntunePackages" # Output directory for .intunewin file
# Ensure output folder exists
if (-not (Test-Path $OutputFolder)) {
New-Item -Path $OutputFolder -ItemType Directory
}
# Path to the IntuneWinAppUtil.exe
$IntuneWinAppUtilPath = "C:\Tools\IntuneWinAppUtil.exe" # Adjust this path
# Execute the packaging tool
& $IntuneWinAppUtilPath -c $SourceFolder -s $InstallerFile -o $OutputFolder -q
- Upload to Intune:
- Apps > Windows > Add > Windows app (Win32).
- Upload the
.intunewinfile. - Configure Program (install/uninstall commands), Requirements (OS architecture, minimum OS version), and Detection rules (e.g., file existence, MSI product code).
- Assign the Application:
- Assign as Required to the same Entra ID security group. This ensures automatic installation during Autopilot enrollment.
Step 4: Verify Autopilot Device Registration
New devices purchased from a vendor participating in the Windows Autopilot program can be pre-registered. For existing devices, manual registration or conversion is required.
PowerShell for Manual Autopilot Device Registration:
# Install the necessary modules if you haven't already
Install-Module -Name Microsoft.Graph.Intune -Force
Install-Module -Name WindowsAutoPilotIntune -Force
# Connect to Microsoft Graph
Connect-MSGraph
# Get hardware hash for a device (run this on the target device)
# Requires administrative privileges
$device = Get-WmiObject -Class Win32_ComputerSystemProduct -Namespace root\cimv2
$serial = $device.IdentifyingNumber
$hardwareHash = (Get-WindowsAutopilotInfo -Online -GroupTag "StandardWin11" -AssignProfile).HardwareHash
# This command will automatically upload the device to Intune Autopilot
# and assign it to a profile if specified in the Get-WindowsAutopilotInfo command.
# If not, you can manually assign it in the Intune portal.
Write-Host "Hardware Hash for device $serial:"
Write-Host $hardwareHash
# To check if device is registered in Intune Autopilot:
Get-AutoPilotDevice | Where-Object {$_.HardwareSerialNumber -eq $serial}
Verification & Functional Testing
After a device completes Autopilot enrollment, verify the following:
- Intune Compliance:
- In Intune, navigate to Devices > All devices. Select the device and check its Device compliance status. It should be “Compliant.”
- Configuration Profile Status:
- On the device’s overview page in Intune, check Device configuration. All assigned profiles should show “Succeeded.”
- Application Installation:
- Verify that all required Win32 applications have been successfully installed on the device.
- Check Apps > Monitor > App install status in Intune.
- Windows 11 Enterprise Edition:
- On the device, open
Settings>System>About. Confirm that the Windows edition is “Windows 11 Enterprise.” - Check
System Information(msinfo32.exe) for confirmation.
- On the device, open
Common Troubleshooting Pitfalls & Rollback
Troubleshooting
- Autopilot Enrollment Failure:
- Issue: Device stuck at “Just a moment…” or “Something went wrong.”
- Fix: Check network connectivity. Ensure the device’s hardware hash is correctly registered in Intune Autopilot. Review the Autopilot deployment profile for misconfigurations.
- Logs: Collect Autopilot diagnostics (
Shift + F10during OOBE, thenMDMDiagnosticsTool.exe -Area Autopilot -cab C:\temp\Autopilot.cab).
- Application Installation Errors:
- Issue: Apps not installing or failing silently.
- Fix: Verify Win32 app detection rules and install/uninstall commands. Check the
IntuneManagementExtension.logon the client device (located atC:\ProgramData\Microsoft\IntuneManagementExtension\Logs).
- Policy Not Applying:
- Issue: Configuration settings not enforced.
- Fix: Check device assignment to the correct Entra ID security group. Force a policy sync on the device (
Settings>Accounts>Access work or school> select account >Info>Sync). - Logs: Review Event Viewer logs (
Applications and Services Logs>Microsoft>Windows>DeviceManagement-Enterprise-Diagnostics-Provider>Admin).
- BitLocker Not Encrypting:
- Issue: Drives remain unencrypted despite policy.
- Fix: Ensure the device has a TPM 2.0 chip and it’s enabled in BIOS. Check for conflicting Group Policies if the device is hybrid joined.
Rollback Strategy
For a device experiencing persistent issues after an Intune deployment, the most effective rollback is often a complete device wipe and re-enrollment.
- Wipe Device in Intune:
- In Intune, navigate to Devices > All devices.
- Select the problematic device.
- Click Wipe (This removes all user data and resets the OS).
- Alternatively, use Fresh Start (retains some user data but re-installs Windows).
- Remove Autopilot Registration (Optional):
- If the device was registered via Autopilot, remove its entry from Devices > Windows > Windows enrollment > Devices under the Autopilot program. This ensures a clean slate for re-registration.
- Re-register and Re-deploy:
- Follow the Autopilot registration steps again, ensuring all prerequisites and configurations are correctly applied.
Need Urgent IT Assistance or Perimeter Defense?
Is your organization vulnerable to active edge exploits, credential harvesting, or compliance audit penalties? Helpdesk.ca provides 24/7/365 managed IT support, emergency incident triage, and co-managed IT escalation for Canadian enterprises.
- Schedule an IT Discovery Call: Book a 15-Minute Consultation With Our Engineering Team
- Emergency Incident Escalation: Connect directly with our frontline operations desk via Helpdesk.ca Support
Modernize Your IT Support with Guaranteed 15-Minute SLAs
From zero-touch Intune provisioning to automated employee onboarding and proactive 24/7 endpoint management, Helpdesk.ca keeps Canadian teams productive and secure.
Sources & References
- Microsoft Learn: Windows Autopilot overview
- Microsoft Learn: Win32 app management in Microsoft Intune
- PowerShell Gallery: WindowsAutoPilotIntune module
- PowerShell Gallery: Microsoft.Graph.Intune module
