What are the server hardware requirements that organizations need to be aware of when planning their Exchange Server 2010 migration project.
In this tutorial two methods of moving public folder replicas from Exchange Server 2003 to Exchange Server 2010 are demonstrated.
Exchange Server 2010 treats some object attributes differently than Exchange Server 2003. The most common issue that this causes is invalid aliases on mailbox users.
During the co-existence period of a transition from Exchange Server 2003 to Exchange Server 2010 you may encounter an issue with the legacy Outlook Web Access URL redirection.
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.
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
Amusing bug in the elapsed time reported on very long mailbox move operations in the Exchange 2007 Mailbox Move wizard.
When planning a mailbox migration to Exchange Server 2007 you should consider the amount of transaction logging that will be generated by the move. In low risk environments circular logging can be used to avoid disk space problems caused by the volume of transaction logs generated during bulk mailbox moves. You can query the current […]
