Hunt SCCM Issues Down

Sharing this query which will provide details of content download history, initiated by different clients and using different method of content download sources . It will also give info on the size of the content downloaded and on the content details too . Feel free to customize according to your Org. need SELECT s.Name0 as 'Device Name',ContentID = ContentID, 'Content Source' = HostName, 'Content Source Type' = CASE DistributionPointType WHEN 1 THEN 'Cloud Distribution Point' WHEN 2 THEN 'Management Point' WHEN 3 THEN 'Peer Cache' WHEN 4 THEN 'Distribution Point' WHEN 5 THEN 'BranchCache' WHEN 6 THEN 'DO Peer (Delivery Optimization)' WHEN 7 THEN 'DO Server (Delivery Optimization)' WHEN 8 THEN 'Microsoft Update' ELSE 'Unknown' END, 'Start DateTime' = StartTime, 'Bytes Downloaded' = BytesDownloaded FROM v_R_System s LEFT OUTER JOIN v_ClientDownloadHistoryDP_BG cdh ON s.Resourc

Download failed for content  under context System, error 0x80091007 . Package hash matching for the package failed. Workaround It turns out that the system file thumbs.db was causing this problem within these packages. Thumbs.db is a system file created by windows when browsing a folder in thumbnail view. If I remove this file from my packages source directory, and update my distribution points, the package installs first time without error.  Please make sure you uncheck the option "Hide Protected System Files" while searching for the Thumbs.db .

ConfigMgr 2012 update scan fails  with 8007000E  and causes incorrect compliance status. Root Cause Because Configuration Manager does compliance reporting, it has extremely broad scan criteria to determine what is applicable. This is different from a typical scan performed by the Windows Update agent which requires a smaller subset of criteria. If an update is on WSUS and in a non-declined state, the Configuration Manager scan criteria will cause the Windows Update agent to try to evaluate it. Windows x86 clients have a much smaller addressable memory range than 64-bit clients. With enough updates, the data returned to Configuration Manager is large enough that RPC can’t allocate the shared section used to return the data. This is because overall memory usage of the svchost.exe process hosting the Windows Update Agent process is extremely high. The result is that there is either not enough memory available to satisfy the request or there is not a large enough contiguous bloc

SCCM client installation with Windows 10 Devices failing with 1603. Recently faced an issue with SCCM client installation with Windows 10 Devices with 1603.  The scenario was the machines got migrated from Win 7 to Win 10 (in place/ task sequence) and the SCCM client evaluation was failing for those and appearing to be as inactive in the console. Even the 1606 client Hotfix installation was also failing on those. After a lot of r&d and troubleshooting. Workaround -  The schedule task for Configuration Manager found to be causing this and we had to delete "HKEY_LOCAL_MACHINE\SOFTWA RE\Microsoft\Windows NT\CurrentVersion\Schedule \TaskCache\Tree\Microsoft\ Configuration Manager" from the registry for those affected systems . Once that entry got deleted , client installation / evaluation / reporting all were going on smoothly as expected. 

SCCM 2012 Migration Connector stops working and gathering of data fails from destination Site. Cause- Check if you have multiple SMS Provider exist in your CM 2012 Hierarchy and that's only causing the issue. Resolution-  Uninstall all the additional SMS Providers and reset the site (happens automatically upon removal). Pre_Checks- You can just open up a Powershell on one SMS Provider you know (you always know at least one) and execute the following query: (Get-WmiObject -class SMS_ProviderLocation -Namespace root\SMS).Machine This will give you something like this: Steps for removing a SMS Provider 1) Open the Start Menu on the ConfigMgr server and select Microsoft System Center 2012 > Configuration Manager > Configuration Manager Setup 2) Getting Started > Select "Perform site maintenance or reset this Site" and click Next 3) Site Maintenance > Select "Modify SMS Provider configuration" and click Next 4) 

Please find the query below. Change the application Name & Publisher Name according to your need. SELECT c.Name0, a.DisplayName0, a.Version0, c.AD_Site_Name0, b.LastUsedTime0 FROM v_GS_ADD_REMOVE_PROGRAMS a Join v_R_System c On a.ResourceID = c.ResourceID Join v_GS_CCM_RECENTLY_USED_APPS B On B.ResourceID = a.ResourceID WHERE a.ResourceID = c.ResourceID AND a.DisplayName0 like '% Adobe % Reader %' AND a.Publisher0 like '% Adobe %' AND Version0 like '11' GROUP BY c.Name0, a.DisplayName0, a.Version0, c.AD_Site_Name0, b.LastUsedTime0 ORDER BY c.name0