Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
1196 Views 3 Replies Latest reply: Oct 9, 2012 8:02 AM by Aidan RSS
bshirish Newcomer 31 posts since
Jan 19, 2012
Currently Being Moderated

Oct 9, 2012 6:52 AM

Mcafee Securtiy for Exchange 7.6 on Ms Exchange Server 2010 dat update issue!

Hello All,


We are using Microsoft Exchage 2010 and Installed Mcafee Security for Microsoft Exchage 7.6 Standalone Setup.


From today we are facing some isue with udpate signature.


  1. On schedule time update status showing failed.

  2. When I run manully It showing connecting to epo and then shows update not found even if we using standalone MSME 7.6,
    we don't know why it  shows connecting to EPO for update. We don't have any extention or packages in the EPO regarding
    MSME or Group Shiled.


So Its should goes at all time to driect to Mcafee for any update rather than local EPO, please provide the solution on the same asap!



Thanks in advance!


Shirish Bhosle

Sr. Support Excutive.

  • Aidan McAfee SME 461 posts since
    Nov 4, 2009

    When an update is called in MSME\GSE - the McAfeeFramework\Agent is used. If you have configured McAfee Agent set to use specific repositories in the ePO then this is sent down to the local sitelist.xml - if this is the case then MSME will use that configuration also - since the McAfee Agent provides common updater for all installed McAfee products.


    Also what is exact failure message - sometimes you can see a failure when MSME starts an update and and McAfee Agent or VSE is already running an update.


    Can you check even if it says failure - are the dats updated correctly by another update task (by VSE\Agent)??? As stated the agent provides common updater for all mcafee products installed.

  • Aidan McAfee SME 461 posts since
    Nov 4, 2009

    As stated in ePO if you have conifgured an Agent Policy which is set to use ePO Master or Distributed Repositories and that agent policy is applied to the MSME\Exchange Server then when MSME calls for the McAfeeAgent\Framework to do the update - it will refer to the local "Autoupdate Repository List"  (sitelist.xml).


    You can see this list :-

    - in VSE  - open Console - Tools - Edit AutoUpdate Repository list

    - for MSME - Start Menu - All Programs - McAfee - Security for Micrsoft Exchange  - Edit Sitelist.

    (This is two views onto the one sitelist.xml file which is used by the McAfee Agent)


    If you wish to change this then Create a new Agent Policy in ePO which Points to the external McAfeeHTTP and McAfeeFTP repositories and apply that policy only to the MSME server - once applied you should see difference in checking the Repository List in either method as stated above.

More Like This

  • Retrieving data ...

Bookmarked By (0)