Explore practical guides, troubleshooting tips, and deployment strategies for Microsoft Endpoint Configuration Manager (SCCM). From application packaging and OS deployment to client health and reporting, this section helps IT admins streamline enterprise device management and keep their environments running smoothly.
The SMS_AppDeploymentAssetDetails Windows Management Instrumentation (WMI) class is an SMS Provider server class, in Configuration Manager, that represents asset-level details about the deployment. The below properties of SMS_AppDeploymentAssetDetails class can be used […]
SCCM Dynamic Collection using Application Deployment Status Read More »
The below SCCM SQL query will summarize the list of Windows 10 / 11 versions along with total device count. This will help in understanding demographic of each windows build
SCCM SQL Query for Windows 10 / 11 Version Summary Read More »
It gives me immense pleasure to announce that Techuisitive blog has been featured in 25 Best SCCM Blogs and Websites (System Center Configuration Manager) ranked by FeedSpot. FeedSpot ranked best
FeedSpot Top 25 SCCM Blogs to Follow in 2023 Read More »
What is Error 0x87d00213? ConfigMgr error 0x87d00213 indicates that an application deployment has timed out. This usually happens when the installation takes longer than the maximum run time defined in
Fix Application Deployment error 0x87d00213 in ConfigMgr Read More »
Win32_OptionalFeature WMI class represents the status of the optional features that are present on the operating system. In ConfigMgr, this class is represented by Server side WMI class SMS_G_System_OPTIONAL_FEATURE. This
SCCM Collection Based on Operating System Optional Features | ConfigMgr Read More »
When deploying Windows 10 using SCCM OSD on HP EliteBook 840 G8 devices, you may encounter a puzzling error: domain join failed with error code 0x54b. Although the operating system
SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8 Read More »
SCCM collect software information from client using different methods such as Software inventory , software file scan, and hardware inventory. These information can be used to create dynamic collection for devices.
Create SCCM Device Collection Based on Installed Software Products & Inventoried Files Read More »
SCCM Computer hardware classes can be used to create dynamic query based device collection. There are different classes such as Computer System , PC_BIOS , System Enclosure , TPM etc which can be used for queries. A collection or query created in Configuration Manager uses WMI Query Language (WQL) to request objects from the SMS Provider WMI Schema, which in turn retrieves the data from site database.
How to Create SCCM Device Collection Based on Computer Hardware Details | ConfigMgr Read More »
To identify a device with Windows Autopilot, the device’s unique hardware identify (hardware hash) must be captured and uploaded to the service. This is usually first step when you want to provision a machine using Windows Autopilot. The hardware hash can be uploaded by manufacturer / raeseller for new devices. However, hardware hash need to be collected manually for the devices which are already in corporate environment and not already enrolled into Microsoft Intune.
Get Hardware Hash for Windows Autopilot Read More »
When deploying the SCCM client, you may encounter the error ccmsetup failed with error code 0x87d00227 in the ccmsetup.log file. This issue typically occurs when the client installation is blocked due to a metered network connection. In this guide, we’ll explain the cause of the error, walk through the solution using the /AllowMetered parameter, and show how to clean up previous installations with ccmclean to ensure a smooth client deployment.
