Windows Autopilot Error Code 0x800705b4 Preparing device for mobile management
We are implementing a number of Windows Autopilot via Lenovo Thinkbook 15-ITL. These are being deployed to authorised users whether they are at home connected to their home broadband or in the office connect to the Wide Area Network. Despite lots of testing, we randomly see the the error (see attached). If we wipe the device a couple of times, it seems to remedy the issue. I've tried to look online about this about various posts talk about the TPM, which it is not. I've tried to look through the logs from the device - what a minefield of information that means something to someone. Has anyone any ideas? Thanks Martin
Autopilot profile is not assigned if a device already registered Azure AD
When import device information for Autopilot, if the devices already registered to Azure AD, the profile status in Windows Autopilot devices have not changed from ”Not Assigned”. After deleting the device from both Autopilot devices and Azure AD, and import again, it has changed to ”Assigned”. It is the same behavior at import csv file, which created by PowerShell script manually or use Autopilot profile to convert targeted devices. Note that we had not applied Autopilot enrollment to all devices, and we use a security group referring ”ZTDId”. And a security group specified Azure AD devices for convert. And, it seems when import csv file to Autopilot, devices register to Azure AD automatically. If we remove it from Azure AD, the device information will not re-register automatically. Or will it work with the security group of all Azure AD device? I want to know: 1. Import Autopilot information of devices that already registered to Azure AD does it work? 2. With the security group reference ZTDId, does it work? 3. The best practice to register Autopilot information, that device already registered to Azure AD and Intune Thank you for reading. If you know anything about it, please teach me.Windows AutoPilot - Hardware Hash
Hi all, I'm running a PowerShell script to generate hardware hashes in order to enroll devices into Intune Autopilot. I followed the instructions from the official MS site, https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/add-devices. The below command runs successfully but the only problem is that when trying to upload to Intune I get an error that the format is incorrect. I then have to manually update the CSV to separate each comma and upload. We have hundreds of devices and, needless to say, it's incredibly tedious to do this for every single one. I can't find a forum that describes a way to edit the script to do this for me. Does anyone have an idea of how to do this, if even possible? md c:\\HWID Set-Location c:\\HWID Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted Install-Script -Name Get-WindowsAutoPilotInfo Get-WindowsAutoPilotInfo.ps1 -OutputFile AutoPilotHWID.csv Any help would be appreciated. Kind regards,Background image via Intune
Hi All, We're currently busy with the Look and Feel of our Autopilot Workplace. One demand of the customer is to have a changeable background image on the workplace. I've found Michael Nihaus' tool but it's not applicable in our environment due Enterprise State Roaming. (source: https://github.com/mtniehaus/AutopilotBranding ) I've searched for CSP strings but did not find what is needed... (source: https://docs.microsoft.com/en-us/windows/client-management/mdm/personalization-csp ) (source: https://www.petervanderwoude.nl/post/easily-configure-desktop-and-lock-screen-image-via-windows-10-mdm/ ) How do you handle this?Company Portal Failing to Install - 0x80073CF0
Hello, We are currently having an issue with one of our AutoPilot deployed laptops. Intune Company Portal is being pushed out to the device via Microsoft Business Store, following this guide I believe: https://docs.microsoft.com/en-gb/archive/blogs/home_is_where_i_lay_my_head/silently-push-the-microsoft-intune-company-portal-to-azure-ad-joined-windows-10-devices Unfortunately, the deployment seems to be failing (hit or miss, fails maybe 1/3 times?) with the following error code: 0x80073CF0 The package couldn't be opened We've deployed Company Portal the same way across multiple other clients and never run in to this issue before. The image is fresh Windows 10 1909 created from Media Creation Tool the other day. Any suggestions why this may be?
systemreset.exe command line options
I'm doing a lot of testing with Windows autopilot. Is there a method to reset the machine solely from the command line using the systemreset.exe tool? I cannot find any documentation for the switches it supports. My goal it to do a full reset of the device but via a script rather than clicking through the UI options. I ran the sysinternals tools 'strings' against it and I see some options like -factoryreset which do work but I'd like to get a full listing/reference.Windows Autopilot to remove all pre-installed apps
Dear community fam, When you create provisioning package from Windows Deployment Toolkit, there is a handy option to "remove pre-installed apps". This is extremely helpful when you don't know what are you getting from the OEM and do not want to reimage the PC. Is there a similar feature in Intune we could achieve the same outcome, whether during the Autopilot or post? Thanks.Cannot Reseal Windows 11 device while pre-provisioning
Before I reinvent the wheel, I thought I’ll post the issue here. I have a AP profile configured as below. Deployment mode User-Driven Join to Azure AD as Azure AD joined Language (Region) Dutch (Netherlands) Automatically configure keyboard Yes ( In know.. please read on) Microsoft Software License Terms Hide Privacy settings Hide Hide change account options Hide User account type Standard Allow pre-provisioned deployment Yes Apply device name template Yes Enter a name XXXX-%SERIAL% I know I’ve set the auto keyboard to yes, but here me out. As far as I understood the previously known issue is fixed in Windows 11. Windows Autopilot for pre-provisioned deployment | Microsoft Docs In Windows 10, version 2004 and later, if the Autopilot deployment profile Language/Region setting is not set to User Select, then OOBE will progress past the language/region/keyboard selection screens. This causes the pre-provisioning technician to arrive at the Azure AD login page, which is too late to enter pre-provisioning. This issue is fixed in Windows 11. For the pre-provisioning part: On Windows 10 21H2 (10.0.19044.1645) I can pre-provision the device successfully. The technician flow completes and I have a green screen giving me the option to reseal. After reboot, the normal user flow follows, and the device is ready to go before you know. AAD joined and MDM enrolled with user affinity. However, on Windows 11 (10.0.22000.675) the technician flow starts OK. I’m presented with the AP profile that is selected, and I can continue pre-provisioning. But it never shows me the green screen and I’m not able to reseal the device. It also does not show any errors what so ever during pre-provisioning. The device simply reboots and ends up at the login screen. The user flow does not seem to start and from the login screen, I’m also not able to sign-in with any account. At this stage, I checked the device in the AP portal. The interesting thing is, that the device seems to be AAD joined and MDM enrolled. And as expected, there is no primary user yet in Intune. So I looked up the device in Azure AD and confirmed it is AAD joined. Although I don’t believe the info presented. I also looked up the device in MEM/Intune and collected the diagnostics logs from the device. Still in the process of diving into the logfiles but here are some of my findings: intunemanagementextension.log shows some interesting things: GetAADJoinInfo - Failed to get Azure AD Join information using NetGetAadJoinInformation 
