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
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.
The Tunnel Client for Windows 10 is more and more growing there are some Custom Configurations that are not in the GUI for the Tunnel Profile as of the 21.05 UEM Release. So let us have a look on the most important Keys that are available in the Tunnel 2.1 Client, but not in the
One of the most underrated feature when it comes to SSO is to be able to automatically select the right certificate based on the domain, while there is mechanism in the SSL protocol to indicate which CA is requested, a device or a user may have multiple certificates depending on the scenario. This may lead
When using the Windows Firewall Profile, there is different options in the rules for configuring the protocol. All, TCP, UDP and CUSTOM. While the first 3 are quite obvious the last one when select offer to put a integer What to put in custom protocol The integer while not listed by Microsoft, are based on
The scenario is not quite “modern” but from time to time we have devices where no user is logged on and you still want to manage it. The list is based on HUB 21.02 and also tested on 21.05 – later versions might change the behaviour. First of all: only commands that are assigned to
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
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
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
Recently we got a question from a customer how to manage Windows local account passwords via UEM. Microsoft does not provide any native CSP for this, so we need a PowerShell script for changing the password. This will also provide some more flexibility when you want to change a different user as the local Administrator
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.