RBAC Roles Control Different Aspects of Tenant Management
One of the first things my customers notice when I demonstrate Exchange Server 2010 management to them is that mailboxes are no longer created or managed in the Active Directory Users & Computers console.
Learn which editions of Exchange Server 2010 are required for the different server roles and high availability features.
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.
This tutorial demonstrates how to use a text file with a list of mailbox names as the input for an Exchange Server 2007 or 2010 mailbox migration using PowerShell.
For an Exchange administrator there are a lot of different situations in which they may need to know how many mailboxes are in the organization. Fortunately this is made easy in Exchange Server 2010 with a few simple PowerShell commands.
Microsoft has released this video from MCM instructor Brian Reid about the header firewall, part of the Exchange Transport architecture that is covered in the Microsoft Certified Master program in depth.
As IT professionals we perhaps hold a slight advantage over the average person when it comes to being prepared for a disaster. A lot of you deal with disaster planning and readiness on a daily basis in your jobs. Those same skills can, and should be put to use for your own personal life as well.
In Exchange Server 2003 the last logon time for a mailbox was visible in the Exchange System Manager. For Exchange Server 2007 and 2010 the last logon time was removed from the Exchange Management Console, and so we need to use a differnet method to find this information.
Mailbox moves in previous versions of Exchange were interactive in nature, in that a wizard, script or shell command was used to move the mailbox and it occured in real time. In Exchange Server 2010 mailbox moves are now handled using move requests.
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.
