I just took Microsoft Online Clinic 6900- Introudction to Exchange Server 2010.
Here is the summary of from the clinic, these are rough notes as I was taking it. This one is from Part 1 – Introduction to Exchange 2010 Overview.
some of the new features introudced in Exchange 2010
Gives you ability to Deploy Services Incremntally (looking for clarification)
Role based Access Control (RBAC)
Self Service Support for end users
Improved Database Engine – Defragmentation Manager
Dicover Feature – Allows to search multiple mailboxes for contents
Archiving and Retention Rules
Improved unified messaging – preview of voicemail outlook, SMS capabilites when a message is missed etc.
Improved Automated Tools
Enhanced archiving and monitoring
Enahnced Caller ID support
Text translation of voicemail in various langugages
Federated Sharing (Allows an organization to share calanders to third parties)
Need for Windows Clustering for Exchange 2010 Database High Availibilty
Redundant Mailbox servers are created such that it makes Clustering services invisible to the Administrator
Migration to Exchange 2010 seems easy except that as I was expecting that there will be in place upgrade from exchange 2007 to Exchange 2010 – YOU CAN’T DO THAT Below are some of the things which will need to be in place to do Side by side/swing migration.
Exchange 2003 SP2/Exchange 2007 SP2 or higher enviroments can be
Upgraded Migrated since you CAN’T do inplace upgrade to Exchange 2010, forest containing exchange 5.5 or exchange 2000 can not be upgraded directly to exchange 2010,
Co-Existance with Exchange 2003 SP2 or Exchange 2007 SP2 and above Only
Just like previous versions of exchange it needs updated AD Schema
Active Directory Should be in Windows 2003 Forest Functionality mode
Needs At least one Windows 2003 SP2 GC in each site where Exchange Server will be installed
Does NOT support RODC or ROGC
DOES NOT Windows 2008 Active Directory
Does NOT support in-place upgrade from Exchange 2003 (understandable) or Exchange 2007 (WHY)
Exchange 2010 servers CAN NOT be used as front end for Exchange server 2003
For Exchange 2003 and Exchange 2007 move to Exchange 2010 will need to be performed as a side by side deployment or swing migration, Exchange 2010 surprisingly DOES NOT Support in place upgrade from Exchange 2007.
Exchange 2010 can be deployed in separate AD Forest – Exchange Resource Forest – to separate Administration of Exchange from AD
Supports more clients than prior versions
some services are Tailored for Hosting partner – I will try to get more details on it.
Need accounts with Schema Admin, Enterprise Admin, domain admins just like prior versions
Extend Schmea – setup /prepareschema
Prepare AD – setup /preparead /organizationName:XYZ (CAN’T BE CHANGED)
Prepare Domain -setup /preparedomain
Start the Setup Wizard – Setup wizard checks for following pre-reqs if they are installed it is grayed out.
Dot net 3.5
Windows Remote Management
Localized Langugage For install and Admin
Typical – HT, CAS, MB and Exchange Managment Server
Custome – HT/CAS/MB/UM/ET/EMC
Answer do you have any client computers running outlook 2003 and eariler or Entourage in your organization? if yes the setup creates Public Folders
It runs Readiness Check
Finishes the installation
EMC is similar to Exchange 2007
Guidelines for Optimizing Exchange Server 2010
Exch2k10 can not be installed on a forest that has Exchange 5.5 or 2000 servers. Exchange 2003 or Exchange 2007 needs to be at SP2 or higher
Ensure that Hub Transport role is installed for sending and receiving emails :).
Deploy Mulitple Hub Transport servers per site.
Consider deploying multip,e CAS in each site.
Filed under Uncategorized