Export (0) Print
Expand All

Microsoft Exchange 2007 Anti-Spam Migration

 

Topic Last Modified: 2007-05-31

The Microsoft® Exchange 2007 Anti-Spam Migration tool (Exchange2007AntiSpamMigration.exe) helps administrators migrate anti-spam settings from their Exchange 2003 environment to an Exchange 2007 environment. The settings are read from Active Directory® directory service and converted to an equivalent Microsoft Windows PowerShell script which consists of Exchange 2007 tasks. The conversion is as close as possible to the original one if there is no direct 1 to 1 mapping. The script can then be run on the Edge Transport or Hub Transport server roles of Exchange 2007.

Exchange 2007 Anti-Spam Migration must be run on a computer that has the following:

  • .NET Framework 1.1 or later versions
  • Windows 2000 Server or Windows Server 2003
  • Exchange Server 2007
noteNote:
The account under which this tool is run must have read rights to the Active Directory configuration container and read access to MSExchange.UCEContentFilter.xml.
The tool does not need to be run on Exchange Server 2003 to get the settings from Active Directory. So, for example, it can be run on a domain controller that does not have Exchange Server 2003 on it. As long as the computer is in the same domain and has read access to Active Directory, it can read Active Directory and create the script.
Exchange Server 2007 is then used for running the output of the tool.

Download the tool (Exchange2007AntiSpamMigration.exe) from the Tools for Exchange Server 2007 Web page at http://go.microsoft.com/fwlink/?linkid=81741. The tool is installed in the \Program Files\Exchange2007AntiSpamMigration\ folder. When you double-click the executable, a PowerShell script configuration file is created named MigrationSettings.ps1.

This section contains descriptions of the settings that are migrated with the tool.

  • Global Accept and Deny List Configuration   Accept and deny list entries are converted to corresponding Exchange 2007 IPAllowListEntry and IPBlockListEntry tasks respectively. For each accept or deny list entry, there is an Add-IPAllowListEntry or Add-IPBlockListEntry task written to the output script.
  • Block List Service Configuration   Each block list service is converted to the corresponding Exchange 2007 Add-IPBlockListProvider task.
  • Exception list to block list service rules   Converted to the BypassedRecipients parameter on the IPBlockListProvidersConfig object using the Set-IPBlockListProvidersConfig task.

  • Filter recipients who are not in the directory   Converted to the RecipientValidationEnabled parameter on the RecipientFilterConfig object using the Set-RecipientFilterConfig task.
  • Block messages that are sent to recipients   Converted to the BlockListEnabled and BlockedRecipients parameters on the RecipientFilterConfig object using the Set-RecipientFilterConfig task.

  • Filter messages with blank sender   Converted to the BlankSenderBlockingEnabled parameter on the SenderFilterConfig object.
  • Drop connection if address matches filter   Not converted because it is not supported in Exchange Server 2007.
  • Archive filtered messages   Not converted because it is not supported in Exchange 2007.
  • Accept messages without notifying sender of filtering   Not converted because it is not supported in Exchange 2007.
  • Block messages from senders   Converted to the BlockedSenders, BlockedDomains, BlockedDomainsAndSubdomains and Action parameters on the SenderFilterConfig object using the Set-SenderFilterConfig task.

  • SenderI ID validation failure action   Converted to the SpoofedDomainAction parameter on the SenderIdConfig object using the Set-SenderIDConfig task.

  • Gateway Blocking Configuration   Converted to one of the three spam confidence level (SCL) thresholds and one of the three SCL-enabled parameters on the ContentFilterConfig object using the Set-ContentFilterConfig task. For example, if the SCL threshold is set to 6 and the action is set to Delete, the corresponding task is Set-ContentFilterConfig -SCLDeleteThreshold:6 -SCLDeleteEnabled:$true -SCLQuarantineEnabled:$false -SCLRejectEnabled:$false.
  • Custom Weight Entries   In Exchange Server 2003, these entries are specified in an XML file, MSExchange.UceContentFilter.xml, that resides where the Intelligent Message Filter DAT file resides. To migrate these entries, the tool can be invoked by using a switch that enables you to specify the location of this file. Then it reads these entries and converts each of them to the Add-ContentFilterPhrase task.

Perimeter IP List and Internal IP Range Configuration   Converted to the InternalSMTPServers parameter on the TransportConfig object using the Set-TransportConfig task.

The syntax of the command and explanations of the parameters is as follows:

Exchange2007AntiSpamMigration [/f:<full path to custom words file>] [/o:<outputfile name>] [/?]

 

Command Parameters Function

/?

Displays usage at the command prompt

/f

Optional full path to MSExchange.UCEContentFilter.xml file. If not specified, custom words or phrases are not migrated.

/o

Optional output file name. If not specified, output is written to MigratedSettings.ps1 in current directory.

An example of extended command use is as follows:

Exchange2007AntiSpamMigration /f:" D:\Program Files\Exchsrvr\bin\MSCFV2\MSExchange.UCEContentFilter.xml" /o:Exchange2003Settings.ps1

The command migrates the settings with the custom words to the Windows PowerShell script called AntiSpamSettings03132007.ps1.

The following error condition can occur when you run the tool.

Error Message: ERROR: Access to the path "D:\Program Files\Exchsrvr\bin\MSCFV2\MSExchange.UCEContentFilter.xml" is denied.

Solution: Make sure that the account under which the tool is run has access to MSExchange.UCEFilter.xml.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft