• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6332
  • Last Modified:

SCCM REPORTS - Detection State Unknown shown in reports for most clients in Microsoft Update Deployment

I've recently deployed SCCM in our network.
Everything seems to have gone well, client agents installed to all pc's, and server configuration complete.
Recently, using the Software Updates feature in SCCM i deployed a number of Microsoft Updates to all clients in my collections.
Problem is, when i run reports to check on the progress of the deployment, over 60% of the clients show as ' Detection State Unknown ' in the reports.
When i check the Updates Deployment log on many of the pc's which show as Detection State unknown in the reports, the updates look to have installed successfully a couple of days ago.
Why are the reports not giving me the correct results ?
Why are they showing Detection State Unknown when the updates have installed correctly ?
Not sure whether this is part of the problem, but when i check i the IIS/WSUS logs, it is full of BITS errors. I've attached the log file for you to look at.

Any help much appreciated.

  • 2
1 Solution
AndrewLegAuthor Commented:
Log file attached.
Adam LeinssCommented:
Try this link: http://www.myitforum.com/forums/m_171978/mpage_1/key_Reset%252CParental%252Ccode/tm.htm#171978
The IUSR_<servername> had been removed from the ACL on the CCM_Incoming Virtual Directory.  Once it was "reinstated" - all was well.  
Other articles point to the IUSR_<servername> for bits errors as well.
AndrewLegAuthor Commented:
I've been told that the logs indicate an Access Denied error, and that i was to ensure that in IIS under CCM_Incoming - BITS Server Extension, the Allow clients to transfer data to this virtual directory, Use default settings option was configured.

My SCCM server is running Windows 2008 IIS7, and when i go to IIS manager, and select the BITS Upload icon from the Default Web Site, i'm receiving the following error :
BITS server was unable to read from the IIS Meta-base as it is corrupt. The settings for this virtual directory have been reset to the BITS defaults.

THis must be the root of the problem, has anyone else experienced it before, what's the easiest solution ?



Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now