The Exchange Profile Analyzer is used to collect statistical information about the Exchange organization that is helpful for understanding the size and makeup of the Exchange data that is to be migrated. When migrating from Exchange Server 2003 to Exchange Server 2010 this information is invaluable and should always be collected during the planning phase of the project.
When Exchange Server 2010 was released some customers assumed that the similarities between Exchange Server 2007 and Exchange Server 2010 would allow in-place upgrades to occur. Microsoft has released a video to explain why this is not the case.
How to enable and configure Outlook Anywhere for Exchange Server 2010 so that remote users can securely connect to the Exchange server.
Exchange Server 2010 includes a useful new feature that can automatically load balance the provisioning of new mailboxes across multiple mailbox databases.
After an outage or maintenance to the Mailbox servers in a Database Availability Group you may find that the mailbox databases are no longer balanced across all of the DAG members.
An Exchange Server 2010 administrator may want to find out if any of the mailbox databases in the organization have been configured for circular logging. In this tutorial I'll demonstrate how to find the mailbox database and how to reconfigure them all using the Exchange Management Shell.
n Exchange Server 2010 the Exchange Management Console doesn't provide a way to visually locate mailboxes that have no storage quota, or mailboxes that have a non-standard storage quota configured. However you can find mailbox storage quota settings quickly using the Exchange Management Shell.
In this tutorial we'll explore the purpose of a Room Mailbox in Exchange Server 2010, how to create a Room Mailbox, and look at different ways to configure a Room Mailbox to suit different scenarios.
Exchange Server 2010 has many environmental pre-requisites that must be met before a successful deployment can be performed. To prepare for Exchange Server 2010 deployment a useful tool to use is the Exchange Pre-Deployment Analyzer
Microsoft Exchange Server 2010 introduced a new high availability feature called the Database Availability Group (DAG). This tutorial describes how Database Availability Groups work in Exchange Server 2010, as well as demonstrating the steps for deploying a DAG using Exchange Server 2010 SP1 and Windows Server 2008 R2.
Exchange Server 2010 SP1 client throttling policies can cause calendar synchronization problems for Blackberry users.
When an Exchange Server 2010 Database Availability Group has been upgraded to Exchange 2010 SP1 you may encounter an error when adding or removing database copies on a DAG member.
