How to Setup Windows Autopilot V1 in Microsoft Intune
Autopilot automatically configures your laptops and computers with all the necessary software and settings. It even integrates with manufacturers like Dell, allowing you to order a brand-new device and have it shipped directly to the end user. When they receive the laptop, all they need to do is connect it to the internet, enter their Microsoft 365 username and password, and all the applications and settings will be applied. It’s seamless and efficient. You might think this sounds expensive, but it’s not. All you need is an Entra ID Plan 1 license. Or, if you follow my recommendation, a Microsoft 365 Business Premium license, which includes Autopilot. Support Platform Platform Supported Editions Windows 11 Pro Pro Education Pro for Workstations Enterprise Education Windows 10 Pro Pro Education Pro for Workstations Enterprise Education Now, let’s dive into the demo. First, we’ll prepare by creating Entra ID groups to organize the devices and look at company branding to personalise the experience. Sign in to the Entra Admin Center. Navigate to Devices > All devices > Device settings. Set Users may join devices to Microsoft Entra to All. For setting up device conditions, use the following query to filter Windows devices based on OS type and version: Copy code(device.deviceOSType -eq “Windows”) and ((device.deviceOSVersion -startsWith “10.0.1”) or (device.deviceOSVersion -startsWith “10.0.22”)) This filter applies to devices running Windows with OS versions starting with 10.0.1 or 10.0.22. Company branding settings allow you to customize the Out-of-Box Experience (OOBE) for users. You can display your company logo and tailor the colors to align with your organization’s theme, ensuring that users enrolling their devices feel connected to the correct organization. Sign in to the Entra Admin Center: Entra Admin Center. Navigate to User experiences > Company branding: Company Branding Settings. Edit the Default sign-in configuration and review all the tabs to adjust the user experience according to your needs. 4. Complete the Sign-in Form and click Review + save to finalize your settings. Create an Autopilot Deployment Profile The next step is to create an Autopilot deployment profile, which customizes the Out-of-Box Experience (OOBE) and deployment mode for end users. This profile controls how devices are configured when users first power them on. You can create up to 350 deployment profiles in a single Intune tenant. To create an Autopilot deployment profile, follow these steps: Sign in to the Intune Admin Center. Navigate to Devices > Windows > Windows enrollment > Deployment Profiles. Click on Create Profile at the top. Select Windows PC as the profile type. Enter a profile name (e.g., “Sales Department Profile”) and click Next. Configure the Out-of-Box Experience (OOBE) settings: Deployment mode: Choose between User-driven or Self-deploying. For most cases, selecting User-driven means the user will enter their credentials during setup. Join to Microsoft Entra ID: Choose Microsoft Entra joined to automatically join devices to your Entra ID. If you’re in a hybrid environment, you can select Hybrid Azure AD Join instead. Microsoft Software Licensing Terms and Privacy Settings: Choose whether to Hide these during setup for a smoother user experience. User account type: Set to Standard to prevent users from having administrative rights on their devices. Allow pre-provisioned deployment: You can choose No to skip this step, or Yes if you want to pre-configure devices. Region and language settings: Choose the appropriate region (e.g., English United Status) to ensure the device’s region matches your needs. Device template name: Set a naming convention for your devices (e.g., Autopilot-XXX, where “XXX” is a random string of numbers). Assign groups: Add the groups you created earlier to the profile, and select any groups you want to exclude if necessary. Click Next and then Create to finalize the deployment profile. Once created, you can go back to Devices > Windows and refresh the device list to check the profile assignment status. It may take a few minutes for the profile to be assigned. Add Hardware Hash to Intune It’s time to load the hardware hashes into Intune. A hardware hash is a unique identifier for each laptop or computer. If you’re purchasing devices directly from manufacturers like Dell, you can set up a relationship with them to provide the hardware hashes of the devices you’re buying, which can then be loaded into Intune. There are a couple of ways to add hardware hashes into Intune. The first method is through a PowerShell script that generates a CSV file containing the hardware hash, stored on your C drive. You can then navigate to the folder and view the hardware hash of the computer you’re working on. For the Demo i just using powershell ISE but you can use powershell administrator only PowerShellCopy [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 New-Item -Type Directory -Path “C:HWID” Set-Location -Path “C:HWID” $env:Path += “;C:Program FilesWindowsPowerShellScripts” Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned Install-Script -Name Get-WindowsAutopilotInfo Get-WindowsAutopilotInfo -OutputFile AutopilotHWID.csv Once you have the hardware hash, you need to upload it to Intune via the Microsoft 365 Admin Center. In Endpoint Manager, go to Devices, then Device Onboarding and Enrollment, and navigate to Windows Autopilot. You can import the hardware hash CSV file here, and after a few minutes, your device will appear in Intune. Its another way to upload the Hardware Hash Directly upload the hardware hash to an MDM service Directly uploading the hardware hash to an MDM service such as Microsoft Intune can be done on any device, but it’s especially useful for a device currently undergoing Windows Setup and OOBE. To directly upload the hardware hash for a device: On a device that is: Currently undergoing Windows Setup and OOBE: At the sign-in prompt after OOBE starts, open a command prompt window with the keystroke Shift+F10. In the command prompt window that opens, start PowerShell by running the following command: Windows Command PromptCopy powershell.exe Already undergone Windows Setup and OOBE: Sign into the device. Open an elevated Windows PowerShell prompt. At the PS PowerShell command prompt, run the following PowerShell commands: PowerShellCopy [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned Install-Script -Name Get-WindowsAutopilotInfo -Force Get-WindowsAutopilotInfo -Online If prompted to do so, agree to
How to Setup Windows Autopilot V1 in Microsoft Intune Read More »