Let’s start with some easy stuff..

Get the number of Public Folders

Get-PublicFolder -Recurse | Measure-Object

Get the sum / number of Mails / Object in all Public Folders

Get-PublicFolderStatistics | Measure-Object -Property ItemCount -Sum

Get the number of Mailboxes

Get-Mailbox | Measure-Object

Get the number of sent messages / emails within a date range

Get-MessageTrackingLog -Start "29.11.2009" -End "30.12.2009" -ResultSize Unlimited | Measure-Object

I’m just upgrading one of our Microsoft Exchange 2007 Servers to Microsoft Exchange Server 2010. I’ve decided to first remove the Exchange 2007 Server and then install the 2010 Version. Well, if you should ever choose the same path, you’ll have to pass a few hurdles… After following the instructions in the links provided below, i finally was able to remove Microsoft Exchange Server 2007. When i then started Microsoft Exchange 2010 Server Setup, i got the message:

Setup.exe – A previous version of Exchange Server is already installed on this machine.

Well, since this Version of Exchange is pretty new and Google nor other search machines give you good results about this issue, i decided to not spend to much time searching the internet but opened the registry editor and searched for Exchange in the HKLM/Software Key.. What i’ve found:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

Rename this Key to _Exchange, start setup.exe again and you’ll be fine ..

Links

This Server is the Source for a Send Connector

Removing Public Folder Databases

How to Remove a Public Folder Database

How to Delete Multiple Public Folders from Your Organization

Get-Mailpublicfolder | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
 
write-output ""
}

or redirect the output into a file for analysis, whatever..

Get-Mailpublicfolder | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
 
write-output ""
} | out-file -filepath c:\publicFolders.txt -encoding ASCII

Get-Mailbox | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
 
write-output ""
} > c:\smtp.txt

or use the out-file cmdlet..

######### Using Out-File Cmdlet ############
 
Get-Mailbox | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
write-output ""
} | out-file -filepath c:\smtp.txt -encoding ASCII

Microsoft Exchange Installation Wizard

The component Microsoft Exchange Messaging and Collaboriation Server cannot be assigned the action “Remove” because:

- This server is the Recipient Update Server for the domain “someDomain.tld”. You cannot uninstall this server until you select a different Recipient Update Server for this domain.

Exchange_2003_removal_RUS_assigned

The trick to remove Microsoft Exchange Server 2003 from your organization is reassigning the Recipient Update Service (RUS). Setup will not allow you to uninstall Microsoft Exchange Server 2003 until the Recipient Update Service (RUS) has been reassigned to another server. This is ironic since Exchange Server 2007 doesn’t even use the Recipient Update Service. However, this task must be performed to proceed the uninstallation of Microsoft Exchanger Server 2003.

Reassigning the Recipient Update Service is fairly easy. Begin the process by opening the Exchange System Manager. Now, navigate through the console tree to Recipients | Recipient Update Service.

Exchange_2003_removal_RUS_reAssign

There are two listings for the Recipient Update Service. There is an enterprise listing, and a domain listing.

At this point in the process, you must right click on the enterprise listing for the Recipient Update Service, and then choose the Properties command from the resulting shortcut menu. When you do, the Exchange System Manager will display the Recipient Update Service properties sheet.

Exchange_2003_removal_RUS_Properties

You will notice that the Recipient Update Service has been assigned to a specific Exchange server. By default, the server that is listed is an Exchange 2003 server. You must click the Browse button, and then choose an Exchange 2007 server from the list. After doing so, click OK to close the Recipient Update Service properties sheet.

Now it’s time to turn our attention to the domain listing for the Recipient Update Service. We will do the exact same thing for this listing that we did for the enterprise listing. Right-click on the domain listing and choose the Properties command from the resulting shortcut menu to reveal the Recipient Update Services properties sheet. Now, click the Browse button next to the listing for the Exchange server, and choose an Exchange 2007 server from the list. Click OK to close the properties sheet, and you’re done.

Conclusion

Now that the Recipient Update Service has been reassigned you should have no trouble uninstalling Exchange server 2003. Simply run the Exchange Server 2003 Setup program, and then use the Change/Remove option to complete the uninstallation process.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
 test@christiano.ch
SMTP error from remote mail server after MAIL FROM:<sunny@christiano.ch> SIZE=6841:
host xyz.christiano.ch [194.123.18.170]: 530 5.7.1 Client was not authenticated

Then you have to change the Receive Connector to allow anonymous connections (probably) ..
You can do this using the Microsoft Exchange Management Shell (EMS)

Set-ReceiveConnector -Identity "Default <SERVERNAME>" -PermissionGroups "AnonymousUsers"

or in the GUI using Microsoft Exchange Management Console (EMC)

Navigate to Microsoft Exchange | Server Configuration | Hub Transport | Receive Connectors

Microsoft_Exchange_Management_Console_ReceiveConnector_Allow_AnonymousUsers

In environments without an Edge server role, these need to be installed manually on the Hub Transport server(s).

To install anti-spam agents on a Hub Transport server, start Exchange Management Shell (EMS), navigate to the “%ProgramFiles%\Microsoft\Exchange Server\Scripts” folder
(by default C:\Program Files\Microsoft\Exchange Server\Scripts)

Microsoft_Exchange_2007_Install-AntispamAgents

Now run/execute:

Microsoft_Exchange_2007_Install-AntispamAgents_PowerShell

[PS] C:\Program Files\Microsoft\Exchange Server\Scripts>.\install-AntispamAgents.ps1

Now restart the Microsoft Exchange Transport Service

Microsoft_Exchange_2007_TransportServiceRestart

Once installed successfully, the command will show each agent installed, whether it is enabled or not, and its priority

Anti-Spam Agents on Hub Transport serverAfter the anti-spam agents are installed, you can see the Anti-spam tab in Organization Configuration | Hub Transport node in Exchange Management Console.
(If your console was open during installation, you will need to restart it).

Microsoft_Exchange_2007_AntiSpamAgents

Alternatively you can run Get-TransportAgent

Microsoft_Exchange_2007_PowerShell_Get-TransportAgents

[PS] C:\>Get-TransportAgent

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
sunny@christiano.ch
SMTP error from remote mail server after RCPT TO:<sunny@christiano.ch>:
host christiano.ch [100.120.200.30]: 550 No Such User Here

If you want your Microsoft Exchange Server to take such mails and put them in a common mailbox, you could use the nice Microsoft Exchange 2007 Transport Protocol Agent which provides the (MTA) catchall functionality from Wilbert De Graaf. The Agent is Open Source published on www.codeplex.com. To download the Agent, click here and click on download..

Setup is quite easy.

The instruction has been taken from the install notes from Wilbert de Graaf..
CatchAllAgent: Exchange 2007 Transport Protocol Agent
=====================================================

Introduction
————
CatchAllAgent is an Exchange 2007 Transport Protocol Agent. If a message comes in, and a
recipient of that message does not exist (unknown recipient), the recipient typically gets
rejected by the Recipient Filtering feature (which is also a Transport Protocol Agent).
The CatchAllAgent can be configured to rewrite the recipient address for unknown recipients
such that such messages end up in a dedicated mailbox. The configuration allows for multiple
domains, but you can only specify a single target address for each of those domains.

Configuration
————-
The configuration is called config.xml and should be found at the same location of the agent’s
assembly (DLL). The contents looks something like this:
<config>
<domain name=”domain1.com” address=”catchall@domain1.com” />
<domain name=”domain2.com” address=”admin@domain2.com” />
</config>
This says that messages to unknown recipients @ domain1.com should be redirected to
“catchall@domain1.com”, and messages to unknown recipients @ domain2.com should be
redirected to “admin@domain2.com”. Recipients that are either known at those domains,
or at other domains (either known or unknown) are unaffected.
Changes to the configuration file will be picked up on the fly. If there is an error
in the configuration file, the (new) content will be ignored.

Installation Steps
——————
1. Create a directory on your Transport server (either Edge or Internet Facing Hub role)
2. Unzip the ExchangeCatchAll.zip file in that directory
3. Edit the config.xml according to your needs
4. Open the Exchange 2007 Management Shell and run the following command to install
the agent, assuming the directory with the CatchAll agent is c:\catchallagent:
[PS] C:\catchallagent>install-transportagent -Name "CatchAll Agent" -TransportAgentFactory:CatchAll.CatchAllFactory -AssemblyPath:"C:\catchallagent\CatchAllAgent.dll"
Identity Enabled Priority
——– ——- ——–
CatchAll Agent False 18
WARNING: Please exit Powershell to complete the installation.
WARNING: The following service restart is required for the change(s) to take effect : MSExchangeTransport
5. Now the priority of the CatchAllAgent needs to be smaller that the priority of the Recipient
Filtering agent. So you first need to figure that out using the get-transportagent task:
[PS] C:\catchallagent>get-transportagent
Identity Enabled Priority
——– ——- ——–
Transport Rule Agent True 1
Journaling Agent True 2
RMS Encryption Agent False 3
AD RMS Prelicensing Agent False 4
Connection Filtering Agent True 12
Content Filter Agent True 13
Sender Id Agent True 14
Sender Filter Agent True 15
Recipient Filter Agent True 16
Protocol Analysis Agent True 17
CatchAll Agent False 18

So in this case (Internet facing Hub) the priority of the Recipient Filtering Agent is 16, and since
11 is available, that’d be a good pick. Use the following command to set the priority:
[PS] C:\catchallagent>set-transportagent "CatchAll Agent" -Priority:11
WARNING: The following service restart is required for the change(s) to take effect : MSExchangeTransport
6. Now the agent can be enabled:
[PS] C:\catchallagent>enable-transportagent "CatchAll Agent"
WARNING: The following service restart is required for the change(s) to take effect : MSExchangeTransport
7. Restart the Transport service:
net stop MSExchangeTransport
net start MSExchangeTransport

Troubleshooting
—————
The agent supports standard .NET tracing. To enable tracing, you have to add the following
section to the application configuration file (edgetransport.exe.config):
<configuration>
<system.diagnostics>
<trace autoflush=”false” indentsize=”4″>
<listeners>
<add name=”myListener”
type=”System.Diagnostics.TextWriterTraceListener”
initializeData=”traces.log” />
<remove name=”Default” />
</listeners>
</trace>
</system.diagnostics>
</configuration>
The result is that traces will be written to file “traces.log” in the applcation’s directory.
There will only be traces for configuration changes, and not when a recipient gets processed.

Links

CatchAllAgent for Microsoft Exchange 2007 Transport Protocol Agent on www.codeplex.com

To install Forefront Security for Exchange Server on a local server (Edge Server in this illustration)

1. Run the Setup.exe file, which is available on your CD image or from the self-extracting package available at the Microsoft Volume Licensing Download Center or from the Trial Download Center (checks links below..)

Exchange_Forefront_Setup_1

2. The initial setup screen is Welcome. Click Next to continue.

Exchange_Forefront_Setup_2

3. Read the license at the License Agreement screen and click Yes to accept it.

Exchange_Forefront_Setup_3

4. On the Customer Information screen, enter User Name and Company Name, if needed.

Exchange_Forefront_Setup_4

5. On the Installation Location screen, select Local Installation.

Exchange_Forefront_Setup_5

6. On the Installation Type screen, select Full Installation.

Exchange_Forefront_Setup_6

7. Setup checks to see if you have the correct version of the Windows Update Agent. If you do not have the correct version, at the end of the installation you are directed to the Microsoft Update Web site to do the opt-in manually. If you do have the correct version, Setup then checks if Microsoft Update is enabled. If it is not, the Use Microsoft Update dialog box appears, permitting you to enable it.
8. On the Quarantine Security Settings screen, select the desired setting.
* Secure Mode causes all messages and attachments delivered from Quarantine to be re-scanned for viruses and filter matches. This is the default.

* Compatibility Mode enables messages and attachments to be delivered from Quarantine without being scanned for filter matches. (Messages and attachments are always scanned for viruses.) Forefront Security for Exchange Server identifies these messages by placing special tag text in the subject line of all messages that are delivered from Quarantine.

Exchange_Forefront_Setup_7

9. On the Engine Updates Required screen, read the warning about engine updates.

Exchange_Forefront_Setup_8

10. If you use a proxy server for scanner updates, select Use Proxy Settings and enter the proxy name or IP address and its port on the Proxy Information screen. This ensures that your proxy server is correctly configured from the start. If you are doing a fresh install, you may enter the proxy information. If this is an upgrade, and proxy data is available in the registry, this screen does not appear and the existing data is preserved. Any changes to existing proxy information can be made in General Options.

If a username and password are required for the proxy server, they must be entered through General Options once FSE has been installed. This must be done immediately, otherwise engine updates will fail.

Exchange_Forefront_Setup_9

11. If the server you are installing to is an edge server you may be asked if you want FSE to enable Anti-Spam Updates. If you’ve never made any change to the Anti-Spam Updates setting on the Exchange Management Console (that is, the setting is in its default state), you are offered this choice. If you have made a change to that setting, you will not see it. If you do not enable Anti-Spam Updates during FSE installation, you can turn them on by clicking Enable Anti-spam Updates in the Action section of the Exchange Management Console.

If you enable Anti-Spam Updates during the installation and subsequently uninstall FSE, they will be disabled.

Exchange_Forefront_Setup_10

12. On the Choose Destination Location screen, either accept the default destination folder for the product, or click Browse to select a different one.

Default: Program Files(x86)\Microsoft Forefront Security\Exchange Server

Exchange_Forefront_Setup_11

13. On the Select Program Folder screen, choose a program folder for Forefront. At this point, Setup checks for running services.

Default program folder: Microsoft Forefront Server Security\Exchange Server

Exchange_Forefront_Setup_12

14. On the Start Copying Files screen, review the data presented to you. If any changes have to be made, use the Back button to navigate to the screen to be changed. Otherwise, click Next to begin the installation. A progress bar indicates that the files are being copied.

Exchange_Forefront_Setup_13

15. After installation is complete, you can start or restart the Exchange Transport Service, depending on whether it was stopped or running when the installation began. For a clean install, the service was probably still running and needs to be recycled. If you are reinstalling the product, the service had to be stopped before FSE could be uninstalled. If the service was running, the Restart Exchange Transport Service screen appears; if the service was stopped, the Start Exchange Transport Service screen appears. In either case, you can start the Transport service automatically so that Forefront Security for Exchange Server can become active. Click Next to have Setup perform this step or click Skip to manually perform this step at a later time. Until the service has been started or restarted, FSE cannot scan mail being sent or received.

Exchange_Forefront_Setup_13_Restart_TransportAgent

16. Depending on whether the Exchange Transport Service is being started or restarted (that is, you clicked Next on the prior screen), the Starting Exchange Transport Service screen or the Recycling Exchange Transport Service screen appears. Wait until the status changes to All services started, before clicking Next to continue.

Exchange_Forefront_Setup_14_Restarting_TransportAgent

Exchange_Forefront_Setup_15_All_Services_Restarted

17. If the Information Store Service was stopped when the install began, the Start Exchange Information Store screen appears. You can start the Information Store service automatically so that Forefront Security for Exchange Server can become active. Click Next to have Setup perform this step or click Skip to manually perform this step at a later time. Until the service has been started, FSE cannot scan mail on the Store. If the Information Store was running when the installation began, this screen does not appear.
18. If the Information Store Service is being started (that is, you clicked Next on the prior screen), the Starting Exchange Services screen appears. Wait until the status changes to All services started, before clicking Next to continue.
19. On the InstallShield Wizard Complete screen, you are advised to view the Readme file (recommended). If you opted to use Microsoft Update and you do not have the correct version of the Windows Update Agent, you are directed to a site to obtain it. Click Finish to complete the installation.

Exchange_Forefront_Setup_16_Installation_Complete

you’re done, installation is complete!

Antivirus scanning on Edge Transport or Hub Transport servers is done by a Forefront AV Agent that is an E12 Transport agent registered with the Edge Transport.exe and loaded by that process.
Antivirus scanning on the Mailbox server for Realtime and Background processing is done by an E12 compatible Forefront VSAPI.dll that is loaded by the Exchange Store.
The actual antivirus scanning of messages is performed by separate Forefront Realtime and Transport processes that provide message scanning isolation from the Exchange Transport and Store processes.

Links

Evaluate Microsoft Forefront Security for Exchange Server

Download Microsoft Forefront Client and Beta Software

Forefront Security for Exchange Server Cluster Installation Guide

Microsoft Forefront Server Security Blog

Information about the Forefront Server Technology Adoption Program (TAP) can be found by logging into http://connect.microsoft.com and selecting the Forefront TAP.

Starting position is: a Server with Microsoft Windows 2008 x64 Datacenter Edition (Installing it on a Standard and Enterprise Edition does not make a difference)..

First Step is, join a the Server to an existing Domain. Exchange Server Setup won’t let you install Exchange Server on a Machine which is not member of a domain.

Whenever you start Setup.exe run it elevated (Run as administrator)

Exchange_Setup_RunAsAdmin

Next step, install PowerShell. You can do this using the Exchange Server Setup or do it from a command prompt using ServerManagerCMD.

Installing_PowerShell_using_Exchange_Setup

or

Installing_PowerShell_using_ServerManagerCmd

ServerManagerCmd -i PowerShell

Now the system is ready for the Exchange Server Setup.

On Windows Server 2008 you need to install the Remote Server Administrations Tools, or at least parts of it.

ServerManagerCmd -i RSAT-ADDS

Consider =>

• To Install Exchange Server you must be a member of the ‘Schema Admins’ and ‘Enterprise Admins’ Groups

Exchange_Setup_Screen_1

Exchange_Setup_Screen_2

Exchange_Setup_Screen_3

Exchange_Setup_Screen_4

Exchange_Setup_Screen_5

Installations done!

Now let’s get started configuring Microsoft Exchange Server 2007!