none
Exchange 2013 anti-malware updates are not available

    Question

  • Hi,

    I originally posted this question here:

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrsecuremessaging/thread/9b583f5d-351e-4f43-a9b1-0a5d6253d794

    But was directed to try TMG forum instead, hope you guys can help :)

    I have a problem getting updates for the anti-malware system in Exchange 2013. The event log reads:

    Event ID 6029

    MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

    The firewall (MS TMG) shows that two request for two .cab files is sent to what I assume are Akamai content servers (it does not reverse) since the IP on this http get request will change based on what forwarder I provide my internal DNS.

    I also see a request for two Microsoft CRLs.

    Are there any useful logs to look at to determine why this isn't working?

    Regards,

    Ola


    Monday, February 25, 2013 7:57 AM

Answers

All replies

  • Hi,

    Thank you for the post.

    As far as I understand, this issue is not related to Forefront Protection for Exchange server. Exchange 2013 includes a basic built-in anti-malware engine to protect your server from malicious code. There is no FPE involved in Exchange 2013.

    Regards,


    Nick Gu - MSFT

    Tuesday, February 26, 2013 8:01 AM
  • Hi, 

    Yes Exchange includes a basic malware scanner which I'm trying to update with no luck, I assume it's an envolment of FPE. As i wrote, I did try the Exchange forums first, but was directed to try here ;). Is there an alternative path I can try to download updates from?

    Regards,

    Ola

    Tuesday, February 26, 2013 8:17 AM
  • Hi,

    Thank you for the update.

    As we cannot install FPE on Exchange 2013, I am not sure whether there is alternative path for malware updates. You may post this issue in Exchange 2013 forum for help.

    Regards,


    Nick Gu - MSFT

    Thursday, March 07, 2013 3:56 PM
  • I have same problem here. In Powershell cmdlt set-malwarefilteringserver there is option such as -secondaryupdatepath which is have $null as default. I think that there is some another path exists but we dont know about it. Or its anti-malware problem. 
    Wednesday, April 17, 2013 11:48 AM