Exchange 2010

Exchange Server 2010 Prerequisites on Windows Server 2008 R2

In order to install Exchange server 2010 with Client Access, Hub Transport, and Mailbox server roles:
1- Servers that will host the Hub Transport or Mailbox server roles require the Microsoft Filter Pack which can be downloaded here:

2- After installing the Filter Pack run the ” Import-Module ServerManager “ command from Windows PowerShell console.

3- Run the following command from Windows Power Shell:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

4- After the restart run ” Set-Service NetTcpPortSharing -StartupType Automatic “ command from Windows PowerShell console.

5- After installing Exchange Server 2010 prerequisites, run Microsoft Update to verify the latest updates are applied to the server before continuing with the Exchange Server 2010 installation.

Exchange 2010 – 1 Week to production

For several weeks / days I have been actively working on migrating our internal Exchange 2007 infrastructure to Exchange 2010.  In my lab setup I can say that Exchange 2010 is an awesome continuation in Microsoft flagship email product..

I will be documenting several of the things I’ve discovered about the process  and share with you all.  So please stop back or subscribe to my RSS for updates.

MapiException: TooManyMountedDatabases when mounting database

I was hit with a nice error when attempting to mount several Exchange databases on my new Exchange 2010 SP2 server that I had setup in a lab envionment for production testing.

The error:

——————————————————–Microsoft Exchange Error——————————————————–
Failed to mount database ‘IJ’.IJFailedError:Couldn’t mount the database that you specified. Specified database: IJ; Error code: An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Database: IJ, Server: EXCHANGE.JERMSMIT.LOCAL].An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Database: IJ, Server: EXCHANGE.JERMSMIT.LOCAL]An Active Manager operation failed. Error Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Server: EXCHANGE.JERMSMIT.LOCAL]MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954)

The cause of this issue is because Unlicensed (trial) of Exchange 2010 servers are limited to 5 databases. In the Application event log I noticed the following message:

Event ID: 9591 – Exceeded the max number of 5 MDBs on this server.

It seems I have exceeded the number of databases that can be mounted during my trail. I will now apply a MSDN license and see how things work out.




Outlook rules not working after Exchange 2010 migration

Last night I moved my email account from Exchange 2007 to Exchange 2010.  All went well with the move and email flowing as expected.   Outside of the issue of me not having email sent to my phone or the ability to check webmail all else was fine. I decided that I had reached the end of my testing, so I moved my account back to Exchange 2007.  Again I moved my mailbox without any issue that I could recognize, until I noticed that my outlook rules were no longer working.

I attempted to recreate the rules from outlook and owa in both cases this did not work.  I am now off to searching Google for answers.  I’ll let you know if I find something…

– Took some time to go searching –

It looks like this is a known issues int he technet forums.  One of the MSFT’s indicated a plan for a permanent fix for this in the next Exchange 2007 SP3 RU7.  There wasn’t a specified release data given.  I don’t think I can wait that long.  I may take the export current mailbox to PST and delete mailbox, create new mailbox and import PST method.  This seems to have worked for users who have done so.

– Took some time to go searching  (again) –

I think I have a solution for this.  I attempted to remove all my rules from OWA (outlook web access) and that wasn’t working.  Later on I found out (via a forum post) that junk email filter is for the most part a rule like that of email rules.   I disabled this and saved, deleted all my rules and recreated them.  Now my rules work once more w/o the need of a RU update or deletion of my mailbox.

Here are some useful steps

Log into webmail (Outlook Web Access)
Delete rules
Disable junk email filtering and save the changes.

This should fix it.  You can then enable junk email filtering if needed


Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

Aparently, this normally happens when you disable IPv6 in Local Area Connection.
This is due to the behavior of IPv6 in Windows Server 2008, when you disable IPv6 in Local Area Connection on Windows 2008 server.

The following error was generated when: “$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”

After doing lot of troubleshooting and searching on the net, found that this is happening due to IPV6, and installation needs IPv6 to be disabled in your local area connection on the system. After disabling my setup went smoothly, follow the below instructions to disable IPv6 from your system.
To completely disable IPv6 on a Windows Server 2008-based system, follow these steps:
1. Open Registry Editor.
2. Locate the following registry subkey:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters
3. In the details pane, click New, and then click DWORD (32-bit) Value.
4. Type DisabledComponents, and then press ENTER.
5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.