Announcing Exchange 2010 Service Pack 3

The Exchange Team is pleased to announce that in the first half of calendar year 2013 we will be releasing Exchange Server 2010 Service Pack 3 (SP3) to our customers. With SP3, the following new features and capabilities will be included:

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We are communicating the required changes ahead of the release date in order to assist our customers with planning their upgrade path ahead of time.

We hope these announcements come as welcome news to you. It is our custom to provide ongoing improvements to features, functionality and security of Exchange Server, based largely on customer feedback, and to provide continual innovation on an already great messaging product. We look forward to receiving your comments and announcing more detailed information as we continue to develop the features that will be included in SP3.


Quick Install Exchange 2010

System Requirements

First, you need to make sure that your Active Directory (AD) environment and your Exchange server meet the minimum requirements:

  • AD forest functional level is Windows Server 2003 (or higher)   
  • AD Schema Master is running Windows Server 2003 w/SP1 or later   
  • Full installation of Windows Server 2008 w/SP2 or later OR Windows Server 2008 R2 for the Exchange server itself   
  • Exchange server is joined to the domain (except for the Edge Transport server role)


In this example we are going to install Exchange 2010 on a Windows Server 2008 R2 operating system.  Before installing Exchange we need to install some Windows components.  It’s important that you don’t miss anything here because the Exchange 2010 installer does not provide very good feedback if Server 2008 R2 is missing required components.

In Exchange management shell Run the following command: Import-Module ServerManager

For a typical install with the Client Access, Hub Transport, and Mailbox roles run the following command:

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

If your Exchange server will have the Client Access Server role set the Net.Tcp Port Sharing Service to start automatically

Open PowerShell via the icon on the task bar or Start >> All Programs >> Accessories >> Windows PowerShell >> Windows PowerShell.  Be sure that PowerShell opened with an account that has rights to modify service startup settings.

Run the following command: Set-Service NetTcpPortSharing -StartupType Automatic




Than just follow the setup, to finish instalation of exchange.

Forwarding Rules Not Working Outlook 2007/2010

Automatic forwarding and Remote Domains

Remote Domains define a bunch of settings, such as message formats, character sets, and OOFs for messages sent to specified domains outside your Exchange organization. The default Remote Domain setting for the address space * (the asterisk character) applies to all external domains except the ones for which you’ve created a Remote Domain for.

The Allow automatic forward setting for remote domains applies only to client-side forwarding using mechanisms like Inbox Rules. For instance, if a user creates a rule in Microsoft Outlook to automatically forward mail to an external email address, the default setting (for address space *) doesn’t allow it. To enable automatic client-side forwarding of mail to external addresses, select the Allow automatic forward checkbox in a remote domain’s properties.

Alternatively, you can do this from the Exchange Management Shell;

set-remotedomain -identity Default -AutoForwardEnabled $true

10 reasons to migrate to Exchange 2010


1: Continuous replication

International research shows that companies lose $10,000 an hour to email downtime. This version of Exchange enables continuous replication of data, which can minimise disruptions dramatically and spare organisations from such loss. Moreover, Microsoft reckons the costs of deploying Exchange 2010 can be recouped within six months thanks in part to the improvements in business continuity.

2: Virtualisation

Exchange 2010 supports virtualisation, allowing consolidation. Server virtualisation is not only a cost cutter, reducing expenditure related to maintenance, support staff, power, cooling, and space. It also improves business continuity — when a virtual machine is down, computers can run on another virtual machine with no downtime.

3: Cost savings on storage

Exchange 2010 has, according to Microsoft, 70% less disk I/O (input/output) than Exchange 2007. For this reason, the firm recommends moving away from SAN storage solutions and adopting less expensive direct attached storage. This translates to real and significant cost savings for most businesses.

4: Larger mailboxes

Coupling the ability to use larger, slower SATA (or SAS) disks with changes to the underlying mailbox database architecture means that far larger mailbox sizes will become the norm.

5: Voicemail transcription

Unified Messaging, first introduced with Exchange 2007, offers the concept of the “universal inbox,” where email and voice mail are available from a single location and consequently accessed from any of the following clients:

  • Outlook 2007 and later
  • Outlook Web App
  • Outlook Voice Access — access from any phone
  • Windows Mobile 6.5 or later devices

A new feature to Exchange 2010, Voicemail Preview, sees text-transcripts of voicemails being received, saving the time it takes to listen to the message. Upon reception of a voice message, the receiver can glance at the preview and decide whether it is an urgent matter. This and other improvements, such as managing voice and email from a single directory (using AD), offer organisations the opportunity to discard third-party voicemail solutions in favour of Exchange 2010.

6: Help desk cost reduction

Exchange 2010 offers potential to reduce help desk costs by enabling users to perform common tasks that would normally require a help desk call. Role-based Access control (RBAC) allows delegation based on job function which, coupled with the Web-based Exchange Control Panel (ECP), enables users to assume responsibility for distribution lists, update personal information held in AD, and track messages. This reduces the call volumes placed on the help desk, with obvious financial benefits.

7: High(er) Availability

Exchange 2010 builds upon the continuous replication technologies first introduced in Exchange 2007. The technology is far simpler to deploy than Exchange 2007, as the complexities of a cluster install are taken away from the administrator. It incorporates easily with existing mailbox servers and offers protection at the database — with Database Availability Groups – rather than the server level. By supporting automatic failover, this feature allows faster recovery times than previously.

8: Native archiving

A large hole in previous Exchange offerings was the lack of a native managed archive solution. This saw either the proliferation of unmanaged PSTs or the expense of deploying third-party solutions. With the advent of Exchange 2010 — and in particular the upcoming arrival of SP1 this year — a basic archiving suite is now available out-of-the-box.

9: Running on-premise or in the cloud

Exchange 2010 offers organisations the option to run Exchange on-premise or in the cloud. This approach even allows organisations to run some mailboxes in the cloud and some on locally held Exchange resources. This offers companies very competitive rates for mailbox provision from cloud providers for key mailboxes, whilst deciding how much control to relinquish by still hosting most mailboxes on local servers.

10: Easier calendar sharing

With Federation for Exchange 2010, employees can share calendars and distribution lists with external recipients more easily. The application allows them to schedule meetings with partners and customers as if they belonged to the same organisation. This might not appeal to every organisation, but those investing in collaboration technologies will see the value Exchange 2010 offers.


Exchange Server 2010 Service Pack 2 Announced

Exchange Server 2010 SP2 is due for release in the second half of this year and Microsoft has released some more detailed information on what to expect in this update.

With SP2, the following new features and capabilities will be included:

  • Outlook Web App (OWA) Mini: A browse-only version of OWA designed for low bandwidth and resolution devices. Based on the existing Exchange 2010 SP1 OWA infrastructure, this feature provides a simple text based interface to navigate the user’s mailbox and access to the global address list from a plurality of mobile devices.
  • Cross-Site Silent Redirection for Outlook Web App: With Service Pack 2, you will have the ability to enable silent redirection when CAS must redirect an OWA request to CAS infrastructure located in another Active Directory site.  Silent redirection can also provide a single sign-on experience when Forms-Based Authentication is used.
  • Hybrid Configuration Wizard: Organizations can choose to deploy a hybrid scenario where some mailboxes are on-premises and some are in Exchange Online with Microsoft Office 365. Hybrid deployments may be needed for migrations taking place over weeks, months or indefinite timeframes. This wizard helps simplify the configuration of Exchange sharing features, like: calendar and free/busy sharing, secure mailflow, mailbox moves, as well as online archive.
  • Address Book Policies: Allows organizations to segment their address books into smaller scoped subsets of users providing a more refined user experience than the previous manual configuration approach. We also blogged about this new feature recently in GAL Segmentation, Exchange Server 2010 and Address Book Policies.
  • Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 2 will also be contained within SP2. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

One thing to note is that SP2 will require an Active Directory schema update.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We’ve heard the feedback loud and clear from our customers on multiple occasions regarding delays that can be caused to deployment as a result of needing to update your schema and as such with the release of Exchange 2010 SP2 are communicating the required changes ahead of release in order to assist our customers with planning their upgrade path ahead of time.

Exchange 2007 Enterprise SP1 IMAP service, load is 100%

If you have problem, that your IMAP service on Exchange 2007 sp1
is taking 100% of your CPU’s, you must check it up how many items your users have in their folders/inbox.

The problem is, when user click on folder which have a large numbers of items in folder such as 300.000 and more, and then run some filtering or rule-ing in that folder.

In our organization service load 100% CPU on our quad-core maschine, and you must restart the imap4.exe service.

I now, that Microsoft recommends max. items per folder to max. 20,000 with Exchange 2007 server, but maybe you will have this problem sometime.

If you want to check how many items have some users, you can simply open the exchange management shell (Powershell) and type;

Get-Mailbox | Get-MailboxFolderStatistics | Where {$_.ItemsInFolder -gt 20000} | fl identity, itemsinfolder

This will prompt any user in your org, that have more than 20.000 items in any folder, trash, inbox,…

You will get something like that;

Identity : yourdomain.local/Users/Sales/Franz Kafka\Inbox

ItemsInFolder : 35851

Identity : yourdomain.local/Users/Sales/John Derre\Trash

ItemsInFolder : 50851

and so on…

This affect only IMAP users not MAPI based clients (Outlook).

More than 40.000 – 50.000 items is problem in our exchange organization.(IMAP users!)

You can limit this by some policy of folders,…

Also exmon is very good tool for exchange mailbox server role;

With exmon you can check in real time witch user is getting a lot of % cpu and then check his mailbox.