Exchange 2010 and Server 2008 R2 Prerequisites Installation Part 3

Server 2008 R2 Prerequisites Installation:

This sub-section will guide you to prepare your Active Directory and Domain environment.

1. To perform this tasks we need an User ID with Schema AdminsDomain Admins and Enterprise Admins group membership.

2. In the Active Directory Domain Server run the following command

Go to StartRunServerManagerCmd -i RSAT-ADDS .This command will install the Active Directory management tools.

3. In the Active Directory Domain Server run the following command.

setup /PrepareAD /OrganizationName: or setup /p /on:

Note: In this command is a variable this will vary according to your environment Ex: setup /PrepareAD /OrganizationName:jasoncoltrin. Before run this command browse to Exchange 2010 binaries path or include the Exchange binaries path Ex: “M:Setup.com /PrepareAD /OrganizationName:jasoncoltrin”

  1. For Hub Transport and Mailbox servers install the MS Filter Pack. The filterpack can be found here: http://www.microsoft.com/downloads/en/details.aspx?familyid=60c92a37-719c-4077-b5c6-cac34f4227cc&displaylang=en . Be sure to install the 64bit version. Run the setup wizard, and complete the install. *Note: On Exchange 2010 RTM, you can meet the prerequisite by installing 2007 Office System Converter: Microsoft Filter Pack. However, MS recommends that you upgrade to the Microsoft Office 2010 Filter Packs.
  2. In the PowerShell, type Import-Module ServerManager – Open powershell. type in import-module servermanager.
  3. Use the Add-WindowsFeature cmdlet to type (in actuality it’s much easier to install the features throught the PowerShell). Go to TechNet page here: http://technet.microsoft.com/en-us/library/bb691354.aspx and find the bullet that lists: “Install the Windows Server 2008 R2 operating system prerequisites”. Below is the command:
    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,Desktop-Experience -Restart

    Prerequisites_Install_Progress
    Click to enlarge image
    * As an alternative you can run the script from the Scripts folder on the Exchange DVD. Go to Start | Run | cmd | Browse to Exchange 2010 Binaries Scripts folder by using cd Scripts command | Run ServerManagerCmd -ip Exchange-Typical.xml –RestartNote: This command should be run from Scripts directory of Exchange 2010 DVD *Note: it’s a good idea to extract the Exchange 2010 binaries to a folder off of your C: drive (something like c:exch2k10, so that it’s easier to find the “Scripts” folder.)
  4. Note: If you aren’t using the UM role you can remove Desktop-Experience. Conclude after the restart by configuring the TCP Port Service to start automatically using (only CAS roles):
    From the PowerShell, execute the command: Set-Service NetTcpPortSharing -StartupType Automatic

This prerequisites guide is not exhaustive, but you should now have all the prerequisites to installing Exchange 2010. Please let me know if you find any other prerequisites missing.

A great installation guide can be found here as well:

http://muc-ug.org.in/index.php/articles/exchange-2010/109-installing-exchange-server-2010.html

 

 

 

A good majority of the content provided in my Blog’s Exchange series is derived from J. Peter Bruzzese’ excellent Train Signals Exchange Server 2010 Video Disk Series, as well as my own Exchange 2010 lab. Trainsignal.com is an invaluable source for accurate, easy to understand, IT information and training. http://www.trainsignal.com

 

Hits: 114

Exchange 2010 Installation Considerations Part 2

More requirements for Exchange 2010:

Your Forest is required to be running at Server 2008 R2 Forest Functional Level.

x64 based hardware is required.

There is no in-place upgrade for Exchange 2007 to 2010.

It’s always important to map out your network prior to installing servers.

Consider your existing infrastructure and the needs of the company.

Discuss your design and deployment goals for using Exchange 2010.

Review the order of your deployments and consider the physical network layout and network connection speeds.

The following table shows minimum CPU core requirements for Exchange 2010 components:

Exchange2010_Cores
Click image to enlarge

The following table shows the minimum memory requirements for Exchange 2010:

Exchange2010_Memory
Click Image to Enlarge

Exchange Server 2010 is available in two different editions: Standard and Enterprise

The edition is determined by the product key, however, when installing as a trial version it will be running as Enterprise Edition.

The Exchange Management tools can run on Windows 7, Windows Vista with Service Pack 2, Server 2008 SP2, Windows Server 2008 R2.

Standard Edition – Limited to 5 Databases per server

Enterprise Edition – Can run up to 100 databases per server (previous editions both standard and enterprise allow database availability groups (High Availability) but require cluster which require Enterprise Edition of Server 2008 Enterprise.

Client Access Licensing (CAL’s) also come with both Standard and Enterprise versions. Sometimes the type of license will limit clients. For example, mobile devices without the correct license may not be able to use certain features.

Prerequisites: Use the powershell commandlet or Server Roles and Features to install prerequisites. Different Exchange roles will have certain requirements. Eg. the UM role requires the Desktop Experience feature installed.

 

More Hardware Requirements:

Processor(s): x64 Intel or AMD

Memory: can change due to different role being installed, but typically 4GB min per server. If combining roles, 8GB. Add 2-10MB memory per mailbox. The maximum memory for a Mailbox role is 64GB

Disk Space: For the Mailbox Role, you will need a minimum of 1.2GB to install Exchange.

Server OS: Server 2008 or Server 2008 R2

Prerequisites for Server 2008 SP2

  1. .NET Framework 3.5 SP1
  2. Install the .NET Framework 3.5 Family Update
  3. Windows Remote Management (WinRM) 2.0 here: http://support.microsoft.com/kb/968929
  4. PowerShell v2
  5. For Hub Transport and MailBox servers, install the MS Filter Pack. *Note: On Exchange 2010 RTM, you can meet the prerequisite by installing 2007 Office System Converter: Microsoft Filter Pack. However, MS recommends that you upgrade to the Microsoft Office 2010 Filter Packs.
  6. From an elevated command prompt, from the Scripts folder, issue the following commands:
  • Sc config NetTCPPortSharing start auto
  • ServerMangerCmd -ip Exchange-Typical.xml -Restart

7.  With the Unified Messaging role type:

  • ServerManagerCmd -i Desktop-Experience

Some useful tools in the scoping and stress testing of Exchange are:

1. Risk and Health Assessment Program for Exchange Server (ExRAP) – Scoping Tool v1.5 http://www.microsoft.com/download/en/details.aspx?id=20857

2. Planning and deployment guide: http://technet.microsoft.com/en-us/library/aa995902.aspx *Especially the Mailbox Server Storage Design

3. Install and run Jetstress on your hardware prior to deployment

The documentation for the Exchange Server 2010 version of Jetstress is available on TechNet at the following location.

http://technet.microsoft.com/en-us/library/ff706601.aspx

 

Version Build Usage Link
14.01.0225.017 32 bit
  • Exchange 2003[1]
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6c9c1180-4dd8-49c4-85fe-ca1cdcb2453c&displayLang=us
14.01.0225.017 64 bit
  • Exchange 2007
  • Exchange 2010
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=13267027-8120-48ed-931b-29eb0aa52aa6

Table 1 – Jetstress version and download table



[1] Refer to Appendix D – Exchange 2003 for information on configuring Jetstress 14.01.225.x for Exchange 2003

 

 

 

A good majority of the content provided in my Blog’s Exchange series is derived from J. Peter Bruzzese’ excellent Train Signals Exchange Server 2010 Video Disk Series as well as my own Exchange 2010 lab. Trainsignal.com is an invaluable source for accurate, easy to understand, IT information and training. http://www.trainsignal.com

 

Hits: 72

Exchange Server 2010 Overview Part 1

Microsoft’s Exchange Server:

Email is a mission critical tool for business. How do you provide that capability? Hosted, in-house, BPOS? There are many options. With Exchange you gain the following:

  • A reliable and flexible messaging platform for business communications.
  • Provides e-mail capabilities
  • Also provides calendar access and contact management
  • Users can have access to their communications anywhere; through their browser, mobile device, or their Outlook client.

Exchange 2010 adds the following:

  • Provides the email typical for Exchange that we’ve come to expect. Some features are the same as Exchange 2007, but new features are notable.
  • Continues the Server Roles for your organization’s deployment strategy. (5 Roles)
  • Includes High Availability and Site Resilience
  • Allows Unified Communications through the Unified Messaging Server Role that will give users a Universal Inbox (fax’s, voicemail, etc)

5 Server Roles: – Prior to Exchange Server 2010, you installed the entire Exchange infrastructure on an Exchange Server. Eg. if a Front-end server was only needed, you still had to install the entire Exchange Infrastructure. Now you have a lighter footprint with Roles. Server 2008 also uses Roles and Features.

  • The Mailbox Role: user mailboxes with mailbox DB’s. Also contains public folders.
  • Client Access Role: connection point for all users to their mailboxes internally or externally. (MAPI, OWA, Outlook Anywhere, ActiveSync, IMAP/POP)
  • Hub Transport Role: Flow of traffic to and from the Mailbox server. (These first 3 roles need to be installed in order for Exchange to work, but not necessarily on the same server.)
  • Optional Role – Unified Messaging Role: Provides the Universal Inbox for voicemail, email, faxes, etc.
  • Optional Role (recommended)- Edge Transport Role: Perimeter-based server to handle anti-spam and anti-virus protection and additional transport rules.

Requirments for Exchange 2010:

1. Domain Controller – AD Domain controller

2. DNS Services

3. Member Server (on which you will install Exchange)

 

For Exchange 2010 running behind your firewall or DMZ on your internal network, you can install the following 4 roles on their own server: Client Access Server, Mailbox Server, Hub Transport Server, and Unified Messaging Server.

To add an Edge Transport Server to your network, you will need to setup a Member Server that is not a member of the Domain. You install Exchange, but only the ET server role. This will sit out on the Perimeter Network (between internal and external firewalls – DMZ). Again, the ET server cannot be a member of the Domain.

New in Exchange 2010:

Storage Architecture – There’s a new focus on the database itself, not on a storage group. Storage groups have been removed from Exchange’s DB design (Exchange 2000 – 2007)

High Availability and Site Resiliency – Database Availability Groups have replaced legacy Exchange  HA versions.

Permissions – Role-based access control has been implemented – permissions to manage exchange.

Control – A cool new Web-Based Exchange Control Panel (ECP). Carries over Exchange 2007’s exchange management console and an exchange management shell.

Voicemail and Unified Messaging – including voicemail preview, better protection.

Exchange 2010 has something for everyone. It is a complete communications platform for organizations large and small.

 

 

A good majority of the content provided in my Exchange series is derived from J. Peter Bruzzese’ excellent Train Signals Exchange Server 2010 Video Disk Series. Trainsignal.com is an invaluable source for accurate, easy to understand, IT information and training. http://www.trainsignal.com

Hits: 11