Configuration Manager Blog

Other than the obvious, if on your site server or client the Hardware Inventory action is missing, most of the time the issue is may be a misconfigured hardware inventory MOF file, configuration.mof, on your primary site. In this case, the Hardware Inventory Action was missing on some of the Primary site Server as shown in the following figure. Also looked in %systemroot%\system32\wbem\logs --> mofcomp.log file, it was showing  following error Error Number: 0x80041026, Facility: WMI In this case the MOF file it was compiling was correct, but somehow from the log file it was showing that there is some issue with WMI. As per the above error, while compiling the mof file, the a ttempt was made to delete or modify a class that has instances in WMI . But anyway it was not happening. Further we compared the sms_def.mof file objects with the WMI & found that one additional customized entry in WMI. On further investigation...

Issue: SMS Site Component Manager failed to install component SMS_MP_CONTROL_MANAGER on server SMS01. If   I check the SCCM status (Go to System Status in the left pane, expand it, and choose Site Status , then your SCCM site code , then Component Status ), it shows me that there were problems with my Management Point which were preventing it from starting. If I right-click on the Critical error , and choose Show Messages , All . It shows me following error The WebDAV server extension is either not installed or not configured properly. Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false.If I checked in SCCM status (click System Status in the left pane,...

The article describes the SMS Advanced Client Push Installation process Pre-installation stage  1. During the pre-installation stage, When the Client Push Installation wizard starts, Client Configuration Request (CCR) is created for each targeted computer. Each CCR is placed into the Inboxes\CCR.box folder on the site server. Client Configuration Manager (CCM) selects a CCR from the Inboxes\CCR.box folder on the site server (CCM tasks are logged in ccm.log on the site server) The CCR file contains the client computer name and additional information.  2. The SMS Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.  3. The Client Configuration Manager attempts to connect to the computer using the Client Push Installation Account (if the connection was not successful it attempts to connect to the computer by using the site server computer account). The Client Configuration Manager connects to the clie...