KB – Enterprise Wipe doesn’t remove all apps

Issue When executing an Enterprise Wipe there are one or more apps left on the device. Root Cause There two reasons why an app was not uninstalled during an Enterprise Wipe: App has an auto update functionality and has changed the version or installer code changed with the automated update instllation An app gets not

KB – AAD join fails with error 8018000a

Today I received a question what happens if the device is already Workspace ONE joined and then the device gets joined to Azure AD. In this use case the customer had AAD Premium licenses and Intune was assigned as MDM provider to all users. So I started to install a workgroup client and installed the

KB – Device status: discovered

We all know the different device status like “Enrolled”, “Unenrolled”, “Enrollment in Progress”….But ever heard of “Discovered”? After some investigations and help from Sergiu Constantin, we were able to reproduce the status and found the root cause. Basically the discovered status means, that the device was connected to UEM but now the device is blocked.

Improve Windows Update for Business management

We all know that the transformation from the good old SCCM/WSUS is hard and from time to time complicated. Of course there are a ton of guides how to manage Windows Update for Business (WUfB) – like this amazing article HERE. But not all customers are ready for the modern way of update management. In

KB – Reboot loop after enterprise reset

Starting with Windows 10 2004 and higher, Microsoft changed the way they creating PPKG’s. This change is causing a reboot loop when the device was setup with a PPKG – like with Factory Provisioning (or now called Drop Ship Provisioning Offline) AND doing enterprise reset. After the reset is done, the PPKG causing a reboot
BCF Shop Theme By aThemeArt.
BACK TO TOP