Deploy Exchange Server 2010 graphics and text tutorials on Windows Server 2008 R2 _win Server

These two products are the second half of 09 Microsoft launched a heavy product, are 64-bit architecture, and its function and performance far beyond its earlier version, there is no longer to do this content too much description.

The combination of Windows Server 2008 R2 and Exchange Server 2010 is "perfect." For a previous version of Exchange Server 2010, Exchange Server 2007来 can only run on the Windows Server 2008 operating platform, so you want to deploy Exchange in Windows Server 2008 R2 It seems that you can only select Exchange Server version 2010. However, there are some problems that have not previously been encountered during the installation process, especially in Exchange Server 2008 R2, where some services are disabled by default and need to be reset to open otherwise the installation will not work. These steps may not be met at all during the deployment of an earlier product, and it may be easier to get started if an Exchange Server 2007 engineer does the operation. However, if an engineer from Exchange Server 2003 does it, it may be frustrating.

The deployment of Exchange Server 2010, like its earlier products, requires support for Active Directory (AD). Therefore, you can only deploy it in a domain environment. In addition, early exchange systems typically do not deploy a certificate server if they are not in need of deployment. However, unlike Exchange Server 2010, which recommends that you deploy a certificate Server in your enterprise, clients will encounter a system validation warning prompt for the enterprise certificate each time they log on. Although it does not affect client access to mailboxes, it is particularly important to note that customers are unfriendly. The following introduction presents an Exchange Server 2010 server deployment process that does not have Certificate Services support, in which you can see the warnings that clients are experiencing.

Experimental environment in the case of a small business, it is best to use Windows Server 2008 R2 as a system platform for the new deployment of Exchange Server 2010. Configure the directory service on this server to act as a domain controller (DC), a DNS server, and so on. Next, if you do an installation of Exchange Server 2010 directly on it that is not checked by the requirements program, you will be notified of a large number of errors (Figure 1).

Figure 1

The role of the environment needs

Because Exchange Server 2010 is installed according to different roles, the configuration of the system is not the same. The details are as follows:

First, you need to install the components for a server that installs mailbox roles (MB) separately (Figure 2):

IIS and its metadata

W3SVC service

At least one Hub Transport server (hub) role exists in the directory site to send and receive mail

At least one Client Access server (CAS) role exists in the directory site to support Outlook Web App (OWA) and Exchange ActiveSync mobile phone access

Recommended to install the 2007 Office System Converter: Microsoft Filter Pack (64bit)

Figure 2

Second, the server for the individual hub role needs to install components (Figure 3):

? IIS and its metadata

? W3SVC service

? The net. TCP port Share server set to auto start

Figure 3

Third, the server for the individual hub role needs to install the components (Figure 4):

Recommended to install the 2007 Office System converter: Microsoft filter Pack (64bit)

Figure 4

Four, for a separate UM role server, you need to install the components (Figure 5):

Require Windows Media Encoder to be installed, that is, you need to install the Desktop health component

Requires the installation of Windows Media Audio Voice Codec To install the Desktop health component

At least one Hub Transport server (hub) role exists in the directory site to use the Unified Messaging feature

Figure 5

Five, for the edge role must be installed separately, and deployed in the DMZ, so this is no longer too much to tell.

Pre-Installation Preparation

If you take the default installation selection, the MB, HUB, and CAS roles are automatically selected. Therefore, IIS should be installed on the server first (Figure 6),

Figure 6

And you need to add Basic authentication, Windows Authentication, digest test authentication, dynamic content compression, and IIS 6 metabase compatibility when you install IIS (Figure 7).

Figure 7

Second, through the Service Management console, open the Net. TCP Port Sharing Service attribute, change its default "disable" Startup type to "Automatic" (Figure 8).

Figure 8

Finally, download and install the 2007 Office System Converter from http://go.microsoft.com/fwlink/?LinkId=123380 as recommended: Microsoft Filter Pack (64bit) (Figure 9).

Figure 9

Specific installation steps

1. Insert Exchange Server 2010 CD, run or manually run the contents of the disc, display the installation Overview dialog on the desktop, and follow the instructions for the installation step. Because the sample server is a Windows Server 2008 R2 system and the Active Directory service is installed, the Windows PowerShell V2 and the. NET Framework 3.5 SP1 have been installed.

Note:1, the PowerShell of Windows Server 2008 R2 is installed by default

2. Windows Server 2008 R2 servers are forced to install the. NET Framework 3.5 SP1 When you install AD (Figure 10)

Figure 10

Therefore, you only need to click Select Exchange Language Options, and then choose only install languages from DVD (Figure 11).

Figure 11

2. Select the "Install Microsoft Exchange" Step, follow the wizard, and when you select Exchange Server Installation type, select Exchange Server Typical installation (Figure 12) and click Next.

Figure 12

3. Write the organization name of the enterprise in the Exchange organization, which can no longer be modified after the deployment of exchange, so you need to decide repeatedly (Figure 13) and click Next.

Figure 13

4. In client settings, it is recommended that you select Yes (Figure 14), because most users in the current domestic enterprise are still using Office 2003, so you should be compatible with Outlook 2003 clients and click Next.

Figure 14

5. In the Configure Client Access server external domain, if you need it to support access from the Internet, you should select the Client Access server role will face the Internet and fill in the registered domain name (Figure 15).

Figure 15

6, the wizard will automatically prepare the situation check, if you follow the previous steps before installation, this will only be a warning about "organizational prerequisites", and the others are satisfied (see Figure 16).

Figure 16

This warning message is prompted because the Exchange Server 2010 installer is used to initialize the Active Directory for it, so that it is ready for the 2010 organization, since there is no Exchange Server 2007 server in the entire forest before, Therefore, this organization will only support Exchange Server 2010 servers, while earlier versions of Exchange Server are not compatible. Here, select Install until the wizard finishes (Figure 17).

Figure 17

Post-installation actions

After the installation is complete, if the server has access to the Internet, it is recommended that you check for updates and install the latest patches. In the Initial Installation Overview dialog box, select "Get Critical Updates for Exchange Server" and the server will use the system's Update tool to complete the update operation.

Finally, some test users need to be set up to perform a simple basic test to ensure the successful installation of the Exchange Server 2010 server.

Note: Exchange Server 2010 allows you to try 120 days and if you need to enter a serial number, it can be an Exchange Management Console (EMS) to operate