[Forefront for Exchange] Disabled vBuster engine keeps trying to update and sending emails

Answered [Forefront for Exchange] Disabled vBuster engine keeps trying to update and sending emails

  • Monday, December 10, 2012 4:46 PM
     
     

    Good day and thank in advance for any help.

    As object, I've disabled vBuster from my FPE, both updates and scans.

    I have also set "update once" on the scheduling for it (even if it's disabled). Sadly It still keeps sending me an email every our telling me vBuster is unable to update! When I call for an "Engine Summary " it correctely reports that Updates are disabled and scans too. 

    I have also restarted fpe services and it is at last rollup. 

    If anyone has an idea on how to solve It would be greatley appreciated.

    Thanks again and kind regards

    Francesco

All Replies

  • Monday, December 10, 2012 8:23 PM
     
     

    Hi,

    can you please run the following commands in a FSE management shell and post the results here:

    Get-FseEngineManagement

    and

    Get-FseSignatureUpdate | fl engine,enableschedule

    Greetings

    Christian


    Christian Groebner MVP Forefront

  • Tuesday, December 11, 2012 8:56 AM
     
     


    The first command output is:

    OverrideAutomaticManagement : True

    OnDemandEngines : <Microsoft, Karspersky, Norman, Authentium>

    RealtimeEngines     : <Microsoft, Karspersky, Norman, Authentium>

    ScheduledEngines  : <Microsoft, Karspersky, Norman, Authentium>

    TransportEngines   : <Microsoft, Karspersky, Norman, Authentium>

    The second one has all engines set to TRUE on EnableSchedule BUT VirusBuster which is:

    Engine: VirusBuster

    EnableSchedule: False 

    It seems correctely disabled but It kept sending emails all night .

     
  • Tuesday, December 11, 2012 9:12 AM
     
     Answered

    Hi,

    ok the output looks fine and the VirusBuster engine is disabled for the scanjobs and updates. That's strange.

    I would try to restart the whole server to make sure that there is no old configuration stuck in one service.

    If this doesn't help you should open a case with Microsoft to fix this.

    Greetings

    Christian


    Christian Groebner MVP Forefront

  • Tuesday, December 11, 2012 10:59 AM
     
     

    I ve also restarted the services. Same old story.

  • Tuesday, December 11, 2012 12:41 PM
     
     

    Hey , 

    I Suggest You to Check updates schedule job  - Signature Redistribution Jobs :

    Please Notify Me if you allready check it 


    I'd be glad to answer any question

  • Tuesday, December 11, 2012 2:07 PM
     
     

    It seems that restarting the whole server solved the problem.

    A great thank you to everyone !

    Francesco