locked
FCS Policy Management RRS feed

  • Question

  • Hello,

    I have the folloiwng policy:

    how could I verify on the client that the start time is correct?

    I checked http://technet.microsoft.com/en-us/library/bb418783.aspx but nothing matched the policy and the registries... the policy has been deployed.

    I saw some registries:

    AM > ScanParameters: 2 this is for the full scan ...

    AM > Schedule Day: 0 everyday

    AM > Schedule time: 120 what is this?

    SSA > Time: 12

    Not sure what is it refering to? I could not find the 9 PM Start Time anyway ...

    Also

    http://technet.microsoft.com/en-us/library/bb418783.aspx I have

    AM > Signature Updates > Schedule Date I could not find on my machine...

    but I have

    AM > Schedule Updates > Schedule Day which has a value of 8 which seems never the definitions would be updated , am I correct?

    Any idea?

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager





    • Edited by Felyjos Wednesday, January 30, 2013 7:08 PM
    Wednesday, January 30, 2013 6:48 PM

Answers

  • Hi,

    Thank you for the update.

    Please refer to this blog: http://blogs.technet.com/b/clientsecurity/archive/2010/03/05/setting-definition-update-keys-via-policy.aspx

    “AM > Schedule time: 120 what is this?” - ScheduleTime should be configured with a DWORD value that represents 12:00 AM – 11:59 PM. The value entered is the number of minutes past midnight (in local time), so specifying 120 would result in a definition update attempt at 2:00 AM. The maximum value is 1439, which would be 11:59 PM.

    “AM > Schedule Updates > Schedule Day which has a value of 8 which seems never the definitions would be updated , am I correct?”- ScheduleDay will already exist in the registry (FCS already publishes it and sets it to 0x8). Your ADM/.reg file will be changing this value, not adding the key.

    Regards,


    Nick Gu - MSFT

    • Marked as answer by Felyjos Friday, February 1, 2013 7:33 PM
    Friday, February 1, 2013 11:14 AM

All replies

  • Hi,

    Thank you for the update.

    Please refer to this blog: http://blogs.technet.com/b/clientsecurity/archive/2010/03/05/setting-definition-update-keys-via-policy.aspx

    “AM > Schedule time: 120 what is this?” - ScheduleTime should be configured with a DWORD value that represents 12:00 AM – 11:59 PM. The value entered is the number of minutes past midnight (in local time), so specifying 120 would result in a definition update attempt at 2:00 AM. The maximum value is 1439, which would be 11:59 PM.

    “AM > Schedule Updates > Schedule Day which has a value of 8 which seems never the definitions would be updated , am I correct?”- ScheduleDay will already exist in the registry (FCS already publishes it and sets it to 0x8). Your ADM/.reg file will be changing this value, not adding the key.

    Regards,


    Nick Gu - MSFT

    • Marked as answer by Felyjos Friday, February 1, 2013 7:33 PM
    Friday, February 1, 2013 11:14 AM
  • Hello,

    2:00 AM is correct. Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Friday, February 1, 2013 7:32 PM