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

Remove Windows 11 built-in apps via CSP

Microsoft change the behavior of the EnterpriseModernAppManagement CSP in Windows 11. In Windows 10 you were able to use the same CSP for devices and users. So, for example you could use And for uninstalling the get help app once for the user (1st example) or for all users (2nd example). As you can see,

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.

Omnissa Android Launcher: Guest Session Mode

With one of the latest release Omnissa release a “Guest Mode” in Launcher which works to login in a Guest session even without Internet. This is a real good solution for devices which have a CheckIn-CheckOut Use-Case and have applications that should be accessed without login. Note: When writing this post some of the features
BCF Shop Theme By aThemeArt.
BACK TO TOP