KB – Windows devices getting unenrolled

If you are seeing Windows devices getting unenrolled, it could have several root causes. A customer reported, that they’re seeing the following device events in the console The devices requested the “Break MDM” command to unenroll the devices. On the devices, we saw the following entry in the AWProcessedCommands log file: Also in the eventlog

KB – Windows Proxy configuration

Workspace ONE and Windows management are always complicated when using a proxy. To avoid further misunderstandings I tested all five different scenarios and here are the results: INET WINHTTP BITS INET+WINHTTP INET+BITS WINHTTP+BITS HUB start yes yes Yes yes yes Yes HUB works yes no no yes restart required Manual Enrollment yes No – *Works

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
  • By -

Workspace ONE – ISO, compliance, security

  • Posted on
  • Posted in KB
Did you asked yourself or got the questions from customers about ISO certifications of the VMware Workspace ONE solutions? Here are some good sources where you can take a look at for the certifications, ISO, compliance and security. Privacy disclosure In this section you will find a lot of information about data privacy, collection of

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.

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