AndrewLeg
asked on
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.
Andrew
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.
Andrew
Try this link: http://www.myitforum.com/f
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
u-ex090429.log