Lecture 8 Exchange and Web mail

Installing Exchange 2010
Microsoft Exchange 2010
• Exchange Server 2010 is a messaging platform that provides
email, scheduling, and tools for custom collaboration and
messaging-service applications.
• 5th major release
• Top Features include:
• Improved message transport rules
• Continuously replicating databases and failover to other databases, not
• MAPI clients now can communicate with Client Access Server (CAS)
• New Anti-Spam features
• Quota improvements
• PowerShell “stuff” using Exchange Management Shell (EMS)
• Unified messaging integration improvements with Lync 2010 and VOIP
• Outlook Web App is way cooler
Exchange 2010
• Exchange Management Console
Exchange 2010
Exchange 2010
• Supports
• Microsoft Outlook
• WebmailOWA
• etc
•64 bit architecture
Varies depending on Exchange features that are installed
Paging file size
The page file size minimum and maximum must be set to physical
RAM plus 10 MB
•At least 1.2 GB on the drive on which you install Exchange
Disk space
•200 MB of available disk space on the system drive
File format
Disk partitions formatted as NTFS file systems
Exchange version
Exchange organization coexistence
Exchange 2000 Server
Not supported
Exchange Server 2003
Exchange 2007
Mixed Exchange 2007 and
Exchange Server 2003 organization
• You can't upgrade an existing Exchange 2000 organization
directly to Exchange 2010.
• You must first upgrade the Exchange 2000 organization to
either an Exchange 2003 or Exchange 2007 organization, and
then you can upgrade the Exchange 2003 or Exchange 2007
organization to Exchange 2010.
Schema master
The schema master must be running any of the
•Windows Server 2003 SP1
•Windows Server 2008
•Windows Server 2008 R2 Standard or Enterprise
Global catalog server
In each Active Directory site where you plan to
install Exchange 2010, you must have at least one
global catalog server.
Domain controller
In each Active Directory site where you plan to
install Exchange 2010, you must have at least one
writeable domain controller.
Active Directory forest
Active Directory must be at Windows Server 2003
forest functionality mode or higher.
• Virtualization
• Microsoft supports Exchange 2010 in production on hardware
virtualization software only when all the following conditions
are true:
• The hardware virtualization software is running:
• 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.
• Virtualization (continued)
• The Exchange guest virtual machine:
• Is running Microsoft Exchange 2010.
• Is deployed on the Windows Server 2008 with SP2 or
Windows Server 2008 R2 operating system.
• Doesn't have the Unified Messaging server role installed. All
Exchange 2010 server roles, except for the Unified Messaging server
role, are supported in a virtualization environment. This is due to the
real-time response requirements associated with voice
communications with the Unified Messaging server role.
• Preparing Active Directory
• Before you install Microsoft Exchange Server 2010 on any
servers in your organization, you must prepare
Active Directory and domains
• If you run the Exchange 2010 Setup wizard with an account that
has the permissions required (Schema Admins, Domain Admins,
and Enterprise Admins) to prepare Active Directory and the
domain, the wizard will automatically prepare Active Directory
and the domain.
• http://technet.microsoft.com/enus/library/bb691354(EXCHG.140).aspx
• http://technet.microsoft.com/en-us/library/bb124778.aspx
• Microsoft Exchange Technet Center:
• http://technet.microsoft.com/enus/exchange/default.aspx
• Microsoft Exchange Resource Site:
• http://www.msexchange.org/
• AD forest functional level is Windows Server 2003 (or
• AD Schema Master is running Windows Server 2003 w/SP1 or
• Full installation of Windows Server 2008 w/SP2 or later OR
Windows Server 2008 R2 for the Exchange server itself
• Target Exchange server is joined to the domain
• Install Microsoft Office Converter:Microsoft Filter Pack
• http://www.microsoft.com/downloads/en/details.aspx?FamilyID=60c92a37-719c-4077b5c6-cac34f4227cc&displaylang=en
• Done via PowerShell
• Server Manager
• .Net
• IISWeb Services
• Remote Server Administration Tools (RSAT)
• These components are for a typical installation of Exchange:
• Client Access
• Hub Transport
• Mailbox Roles
• Minimum required for a single Exchange server installation
PowerShell Commands:
Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-BasicAuth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-MgmtConsole,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-DigestAuth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
For the Client Access Server role, you need to set the port sharing
Set-Service NetTcpPortSharing -StartupType Automatic
• Additional Exchange Role services can be found here(Ie,
Unified Messaging, Edge Transport):
• http://technet.microsoft.com/en-us/library/bb691354.aspx#WS08R2
• Prep work is finished for a “typical” installation
• ALWAYS Log onto your target Exchange server as the
Domain Administrator
• Run setup from the installation media
• Option to select are:
• Install only language from media
• Start installation
• Turn on error reporting
• Leave default name for organization
• Determine client settings (Outlook 2003 or no?)
External domain name: http://mail.mydomain.com
Complete installation can
take up to 30 minutes
depending on your
• 38 minutes in a virtual
machine with limited
• After installation completes, return to the setup screen and
update the system
• Microsoft update will be installed
• Will automatically install updates for Exchange 2010
Lots more
• Stay Tuned!
• More next week

similar documents