locked
Last scan date and time is not available on Forefront Client Security RRS feed

  • Question

  • Hi,

    We are having issues for a site where the client computers are not updating the last scan date and time for Forefront Client Security. All other sites are showing it. It is just happening to a particular site. It says "Not Available". The client machines in this site are missing two consecutive scheduled scans (more than 14 days). It is making the client concerned whether the automatice scan is working on these machines or not. If it is automatically scanning after 14 days, why it is not updating the last scan date and time. However, if scanning is done manually it updates the last scan item on those machines.

    Please advise asap.

    Thanks.

    Hasan
    Monday, June 22, 2009 11:07 PM

Answers

All replies

  • Hi,

     

    Thank you for posting.

     

    According to your description, I’d like to confirm how do you deploy the Forefront Client Security? If the client security is deploy to agent via policies, please check whether the policy is applied to the agent correctly. For more information, you may refer to the following link.

     

    http://technet.microsoft.com/en-us/library/bb418853.aspx

     

    Regards,


    Nick Gu - MSFT
    Tuesday, June 23, 2009 9:14 AM
  • Hi Nick,

    Thanks for your reply. In our environment Forefront is deployed through the policy created using Forefront Console. We have one policy for all the sites. The policy is linked to the OU in which the server is. RSOP.msc ensured that the policy is getting applied to the clinet machines having the issue.  

    Regards,

    Hasan
    Wednesday, June 24, 2009 12:27 AM
  • Are the machines in that site turned off during their scheduled scan periods?
    CSS Security Support Engineer (FCS/MBSA/WUA/Incident Response) Check out my blog http://blogs.technet.com/kfalde
    Wednesday, June 24, 2009 2:20 PM
  • Kurt,

    The machines are turned off during the scheduled scanning time.

    Thanks Hasan

    Thursday, June 25, 2009 12:08 AM
  • Hi,

     

    Thank you for your update.

     

    I think that is the reason why the last scan date is not updated. please make sure the machines are running during the scan periods and see if it works.

     

    Regards,


    Nick Gu - MSFT
    • Marked as answer by Nick Gu - MSFT Tuesday, June 30, 2009 8:02 AM
    • Unmarked as answer by Hasanul Karim Wednesday, July 1, 2009 1:55 AM
    Tuesday, June 30, 2009 8:02 AM
  • Are you doing scheduled scans or interval scans?

    This might help you understand what should be happening when a scan is missed:

    http://blogs.technet.com/fcsnerds/archive/2009/06/18/understanding-catch-up-scans.aspx

    -Eddie
    Tuesday, June 30, 2009 11:45 PM
  • Nick,

    Thanks for your response. But should not it be doing a catch up scan after missing two consecutive scheduled scans? The machines are turned off while the scheduled scan is scheduled (2 AM on every friday). But it should do a catch up scan (may be Monday morning when a user is logged in) and update the last scan data which it is not doing. And that is my question about.

    Regards,

    Hasan

     

     

     

    Wednesday, July 1, 2009 2:00 AM
  • Hi,

     

    Thank you for your update.

     

    I agree with Eddie. You may pay attention to that words “If a client computer is offline for two consecutive scheduled scans, Client Security starts a scan the next time someone logs on to the computer.The machines are turned off while the scheduled scan is scheduled (2 AM on every Friday). But it should do a catch up scan(may be next Monday morning when a user is logged in).  Do you agree?

    For more information, please refer to the following link.

     

    http://technet.microsoft.com/en-us/library/bb418896.aspx

     

    Regards,


    Nick Gu - MSFT
    Thursday, July 2, 2009 9:09 AM