In this tutorial you will learn how to plan a backup strategy for your Exchange 2010 Client Access servers, and how to use different methods to backup and restore the Client Access server role in Exchange Server 2010.
Microsoft has released Exchange Server 2010 Service Pack 1. Organizations already running Exchange Server 2010 (RTM) can upgrade to Service Pack 1, however the upgrade must be planned out properly to ensure a successful outcome.
When Exchange Server 2010 was released a lot was made of the decision by Microsoft to remove Single Instance Storage (SIS) from the Exchange database engine. What does this really mean for Exchange Server 2010 storage?
When you attempt to remove or reinstall an Exchange Server 2010 server role you may encounter error 1638 and a message that another version of this product is already installed.
In this video I demonstrate the end user experience during different failure scenarios in a highly available Exchange Server 2010 environment.
In an Exchange Server 2010 environment Outlook 2003 users may receive an error message when they attempt to connect to an Exchange 2010 Mailbox server.
When you are deploying Exchange Server 2010 in an environment in which Outlook 2003 is still in use there are some steps to be aware of.
Outlook Web App is hosted on the Client Access Server role for Exchange Server 2010 and integrated with IIS 7. The OWA virtual directory can be secured using different authentication settings depending on the network environment.
This tutorial demonstrates how to update a Client Access Server array without causing the entire array to go offline at once.
This tutorial will demonstrate the steps for deploying Exchange Server 2010 as a Client Access Server array using Windows Network Load Balancing.
An error may occur when establishing an NLB cluster using Hyper-V guest machines.
There is a change in behaviour between Commvault version 7 and version 8 in the way that the Public Folder iData Agent handles public folders, which can lead to some undesirable outcomes.
