Installing Exchange 2010 IT:Network:Applications

Microsoft Exchange 2010 Exchange Server 2010 is a messaging platform that provides , 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 servers 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

Supports Microsoft Outlook SMTP Webmail  OWA etc

Requirements ComponentRequirement Processor 64 bit architecture MemoryVaries 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 Disk space At least 1.2 GB on the drive on which you install Exchange 200 MB of available disk space on the system drive File formatDisk partitions formatted as NTFS file systems

Requirements Exchange versionExchange organization coexistence Exchange 2000 ServerNot supported Exchange Server 2003Supported Exchange 2007Supported Mixed Exchange 2007 and Exchange Server 2003 organization Supported

Requirements You can't upgrade an existing Exchange 2000 organization directly to Exchange 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.

Requirements ComponentRequirement Schema master The schema master must be running any of the following: 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.

Requirements 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.Windows Server Virtualization Validation Program

Requirements Virtualization (continued) The Exchange guest virtual machine: Is running Microsoft Exchange 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.

Installation 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.

Installation us/library/bb691354(EXCHG.140).aspx us/library/bb691354(EXCHG.140).aspx Microsoft Exchange Technet Center: us/exchange/default.aspx us/exchange/default.aspx Microsoft Exchange Resource Site:

Installation AD forest functional level is Windows Server 2003 (or higher) AD Schema Master is running Windows Server 2003 w/SP1 or later 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

Installation Install Microsoft Office Converter:Microsoft Filter Pack b5c6-cac34f4227cc&displaylang=en b5c6-cac34f4227cc&displaylang=en Done via PowerShell Server Manager.Net IIS  Web Services Remote Server Administration Tools (RSAT)

Installation 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: 1.Import-Module ServerManager 2.Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic- Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt- Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest- Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart For the Client Access Server role, you need to set the port sharing service: 1.Set-Service NetTcpPortSharing -StartupType Automatic Installation

Additional Exchange Role services can be found here(Ie, Unified Messaging, Edge Transport):

Installation 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

Installation 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:

Installation Complete installation can take up to 30 minutes depending on your deployment 38 minutes in a virtual machine with limited RAM

After installation completes, return to the setup screen and update the system Microsoft update will be installed Will automatically install updates for Exchange 2010 Update

Lots more Stay Tuned! More next week