RE: IMF Install
- From: "Wayne Snow" <wsnow@xxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Tue, 29 Nov 2005 13:38:52 -0800
Carl I failed to mention my front-end server has SP2. But when I look at
my front-end server SMTP Virtual Server IMF is no where to be found as
an option. How do I enable IMF? It is not showing up under ESM ,Server,
Protocols, SMTP.
________________________________
From: Carl Houseman [mailto:c.houseman@xxxxxxxxx]
Sent: Tuesday, November 29, 2005 1:16 PM
To: [ExchangeList]
Subject: [exchangelist] RE: IMF Install
http://www.MSExchange.org/
Please delete all copies of the Exchange IMF .MSI file.
Why? The answer is in the release notes for SP2.
(cliff notes - you don't need it any more and installing it is harmful)
________________________________
From: Wayne Snow [mailto:wsnow@xxxxxxxxxxx]
Sent: Tuesday, November 29, 2005 3:46 PM
To: [ExchangeList]
Subject: [exchangelist] IMF Install
http://www.MSExchange.org/
Help
I recently upgraded my three node Exchange 2003 cluster servers with
SP2 for exchange. I have one front-end exchange node with SP2 installed
also. The IMF tab appears in ESM under message delivery properties I
setup my SCL for Gateway and Junk Email. I understand I should only
install IMF on front-end nodes in a exchange 2003 cluster. Is the only
way to finish installation is to install on front-end also a
bridge-head server is to down load ExchangeIMF.MSI file and install on
front-end server?
Wayne Snow
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
wsnow@xxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx
Other related posts:
