PureMessage for Exchange: 2007/2010 Edge Transport installation fails due to unexpected SMTP service.

  • Article ID: 114416
  • Rating:
  • 1 customers rated this article 3.0 out of 6
  • Updated: 17 Feb 2012

Issue

During the installation of PureMessage for Exchange on an Edge Transport running Exchange 2007 or Exchange 2010

First seen in

PureMessage for Microsoft Exchange

Operating systems
Windows systems running Exchange 2007 and 2010.

Cause

On the Exchange 2007/2010 Edge Server role, the PureMessage installer is attempting to detect the wrong SMTP agents.
 
On machines configured to be edge servers for Exchange 2007/2010, the installer makes the following errors:

1) It expects the IIS SMTP Service to be installed. This is wrong because Exchange 2007 and 2010 have their own SMTP process called Microsoft Exchange Transport.

2) It installs the Exchange 2003 SMTP sinks in the Windows SMTP Service; however, this is not appropriate for Exchange 2007 or 2010 because the Microsoft Exchange Transport service has no registered SMTP agents. These sinks should only be installed for Exchange 2003 or systems using the built-in Windows SMTP server. They should NOT be present for any 2007 or 2010 server.  

Steps to Reproduce

Install on a machine configured to be an Edge server for Exchange 2007 and run the Get-TransportAgent commandlet in the Exchange Shell (power shell).  Verify that you do NOT see the Sophos .NET SMTP agents (PmE12transport, PmE12Protocol).

Next, install the E2k3SDK.exe (Exchange 2003 SDK). You will find a file called smtpreg.vbs

Run:

smtpreg.vbs /Enum

In the various message boxes, look for entries that refer to PmIisTransport.SmtpSubmissionSink.1

These entries are only expected in Exchange 2003 environments or where the built-in Windows SMTP server is used. They should NOT be present for any 2007or 2010 server.

What to do

Note: In the following lines, {appPath_bin} is the path to PureMessage's bin directory -- the default path used by the installer is C:\Program Files\Sophos\Puremessage\bin


In the Exchange PowerShell, run the following commands:

Install-TransportAgent -Name PmE12Transport -AssemblyPath "{appPath_bin}\PmE12Transport.dll" -TransportAgentFactory "PmE12Transport.PMTransportAgentFactory"

Install-TransportAgent -Name PmE12Protocol -AssemblyPath "{appPath_bin}\PmE12Transport.dll" -TransportAgentFactory "PmE12Protocol.PMProtocolAgentFactory"


enable-TransportAgent -Identity PmE12Transport


enable-TransportAgent -Identity PmE12Protocol


Set-TransportAgent -Identity PmE12Transport -Priority 1
 

You must then restart the Microsoft Exchange Transport service. Upon restarting the service, rerun the smtpreg.vbs command to verify that the sinks are on the proper SMTP service.
 

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments