Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter >
> 
> 
FPSMC failed to download engine

דיון כללי FPSMC failed to download engine

  • Thursday, August 30, 2012 12:57 PM
     
     
    Sign In to Vote
    0

    New install of FPSMC 11.1.1614.0 on a standalone server and forefront protection for exchange 11.0.677.0 on 3 new Exchange servers.

    The agent deployed to the servers fine. Created a simple job to update the servers and it fails everytime, this is the message and only error I see:

    Also what are the latest build numbers and what should I be on?

    Job Name: Update Servers
    Job Type: Redistribution
    Success: false
    Completed: 30 August 2012 00:00:03

    Engine(s) downloaded

    Command,Kaspersky,Microsoft,Norman,VBuster,WormList

    Source

    http://forefrontdl.microsoft.com/server/scanengineupdate

    Message(s)

    Diagnostics Messages

     

All Replies

  • Friday, August 31, 2012 7:45 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Thank you for the post.

    FPSMC downloads engines on the schedule that you specify when you create a signature redistribution job. It only downloads signatures when you create a job and you specify when and how often it does so. If you find that some of your engines are not updating, you should manually run a Signature Redistribution job that targets the managed servers with the out-of-date engines

    Regards,

    Nick Gu - MSFT

     
  • Friday, August 31, 2012 12:35 PM
     
     
    Sign In to Vote
    0

    Its the signature redistribution job that is failing (every time). I have it scheduled twice a day, I have also ran it manually it always fails. The internet access is locked down pretty tight on our servers but it dosnt give me any useful error to see why its failing - Success = false is all I get.

    I downloaded a powershell script http://support.microsoft.com/kb/2292741 that gets the updates from the same place:

    http://forefrontdl.microsoft.com/server/scanengineupdate and that works so I know it can get there. I am thinking of scheduling that to run everyday and having the servers get the updates by url but that dosnt seem like the best solution.