Installing Exchange Understanding the Exchange …

1 CHAPTER 7 Installing ExchangeServer 2010IN THIS the ExchangeServer 2010 Server thePrerequisites for ExchangeServer High Availabilityand Site Resilience inExchange Server Server 2010 Hardware the ActiveDirectory Requirements forExchange Server Role BasedAccess Your Exchange Server2010 Active Directory Your Environment forExchange Server Exchange Server the DeploymentInstalling an Exchange Server is like taking a hike throughthe woods. If you have a map and can accurately follow thedirections, you can quickly and safely arrive at your destina-tion. If you get lost in the process (or try to wing it ) youmay or may NOT reach your destination, but even if youdo, it is likely that you will take a lot longer and travel overmore challenging those who have worked with Exchange Server 2007 inthe past, the Exchange Server 2010 Installation Wizard willseem very familiar. The Wizard walks the administratorthrough the installation of several of the prerequisites andallows for the selection of specific server roles for deploy-ment.

2 However, the installation wizard does notcover alltwists and turns. There are steps that must be taken toprepare the Active Directory environment and steps thatmust be taken to prepare the underlying operating systemon the server you are Installing chapter will focus on the installation process for a newMicrosoft Exchange Server 2010 server in a typical configu-ration. In addition, this chapter assumes that the support-ing infrastructure and server operating system do not existand includes step-by-step instructions on how to installWindows Server 2008, Active Directory, supporting configu-ration settings, and the Exchange Server 2010 prerequisitesfrom 9/18/09 8:56 AM Page 169170 CHAPTER 7 Installing Exchange Server 2010 Understanding the Exchange Server 2010 Server RolesAs with Exchange Server 2007, Exchange Server 2010 has various roles that can beinstalled on the server to perform specific functions. There are five major server roles,most of which are modular and can reside on a single server (for small environments) orbe distributed to multiple servers throughout an roles are as follows.

3 Edge Transport server Access server Transport server server Messaging server roleEdge Transport Server Role Establishing Perimeter SecurityThe Edge Transport server role provides antivirus and antispam message protection for theExchange Server infrastructure. Edge Transport servers act as message hygiene gatewaysand are designed to reside in a perimeter network or demilitarized zone (DMZ). Thisallows them to block harmful traffic beforeit reaches the corporate Transport servers are often utilized as the SMTP gateway for sending and receivingmail to and from the more information on the Edge Transport server role and details on how to install andconfigure the role, review Chapter 8, Implementing Edge Services for an Exchange Server2010 Environment. Client Access Server Role Providing User ConnectivityAs its name suggests, a client access server is responsible for providing connectivitybetween the user community and their data. Like the front-end servers found in ExchangeServer 2003, client access servers manage connectivity via Outlook Web Access andActiveSync, and like the client access servers in Exchange Server 2007, they also manageconnectivity from POP and IMAP Exchange Server 2010, however, the client access servers also manage MAPI (such asOutlook) client connectivity.

4 In a pure Exchange Server 2010 environment, clients neverhave to connect directly to their mailbox servers all connectivity is to the client taking responsibility for managing these additional connections, client access serversallow Mailbox servers to focus on their primary role processing messaging 9/18/09 8:56 AM Page 170171 Understanding the Prerequisites for Exchange Server 2010 For more information on the Client Access server role and details on how to install andconfigure the role, review Chapter 17, Implementing Client Access and Hub TransportServers. Hub Transport Servers Routing the MailThe Hub Transport server role is responsible for moving mail between Exchange Mailboxservers, similar to how bridgehead servers worked in the past. This role can be configuredon a dedicated server or it can be deployed on an existing mailbox Hub Transport server must be deployed in each Active Directory site that contains anExchange Server 2010 Mailbox server, as all message routing in other sites goes throughone or more Hub Transport if the sender and recipient are on the same Mailbox server, the message will routethrough a local Hub Transport server.

5 This ensures that all messages are subject to anytransport rules that may be configured for the more information on the Hub Transport server role and details on how to install andconfigure the role, review Chapter Messaging Servers Combining All the DataThe Unified Messaging server role was introduced with Exchange Server 2007. It acts as agateway for combining email, voice, and fax data into a single mailbox. All this data canbe accessed via the mailbox or a more information on the Unified Messaging server and detailed steps on installingand configuring the role, refer to Chapter 24, Designing and Configuring UnifiedMessaging in Exchange Server 2010. Mailbox Servers What It s All AboutThe Mailbox server role is the core role within Exchange Server 2010. Without mailboxservers to store the user data, all of the other server roles would be without Mailbox servers host mailboxes and mail enabled objects such as contacts and distrib-ution the Prerequisites for ExchangeServer 2010 Before Installing Exchange Server 2010, the administrator should become familiar with theprerequisites for each of the server roles.

6 This section covers the prerequisites for theimplementation of Exchange Server 2010 in a windows networking 9/18/09 8:56 AM Page 171172 CHAPTER 7 Installing Exchange Server 2010 Active Directory InfrastructureExchange Server 2010 relies on an Active Directory infrastructure to do its job. AD Sitesand Services, DNS, Global Catalog Servers, Domain Controllers all must be in place andconfigured properly for Exchange Server to function importance of each of these services, and the steps to deploy them, will be explainedin greater detail later in the Server 2008 64-Bit All the WayFrom inception through Exchange Server 2003, Exchange Server was always a 32-bit appli-cation. While this technology was able to handle the needs of organizations in the past,organizations today have more demanding messaging a world with ever-increasing message traffic, the need for highly available systems thatallow access from multiple client technologies, through the Internet, and through contin-uous synchronization with wireless devices resulted in the desire for increased productiv-ity through increased address these growing needs, Microsoft released a 64-bit version of their ExchangeServer 2007 server for production environments.

7 While they still produced a 32-bit versionof the product, it was intended primarily for non-production Exchange Server 2010, 32-bit support has gone away, and the product is only beingreleased in a 64-bit utilizing 64-bit architecture, Exchange Server has significantly enhanced processor andmemory utilization. This ensures higher performance gains, the ability to handle an ever-increasing volume of messages, the capability of supporting more users per server, andmore simultaneously connected mail clients. This last item is critical as more and moreorganizations take advantage of the capabilities of Outlook Web App (OWA) Exchange Server 2010 application can only be installed on a 64-bit edition of theWindows Server 2008 Service Pack 2 (or later) operating system. Either the standard orenterprise edition of windows Server can be utilized; however, if you plan on takingadvantage of some of the more advanced features of Exchange Server 2010 (such as data-base availability groups and mailbox database copies) you must use the Enterprise Exchange Server 2010 management tools can be installed on a 64-bit edition ofthe windows Server 2008 Service Pack 2 (or later) operating system, or on theWindows Vista Service Pack 2 (or later) operating 9/18/09 8:56 AM Page 172173 Understanding the Prerequisites for Exchange Server 2010 Microsoft.

8 NET Framework Microsoft .NET Framework is a Microsoft windows component that allows the abilityto build, deploy, and run Web Services and other applications. The .NET framework is akey offering from Microsoft, and most new applications created for the windows platformrely on it in one way or Framework builds on the features added in previous releases and includes servicepacks for both .NET Framework and .NET Framework Additionally, there are anumber of new features which have been Server 2008 ships with .NET Framework already installed. However, Exchange Server 2010 requires .NET Framework or above. When applying updates tothe windows Server 2008 server, if you elect to apply all updates the latest version of .NETF ramework will be installed. If you elect to selectively install updates, make sureyou installthis Remote Management Exchange Management Shell is a command line interface that enables you to manageyour Microsoft Exchange organization without having to rely on a GUI windows Remote Management (WinRM) is the transport mechanism that enablesyour local version of windows powershell to connect to remote Exchange servers,whether that server is in the next rack or across the country.

9 Utilizing WinRM , admin-istrators can manage servers, devices, and applications throughout their organization froma single management Remote Management can be downloaded and installed from the Internet,and instructions on how to do so are included later in this powershell V2 Administrators who are familiar with Exchange Server 2007 have most likely had someexperience with windows powershell . For many, the implementation of PowerShelladdressed one of the most glaring shortcomings of older windows installations the lackof a usable command line interface for performing administrative is an extensible command-line shell and scripting language from Microsoftthat integrates with the .NET Framework to allow administrators to perform just aboutany task in an Exchange environment from a command line. From simple to complex,scripts can be written using the powershell scripting language to save administrators fromtime consuming and repetitive some have found the powershell scripting language to be difficult to learn andchallenging to implement, few who have seen the results of this product being put intoaction can complain about the 9/18/09 8:56 AM Page 173174 CHAPTER 7 Installing Exchange Server 2010 windows powershell V2 introduces several new features to powershell that extend itscapabilities including.

10 powershell Remoting Allows scripts and cmdlets to be executed on a remotemachine, or several remote powershell Integrated Scripting Environment (ISE) GUI-basedPowerShell host that provides an integrated debugger, syntax highlighting, tabcompletion, and up to eight powershell Debugging Allows breakpoints to be set in a powershell script or Allows listening, forwarding, and acting on management and powershell V2 can be downloaded and installed from the Internet, and instruc-tions on how to do so are included later in this Management Console Microsoft Management Console (MMC) was originally released back in 1996 with theWindows NT Option Pack. This was the first time Microsoft released a consistent andintegrated management tool that aimed at standardizing the way administrators conductedadministrative and operational tasks on Microsoft software. Since 1996, Microsoft has beenupdating and improving its management console and releasing new Exchange Server 2010 Management Console utilizes MMC , but as windows Server2008 ships with the product already installed, it is not listed as a prerequisite and you donot have to install it Information Services (IIS) Information Services (IIS) remains a critical component that allows users toconnect to Exchange services over the Internet using Outlook Web App (OWA), OutlookMobile Access (OMA) and with the MMC above, IIS is installed by default with windows Server High Availability and Site Resiliencein Exchange Server 2010In Exchange Server 2007, Microsoft introduced new technologies that allowed organiza-tions to deploy their Exchange environments with improved availability.