Jawab software update

  • Tuesday, August 26, 2008 2:34 PM
     
     

    Hi,

     

    Can any help in know the statement Enforcement state unknown in software update. What is this actually means. I find this for some of the software update reports.

     

    rgds

    Manju

All Replies

  • Tuesday, August 26, 2008 5:12 PM
     
     

    Unknown means that the client has not been scanned so it doesn't know if a patch is needed or not.

     

  • Tuesday, August 26, 2008 6:49 PM
     
     
     Matthew Hudson wrote:

    Unknown means that the client has not been scanned so it doesn't know if a patch is needed or not.

     



    Are you sure about that?

    I thought it meant that the client has not reported back anything about that particular deployment therefore the state of that deployment for that comptuer is "unknown"


  • Tuesday, August 26, 2008 7:49 PM
     
     

    What's the difference between "has not been scanned" and "has not reported back"? ;-)

  • Tuesday, August 26, 2008 7:53 PM
     
     
    In my mind scan refers to the determination of what patches are applicable to a computer. This would not be a part of the patch deployment but rather what determines if patches are applicable prior to deployment. (scan causes you to see xxx number of machines require MS08-041)

     Does that make sense at all the way I am trying to explain it?


  • Tuesday, August 26, 2008 8:53 PM
     
     
    This may make what I was trying to say more clear.


    For scan status you would use th
    report in the scan D. category that tells you which machines scanned successfully per site or per collection.

    For deployment status you would use
    Software Updates - C. Deployment States



    So there is a difference in scanning and reporting the status of a deployment and scanning is not directly related to the deployment itself. The OP asked why the enforcement state was unknown. The enforcement state doe not refer to the scan but rather to the deployment.
  • Wednesday, August 27, 2008 7:45 AM
     
     

    Hi

     

    So the final result is "enforcement state unknown" means that client has not reported any on the patched deployed to it.

    Is this sound correct please let me know.

     

    rgrds

    Manju 

  • Wednesday, August 27, 2008 12:52 PM
     
     

    Correct, you can consider this machine to be unpatched.

     

     

  • Wednesday, August 27, 2008 12:57 PM
     
     
    I would expect to see that number drop as those machines come back online or reconnect to the network and report a status.


  • Thursday, August 28, 2008 10:00 AM
     
     Answered

    Hi,

     

    Thank for the update finally, I got the answer.

     

    Enforcement state for a deployment : which can be used to determine overall progress of an ongoing deployment, providing the number of clients in each state along with drill-down capablilites to identify the extact clients that are in each state. computer experience failures or that have not progressed from a particular state can be efficiently identified and remediated.

     

    In this "enforcement state unknown" means computer has not updated any of the status message to the SCCM Server.

    (example:- like Installed, pending for restarted or failure). Then the SCCM report show "Enforcement state Unknown".

     

    Thank for all you guys,

     

    Regards

    Manju

  • Thursday, August 28, 2008 5:47 PM
     
     
     mashg4u wrote:

     "enforcement state unknown" means computer has not updated any of the status message to the SCCM Server.

    (example:- like Installed, pending for restarted or failure). Then the SCCM report show "Enforcement state Unknown".

     

     

    Isn't that a fancy way of saying, "the client has not reported back anything about that particular deployment" which was what I posted several days ago :-)

     

     

  • Friday, August 29, 2008 9:14 PM
    Owner
     
     

    For the question:

     

    What's the difference between "has not been scanned" and "has not reported back"? ;-)

     

    There is a big difference.

     

    Not been scanned can mean that there is an issue with the Windows Update Agent so it CAN'T scan, and WON'T scan.

     

    Not reporting in state messages means that it DID scan, so the client is functioning fine, but maybe can't report through the MP, or maybe there is a backlog of state messages on the site server. Both those are much different in troubleshooting that a client that can't scan :-)

     

  • Friday, August 29, 2008 9:15 PM
    Owner
     
     

    Oh, and I'm moving this thread to the Software Updates forum where it is applicable (does not seem to have anything to do with software distribution).