Author Archives: Frank Maxwitat

Add x86 images after ADK update to 22621 (Windows 11 22H2)

With the ADK for Windows 22H2, Microsoft has dropped support for x86 images. When you try to add or update an x86 image in ConfigMgr you’ll get an error. The workaround is simple: Locate the PE image in the ADK installation folder (usually C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment), copy the amd64… Read More: Add x86 images after ADK update to 22621 (Windows 11… »

Installing and configuring HP Officejet Pro and Officejet Printers with Intune (or MECM)

There are some really good print driver installation guides for Intune like the one from Ben Whitmore (msendpointmgr) and Rudy Ooms (call4cloud). Their approach is to extract the driver from the installation package of the vendor, install it by using pnputil and then to run the Add-Printer PowerShell cmdlet with printer name (e.g. “Floor 1… Read More: Installing and configuring HP Officejet Pro and Officejet Printers with… »

License assignment failed – License cannot be assigned to a user without a usage location specified

If you are getting the error above when assigning licenses, it is because the entry UsageLocation isn’t set for the user. The quick way to fix the issue is obviously to set the entry manually. If you want to apply the change to larger number of users, the code snippet below may help: Connect-AzureAD Write-Host… Read More: License assignment failed – License cannot be assigned to a… »

Custom report to display Windows 11 readiness information in MECM

If you plan to migrate to Windows 11, you will probably want to determine which machines fulfill the requirements for an upgrade. If you are using MECM, you can find this information for single machines in the Resource Explorer. The Resource Explorer item is based on the view v_GS_UPGRADE_EXPERIENCE_INDICATORS which is fed by the hardware… Read More: Custom report to display Windows 11 readiness information in MECM »

Powershell script to check if Azure AD Connect is affected by the vulnerability described in CVE-2021-36949

The script below will check if your Azure AD Connect is running a version affected by the vulnerability described in CVE-2021-36949. Affected versions are 1.6.4.0 and 2.0.3.0. #Disclaimer: This script is provided as-is with no warranties of any kindWrite-Host “Checking if your Azure AD Connect version is affected by the vulnerability described in CVE-2021-36949″Try{$params =… Read More: Powershell script to check if Azure AD Connect is affected… »