Exchange 2010 at a glance
Microsoft Korea
CSS
Eun Sung Choi
Exchange 2010 System Requirements
•
Network and Directory Servers
Component
Requirement
Schema master
The latest 32-bit or 64-bit edition of the Windows Server 2003 Standard or Enterprise operating system
or the latest 32-bit or 64-bit edition of the Windows Server 2008 Standard or Enterprise operating system.
Global catalog server
In every Active Directory site where you plan to install Exchange 2010, you must have at least one global
catalog server that is either the latest 32-bit or 64-bit edition of Windows Server 2003 Standard or
Enterprise or the latest 32-bit or 64-bit edition of Windows Server 2008 Standard or Enterprise.
Active Directory Forest
Active Directory must be at least in Windows Server 2003 forest functionality mode.
•
After Exchange 2010 is installed, changing its role from a member
server to a directory server, or vice versa, isn't supported.
Exchange 2010 System Requirements
•
Operating System
Component
Requirement
Operating system on a computer that has a 64-bit processor
One of the following:

64-bit edition of Windows Server 2008 Standard Service Pack 2

64-bit edition of Windows Server 2008 Enterprise Service Pack
2
Operating system for installing the Exchange management tools
on a computer that has a 64-bit processor

64-bit edition of Windows Server 2008 Standard R2

64-bit edition of Windows Server 2008 Enterprise R2
One of the following:

Windows Vista with Service Pack 2 or later for management
tools only installation

Windows 7
Hardware Virtualization
Host:
•
Windows Server 2008 with Hyper-V technology
•
Windows Server 2008 R2 with Hyper-V technology
•
Microsoft Hyper-V Server 2008
•
Microsoft Hyper-V Server 2008 R2
•
Any third-party hypervisor that has been validated under the Windows
Server Virtualization Validation Program.
Hardware Virtualization
Guest:
•
Is running Microsoft Exchange 2010.
•
Is deployed on the Windows Server 2008 Service Pack 2 (SP2) or
Windows Server 2008 R2 operating system.
•
Does not have the Unified Messaging server role installed. All
Exchange 2010 server roles, except for the Unified Messaging role,
are supported in a virtualization environment.
•
Meets all of the requirements set forth above in this topic.
Hardware Virtualization
Disk
•
In a Hyper-V environment, each fixed VHD must be less than 2,040
gigabytes (GB). For supported third-party hypervisors, check with the
manufacturer to see if any disk size limitations exist.
•
Virtual disks that dynamically expand are not supported by Exchange.
•
Virtual disks that use differencing or delta mechanisms (such as
Hyper-V's differencing VHDs or snapshots) are not supported.
•
Exchange guest machine must use a fixed sized disk that has a
minimum size equal to 15 GB plus the size of the virtual Memory.
This requirement is necessary to account for the operating system and
paging file disk requirements.
Hardware Virtualization
Other
•
Only management software (antivirus software, backup software, virtual machine
management software, etc.) can be deployed on the physical root
machine. No other server-based applications (Exchange Server, SQL
Server, Active Directory, SAP, etc.) should be installed on the root machine.
•
Microsoft does not support combining Exchange high availability
solutions (namely, database availability groups (DAGs)) with
hypervisor-based clustering, high availability or migration solutions.
•
Virtual machine snapshots of an Exchange guest virtual machine is
not supported.
•
Exchange supports a virtual processor-to-logical processor ratio no
greater than 2:1.
Quad X 2 = 8, 16<= virtual processor
•
Exchange 2010 Prerequisites
•
Functional level of your forest is at least Windows Server 2003
•
Schema Master is running Windows Server 2003 with Service Pack 1
or later
•
Must be running the Enterprise Edition of Windows Server 2008 or
Windows Server 2008 R2 for DAG(Database Availability Group).
Windows Server 2008 SP2 prerequisites
•
Microsoft .NET Framework 3.5 Service Pack 1 (SP1).
•
Microsoft .NET Framework 3.5 Family Update for Windows Vista x64,
and Windows Server 2008 x64 updates.
•
Windows Remote Management (WinRM) 2.0 and Windows
PowerShell V2 (Windows6.0-KB968930.msu).
•
On servers that will host the Hub Transport or Mailbox server role,
install the Microsoft Filter Pack.
•
Typical installation of Client Access, Hub Transport, and the Mailbox
role:
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-Typical.xml -Restart
Windows Server 2008 R2 prerequisites
•
On servers that will host the Hub Transport or Mailbox server role,
install the Microsoft Filter Pack.
•
1 Import-Module ServerManager
•
Typical installation of Client Access, Hub Transport, and the Mailbox
role:
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,WebBasic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-LgcyMgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPIExt,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPCOver-HTTP-Proxy -Restart
•
`Set-Service NetTcpPortSharing -StartupType Automatic
New Rights-Protected E-Mail Functionality with
Active Directory RMS
•
Transport rules to apply AD RMS protection to messages based on
conditions.
•
Persistent protection of attachments in rights-protected messages.
•
Support for AD RMS templates.
•
An Internet confidential AD RMS template for protection over the
Internet.
•
AD RMS protection for Unified Messaging voice mail messages
New Transport and Routing Functionality
•
Cross-premises mail routing An organization can choose to
outsource some of their mailboxes to a hosted solution while
maintaining their on-premises deployment.
•
Enhanced disclaimers Exchange 2010 lets you add disclaimers
that can include hyperlinks, images, and HTML-formatted text. You
can also insert Active Directory attributes that are substituted for the
sender's attributes when a disclaimer rule is triggered.
•
Transport rules integration with AD RMS Exchange 2010 gives
you the ability to create rules that require AD RMS protection based
on keywords or patterns.
•
Moderated Transport Exchange 2010 provides an approval
workflow for sending messages to recipients. When you configure a
recipient for moderation, all messages sent to that recipient must go
through an approval process.
New Transport and Routing Functionality
•
Shadow redundancy Messages that are submitted to an Exchange
2010 Hub Transport server are stored in the transport database until
the next hop reports successful delivery of the message. If the next
hop doesn't report successful delivery and it fails, the message is
resubmitted for delivery.
•
Transport Dumpster truncation based on log copy status When
messages that are in the dumpster are replicated to all mailbox
databases, they're removed from the dumpster.
•
Latency SLA management Exchange 2010 Transport lets you
measure service levels delivered relative to your service level
agreement (SLA) goals. Exchange 2010 gives you the ability to
measure latencies for each hop, as well as end-to-end latency.
•
Transport database improvements Performance improvements in
the Transport database result in reduced database I/O per second
(IOPS) per message, which increases message throughput.
New Permissions Functionality
•
Role Based Access Control (RBAC) has replaced the permissions
model that was used in Exchange 2007.
•
For administrators and specialist users, management role groups
define what these users can manage in the organization.
•
The RBAC model in Exchange 2010 is flexible and provides you with
several ways to customize the default permissions
•
On Edge Transport servers, RBAC isn't used to control permissions.
•
The local Administrators group is used to control who can configure
Exchange features on the local server
New High Availability Functionality
•
Exchange 2010 integrates high availability into the core architecture of
Microsoft Exchange to enable customers of all sizes and in all
segments to be able to economically deploy a messaging continuity
service in their organization.
•
Exchange 2010 includes many changes to its core architecture. The
following features in Exchange 2007 and Exchange 2007 Service
Pack 1 (SP1) no longer exist in Exchange 2010:
−
−
Local continuous replication (LCR)
Single copy clusters (SCC)
•
The concept of a clustered mailbox server(CMS) no longer exists in
Exchange 2010.
•
Cluster continuous replication(CCR) and standby continuous
replication(SCR), have been merged and renamed as a set of new
features in Exchange 2010: incremental deployment, continuous
mailbox availability, database mobility, database copies, and
database availability groups.
New Messaging Policy and Compliance Features
•
Exchange 2010 compliance features make retention independent of
users' mailbox management and filing habits, and ensure retention
policies are applied continuously. The following is a list of new
messaging and compliance features that have been included in
Exchange 2010:
•
New interface for applying retention policies
•
Auto tagging for retention policies
•
Mailbox search features for cross-mailbox search with AQS support
•
New transport rules predicates and actions
•
Discovery
New Messaging Policy and Compliance Features
•
•
•
•
Discovery
Search mailbox content in selected mailboxes across the entire
Exchange 2010 organization. The scope of the RBAC role assignment
determines which mailboxes can be searched. Messages returned by
the search are copied to a folder in the specified Discovery mailbox.
Discovery allows legal and IT departments to easily comply with legal
discovery requirements, or search message content for purposes such
as internal investigations, and messaging policy compliance.
•
The new Discovery Management role can be assigned to a user or a
security group to perform Discovery-related tasks.
•
An easy-to-use browser-based interface accessible from the
Exchange Control Panel (ECP) allows non-technical professionals to
easily perform Discovery functions.
New Outlook Web App Features
•
Favorites in the Navigation Pane
•
Search folders
•
Message filtering
•
The ability to set categories in the message list
•
Options in the Web management interface for Outlook Web App
•
A side-by-side view for calendars
New Outlook Web App Features
•
Multi-client language support
•
The ability to attach messages to messages
•
Expanded right-click capabilities
•
Integration with Office Communicator, including presence, chat, and a
contact list
•
Conversation view
•
The ability to send and receive text (SMS) messages from Outlook
Web App
•
Outlook Web App mailbox policies
New Unified Messaging Features
Call answering rules
•
Users can create up to 9 call answering rules
•
Similar to the Exchange Server 2007 UM auto attendant (AA)
−
Leave a voice message for the UM-enabled user.
−
Transfer to an alternate contact of the UM-enabled user.
−
Transfer to an alternate contact's voice mail of the UM-enabled user.
−
Transfer to other phone numbers that the UM-enabled user has configured.
−
Use the Find-Me feature or locate the UM-enabled user via a supervised transfer.
New Unified Messaging Features
•
Additional language support including in Outlook Voice
Access
•
All UM language packs include the pre-recorded prompts, grammar files,
Text to Speech (TTS) translation and Automatic Speech Recognition (ASR).
•
Not all of the UM language packs contain support for Voice Mail Preview.
The following UM language packs will contain support for all of the
components and features including Voice Mail Preview:
−
−
−
−
−
−
English (US) - (en-US)
English (Canada) - (en-CA)
French (France) - (fr-FR)
Italian - (it-IT)
Polish - (pl-PL)
Portuguese (Portugal) - (pt-PT)
New Unified Messaging Features
Enhancements to name lookup from caller ID
•
In Exchange 2007,
−
−
−
−
•
Same dial plan as the user being called,
Using an Exchange Unified Messaging proxy address (EUM proxy address),
Personal contacts of the user receiving the call,
Using the msRTCSIP-Line attribute in Active Directory if Service Pack 1 (SP1) for
Exchange 2007 is installed and Exchange 2007 is integrated with Office
Communications Server 2007.
In Exchange 2010,
−
Exchange 2010 extended this by adding the ability to use eight (8) other Active
Directory attributes to resolve a caller ID to a name.
−
−
−
−
−
−
−
−
a.TelephoneNumber
b.HomePhone
c.Mobile
d.facsimileTelephoneNumber
e.OtherTelephone
f.OtherHomePhone
g.OtherMobile
h.OtherFacsimileTelephoneNumber
New Unified Messaging Features
•
Messaging Waiting Indicator
•
Message Waiting Indicator is a feature found in most legacy voice
mail systems and can refer to any mechanism that indicates the
existence of a new message.
•
In Exchange 2007, this functionality was provided by a third-party
application, which indicated receipt of a new voice mail by lighting the
lamp on the desk phone. (OC ?)
•
This feature has been added to Exchange 2010, and third-party
software is not needed. Enabling or disabling Message Waiting
Indicator is done on the user's mailbox or on a UM mailbox policy.
New Unified Messaging Features
•
Missed call and voice mail notifications using text messaging (SMS)
•
Protected voice mail
−
•
Protected by Microsoft Rights Management Services (RMS), and is restricted to
forwarding, copying, or extracting the voice file from mail
Incoming fax support
−
Customers who require a fax solution that works with Exchange 2010 will need to
deploy a fax partner solution that is available from several fax partners
•
Addressing to Groups (Personal Distribution Lists) and personal
contacts support
•
Built-in Unified Messaging administrative roles
−
−
−
−
UM Mailboxes
UM Prompts
Unified Messaging
UM Management
Web Management Interface
•
Text messaging (SMS) integration
•
Voice messaging integration
•
Mailbox Search
•
Additional proxy addresses for mailboxes
•
Moderation and approval for distribution list submission
New Exchange Store and Mailbox Database
Functionality
•
Storage groups are deprecated.
•
Mailbox databases are no longer connected to the server object.
•
Extensible Storage Engine (ESE) has many improvements for high
availability, performance, and database mobility.
•
The Exchange Store schema has been flattened.
−
•
Server to Organization
Enhanced reporting with Public Folders
−
Get-PublicFolderStatistics
New Mailbox and Recipient Functionality
•
Users can share information such as calendar free/busy and contacts
with users who reside in a different organization
•
Scheduling and configuring resource mailbox calendar processing has
been improved
•
You can now move a mailbox while the end user is still accessing it
•
New parameters have been added to the distribution group cmdlets to
allow users to create and manage their own distribution groups in
Outlook Web App and Outlook 2010
•
You can manage folder-level permissions for all folders within a user's
mailbox
•
Bulk recipient management has been expanded to allow you to bulk
manage recipient properties
•
You can send mail to recipients from the EMC
New Administration Functionality in the Exchange
Management Console
•
Customer Experience Improvement Program (CEIP)
•
Organizational Health
•
Community and Resources
•
Command logging
•
Property dialog command exposure
•
UI is RBAC aware
New Administration Functionality in the Exchange
Management Shell
•
Remote administration With the new Shell, you can connect to
remote Exchange 2010 servers across the network with only the
Windows Management Framework installed, which includes Windows
PowerShell.
•
RBAC integration The Shell works with RBAC to give you and your
users access only to the cmdlets and parameters they're allowed to
use. If your permissions don't allow you to configure a certain feature,
you aren't given access to the cmdlets, parameters, or both, that
manage that feature.
•
Administrator audit logging Actions that result in the modification
of Exchange organization configuration and other object properties in
the Exchange Management Console, the Web management interface,
and the Shell can now be logged for later review.
•
Improved multiple-valued property syntax Instead of running
multiple commands to add and remove values from a single property,
you can now add and remove values with a single command line.