InstallGuide 2010 CAS

  • View
    215

  • Download
    0

Embed Size (px)

Text of InstallGuide 2010 CAS

  • 7/31/2019 InstallGuide 2010 CAS

    1/25

    Contents

    Installation Guide Template - Client Access Server ...................................................... ..... .............. . 2

  • 7/31/2019 InstallGuide 2010 CAS

    2/25

    Installation Guide Template - Client Access

    ServerThis topic provides you with an installation guide template that you can use as a starting point for

    formally documenting your organization's server build procedures for Microsoft Exchange Server

    2010 servers that will have the Client Access server role installed.

    The template includes the following key sections:

    Executive Summary

    Server Configuration

    Load Balancing Configuration

    Verification Steps

    Exchange Server Role Installation

    Exchange Server Role Configuration

    For purposes of providing an example, the template uses the fictitious company name of Contoso.

    Also, you can download this template, along with templates for other server roles, as a download

    package in .zip file format at Microsoft Exchange Server 2010 Install Guide Templates

    (http://go.microsoft.com/fwlink/?LinkID=187961).

    Executive SummaryThe purpose of this document is to explain the installation and configurations necessary to install

    the Exchange 2010 Client Access server role on the Windows Server 2008 platform.

    Business Justification

    By having an installation guide, Contoso will be able to ensure standardization across the

    enterprise, reducing total cost of ownership (TCO), and easing troubleshooting steps.

    Scope

    The scope of this document is limited to installation of an Exchange 2010 Client Access server for

    Contoso on the x64 version of the Windows Server 2008 (SP2 or R2) operating system.

    PrerequisitesThe administrator should have working knowledge of Windows Server 2008 concepts, Exchange

    2010 concepts, the Exchange Management Console and Exchange Management Shell, the

    command line, and various system utilities. This document does not elaborate on the details of any

    system utility except as necessary to complete the tasks within.

    2

    http://go.microsoft.com/fwlink/?LinkID=187961http://go.microsoft.com/fwlink/?LinkID=187961
  • 7/31/2019 InstallGuide 2010 CAS

    3/25

    In addition, before implementing the server role, the administrator should review the Understanding

    Client Access topic in the Exchange Server 2010 Library (http://go.microsoft.com/fwlink/?

    LinkId=187352).

    AssumptionsThis document assumes that Windows Server 2008 x64 Edition is installed on the intended Client

    Access server per company baseline regulations which include the latest approved service pack

    and hotfixes. In addition, the following system prerequisites have been installed:

    Microsoft .NET Framework 3.5 SP1 and the update for .NET Framework 3.5 SP1 For more

    information, see Microsoft Knowledge Base article 959209,An update for the .NET Framework

    3.5 Service Pack 1 is available (http://go.microsoft.com/fwlink/?linkid=3052&kbid=959209).

    Windows Management Framework (Windows Remote Management 2.0 and Windows

    PowerShell 2.0).

    This document assumes that forest and domain preparation steps have been performed as

    described in the Prepare Active Directory and Domains topic in the Exchange Server 2010 Library(http://go.microsoft.com/fwlink/?LinkId=187262).

    This document assumes that the account you will be using for the Exchange tasks has been

    delegated the Server Management management role, as described in theServer Management

    topic in the Exchange Server 2010 Library (http://go.microsoft.com/fwlink/?LinkId=187265).

    This document also assumes that both Exchange 2010 Windows Server 2008 and Windows Server

    2008 will be secured following the best practices found in theWindows Server 2008 Security Guide

    (http://go.microsoft.com/fwlink/?LinkId=122593).

    Important:

    The procedures within this document should be followed sequentially. If changes are made

    out of sequence, unexpected results may occur.

    Server ConfigurationThe following media are required for this section:

    Windows Server 2008 installation files

    The following procedures are in this section:

    1. Additional Software Verification

    2. Network Interfaces Configuration

    3. Drive Configuration

    4. Windows Server 2008 Hotfix Installation

    5. Domain Membership Configuration

    6. Local Administrators Verification

    7. Local Administrator Account Password Reset

    8. Debugging Tools Installation

    9. Page File Modifications

    3

    http://go.microsoft.com/fwlink/?LinkId=187352http://go.microsoft.com/fwlink/?LinkId=187352http://go.microsoft.com/fwlink/?linkid=3052&kbid=959209http://go.microsoft.com/fwlink/?linkid=3052&kbid=959209http://go.microsoft.com/fwlink/?LinkId=187262http://go.microsoft.com/fwlink/?LinkId=187265http://go.microsoft.com/fwlink/?LinkId=187265http://go.microsoft.com/fwlink/?LinkId=122593http://go.microsoft.com/fwlink/?LinkId=122593http://go.microsoft.com/fwlink/?LinkId=187352http://go.microsoft.com/fwlink/?LinkId=187352http://go.microsoft.com/fwlink/?linkid=3052&kbid=959209http://go.microsoft.com/fwlink/?linkid=3052&kbid=959209http://go.microsoft.com/fwlink/?LinkId=187262http://go.microsoft.com/fwlink/?LinkId=187265http://go.microsoft.com/fwlink/?LinkId=122593
  • 7/31/2019 InstallGuide 2010 CAS

    4/25

    10. Drive Permissions

    11. Windows Network Load Balancing Installation and Configuration

    12. DNS Entry Creation

    Additional Software Verification

    1. Verify that Remote Desktop is enabled.

    2. As an optional process, installMicrosoft Network Monitor(http://go.microsoft.com/fwlink/?

    LinkId=86611).

    Network Interfaces Configuration

    1. Log on to the server with an account that has been delegated at least local administrative

    access.

    2. Click Start > Control Panel, and then double-click Network and Sharing Center.

    3. Click Manage Network Connections.

    4. Locate the connection for the internal network and rename it according to your

    organization's naming standards.

    5. Right-click the connection and then select Properties.

    6. For Internet Protocol Version 4 (TCP/IPv4), add the following:

    a. Static IP Address, Subnet Mask, and Gateway

    b. DNS Server IP Addresses

    c. Select the check box to Append parent suffixes of the primary DNS suffix.

    d. WINS IP Addresses (if using WINS)

    7. If you are using Internet Protocol Version 6 (TCP/IPv6), configure the IPv6 settingsaccording to your organization's network standards.

    Drive Configuration

    1. Connect to the server through Remote Desktop and then log on with an account that has

    been delegated local administrative access.

    2. Click Start > Administrative Tools, and then select Computer Management.

    3. Expand Storage and then click Disk Management.

    4. Using the Disk Management snap-in of the Microsoft Management Console (MMC), format,

    rename, and assign the appropriate Drive Letters so that the volumes and DVD drive match

    the appropriate server configuration.

    4

    http://go.microsoft.com/fwlink/?LinkId=86611http://go.microsoft.com/fwlink/?LinkId=86611http://go.microsoft.com/fwlink/?LinkId=86611http://go.microsoft.com/fwlink/?LinkId=86611
  • 7/31/2019 InstallGuide 2010 CAS

    5/25

    Drive configuration

    LUN Drive letter Usage

    1 C Operating system and

    Exchange binaries

    2 Z DVD drive

    Windows Server 2008 Hotfix Installation

    1. Connect to the server via Remote Desktop and log on with an account that has local

    administrative access.

    2. Obtain the latest hotfixes approved by your company for your version of Windows Server

    2008 x64 (SP2 or R2) and copy them to the server.

    3. Launch the hotfix setup via one of two ways:

    a. Double-click the file and follow the GUI instructions.

    b. Perform a silent installation using the following command from an administrative

    command prompt:

    .msu /quiet /norestart

    4. ClickYes for any Digital Signature not Found dialog boxes that may appear.

    Note:

    These dialog boxes will not appear in environments that have not deployed the

    Windows Security templates.

    5. Wait for all file copies to complete, and then restart the server. You can use the Processes

    tab in Windows Task Manager to monitor the hotfix installation progress. When the wusa.exeprocess has exited, the hotfix installation is complete.

    Domain Membership Configuration

    1. Connect to the server through Remote Desktop, and then log on with an account that has

    been delegated local administrative access.

    2. Click Start, right-click My Computer, and then select Properties.

    3. Under the Computer Name, domain, and workgroup settings, click Change Settings.

    4. Click Change.

    5. Choose the Domain option button, and then enter the appropriate domain name.

    6. Enter the appropriate credentials.

    7. Click OK and OK.

    8. Click OK to close System Properties.

    9. Restart the server.

    5

  • 7/31/2019 InstallGuide 2010 CAS

    6/25

    Local Administrators Verification

    1. Connect to the server through Remote Desktop, and then log on with an account that has

    been delegated local administrative access.

    2. Verify (or add if not already there) that the Domain Admins account and the user account

    that will perform the Exchange installation are members of the local Administrators group on

    this server.

    3. Verify that your user account is a member of a group which is a member of the local