Antigen not updating
Ideally, you’d use a script to frequently check for and download new engines (2 files per engine; and This method also has the disadvantage of you needing to download the full engine package each time, whereas all of the aforementioned methods do not (they will frequently use incremental update packages).Full updates can comprise of 15-60MB of data, so this method is not only a pain to setup, but is also bandwidth-intensive.Make sure that you have disabled all local updates on each Antigen and Forefront server before using FSSMC to deploy updates to them.You’ll see that this is almost always down as the “Last Resort” in the table above, because it really does take a lot of hassle to set up.You then share the ‘Engines’ folder within that installation, so that other Antigen / Forefront servers can use a UNC path to update from the hub (rather than from Microsoft HTTP servers): Antigen 9 or Forefront (FSE/FSSP/FSOCS) products permit up to 2 update locations per scan engine.Use these to your advantage to provide redundancy in your environment.
After Antigen is installed, engine updates automatically begin.
For more information on configuring scanning options, see Chapter 6 - Configuring Manual Scan Jobs, Chapter 7 - Configuring Realtime Scan Jobs, Chapter 8 - Configuring SMTP Scan Jobs, and Chapter 9 - Configuring MTA Scan Jobs.
After an upgrade to Antigen, the Microsoft Engine will not be scheduled for updates.
Microsoft is aware of an issue with the Microsoft AV engine not updating on some installations of Antigen and Forefront Server Security products.
The issue arose because the ave in one of the Microsoft AV engine updates was marked as hidden, causing all subsequent updates to fail when attempting to delete this file.