Configuration Manager Blog

If you are reinstalling SCCM on the same hardware with same old site code then refer this link It's not best practice nor is it supported to re-use site codes. It's best if you make site codes totally random. Nobody will ever see the secondary site code except for the SCCM admin. Site codes are a bigger deal on primary sites. In that case you CAN NOT reuse them because the site code is appended to all package, advertisement, etc. This would be a major problem because they could end up being duplicated from the old environment to the new one which would wreak havoc on your clients.   Where you want to replace a primary they only way to reuse that site code is to restore the primary site from the SCCM backup created on the server before it died.

I had uninstalled the SCCM 2007 secondary site & again was trying to install it on the same hardware without formatting the OS. In the setup installation, while installing the SMS provider component it gave the error  'Setup failed to install SMS provider' When I checked it in ConfigMgrSetup.log CompileMOFFile:Failed to compile MOF E:\SMS\bin\i386\NetDisc.mof, error -2147217407 Setup cannot compile MOF file E:\SMS\bin\i386\NetDisc.mof. Do you want to continue? Setup failed to install SMS Provider. For more information about this error, see Microsoft Knowledge Base at http://microsoft.com or contact Microsoft Technical Support for further assistance. This type of error can also occur when the namespace 'NetworkModel' is not removed from WMI, while uninstallation of SCCM, on the same machine and then an SCCM 2007 RTM install is attempted. In my case  I had uninstalled the secondary site from the same hardware machine & was trying to install SCCM

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 we found that earlier, some day’s back one

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,