• 1. London, UK
  • 2. New York, NY
  • 3. Sydney, Australia
  • 4. Melbourne, Australia
  • 5. Moscow, Russia
  • 6. Singapore
  • 7. Paris, France
  • 8. Chicago, IL
  • 9. Hong Kong
  • 10. Houston, TX

Wednesday, November 29, 2006


Update: Manually removing IMF v1

Posted by Bharat Suneja at 9:57 AM
Scott Schnoll has an update regarding the recent post Intelligent Message Filter (IMF) v1 download removed from microsoft.com, and the issue of not being able to remove IMF v1 from Add/Remove Programs (if one doesn't remember which account was used to install it or the account is no longer available) without reinstalling it. Here's the process to manually remove IMF v1 as documented in Microsoft Exchange Server Intelligent Message Filter v2 Operations Guide [available here].

To manually remove Intelligent Message Filter v1:
1. Stop all Exchange services (Information Store, System Attendant, SMTP, and Exchange-aware antivirus services).
2. Rename the MSCFV1 folder in X:\Program Files\Exchsrvr\bin, where X is the drive letter where Exchange Server is installed.
3. Rename the ContentFilter.dll file in \Exchsrvr\bin\
4. Open Regedit and export the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange
5. Delete the ControlFilterVersion subkey from the registry.
6. Restart the server. You should now be able to install Exchange Server 2003 SP2 without errors.

Labels: ,


July 11, 2007 12:05 AM
Anonymous Richard Tubb said...

Thankyou Bharat - this solution saved me during a problematic SBS R2 re-install today! :-)

July 27, 2008 12:36 AM
Anonymous Anonymous said...

Will give it a go in 3 minutes.

See what happens.

BR Jure

August 25, 2008 8:19 AM
Anonymous Anonymous said...

If this doesn't work does anyone know of another solution?

September 20, 2008 3:01 AM
Anonymous Anonymous said...

Thanks, this worked realy wel! :)

April 17, 2009 7:14 AM
Blogger qlinden said...

This Guy is my new hero, Thanx a millloin!

June 4, 2009 12:20 PM
Anonymous Anonymous said...

Steps 2 and 3 could not be found but the registry entry was there and that is all it took for me to continue on with the SP2 update. Bizarre!

January 28, 2010 1:08 PM
Anonymous Anonymous said...

Just a rant - in the registry, delete the VALUE "ControlFilterVersion" - it's not a SUBKEY...

April 6, 2010 3:54 PM
Anonymous Anonymous said...

Actually its not ControlFilterVersion. Its ContentFilterVersion. ;)


Post a Comment

Links to this post:

Create a Link

<< Home