Lesson 2: Preparing the Servers for Exchange Installation

  • Article

Once the network infrastructure is prepared for the deployment of Exchange Server 2007, it is necessary to prepare the computer that will host Exchange Server 2007. As mentioned earlier, Exchange Server 2007 is an extremely sophisticated piece of software that requires planning and preparation to install. At the start of the installation process, covered in detail in Chapter 2, an application runs that checks that the appropriate components have been installed and settings have been applied. If these components are not installed, the installation routine will terminate, reminding you that you need to install component X or change setting Y. If you have not prepared properly for this, you will find yourself constantly restarting the installation process and returning to Microsoft’s Web site yet again to download another required component. Rather than taking this stop-and-start approach to Exchange deployment, it is far simpler to download and install the relevant components in one go prior to launching Exchange installation. This lesson will examine all the components and extra software that need to be installed on the computer that will host Exchange Server 2007 before it is possible to successfully install the product.

After this lesson, you will be able to:

  • Prepare a Windows Server 2003 computer for the installation of Exchange Server 2007.
  • Ensure that the server meets the minimum hardware requirements.
  • Ensure that the appropriate server components are installed.
  • Verify that DNS has been configured appropriately.

Estimated lesson time: 40 minutes

Exchange 2007 Operating System and Hardware Requirements

The first step in determining whether a computer is capable of running Exchange Server 2003 is to determine whether it meets the minimum hardware requirements. Most organizations have a complex process when it comes to ordering new servers, and you do not want to go through filling out all those forms and then find that the server that you ordered either will not run Exchange Server 2007 well or cannot run it at all. The following list details the hardware requirements of the computer that will host Exchange Server 2007:

  • x64 architecture–based processor that supports the Intel EM64T or AMD64 instruction set
  • 2 GB of RAM plus 5 MB of RAM per mailbox
  • 1.2 GB of disk space on the volume on which Exchange is installed plus 500 MB per unified messaging language pack that is to be installed
  • 200 MB of free disk space on the system volume

Once you have verified that the computer you wish to install Exchange Server 2007 on has met the hardware requirements, you need to verify that the software environment computer meets the Exchange Server 2007 requirements.

BEST PRACTICES Fresh is best

Although you can install Exchange Server 2007 on any computer that meets the minimum requirements, best practice is to install Exchange on a fresh install of Windows Server 2003 or Windows Server 2003 R2 rather than one that has been used for another task. A computer that has been explicitly prepared to run Exchange Server 2007 will provide better performance than a computer that was configured for another task and that has then had Exchange Server 2007 installed on it.

Prior to the installation of Exchange, the software environment should meet the following requirements:

  • 64-bit edition of Windows Server 2003 or Windows Server 2003 R2. If you plan to use single-copy cluster or cluster continuous replication, the enterprise editions of Windows Server 2003 and Windows Server 2003 R2 are required.
  • The following volumes must be formatted with the NTFS file system:
    1. System volume
    2. Volumes that store Exchange program files, storage group files, transaction log files, database files, and all other Exchange files
  • Microsoft .NET Framework version 2.0.
  • Microsoft Windows PowerShell. This can be downloaded from Microsoft’s Web site. Consult Microsoft Knowledge Base Article 926139.
  • MMC 3.0. This version of the MMC is included with Windows Server 2003 R2 but not with Windows Server 2003. This MMC is installed when you apply SP2 to Windows Server 2003 R2.
  • Update for Windows Server 2003 x64 edition KB904639.
  • Update for Windows Server 2003 x64 edition KB918980.
  • The Simple Mail Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP) service must not be installed.

NOTE Does not work with Itanium

Exchange Server 2007 requires a processor that conforms to the x64 (also known as x86-64, AMD64, or EMT64T) architecture. The IA64 Itanium processor architecture, even though it is also 64 bit, uses a different instruction set to the x64 architecture. This means that Exchange Server 2007 will not run on the IA64 Itanium processor even though it is also 64 bit.

Although the different Exchange Server 2007 roles are discussed in Chapter 2, the following section will detail the prerequisite software environment that is necessary for particular Windows components to be installed. These components can be added to the server through the Add/Remove Programs item in Control Panel.

Windows Server 2008 Roles

In Windows, Server 2008 components are called roles. Roles are added through the Roles node of the new Server Manager console. Roles that can be added to Windows Server 2008 include Web server, DNS server, fax server, and file services. Windows Server 2008 also has a separate way of adding components called features. Features that can be added include Microsoft .NET Framework version 3.0 and PowerShell. Whereas the preparation for installing Exchange Server 2007 on Windows Server 2003 R2 still requires you to download files from Microsoft’s Web site, it is possible to install Exchange Server 207 on Windows Server 2008 by adding roles and features directly from the operating system installation media.

Do not worry if you do not understand what the different role types mean initially; you can refer back to this section once you’ve read about the tasks that each can be used to achieve in Chapter 2.

MORE INFO System requirements

To find out more about the Exchange Server 2007 system requirements, navigate to the following link: https://technet.microsoft.com/en-us/library/aa996719.aspx.

Mailbox Server Role

If the computer on which you are going to install Exchange Server 2007 will be assigned the Mailbox server role, it will be necessary to install the following Internet Information Services (IIS) 6.0 components prior to installation:

  • COM+ Access
  • IIS World Wide Web Service

Client Access Server Role

If the computer on which you are going to install Exchange Server 2007 will be assigned the Client Access server role, it will be necessary to install the following components prior to installation:

  • World Wide Web Service
  • Remote procedure call (RPC) over HTTP Proxy ASP.NET version 2.0

Unified Messaging Server Role

If the computer on which you are going to install Exchange Server 2007 will be assigned the Unified Messaging server role, it will be necessary to install the following components prior to installation:

  • Microsoft Windows Media Encoder
  • Microsoft Windows Media Audio Voice Codec
  • Microsoft Core XML Services (MSXML) 6.0

Hub Transport Server Role

The Hub Transport server role does not require any extra components to be installed other than those listed in the minimum specifications section.

Edge Transport Server Role

Edge Transport servers require that Active Directory Application Mode (ADAM) be installed. This software can be added using the Add/Remove Programs item on computers running Windows Server 2003 R2 or can be downloaded from Microsoft’s Web site at https://www.microsoft.com/adam. ADAM is a directory service similar to Active Directory but runs as a user service rather than as a system service. ADAM can be installed on servers without requiring that they be promoted to domain controllers in an Active Directory domain. ADAM also has the advantage of being able to be installed on stand-alone servers that are not members of an Active Directory forest.

MORE INFO Application mode

To find out more about Active Directory application mode, navigate to the following link: https:// www.microsoft.com/windowsserver2003/adam/ADAMfaq.mspx

.

Exchange Server 2007 on Domain Controllers

Even though the practices in this book have you install Exchange Server 2007 on a domain controller, this is done for the sake of expediency rather than as a recommended deployment option. Ideally, you should install Exchange Server 2007 only on a member server or as a stand-alone in the case of the edge transport. One limitation of installing Exchange Server 2007 is that you will not be able to use the DCPROMO command to add or remove the directory server role. You can not promote a member server that has Exchange installed to a domain controller, and you can not demote a domain controller that has Exchange installed to the status of member server.

Quick Check

  1. Which components should you ensure are not installed on a Windows Server 2003 R2 computer prior to attempting the installation of Exchange Server 2007?
  2. Which Exchange Server 2007 role does not require any special components to be installed above the minimum components required to install Exchange?

Quick Check Answers

  1. SMTP and NNTP components.
  2. Hub Transport server role.

Networking Configuration

A computer that is going to host Exchange Server 2007 needs to have a static IP address and the appropriate records created in DNS to support the exchange of mail. You can verify that a computer has a static IP address configured by opening a command prompt and issuing the IPCONFIG /ALL command. As shown in Figure 1-7, the DHCP Enabled line should read No. If this line does not read No, it will be necessary to edit the properties of the TCP/IP protocol for that adapter and to assign a static IP address.

Cc505889.Figure_C01624108_7(en-us,TechNet.10).png

Figure 1-7 Verifying static IP address configuration

For a mail server to send and receive mail, an MX record must exist within the DNS zone that it will answer mail for. For example, for the host glasgow.tailspintoys.inter-nal to receive mail for the tailspintoys.internal DNS zone, an MX record must be configured in the tailspintoys.internal DNS zone that points to glasgow.tailspintoys. internal. You can determine which MX records exist for a DNS zone by using the nslookup command from the command prompt. The commands that you enter to determine the MX records for a DNS zone are the following:

nslookup –querytype=mx <dns.zone>

Each MX record can be assigned a priority, with the default priority being 10. The higher the assigned number, the lower its priority. For example, an MX record with a priority of 10 will be favored over an MX record with a priority of 30. Priorities are used in mail transport, with a connection attempted to the highest-priority mail server first and then connections attempted to lower-priority mail servers if that initial connection fails. The process of creating an MX record is demonstrated in Practice 3 at the end of this lesson.

Security Configuration Wizard

The Security Configuration Wizard (SCW) is a tool that can be used to reduce the attack surface of a computer running Windows Server 2003. The attack surface can be thought of as operational ports and services on a computer. The more services and ports that are open to the network, the greater the attack surface. The SCW works by limiting the number of operating services and open ports to only those that are required to carry out the server’s function. The SCW is a component that can be installed by using the Add/Remove Programs item on computers running Windows Server 2003 with SP1 or Windows Server 2003 R2.

You have to have Exchange Server 2007 installed to access the Exchange Server 2007 Security Configuration Wizard templates as these are not available in the default installation of this application. Once you have installed the Security Configuration Wizard on a computer that hosts an Exchange Server 2007 role, you need to manually register the Exchange Server 2007 Security Configuration Wizard templates by issuing the following command:

scwcmd register /kbname:Ex2007KB /kbfile:“%programfiles%\Microsoft\Exchange Server\scripts\Exchange2007.xml”

Practice 2 at the end of this lesson provides a walk-through of the SCW.

MORE INFO Security Configuration Wizard

You can find out more about the Security Configuration Wizard with Exchange Server 2007 by navigating to the following link: https://technet.microsoft.com/en-us/library/aa998208.aspx.

The Exchange Best Practices Analyzer

The Exchange Best Practices Analyzer, shown in Figure 1-8, is a tool designed to assist in tuning an Exchange installation, diagnosing common misconfiguration issues with the intention of making Exchange function as efficiently as possible. Once the tool is run, a detailed report will be generated that lists a set of recommendations that can be made to the environment to achieve greater performance, scalability, and uptime. The Exchange Best Practices Analyzer is located in the Toolbox of the Exchange Management Console. This tool is presently available only after you have installed Exchange Server 2007. To perform the readiness check, install the tool without assigning any roles to the server.

NOTE Use the included version

At the time of this writing, you need to use the Exchange Best Practices Analyzer included with Exchange Server 2007 rather than the one that is available from Microsoft’s Web site, as there are difficulties installing the utility if Microsoft .NET Framework 2.0 rather than 1.1 is installed.

The Exchange Best Practices Analyzer can be configured to perform the following scans:

  • Health check This check examines the Exchange environment for errors, warnings, and configuration settings that differ from the default. Permission check This check examines the Exchange administrative groups and the permissions assigned to Exchange servers and reports on critical issues and settings that deviate from the installation defaults. Connectivity test This check tests network connectivity. It is often used to verify that firewall configuration is not impeding Exchange. Baseline This scan reports on all settings that differ from a user-configured baseline. Exchange 2007 readiness check Used prior to an exchange deployment, this check will highlight issues in the network infrastructure that may cause deployment problems.

Cc505889.Figure_C01624108_8(en-us,TechNet.10).png

Figure 1-8 Exchange Best Practices Analyzer tool

Multiple Volumes

Although it is possible to install Exchange on the same volume as the Windows Server 2003 operating system, there are benefits of having multiple disks and multiple volumes. This involves performing a custom installation, the process for which will be covered in more detail in Chapter 2. Windows Server 2003 supports several levels of RAID (redundant array of independent disks) functionality that can be utilized to support an Exchange Server 2007 deployment. These are configured through the Disk Management node of the Computer Management console.

  • RAID 0, also known as disk striping, improves disk read and write performance at the expense of redundancy. It achieves this by spreading data across two or more volumes. Data can be written and read from both disks at the same time, increasing performance. If one of the disks in a RAID 0 set fails, all data on the volume is lost. RAID 0 is supported through software on Windows Server 2003.
  • RAID 1, also known as disk mirroring, provides redundancy. A RAID 1 volume involves a pair of disks with the data on the first disk mirrored on the second disk. In the event that one disk fails, the other disk can still be used without the loss of data. RAID 1 provides no performance benefit. RAID 1 is supported through software on Windows Server 2003.
  • RAID 5, also known as disk striping with parity, provides redundancy and a performance improvement. RAID 5 requires a minimum of five disks. Data in a volume is spread across all disks in the RAID 5 array. Parity data, used in data recovery should a disk in the RAID array fail, is also spread across all disks. The data on a volume can be recovered if a disk fails by replacing the failed disk.
  • Other types of RAID, including RAID 1+0 and RAID 0+1, are available, but these require the use of special hardware and cannot be implemented directly through the Windows Server 2003 operating system.

MORE INFO More on RAID

You can find out more about RAID by navigating to the following Web site: https:// technet2.microsoft.com/windowsserver/en/library/cb871b6c-8ce7-4eb7-9aba-52b36e31d2a11033.mspx?mfr=true.

In most situations, you would want to place mailbox data on volumes that are redundant. In the event that a disk failure occurs on the Exchange Server 2007 computer, data hosted on a redundant volume can be quickly recovered. The choice of which method of redundancy to use is determined by the costs involved. Small to medium-sized businesses are generally able to implement only RAID 1 on their mail servers, whereas large businesses can afford to buy the equipment necessary to implement RAID 1+0 or 0+1.

Exam Tip

It is likely that knowledge of which components are required for each role will be a topic presented on the exam. Use Microsoft PowerPoint or similar software to create a set of flash cards so that you can build an association in your mind between components and roles. You’d be surprised how you can adapt software that you already have available to improving your chances of passing a certification exam.

Practice: Preparing the Server for the Installation of Exchange Server 2007

In these practices, you will perform several exercises that will prepare your Windows Server 2003 x64 computer for the installation of Exchange Server 2007. You will also familiarize yourself with the SCW and the Exchange Best Practices Analyzer.

Practice 1: Installing Software Components

In Chapter 2, you will install Exchange Server 2007 with all roles except the Edge Transport server role. In this practice, you will install all extra components that are not located on the Exchange Server 2007 installation media so that when you reach the practices in Chapter 2, the installation process will run without interruption. In Practice 2 of Lesson 1 in this chapter, you installed the Microsoft .NET Framework version 2 and Windows PowerShell on the schema master. If you are going to install Exchange Server 2007 on a computer other than the one functioning as schema master, you will need to perform steps 8 through 11 of Practice 1 on the computer that you will deploy Exchange on prior to beginning this practice. To complete this practice, log on to the computer on which you will be deploying Exchange Server 2007 using the Administrator account and perform the following steps:

  1. Navigate to the following four links on Microsoft’s Web site. Download these updates to the server’s desktop:

    1. https://go.microsoft.com/fwlink/?linkid=74465
    2. https://go.microsoft.com/fwlink/?LinkId=67406
    3. https://go.microsoft.com/fwlink/?LinkId=67407
    4. https://go.microsoft.com/fwlink/?LinkId=70796 (Ensure that you download the x64 version of this update.)

    IMPORTANT .NET hotfix

    Even though you have already installed the Microsoft .NET Framework version 2.0 using the Add/Remove Programs item in an earlier practice, the Exchange Server 2007 installation requires that you install a hotfix for this software prior to deployment.

  2. Install each of these updates. Ensure that you install the Windows Media Encoder before you install the update to the encoder.

  3. Open the Add/Remove Programs item in Control Panel and select Add/Remove Windows Components.

  4. Click Application Server and then click Details.

  5. Select the Enable network COM+ Access item.

  6. Select the Internet Information Services item and then click Details.

  7. Verify that the NNTP and SMTP services are not enabled.

  8. Select the World Wide Web Service item and then click OK twice.

  9. Select the Networking Services item and then click Details.

  10. Select the RPC Over HTTP Proxy item and then click OK.

  11. Click Next to install these items. Click Finish when the items are installed.

    BEST PRACTICES Reapply SP2

    After installing critical components, you should reboot the computer and reapply Windows Server 2003 SP2. This will update the newly installed components. A common mistake made by systems administrators is to forget to reapply service packs after modifying the components of a server. Reapplying service packs is not necessary if you have used the Slipstream technique on the installation files.

Practice 2: Installing and Running the SCW

In this practice, you will explore the functionality of the SCW. In the best of worlds, this wizard should be run after all applications and services that the server will provide to the network are made active. If you apply the results of the SCW to a computer prior to installing necessary services, you may block something that you will need later. In this practice, you will go through the SCW process and then roll the computer back to its original configuration. Although this practice is long, it will give you a good overview of the SCW’s capabilities. This practice is being performed prior to the full installation of Exchange Server 2007 so to ensure that important services are not accidentally disabled. To complete this practice, perform the following steps:

  1. Select the Add/Remove Programs item from Control Panel.

  2. Click on Add/Remove Windows Components, place a check next to the Security Configuration Wizard component, and then click Next to complete the installation. Open the SCW from the Administrative Tools menu.

  3. On the Welcome page, click Next.

  4. On the Configuration Action page of the wizard, select Create A New Security Policy and then click Next.

  5. Verify that the current server name appears on the Select Server page and then click Next.

  6. On the Processing Security Configuration Database page, click View Configuration Database. This will bring up the current configuration. Scroll down to the Domain Controller entry and expand it as shown in Figure 1-9.

    Cc505889.Figure_C01624108_9(en-us,TechNet.10).png

    Figure 1-9 The SCW Viewer displays information about ports and services required for specific roles

  7. Close the SCW Viewer and then click Next on the Processing Security Configuration Database page.

  8. On the Select Server Roles page, examine which roles the SCW has detected and then click Next.

  9. On the Select Client Features page, shown in Figure 1-10, examine the list of features that the SCW has detected and then click Next.

  10. On the Select Administration And Other Options page, review the detected administration options and then click Next.

  11. On the Select Additional Services page, review the additional services that the server requires and then click Next.

  12. On the Handling Unspecified Services node, ensure that the Do Not Change The Startup Mode Of The Service option is selected and then click Next.

    Cc505889.Figure_C01624108_10(en-us,TechNet.10).png

    Figure 1-10 A list of installed features as detected by the SCW

  13. On the Confirm Service Changes page, shown in Figure 1-11, review the list of services that have had their configuration changed and then click Next.

    Cc505889.Figure_C01624108_11(en-us,TechNet.10).png

    Figure 1-11 Services modified by the SCW

  14. On the Network Security page, ensure that the Skip This Section option is not selected and then click Next.

  15. On the Open Ports And Approve Applications page, review the ports that are being used by the computer and then click Next.

  16. On the Confirm Port Configuration page, shown in Figure 1-12, check which ports have been left open and which ports have been closed and then click Next.

    Cc505889.Figure_C01624108_12(en-us,TechNet.10).png

    Figure 1-12 Confirming port configuration

  17. On the Registry Settings page, verify that the Skip This Section option is not selected and then click Next.

  18. On the Require SMB Security Signatures page, verify that both the All Computers That Connect To It Satisfy The Following Minimum Operating System Requirements and the It Has Surplus Processor Capacity That Can Be Used To Sign File And Print Traffic options are enabled. Click Next.

    CAUTION Using older editions of Windows with Exchange Server 2007

    You should note that selecting these options does not mean that Windows NT 4.0, Windows 95, or Windows 98 computers will not be able to connect to the computer hosting Exchange Server 2007; it just means that each of these clients will require that the appropriate updates are installed.

  19. On the Require LDAP Signing page, verify that the Windows 2000 Service Pack 3 Or Later option is not selected. This option should be enabled only if all clients are running Windows 2000 SP3 or later. Click Next.

  20. On the Outbound Authentication Methods page, verify that only the Domain Accounts option, shown in Figure 1-13, is enabled and then click Next.

    Cc505889.Figure_C01624108_13(en-us,TechNet.10).png

    Figure 1-13 Confirming port configuration

  21. On the Outbound Authentication Using Domain Accounts page, verify that the Windows NT 4.0 Service Pack 6a Or Later Operating System and the Clocks That Are Synchronized With The Selected Server’s Clock options are selected and then click Next.

  22. On the Inbound Authentication Methods page, verify that only the Computers That Have Not Been Configured To Use NTLMv2 Authentication and the Computers Using RAS Or VPN To Connect To RAS Server That Are Not Running Windows Server 2003 Service Pack 1 Or Later options are selected and click Next.

  23. On the Registry Settings Summary page, review the setting and then click Next.

  24. On the Audit Policy page, ensure that the Skip This Section option is not selected and then click Next.

  25. On the Audit Policy Summary page, review the settings and answer the questions below. Ensure that the Also Include The SCWAudit.inf Security Template option is not selected and then click Next.

  26. On the Save Security Policy page, click Next.

  27. Enter the security policy file name as 70-236-Chapter1.xml and click Next.

  28. Click OK to dismiss the reboot warning and then select the Apply Now option. Click Next. The security policy will now be applied to your computer. When the policy has been applied to your computer, click Next and then click Finish.

    NOTE If a reboot is required

    You should not have to reboot your computer after applying the policy, but in the event that you do, once the computer has rebooted, log back on with administrator credentials.

  29. Restart the SCW and then click Next.

  30. On the Configure Action page, select the Rollback The Last Applied Security Policy option and then click Next.

  31. On the Select Server page, ensure that the local computer is selected and then click Next.

  32. On the Rollback Security Configuration page, click Next. After the rollback completes, click Next and then click Finish.

Quick Check

  1. Which audit event type will not be audited if the settings outlined in step 26 are applied?
  2. What caveat exists in applying the SCWAudit.inf security template using the SCW?

Quick Check Answers

  1. The Privilege Used audit event type will not be audited.
  2. The Audit Policy Summary page explains that the SCWAudit.inf SACLs cannot be used using the SCW rollback action.

Practice 3: Configuring an MX Record in DNS

In this practice, you will perform the necessary steps to create an MX record for the future Exchange Server 2007 computer within the DNS system. To complete this practice, perform the following steps:

  1. Open a command prompt and run the IPCONFIG command to determine the IP address of the computer that will host Exchange Server 2007. As mentioned earlier in the lesson, this IP address should be statically configured.

  2. From the Administrative Tools menu, open the DNS console.

  3. Expand the Forward Lookup Zones node, then the tailspintoys.internal node. Verify that the host record for Glasgow.tailspintoys.internal exists, as shown in Figure 1-14. This record should have been created when you installed the server operating system and Active Directory as described at the start of the practices in Lesson 1. If this record does not exist, it will be necessary for you to create it. Map the host name Glasgow.tailspintoys.internal to the IP address of the server and proceed to the next step.

    Cc505889.Figure_C01624108_14(en-us,TechNet.10).png

    Figure 1-14 Confirming the existing host record

  4. Right-click the tailspintoys.internal node and then click New Mail Exchanger. This will bring up the New Resource Record dialog box.

  5. Click on Browse, navigate to the host record for glasgow.tailspintoys.internal, and then click OK.

  6. Verify that the details match those in Figure 1-15 and then click OK.

  7. Open a command prompt and issue the following command:

    nslookup –querytype=mx tailspintoys.internal

  8. Verify that Glasgow.tailspintoys.internal is returned as the mail server for the tailspintoys.internal domain.

  9. Type Exit to leave the command prompt.

    Cc505889.Figure_C01624108_15(en-us,TechNet.10).png

    Figure 1-15 Creating an MX record

Lesson Summary

  • Exchange Server 2007 must be installed on a computer running a 64-bit edition of the Windows Server 2003 operating system. The operating system needs to be patched to SP1 or R2.
  • It is necessary to install several software components, some of which must be downloaded from Microsoft’s Web site and some of which can be added using the Add/Remove Programs item prior to installing Exchange Server 2007.
  • The SCW can be used to lock down a computer so that only those services that the computer provides to the network are enabled.
  • The Exchange Best Practices Analyzer can examine your environment for problems that might cause the deployment of Exchange Server 2007 to fail.
  • Exchange servers should be configured with static IP addresses. MX records on the DNS servers should be created and point to the host records of the computers that will host Exchange Server.

Lesson Review

You can use the following questions to test your knowledge of the information in Lesson 2. The questions are also available on the companion CD if you prefer to review them in electronic form.

NOTE Answers

Answers to these questions and explanations of why each answer choice is correct or incorrect are located in the “Answers” section at the end of the book.

  1. Five Windows Server 2003 R2 computers are located at a remote site in your organization. The servers have the following roles:
    • Server A: Domain controller and global catalog server
    • Server B: File and print server
    • Server C: SQL Server 2005 database server
    • Server D: Exchange Server 2007 server
    • Server E: Intranet Server
  2. Server A fails completely and needs to be replaced. It will be several days before you can install a replacement. Although users can currently log on over the WAN, you would like to temporarily promote one of the other servers at the site to act as a domain controller. Which of the following servers can you promote? (Choose all that apply.)
    1. Server A
    2. Server B
    3. Server C
    4. Server D
    5. Server E
  3. Which of the following components need to be installed if an Exchange Server 2007 computer is to be assigned the Mailbox server role? (Choose all that apply.)
    1. COM+ Access
    2. IIS
    3. World Wide Web Service
    4. Windows PowerShell
    5. ASP.NET version 2.0
  4. You are preparing a computer with Windows Server 2003 R2 x64 already installed for the installation of Exchange Server 2007. The Exchange Server will be assigned the Hub Transport server role. Which of the following components must you install prior to performing this deployment? (Choose all that apply.)
    1. Microsoft Core XML Services (MSXML) 6.0
    2. RPC over HTTP Proxy
    3. Microsoft .NET Framework version 2.0
    4. Microsoft Windows PowerShell
    5. MMC version 3.0
  5. Which of the following checks should you perform using the Exchange Best Practices Analyzer prior to deploying Exchange Server 2007 in a new network environment?
    1. Health check
    2. Permissions check
    3. Connectivity test
    4. Baseline
    5. Exchange 2007 readiness check
  6. Which of the following tools can you use to locate the mail servers in a DNS zone?
    1. Ping
    2. Telnet
    3. Pathping
    4. Tracert
    5. Nslookup

< Back      Next >

 

 

© Microsoft. All Rights Reserved.