Exchange 2003 Server SP2 rounds out the anti-spam capabilities of Exchange Server 2003. With addition of Sender ID and IMF filters Exchange server is now capable of protecting an Exchange organizat...
Published Dec 14, 2005
Version 1.0
Blog Post
We applied Exchange 2003 SP2 last year without incident, and we enabled and
configured IMFv2 to pull updates down from Microsoft Update with no
problems.
The December 15, 2005 IMF Update (6.5.7757.0) was identified and installed
correctly last year.
Last night as part of the regular monthly updates, a new update to IMF was
identified, January 5, 2006 IMF Update (6.5.7765.0), we applied it along
with the other Critical Updates and rebooted the server.
When the server came back up shortly after, Automatic Updates identified the
old December Update to IMF as needing to be installed even though it had
already been installed a month ago. (The "updates needed" notification is
from the yellow shield icon in the system tray.)
We went ahead and re-installed it, and once it was applied, Automatic
Updates then identified the January Update to IMF again, and we applied it
again.
Once again, Automatic Updates claimed that the December Update to IMF was
needed - we stopped there and are for now ignoring the notification message.
Automatic Updates notification appears to be caught in a loop trying to
apply IMFv2 updates.
Is anyone else seeing this behavior? How can this be fixed so that it
doesn't incorrectly identify IMF updates that have already been applied (yet
will continue to look for _real_ new updates)?
configured IMFv2 to pull updates down from Microsoft Update with no
problems.
The December 15, 2005 IMF Update (6.5.7757.0) was identified and installed
correctly last year.
Last night as part of the regular monthly updates, a new update to IMF was
identified, January 5, 2006 IMF Update (6.5.7765.0), we applied it along
with the other Critical Updates and rebooted the server.
When the server came back up shortly after, Automatic Updates identified the
old December Update to IMF as needing to be installed even though it had
already been installed a month ago. (The "updates needed" notification is
from the yellow shield icon in the system tray.)
We went ahead and re-installed it, and once it was applied, Automatic
Updates then identified the January Update to IMF again, and we applied it
again.
Once again, Automatic Updates claimed that the December Update to IMF was
needed - we stopped there and are for now ignoring the notification message.
Automatic Updates notification appears to be caught in a loop trying to
apply IMFv2 updates.
Is anyone else seeing this behavior? How can this be fixed so that it
doesn't incorrectly identify IMF updates that have already been applied (yet
will continue to look for _real_ new updates)?