Exchange Server 2010 Learning (ii) Deploying a triple role (CAS+HT+MBX)

After exploring the role features of Exchange Server2010, today we'll look at how to deploy the triple role (CAS+HT+MBX) Exchange Server SP1 in a small business environment, but there are a few things to know before you do it:

1. The Exchange server and Active Directory are tightly integrated, and AD DS deployment must be done to meet the need for Exchange Server to function properly. Therefore, the AD DS schema must be extended before installation to provide the related properties that Exchange needs to store data. Account information in exchange is stored in the ad AD database, on the other hand, and Exchange configuration information is not stored on this computer, but in the configuration directory partition of AD DS. When Exchange needs to obtain data on AD DS, it is already connected to the DC through DNS name resolution to access data on it. If the DC fails to respond properly, it will affect the normal operation of the Exchange service and therefore require the proper configuration of DNS information, or it will cause the contact DC to fail.

2. Exchange Server2010 and Exchange Server 20,071, use the AD Site topology and settings in AD DS to control the scheduling, replication interval, and cost of information routing. Therefore, before you install and plan Exchange Server, you need to be sure that the AD DS site plan meets the needs of exchange when it crosses low-speed connections.

3. There is also a need to ensure that the Global catalog server GC is normal, because the client Access server role needs to connect to a global catalog server when it looks up mailbox databases for client mailboxes and when clients use the Global address list. Therefore, you should ensure that at least one GC per AD site is regular. For GC availability and performance issues, you can set up multiple units.

Here's a look at the hardware and software requirements for installing Exchange Server2010:

Hardware requirements:

Cpu:inter EM64T or AMD64 hardware platform

Memory: At least 4GB of memory. It is recommended to multiply the number of CPU cores by 1GB, which recommends using 4 cores. The individual MBX role takes 4GB as the starting point, with each user mailbox plus 2-10MB memory cumulative estimate. Here we are deploying the CAS+HT+MBX triple role server. is based on 8GB, plus per-user mailbox 2-10MB memory cumulative estimate.

Disk space: At least 1.5GB or more, the file system must be NTFS.

Software Requirements:

AD domain: Must be the AD domain environment above Windows Server2003 SP1

Operating system: it must be either a standard version of Windows Server2008 X64 or an enterprise version SP2 or a Windows Server 2008 R2 Standard or Enterprise Edition. If you are installing on Windows Server 2012, you will need to make an Exchange Server SP3 patch.

Other: NET Framework 3.51 SP1, PowerShell2.0, Windows Remote Managerment2.0, Office Filter packs. The net Framework 3.51 SP1, PowerShell2.0, and Windows Remote Managerment2.0 are already in Windows Server 2008 R2 and do not need to download the installation, which makes deployment much simpler. We use the Windows Server 2008 R2 Enterprise Edition SP1 here. If you install Exchange Server SP1 only on Windows Server 2008 R2, you will need to install the necessary hotfix beforehand, such as KB79099, KB979744, KB982867, KB983440, KB977020, and so on. But luckily we are using the Windows Server 2008 R2 Enterprise Edition SP1, and these hotfix do not have to download the installation earlier. On the server that will host the Hub Transport server role (hub) and the Mailbox server role (MBX), install the Microsoft Filter packs.

Now let's comb through the installation steps for the triple role to fully prepare for the installation of the following Exchange Server2010 SP1.

Step 1. Prepare for AD DS domain environment. Here we prepare two servers, one name is DC1, use the domain controller. Another name is Server1, and we will install Exchange Server2010 SP1 on this machine, so we need to add Server1 to the AD DS domain.

Step 2. Install the Microsoft Office Filter packs on the Server1 machine.

Step 3. Install the IIS components using PowerShell.

Step 4. Enable remote administration of the server, including automatic sharing of TCP ports, remote administration of servers, and open firewall port settings for remote administration. This feature should be set up on all Exchange Server 2010 server roles.

Verify that the startup type of the Net.TCP Port sharing service services is set to Automatic.

Step 5. AD DS domain Extensions, this step can use the Setup/ps, setup/p, SETUP/PD commands, or the Exchange Server can be installed directly during setup.

Step 6. Installation of Exchange Server SP1.

All right, guys, everything's ready, let's go:

Step 1:ad DS domain environment

We first deploy the domain controller DC1 and configure the computer name and network as shown in the following illustration:

Then, run: Dcpromo is ready to be promoted to a domain controller, as shown in the following illustration:

After a moment, you can see the interface shown in the following image and click Next: