Upgrade domain controllers running core server installation Check the Microsoft documentation for prereqs [1]. Mind that you’ll be prompted for a license key when running the upgrade and that different versions require different KMS keys [2]. Reboot the server Run dcdiag to check that the DC is working properly. Optionally, run systeminfo to check the… Read More »
There is no easy way to detect core servers in SCCM by using the default inventory information. Here’s how to extend it to distinguish core and GUI servers. Microsoft recommendation to check remotely if a server is running the core setup is to use the ServerLevels registry hive in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Server [1]. On a GUI… Read More »
The information about processors, cores and logical processors is a bit confusing. However, since it may be required for Windows and SQL server licensing [1], below some queries and links. Get details about SQL Server installations: select distinct fcm.Name as [Machine Name], arp.DisplayName0, sys.Active0 , WS.LastHWScan as [Last Inventory], sys.CPUType0 as [CPU Type], p.Name0 as… Read More »
If you are patching your Windows machines with ConfigMgr and WSUS, you rely on the selection that you make in the product catalog: The Windows Update Agent will only search updates for products that you selected. Unfortunately, the list has a long history and there’s no documentation available. If you select products that are not… Read More »
I observed a strange behavior of the reporting services setup process. Below a scripted workaround for it. Symptoms:The setup of the reporting point role fails. Under Monitoring->System Status, you see that the installation reruns every hour with the same result. Components error message: Site Component Manager failed to install this component, because the Microsoft Installer… Read More »
A common concern when introducing Autopilot are the limitations regarding the workstation name: Out-of-the-box, you only have these options: Use a prefix and a random number in the deployment profile Use a prefix and the serial number of the device Enter a fixed string in AutoPilot registered devices Rename the device after the setup… Read More »
Changing the account that is running a service is a little bit tricky with PowerShell. The script below will replace the current account (let’s assume it’s local system) with a local user account that the script creates and adds to the local admin group. Local admin rights are generally not required for the purpose of… Read More »
In rare cases, you may see that the inventory isn’t working after an upgrade of the Configuration Manager. In my case, it took two weeks until the issue was noticed and it needed some investigation to find out there was no hardware inventory entry was newer than the date of the upgrade to 2303. On… Read More »
Go to https://learn.microsoft.com/en-us/surface/manage-surface-driver-and-firmware-updates and find the appropriate download link for your model. Create the folder that you want to place the drivers in, for example D:\Sources\Drivers\Win10\Microsoft\SurfaceLaptop5 Run the msiexec command to place the drivers in that folder: msiexec /a SurfaceLaptop5_Win10_19044_22.102.17126.0.msi targetdir=D:\Sources\OSD\Win10\Driver\Microsoft\SurfaceLaptop5 Now go to the ConfigMg console, navigate to Software Library -> OSD and open… Read More »
With the critical vulnerabilities in Word (CVE-2023-21716) and Outlook (CVE-2023-23397) the update status of Office 365 has come into focus. The easiest way to check the version status is to go to \Software Library\Overview\Office 365 Client Management in the console. The dashboard behaves a bit beastly but if you succeed to get it loading it… Read More »