KB – Sync Button Azure Compliance in WS1

When using the compliance for Azure conditional access, there is two sync buttons available. For more information about the compliance integration have a read on this article from Sascha Warno : Workspace One UEM 3rd party compliance integration – Microsoft Graph API “Sync Azure Services” Button This button is used when the administrator is making

iOS and Android/rugged Check in Check out (CICO) using third party IdP (PingFederate)

iOS and Android/rugged Check in Check out (CICO) using third party IdP (PingFederate) check-in check-out enables simple and secure device sharing among multiple users within an organisation. CICO enables a user to check-in on a shared device to access their appropriate apps and data. Access is maintained until check-out, at which time the user and

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

Create a custom PPKG for the Factory Provisioning Tool

Sometimes you need to add/modify something in a PPKG and you don’t want to create a new PPKG in the Workspace ONE console. Normally this is not supported since the Factory Provisioning Tool checking the PPKG for a “watermark”. This guid will show you how to create a custom PPKG with the Windows ICD and

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

KB – Target Release Version for 20H2 and 21H1

Since the target release version CSP is still not working since 20H2 and Microsoft seems not able to fix this, we need to change the target release version via registry. The reason why the CSP does not work is, that Microsoft introduced letters in the Windows version – like 20H2 or 21H2. The CSP only
Theme BCF By aThemeArt - Proudly powered by WordPress .
BACK TO TOP