Hunt SCCM Issues Down

This is the post where we can find some useful details about removal or uninstallation or deletion of Site server (s) rather Decommission of sites and Hierarchies. Also, we’re going to discuss about the difference between the options  Uninstall  and  Delete  (Secondary site/s). We will be able to   REUSE the site code of secondary server/s   if is  no longer in use in your Configuration Manager hierarchy or in the Active Directory forest . However, Site codes cannot be used more than one time in a   ConfigMgr   hierarchy for a CAS or primary sites. If you reuse a site code, you run the risk of having   object ID conflicts   in your ConfigMgr hierarchy. When we want to remove entire SCCM/ConfigMgr hierarchy with lot of site servers (primary and secondary etc..), we’ve to follow   bottom up   approach. That means, Remove secondary sites attached to primary sites, primary sites from the central administration site (CAS), and then the central administration site (CAS) itself. Un

ConfigMgr will definitely be able to let SCCM admins know what are installed in the environment regardless if it is a server or workstation. SCCM by default comes with a set of reports that SCCM admins can utilize to gather information. The one that I am going to mention today is , "Computers that has a metered program but have not run the program since a specific date". What is so special about this report you may think, I had the same thinking as you but it is pretty interesting to know how is this data derived. The data set for this is based on Software Inventory and this means gathering file types that are on machines. The last used time is gathered asp art of software metering. This report will provide the information based on the files inventoried and their respective last used date. Nothing unique right? Here comes the interesting part, picture the scenario as below. All of us will know that in order for Microsoft Office to be used, it has to be inst

Wanted to share.. It will be helpful to achieve maximum rate of patching compliance. As we often face issues to troubleshoot the systems with  "Enforcement Status Unknown" state. Issue Some of the servers / workstations are appearing as “ Enforcement Status Unknown ” in Patching Deployment Report. Logs mentioned below. Unable to find or read WUA Managed server policy. Unable to read existing WUA Group Policy object. Error = 0x80004005. Failed to Add Update Source for WUAgent of type (2) and id ({6219E813-D37D-4D15-ADA7-3E4DADF55C9E}). Error = 0x80004005. Resolution Issue appears to be with corrupt policy info locally on the machine.  Please go to c:\windows\system32\grouppolicy\machine and delete the registry.pol  file.  Run GPUpdate /force command after that .