Microsoft Press 70 284 training kit exchange server 2003 phần 2 potx

2-26 Chapter 2 Planning a Microsoft Exchange Server 2003 Infrastructure F02es10 Figure 2-10 Tracking the progress of the installation Because you performed the pre-installation tasks of running ForestPrep and DomainPrep, Setup will progress quickly to the Microsoft Exchange Messaging and Collaboration Services task after verifying the initial information in Active Directory. If you had not run ForestPrep in advance, Setup would do it for you in the Microsoft Exchange Forest Preparation stage, and it would take just as long as it did when you ran it separately—potentially an hour or more. After Setup fin- ishes its tasks, the installation wizard will display a dialog box informing you that Exchange Server 2003 was successfully installed. 9. Click Finish, and your Exchange server is installed and ready to be configured for use. If a screen still appears prompting you to click Next when the installation is done, do so, and then click Finish. Lesson Review The following questions are intended to reinforce key information presented in this lesson. If you are unable to answer a question, review the lesson materials and then try the question again. You can find answers to the questions in the “Questions and Answers” section at the end of this chapter. 1. You are the administrator of an Exchange 2000 Server organization for the Active Directory domain contoso.com. You want to set up a separate test organization for Exchange Server 2003. You install a Windows Server 2003 server and join it to the domain and then attempt to install Exchange Server 2003 (since it is a test envi- ronment, you run ForestPrep and DomainPrep at the same time that you install the program). However, Setup only gives you the option to join an existing Exchange Server organization. Why? Lesson 3 Performing an Exchange Server 2003 Installation 2-27 2. In which of the following circumstances would you install Exchange Server 2003 into a new organization? (Choose two.) a. Exchange Server 2003 must coexist with Exchange Server 5.5 or Exchange Server 2000. b. You are preparing to migrate from Lotus Notes. c. You are setting up e-mail for a new company that is just opening. d. You already have an existing Exchange Server 2003 organization and need to install a second server to reduce the load on the first server. 3. Which of the following is not a valid Setup switch for Exchange Server 2003? a. /disasterrecovery b. /choosedc c. /? d. /forceremoval e. /noerrorlog f. /noeventlog g. /all Lesson Summary ■ The Microsoft Exchange Installation Wizard allows you to create a new organiza- tion or to join an existing Exchange Server 5.5 organization. ■ Exchange Server 2003 is licensed in Per Seat mode only. ■ Choose an organization name that is reflective of the organization but not so restrictive that a reorganization or other corporate change is likely to make it out of date. ■ Changing the organization name after installation can be accomplished manually with ADSIEdit, but it is not recommended. ■ Setup.exe can be modified with a number of switches to change the way it runs. 2-28 Chapter 2 Planning a Microsoft Exchange Server 2003 Infrastructure Lesson 4: Unattended Setup You’ve now used the Microsoft Exchange Installation Wizard to manually install Exchange Server 2003. In this lesson, you will install a second server into your organi- zation using the unattended method of installation. In the real world, unattended installations are very useful when you need to perform an installation remotely. By supplying someone on site with the installation media and the .ini file for the unat- tended installation, that person can run Setup without any intervention, ensuring that settings are not inadvertently selected or modified. Unattended installations are also useful when you were deploying a number of new Exchange servers in an existing organization. With the ability to also perform unat- tended installations of Windows Server 2003, you can save time deploying multiple servers by automating the entire installation process. After this lesson, you will be able to ■ Create an .ini file for use with an unattended installation ■ Successfully install Exchange Server 2003 using the /unattendfile switch Estimated lesson time: 60 minutes Creating an .ini File for Unattended Setup Creating an unattended installation file can be very useful for deploying Exchange Server 2003. The process of creating the file is essentially the same as the process for a manual setup: selecting the components you want to install and the installation path; choosing whether to create a new organization or to join an existing one; agreeing to the licensing; and so on. However, rather than beginning installation of the compo- nents after you confirm your installation choices on the Installation Summary dialog box, the Microsoft Exchange Installation Wizard writes the configuration to an .ini file, which is a text file formatted specifically for use with the /unattendfile Setup switch. Planning An unattended installation will not eliminate the need for the pre-installation work that is required for installing Exchange Server 2003. You still have to ensure that the Windows server installation has the required components installed and configured to support the Exchange installation. You must meet any requirements, such as permissions, to perform the installation. In this lesson, you will add a second Exchange Server 2003 server to the existing forest and domain. You can also use the unattended installation to create a new organization, which is similar to what you did in Lesson 3 with the manual installation. The only Lesson 4 Unattended Setup 2-29 limitation when creating a new organization with an unattended installation file is that the file is not reusable because Setup would not be able to create the organization on subsequent installations. Therefore, creating an unattended installation file is more use- ful for additional installations after the creation of the organization. Note If you have only a single lab computer to work with, you can alternatively uninstall Exchange Server 2003 and then perform the following steps to create an unattended installa- tion file to use in setting up a new organization. The process would be similar to the manual installation, including choosing the same options. However, this will not allow you to add the server to an existing organization, which is covered in a section and practice later in this chapter. You can choose any name for the .ini file; however, the extension should be .ini. While technically you can use any extension, such as .txt, the format is that of an .ini file and it is recommended to leave the extension as such for consistency. Creating an .ini file for an unattended installation will be covered in the practice at the end of this lesson. Unless there is a specific need for all your unattended installations to have custom components installed, choose a Typical installation. If you change the installation path for Exchange Server 2003, it will apply to all servers on which you run the unattended installation. Plan carefully to ensure that the Windows servers are configured consis- tently with their drives and partitions. When you are deploying a test environment of Exchange Server 2003, it isn’t sufficient to set up a separate lab server in an existing production forest or domain; you must set up a separate Active Directory forest for testing. Otherwise, you may be faced with unwanted forest level settings that are difficult to get rid of when you go to a live deployment of Exchange Server 2003. Exam Tip Watch for exam scenarios where an option is to install a second Exchange Server 2003 organization into an existing forest. Because of the nature of the Exchange Server 2003 integration with Active Directory, a forest can support only a single Exchange organization. When you run Setup and create an Unattend.ini file, you are creating a text file that contains the configuration settings you selected. Since it is a text file, you can view Unattend.ini in Microsoft Notepad. When you do, you’ll see something similar to the following: “This Unattend.ini file was created using a Typical installation onto a new server in an Active Directory domain, which already has another domain controller running an Exchange 2003 organization.” Because you selected a Typical installation, fields for components that aren’t being installed are blank. The [InstallOrder] subsec- tion tells you which components are being installed. ! 2-30 Chapter 2 Planning a Microsoft Exchange Server 2003 Infrastructure Note The following example has been edited for length. The real file is much longer, as you can see by viewing it on your system. [Version] Signature="$Windows NT$" Provider="Microsoft Exchange" [CompleteComponentList] exsetdata.dll srchcomp.dll [PreInstallOrder] gfn_mid microsoft search gfn_mid microsoft exchange gfn_mid microsoft exchange server component gfn_mid microsoft exchange system management tools [InstallOrder] gfn_mid microsoft search gfn_mid microsoft exchange gfn_mid microsoft exchange server component gfn_mid microsoft exchange system management tools [PostInstallOrder] gfn_mid microsoft search gfn_mid microsoft exchange gfn_mid microsoft exchange server component gfn_mid microsoft exchange system management tools [Component Error List] [gfn_mid microsoft search] gfn_pid stockprop hidden=1 [Additional Global Property Names] {DF8FF64A-1967-4871-9E32-CA2F819BAB81},HWNDForLoadingDialog,0,0 [Global Properties] gfn_pid core password= gfn_pid core autologon=0 gfn_pid core autologon previously enabled=0 gfn_pid core user name=Will Willis gfn_pid core organization= gfn_pid core pid 20=111-1111111 gfn_pid core pid 30=J6T48-XCF7K-QCGKD-QV887-4BJYB gfn_pid core license file=eula.txt gfn_pid core suite directory=C:\Program Files\Microsoft Integration gfn_pid core post reboot=0 gfn_pid core suite name=Microsoft Exchange gfn_pid core disk requirement=31457280 gfn_pid core progress show subs=1 gfn_pid core progress show tasks=0 gfn_pid core ask for pre install=0 gfn_pid core ask for post install=0 gfn_pid core suite mode=0 Lesson 4 Unattended Setup 2-31 gfn_pid core suite baseline=0 gfn_pid core install scenario baseline=0 gfn_pid core force disk space ok=0 gfn_pid core ignore final disk space check=0 gfn_pid core registry=Software\Microsoft\Microsoft Integration\3D5A0E1C-B6DA-42a7-A871- 03CD2E30FEA3\SetupData gfn_pid core no error log=0 gfn_pid core no event log=0 gfn_pid core system drive=C: gfn_pid core program files=C:\Program Files\ gfn_pid encrypted mode=0 {E0C022B6-2029-11D3-8DFC-00C04F797FB8}=10 {CDD00162-2E69-11D3-A829-00C04FB1799F}=3D5A0E1C-B6DA-42a7-A871-03CD2E30FEA3 {CDD00163-2E69-11D3-A829-00C04FB1799F}= {AA62DF98-3F2C-11D3-887B-00C04F8ECDD6}=0 {F24FCE05-8B5C-472F-9F53-9C9BB3DE50AF}=7 gfn_pid core dont install suite files=0 {9843461C-2F7A-4000-B91C-2DDD224C9E91}=c:\Unattend.ini {DF8FF64A-1967-4871-9E32-CA2F819BAB81}=0 [Scenario Factory] ActiveScenario={8BED5C7A-CDC9-11D2-92F4-00C04F79F1A8} You can edit this file manually to make changes to the installation behavior, such as if you want Setup to install the server into a specific administrative or routing group. Other options you might configure are those under the [Global Properties] subsection, such as changing the installation path. If you do edit the file, ensure that Notepad doesn’t add a .txt extension when you save the file. Performing an Unattended Installation of Exchange Server 2003 Using an unattended installation .ini file is a matter of using the /UnattendFile Setup switch with the correct Unattend.ini file. The following command line is an example of starting an unattended installation with the Unattend.ini file on a floppy disk in drive A and the Exchange Server 2003 CD in the D drive: D:\setup\i386\setup.exe /unattendfile a:\unattend.ini After executing the command, Setup will run without any input required. It is not a “silent” installation without user interface displayed; the progress window opens, and you can see the installation tasks being performed. Unlike a manual installation, Setup will not prompt you when it is finished installing Exchange Server 2003. Setup quits automatically when complete. Practice: Performing an Unattended Installation of Exchange Server 2003 In this practice, you will create a file named Unattend.ini and then install Exchange Server 2003 using the file. The procedure will result in a second Exchange 2003 server being installed in your organization. 2-32 Chapter 2 Planning a Microsoft Exchange Server 2003 Infrastructure Exercise 1: Create an Unattend.ini Configuration File 1. From the Start menu, click Run and type the following command (substitute the drive letter for your CD-ROM drive if it is not D, and substitute C:\ with the path to your unattend.ini file if it is different): D:\setup\i386\setup.exe /createunattend c:\Unattend.ini The Microsoft Exchange Installation Wizard starts as if you ran Setup.exe without any switches. 2. At the Welcome page, click Next, accept the license agreement, and then click Next to open the Component Selection page. 3. In the Action column for the Microsoft Exchange component, click Typical, and then click Next. 4. If the Installation Type page is displayed, select Join Or Upgrade An Existing Exchange 5.5 Organization, and then click Next. Whether you have the option of choosing to create a new Exchange organization or upgrade to or join an existing Exchange organization depends on whether Setup detects an existing Exchange organization in the forest. If Setup detects an existing Exchange organization, it will automatically default to joining an existing organization and will not prompt you to choose. This is because an Active Direc- tory forest can support only a single Exchange organization. 5. Review the Installation Summary, and then click Next. 6. Accept the licensing agreement and click Next to finish. Setup writes your choices into a configuration file with the path you specified and displays a message stating that Setup completed successfully. Exercise 2: Perform an Unattended Installation of Exchange Server 2003 1. From the Start menu, click Run and type the following command (change drive D to match your CD-ROM drive letter, and change drive C to match the location where you have stored the unattended installation file, if necessary): D:\setup.i386\setup.exe /UnattendFile c:\Unattend.ini 2. Monitor the installation, seeing that Setup utilizes the custom settings from the Unattend.ini file, including installing the Microsoft Exchange 5.5 Administrator program. After Setup completes, from the Start menu, point to All Programs, then point to Microsoft Exchange, and start Exchange System Manager. View the organization in Exchange System Manager, verifying that the new server is installed into the orga- nization by expanding the Servers container. Quit the program. Lesson 4 Unattended Setup 2-33 Lesson Review The following questions are intended to reinforce key information presented in this lesson. If you are unable to answer a question, review the lesson materials and try the question again. You can find answers to the questions in the “Questions and Answers” section at the end of this chapter. 1. You are attempting to create a file called Unattend.ini in order to automate the deployment of Exchange Server 2003 servers in your organization. You cur- rently do not have an Exchange Server 2003 organization. You run Setup with the /createunattend switch and create the Unattend.ini file, which works perfectly when you install your first Exchange Server 2003 server. However, subsequent installations to servers in the same domain fail using the Unattend.ini file. Why might this be happening? 2. You are the Exchange administrator for a single-forest/single-domain organization that spans three locations. You create an Unattend.ini file for use in deploying additional Exchange Server 2003 servers in your Exchange organization, which already consists of two Exchange Server 2003 servers at the main location. The other two locations have junior administrators who have been delegated the abil- ity to administer accounts and computer objects in the domain, which they normally do by logging on to their local domain controllers. You verify that the necessary Windows components are installed on the remote servers to support Exchange Server 2003, copy the Unattend.ini file to the local hard drive on each server, and create a batch file for the local junior administrators to run on their server once they insert the Exchange Server 2003 installation CD that executes Setup with the required /unattendfile Setup switch. One junior administrator runs the batch file, and Exchange Server 2003 Setup completes successfully. The other junior administrator calls you and tells you that Setup failed. Why might that have happened? 3. Identify the two things that are incorrect about the following command line: d:\setup\i386\setup.exe /createunattendfile unattend.txt 2-34 Chapter 2 Planning a Microsoft Exchange Server 2003 Infrastructure 4. You have been asked to coordinate the installation of Exchange Server 2003 on servers at six remote offices. The personnel performing the installation are with a consulting firm, and you won’t be physically present during the installations. You want to limit their access to the organization’s sensitive security information, yet allow the consultants to successfully install the product. Describe how you will meet these requirements. Lesson Summary ■ Unattended installations are useful for rapidly deploying subsequent Exchange Server 2003 installations into an existing organization. ■ Unattended installations are great for delegating the task of installing the Exchange Server 2003 binaries to a lower-level IT professional or for deploying Exchange Server 2003 at a remote location. ■ Performing an unattended installation is subject to the same prerequisites (permis- sions, Windows components, and so on) as performing a manual installation. ■ An Active Directory forest can support only a single Exchange Server 2003 organi- zation, so an Unattend.ini file that is used to create an organization cannot be used for subsequent installations. ■ An Unattend.ini file is a specially-formatted text file that can be read and manually edited in Notepad after its creation, if changes are necessary. Lesson 5 Removing an Exchange Server 2003 Server from an Organization 2-35 Lesson 5: Removing an Exchange Server 2003 Server from an Organization Certain situations may require you to remove a server from an Exchange organization, such as retiring an aging server in favor of a newer and faster server or phasing out a previous version of Exchange that has been migrated to Exchange Server 2003. In this lesson, you will learn how to remove an Exchange Server 2003 server from an Exchange organization. After this lesson, you will be able to ■ Remove an Exchange Server 2003 server from an organization using the Microsoft Exchange Installation Wizard ■ Forcibly remove an Exchange Server 2003 server from an organization Estimated lesson time: 30 minutes Removing an Exchange Server 2003 Server Using the Microsoft Exchange Installation Wizard The usual way to remove an Exchange Server 2003 server from an organization is with the Microsoft Exchange Installation Wizard. This is the preferred removal method because Setup is able to read and write information to Active Directory and to remove all references to the server. However, to use the Microsoft Exchange Installation Wiz- ard, there are some prerequisites that must be met. ■ You must move all mailboxes to another Exchange server in the organization or remove them from each user account. ■ The server must not be a bridgehead server or routing group master. If it is, the role must first be transferred to another Exchange server in the routing group. ■ The server must not be a part of any connection agreements. ■ The server must not have any connectors installed and in use. If you attempt to set the Microsoft Exchange component to Remove in the Microsoft Exchange Installation Wizard, and your server does not meet the prerequisites, Setup displays an error message advising you of the problem. Figure 2-11 shows an example of an error when there are user mailboxes on the server that you are trying to remove. [...]... Windows 20 00 Server SP3 or later or on Windows Server 20 03 Not all functionality is available when Exchange Server 20 03 is installed on Windows 20 00 Server ■ Exchange Server 20 03 is the only version that can run on Windows Server 20 03 ■ Prior to deploying the Exchange Server 20 03 application, you must first prepare Active Directory by running ForestPrep and DomainPrep ■ An Exchange Server 20 03 server. .. of Exchange Server 20 03? (Choose all that apply.) a Windows NT 4 b Windows NT 4 SP6a c Windows 20 00 Server SP1 d Windows 20 00 Server SP3 e Windows 20 00 Server SP4 f Windows Server 20 03, Standard Edition g Windows Server 20 03, Enterprise Edition h Windows Server 20 03 SP1 The correct answers are d, e, f, g, and h 2- 48 Chapter 2 Planning a Microsoft Exchange Server 20 03 Infrastructure 4 You install Exchange. .. World Microsoft Exchange Server 20 03 Services and Server Reboots Anyone who has administered a version of Microsoft Exchange Server in the real world knows that rebooting a server running Exchange Server, whether on Microsoft Windows NT 4, Windows 20 00 Server, or Windows Server 20 03, can take much longer than normal Exchange Server 20 03 is no different, and if it is installed on a Windows Server 20 03 server. .. protocol Microsoft Exchange Routing Engine Provides topology and routing information to Exchange Server 20 03 servers If this service is stopped, optimal routing of messages will not be available Microsoft Exchange Site Replication Service Allows Exchange Server 20 03 to coexist in an Exchange Server 5.5 site by presenting the Exchange Server 20 03 server as an Exchange Server 5.5 directory service to other Exchange. .. the Exchange Server 20 03 installations Requirement 1 The first requirement involves installing Exchange Server 20 03 on 10 servers at the corporate office 1 Describe how you would deploy the 10 servers in a way that is consistent and efficient 2- 42 Chapter 2 Planning a Microsoft Exchange Server 20 03 Infrastructure 2 Which of the following tasks must you perform on each server prior to installing Exchange. .. an Exchange Server organization 2 In which of the following circumstances would you install Exchange Server 20 03 into a new organization? (Choose two.) a Exchange Server 20 03 must coexist with Exchange Server 5.5 or Exchange Server 20 00 b You are preparing to migrate from Lotus Notes c You are setting up e-mail for a new company that is just opening d You already have an existing Exchange Server 20 03. .. the installation wizard to remove the Exchange Server 20 03 installation, and monitor its progress as it runs through the steps Quit the installation wizard when it completes 2- 38 Chapter 2 Planning a Microsoft Exchange Server 20 03 Infrastructure Exercise 2: Forcibly Remove Exchange Server 20 03 from an Organization 1 Disable all Microsoft Exchange services on the server, and then delete the following... an Exchange Server 20 03 server ForestPrep creates the attributes and classes that define Exchange Server 20 03 objects, such as mailboxes, and extends Active Directory so that existing objects gain Exchange Server 20 03 functionality DomainPrep DomainPrep is a Setup switch that makes changes to a domain to support an Exchange Server 20 03 installation DomainPrep creates two security groups when run, Exchange. .. Directory data As an added benefit of this approach, servers 2 through 10 could all be installed simultaneously, dramatically reducing the time it takes to deploy the Exchange Server 20 03 servers Questions and Answers 2- 53 2 Which of the following tasks must you perform on each server prior to installing Exchange Server 20 03 on Windows Server 20 03 servers in the contoso.com domain? (Choose all that... to Exchange Server 20 03 Management wants a clean start on the new e-mail organization ■ Requirement 2 The server group has already purchased the servers for deployment of Exchange Server 20 03 and placed them at each location The servers have state-of-the-art hardware and are installed with Windows Server 20 03, Enterprise Edition and configured as member servers in the appropriate domains Windows Server . install Exchange Server 20 03 using the file. The procedure will result in a second Exchange 20 03 server being installed in your organization. 2- 32 Chapter 2 Planning a Microsoft Exchange Server 20 03. of Exchange Server 20 03 1. Log on to the Exchange Server 20 03 server that you configured the mailbox on, and run Setup from the Exchange Server 20 03 installation CD. 2. Proceed through the Microsoft. when it completes. 2- 38 Chapter 2 Planning a Microsoft Exchange Server 20 03 Infrastructure Exercise 2: Forcibly Remove Exchange Server 20 03 from an Organization 1. Disable all Microsoft Exchange services