Mastering Microsoft Exchange Server 2003 phần 3 ppsx

Directory on a newly installed Windows 2003 server. Then, after you upgrade each NT domain to a Windows Server 2003 domain, which brings NT 4 information into Active Directory, you use ADACUW to merge the two kinds of information in Active Directory. Until you upgrade an NT 4 domain, the Exchange 5.5 information lies in a dormant or disabled object. With the upgrade, an enabled user object is created for each user in the upgraded NT 4 domain. ADACUW merges the disabled and enabled objects, creating fully functional Active Directory users. Active Directory Population Strategy #4 This strategy is similar to the third strategy, but you dont create the second domain by upgrading an NT 4 domain controller. Instead you use ADMT to clone accounts from the NT 4 domain into a transition domain: Install Windows Server 2003 from scratch, creating a new Windows Server 2003 domain.1. Synchronize Exchange 5.5 with Active Directory on the new Windows 2003 server using Active Directory Connector, thereby creating disabled user objects that contain Exchange information. 2. Create a transition Windows Server 2003 domain, and use the ADMT to clone Windows NT user accounts into Active Directory in the transition domain. 3. Use the ADACUW to merge the Active Directory Connectorcreated accounts with cloned accounts.4. See Figure 6.11 for a graphic view of the fourth directory population strategy. Heres how it works: In this strategy, you create two domains in the same forest by installing Windows Server 2003 from scratch on two different computers. Then you use the Active Directory Connector to create disabled Exchange 5.5 user information in the first domain. You also use the ADMT to clone NT 4 users into the second (transition) domain. Because the two domains are in the same forest (Active Directory), you can then run the ADACUW to merge Exchange 5.5 and NT 4 information. Figure 6.11: Active Directory population strategy #4 Active Directory Population Strategy #5 This is the last strategy for populating Active Directory. Like the first two strategies, this one uses a single Windows Server 2003 domain: More Complex Upgrades from Windows NT 4to2003 and Exchange 5.5to2003 132 Install Windows Server 2003 from scratch, creating a new Windows Server 2003 domain.1. Synchronize Exchange 5.5 with Active Directory on the new Windows 2003 server using ADC, thereby creating disabled user objects that contain Exchange information. 2. Enable the user objects created from Exchange 5.5 information in Active Directory by ADC.3. Use the ADMT to match user objects in the new Windows 2003 domains Active Directory to existing NT 4 accounts. 4. Figure 6.12 shows the fifth Active Directory population strategy. In this strategy, you enable the user objects created from your Exchange 5.5 environment by the Active Directory Connector. Because user objects have been enabled, NT 4 information is merged with Exchange 5.5 information in Active Directory through the use of the ADMT. Figure 6.12: Active Directory population strategy #5 You enable a disabled user object through the Active Directory Users and Computers snap−in for the Microsoft Management Console. Find the user in the Users subcontainer; right−click the user, and select Enable Account. Thats it. (You can also enable user objects by updating the Active Directory schema, but that is something you dont want to get into unless you really know what youre doing.) Do You Need a Group Management Domain? Before we finish with Active Directory population strategies, we should talk about one other issue. Exchange 5.5 distribution lists can be used to send messages to a group of recipients. They can also be used to control access to Exchange resources such as public folders. If you use distribution lists for this latter function, you might have a bit of a problem in Exchange Server 2003. With Exchange Server 2003, you can control access to Exchange resources only by using Windows 2003 universal security groups. When you run the Active Directory Connector with a connection agreement between an Exchange 5.5 server and a Windows 2003 domain at the Windows Server 2003 functional level, Exchange 5.5 distribution lists serving an access control function in Exchange 5.5 become universal security groups in Windows 2003. As such, you can use these groups for Exchange Server 2003 access control. Unfortunately, universal security groups are available only when a Windows 2003 domain is running at the Windows Server 2003 functional level. So, if youre all switched to this level, all is well. If youre not, you have to run what Microsoft calls a group management domain. A group management domain is a Windows Server 2003 domain running at the Windows Server 2003 functional level. More Complex Upgrades from Windows NT 4to2003 and Exchange 5.5to2003 133 Remember that you need a group management domain only if you want to continue using distribution listlike management of access to Exchange resources. You could also use Windows 2003 local or global domain groups. Note, however, that using local or global groups for this function requires more time and effort, and might require more involvement by Windows 2003 networking managers outside your group of Exchange managers. If you opt for a group management domain, you need to set up a Windows Server 2003 domain and switch it to the Windows Server 2003 functional level. Before you upgrade any Exchange 5.5 servers, you also need to set up one or more Active Directory Connector connection agreements between your new Windows 2003 group management domain and NT 4 domains containing the Exchange 5.5 servers. Yes, Active Directory Connector can run in a Windows Server 2003 domain at the Windows Server 2003 functional level. If you decide to use the fourth Active Directory population strategy and you can switch the transition server domain to the Windows Server 2003 functional level, youre in luck. You can use the transition domain as your group management domain. Exchange Server 5.5 Upgrade Strategies for More Complex Exchange 5.5 Environments Upgrading Exchange 5.5 servers to Exchange 2003 is pretty much done as it is with the simple upgrade I discussed earlier. Basically, you install Windows 2003 (or upgrade to it, if its not supporting Exchange 5.5). Then you go through the Exchange 2003 server installation/upgrade process as per my discussion of a simple upgrade. With more complex Exchange environments, you might want to consider consolidating two or more Exchange 5.5 servers on a single Exchange 2003 server. Youll need quality server hardware, good CPU horsepower, more RAM memory, and solid, higher−speed disk drives, but like Windows 2003, Exchange 2003 is designed to support lots of users. So, go for it. Exchange 5.5/2003 Coexistence Active Directory Connector allows Exchange 5.5 servers and Exchange 2003 servers to coexist. In most cases, coexistence is required only long enough to upgrade all Exchange 5.5 servers to 2003 status. However, I have worked in situations where coexistence was a long−term thing. For example, your Exchange 5.5 organization might include some sites that lack adequate technical or financial resources to permit an upgrade to Windows 2003 and Exchange 2003. The nice thing about the upgrade paths that Microsoft has architected for Exchange is that everything will work pretty well, whether short− or long−term coexistence is necessary. Summary Whew! That really was hell. Just kidding. (I think.) In this chapter, we focused on upgrade issues. First we looked at upgrades from Windows 2000 to Windows 2003 and from Exchange 2000 to Exchange 2003. These upgrades are pretty much no−brainers, though you do have to be sure that forest and domain data in Active Directory for both Windows 2003 and Exchange 2003 are properly upgraded. Next, we took a long, hard look at the upgrade process from NT Server 4 to Windows Server 2003. Then we walked the upgrade path from Exchange Server 5.5 to Exchange Server 2003. We discovered that Exchange 2003 upgrades are intimately linked to Windows 2003 upgrades. We also discovered that, except for the fact More Complex Upgrades from Windows NT 4to2003 and Exchange 5.5to2003 134 that you cant do an in−place Exchange 5.5to2003 upgrade, upgrades from NT 4 to Windows 2003 are more difficult than Exchange 5.5to2003 upgrades. Upgrades from NT 4 to Windows 2003 begin with a clear mapping between your current NT 4 domain structure and your future Windows 2003 domain structure. There is nothing to stop you from mapping any of the four NT 4 domain models to a nearly parallel Windows 2003 domain model. However, the preferred approach is to create a single Windows 2003 domain that incorporates all your NT 4 domains. Windows 2003 includes features that make this process easier such as sites and organizational units. Also, when upgrading from NT 4 to Windows 2003, you must select from among the three flavors of Windows Server 2003: Standard, Enterprise, and Datacenter Edition. And you must select carefully, remembering to keep the power of Windows 2003 Server editions in line with the Exchange Server 2003 youll be using. You must also ensure that your servers hardware is adequate to support the Windows 2003 software that youll be installing and that all the software on the server is compatible with Windows 2003. In addition, you must create an upgrade plan that takes into account the specifics of your NT Server 4 environment, the Windows 2003 domain model that youre shooting for, and the process of getting from NT 4 to Windows 2003 without risking a large amount of downtime. As with Windows 2000toWindows 2003 upgrades, you need to upgrade your forest and the domain in which youre installing Windows 2003. And, unlike a Windows 2000toWindows 2003 upgrade, depending on how you upgrade to Windows 2003, you might have to replicate NT 4 account and other security information into Active Directory. You must complete a number of tasks to upgrade Exchange 5.5 environments to Exchange 2003. Fortunately, Microsoft developed and provides a set of mandatory Exchange Deployment Tools that walk you through the upgrade process. You must run all of the tools or you wont be able to install Exchange 2003. Steps in an Exchange upgrade include an assessment of your network and servers, preparation of your Windows 2003 forest and domain or domains for an Exchange 2003 installation, and installation of Active Directory Connector to import Exchange 5.5 directory information into Windows 2003s Active Directory. Now were ready to move on to the hands−on part of this book. Well begin by installing and using Windows Server 2003 and Exchange Server 2003. Even though Chapters 7 and 8 dont include specific upgrade information, you should read both chapters carefully. Why? See the introduction to Part II, Installation. More Complex Upgrades from Windows NT 4to2003 and Exchange 5.5to2003 135 Part 2: Installation Chapter List Chapter 7: Installing Windows Server 2003 as a Domain Controller Chapter 8: Installing Exchange Server 2003 136 Chapter 7: Installing Windows Server 2003 as a Domain Controller Overview This is a dual−purpose chapter. First, its designed to help you install Windows Server 2003 as a domain controller that fully supports network login, access to various resources, DHCP, and DNS. Second, this chapter is designed to help you install a stand−alone Windows Server 2003. It assumes that you will install a Windows 2003 domain controller first and then, in conjunction with reading Chapter 8, Installing Exchange Server 2003, install a stand−alone server on which you will install and run Exchange Server 2003. I have constructed this chapter so that you know when Im talking about installing a domain controller and when Im talking about installing a stand−alone server. I use warning notes to call your attention to critical points at which you take one path if installing a domain controller and another path if installing a stand−alone server. Note This is ultimately a book about Exchange Server 2003. So, its not possible for me to cover everything about Windows Server 2003 in great detail. For more, check out Mastering Windows Server 2003, by Mark Minasi, Christa Anderson, Michele Beveridge, C.A. Callahan, and Lisa Justice (Sybex, 2003). In this chapter, I presume that youll be installing Windows Server 2003 on a computer with nothing on it that you want to preserve. For example, I assume that you dont need to upgrade an NT 4 or Windows 2000 server to Windows Server 2003 and preserve the software that youve installed under the existing operating system. If you need to upgrade an NT 4 server, see Chapter 6, Upgrading to Windows Server 2003 and Exchange Server 2003. Windows Server 2003 installation is a multi−step process. These steps are listed at the start of this chapter, and well look at each of these steps in detail. Warning Things are likely to change by the time you read this book. The Internet and the high−speed, high−pressure marketing and software delivery channels that it has fostered make unending, unpredictable, and incredibly quick software modification not only possible, but also economically necessary for vendors. Before you install Windows Server 2003, check the Web to be sure that a new service pack isnt available for the product or that you dont have to do something new and special when installing Windows Server 2003, if you plan to install Exchange Server 2003. The best websites are www.microsoft.com/ windows2003 (or, as time passes, www.microsoft.com/windows) and www.microsoft.com/exchange for updates. You can also update Windows 2003 directly over the Internet. Just select the Windows Update option on the Start menu. The system can even check for new updates and let you know when an update is available. This is a really neat capability. Have you ever gone on the Alice in Wonderland ride at Disneyland? It starts by taking you down a rabbit hole, with Alice saying, Here we gooooooooooooooooooo. That extended go fades away toward the end, adding to the rides excitement and sense of entering the unknown. Like Alice, were about to embark on a wild and exciting adventure. I promise to do all I can to make our hands−on trip through Windows and Exchange 2003 interesting, productive, and funbut a little less bumpy, arbitrary, and confusing than Alices sojourn through Wonderland. Lets go. Featured in this chapter: Setting up server hardware• Installing Windows Server 2003 software• 137 Configuring your first Windows 2003 server• Using Microsoft Management Console• A quick look at Active Directory• Configuring DHCP and Dynamic DNS• Configuring unallocated disk space• Installing an uninterruptible power supply• Setting up a Windows Server 2003 backup• Setting Up Server Hardware Setting up the hardware is a pretty straightforward process. First, you pick a server platform and outfit it with various components. Then you test its memory, disk drives, and other hardware to ensure that everything is working well. From a hardware perspective, Windows Server 2003 is much easier to install than NT 4. Running on a modern plug−and−play PCI busbased computer, with PCI adapters and its own Windows XP like plug−and−play capabilities, Server 2003 automatically recognizes and installs hardware drivers. In such an environment, you rarely have to manually configure video, SCSI, modem, or other adapters. That alone is almost worth the price of admission to Windows Server 2003. Warning Throughout this chapter and in Chapter 8, I assume that the first Windows Server 2003 that you will install will be a domain controller. I also assume that you will not run Exchange Server 2003 on this computer. When we get to Chapter 8, well install Exchange on another Windows 2003 server, a stand−alone Windows Server 2003 that isnt a domain controller. If youre hard−pressed for hardware, for testing purposes, you can try installing Exchange on a Windows 2003 domain controller. However, I join Microsoft in strongly recommending against doing this in a production environment, no matter how powerful you might think your computing hardware is. In this chapter, youll learn how to install Windows 2003 as both a domain controller and a stand−alone server. Ill use a warning note like this one at the beginning of sections of this chapter where you should do things differently depending on whether youre installing a domain controller or a stand−alone server. What to Buy Microsoft publishes a hardware compatibility list for its Windows products. The HCL names the components that work with Windows Server 2003 and other Windows−based operating systems. You can find this list on the Web at www.microsoft.com/hwdq/hcl/. Before you buy anything, consult this guide. One crucial bit of advice: Dont be cheap! Lots of vendors sell components such as SIMMs, DIMMs, disk drives, motherboards, and CPUs at unbelievably low prices. Dont bite. Trust me on this one: Ive been through the mill with cheap, flaky components. Windows Server 2003 all by itself can beat the living daylights out of a computer. Add Exchange Server 2003, and youll pay back in your own sweat and time every penny and then some that you saved by buying cheap. Buy from stable, long−lived vendors at reasonable but not fairy−tale prices. RAM for a Windows Server 2003 should always be ECC−type. Quality components cost a little more but are well worth the money. Nuff said. Setting Up Server Hardware 138 Getting Server Components in Order In Chapter 5, Designing a New Exchange 2003 System, I wrote of my computer of choice for running Exchange Server 2003: 1GHz Pentium III or 4 or Xeon machine with 768MB of memory and at least two 9GB SCSI hard drives. Thats pretty much my recommendation for an Exchange−less Windows 2003 domain controller in a serious networked computing environment. Ideally, Id like to see you use a dual−processor machine with 1GB of RAM memory and at least 60GB of RAID 5 disk storage for your domain controller. If youre just going to test Windows 2003 and promise not to put your test configuration into production, you can use a somewhat lesser hunk of hardware than the one that I tout. Id recommend, at minimum, a 800MHz Pentium PC with 512MB of RAM and a 40GB or so IDE or SCSI hard disk. I suggest that you outfit your system with a high−resolution VGA display adapter, at least a 17− inch monitor, a 24−speed or faster CD−ROM drive, two or more serial ports, two or more USB ports, a mouse, and one or more network adapters. Regarding the serial and USB ports, you need one serial or USB port to interface your Windows Server 2003 to an uninterruptible power supply (UPS). This assumes that you are not using a UPS that communicates with servers using the TCP/IP protocol, which is the method of choice for connecting very large, very high−capacity UPSs to the servers they protect. You also might want to use a serial port for a mouse. If you plan to provide Microsofts Remote dial−up access to your Windows Server 2003 users, use a PS/2 mouse port to free a serial port for dial−up. If you need a lot of dial− up ports, look at multiport boards from companies such as Digi International (www.dgii.com). Testing Key Components The networking services provided by a Windows 2003 server are critical applications. You should also consider fault−tolerant hardware, as discussed in Chapter 5. But even before you consider this option, you should be sure that everything in your server is working properly. Youll want to test five key components as soon as your server is in−house: Memory• Hard disks• CD−ROM drives• SCSI controllers• Network adapters• Good memory and disk tests are time−consuming. Testing out the high−end computer that I recommend could take a week or more. Dont let that deter you, though. You want to be sure that youve got a solid platform under your organizationif for no other reason than that youll sleep better at night. During Windows Server 2003 installation, the system is automatically configured for a variety of hardware options, so you should be sure that all your hardware is working during the installation process. For this reason, youll want to test your CD−ROM drive, SCSI controllers, and network adapters before installing Windows Server 2003. Test all these together to be sure that no IRQ, I/O address, or DMA conflicts occur, although this should be less of a problem if your computer and adapters support plug−and−play hardware. It should go without saying, but Ill say it anyway: Dont consider your testing phase finished until all components pass the tests you set out for them. Now lets start testing: Getting Server Components in Order 139 Testing memory Because the quick boot−up memory test on Intel−based PCs cannot find most memory problems, use Smith Micro Softwares CheckIt (www.smithmicro.com/checkit/) or PC− Doctors PC−Doctor for DOS (www.pc−doctor.com) to test memory. You should run either of these programs from DOS with no memory manager present, and run the complete suite of tests in slow rather than quick mode. Testing hard disks There are two kinds of software−based hard disk testers: those that write one pattern all over the disk and then read to see whether the pattern was written correctly (MS− DOSs SCANDISK is such a tester), and those that write a range of patterns and test to see whether each was properly written. Youll want a multipattern tester because it is more likely to find the bit−based problems on a disk. SpinRite from Gibson Research (http://grc.com/ default.htm) is a good multipattern tester that can find and declare off−limits any bad areas on the disk that the manufacturer didnt catch. Testing CD−ROM drives I test my CD−ROM drives in DOS using MSCDEX.EXE and the DOS driver for the drive. If I can do a directory (DIR) on a CD−ROM in the drive that Im testing and copy a file or two from the CD−ROM, I assume that its working well enough to move on to Windows 2003 installation. Testing SCSI controllers If you tested your hard drives as suggested previously, youve also tested their controllers, at least in isolation from other adapters. Just be sure to run your tests again with active CD−ROM drives and network cards to ensure that no adapter conflicts are lurking in the background just waiting to mess up your Windows Server 2003 installation. Tip If youve got enough hardware, you might want to run your RAM and disk tests simultaneously. This will cut down on testing time somewhat. Testing network adapters I never install a machine that will be networked without making sure that it can attach in MS−DOS mode to a server. I use Microsofts NDIS drivers. Make sure to connect your LAN−side adapter to your network before you begin installing Windows 2003. If youre going to connect your server both to your LAN and directly to the Internet without an intervening firewall, I strongly suggest that you install only the LAN−side network adapter before installing Windows 2003. That way, theres no chance that the adapter might be accidentally activated by Windows Plug−and−Play hardware system when you first boot up after installing Windows 2003. This could expose your server to the Internet and its seemingly endless threats to computer security. While Im strongly urging you to do things, let me almost insist that you put your server behind a firewall. Ill talk more about how you do this in Chapter 18, Exchange Server System Security. Warning Use solid, top−name brand server−quality adapters. Ive seen a lot of workstation−quality adapters from second−level name−brand vendors such as LinkSys and D−Link permanently or temporarily go south at the worst times. Youre better off with cards from vendors such as 3Com. I like the 3C905CX−TX adapters. Ive experienced breakdowns with these cards, but far less frequently than with the others. And dont think you need good adapters only for Internet connections. Windows 2003 servers need LAN access too, and Exchange 2003 cant function at all without access to domain controllers, which should be on the LAN side. Getting Server Components in Order 140 Installing Windows Server 2003 Software As with setting up hardware, installing Windows Server 2003 is fairly straightforward. If youve read Part I, Understanding and Planning, you should encounter no surprises. Well go through all the steps that you take to get Windows Server 2003 up and running. Id love to show you all the screens that youll see during installation. However, because no operating system is yet in place, theres no way to capture these screens. Rest assured that each step discussed here parallels a screen that youll see during installation. Later in this chapterafter weve got Windows Server 2003 installedIll show you enough setup screens to make up for the early deficit. Tip My first encounter with the Windows Server 2003 documentation was pretty scary. I nearly panicked when I saw nothing about choosing whether a new server was to be a domain controller or a stand−alone server. After all, this was a major and irrevocable decision point in the installation of an NT 4 server. My discomfort subsided when I realized that Windows 2003 servers become domain controllers after, not during, initial installation. So, relax and track through the initial installation process with me. After that, well turn our newly installed server into a domain controller. Starting the Installation Now Im going to discuss how to install Windows Server 2003 Enterprise Edition. If youre installing this product or the Datacenter Edition, your experience will be pretty much the same as what I show you here. To make things a bit easier, Ill refer to the product that were installing as Windows Server 2003. Windows Server 2003 comes on a CD−ROM. Insert the CD in the CD−ROM drive, and boot your computer. The Windows 2003 Setup program will start automatically. The first notable thing youll see is a blue screen with Windows Setup displayed in white letters at the top of the screen. At the bottom of the screen, you are offered an opportunity to load drivers that arent on the Windows 2003 CD. If you need such drivers, insert the disk containing them and press F6. After the drivers are loaded from the disk, youll see the message Setup is loading files, along with text in parentheses indicating which file is being loaded. Windows 2003 is loading files into RAM memory at this point. These files support the installation of Windows 2003 itself, as well as a variety of disk drives, CD−ROM drives, SCSI and RAID devices, video adapters, file systems, and so on. Windows 2003 will use these drivers during the setup phase. All this takes some time, from 1 to 5 minutes, so be patient. Next you have the option of installing Windows 2003 or exiting the Setup program. Press Enter to continue with the installation. The following screen lets you set up Windows 2003, repair an existing Windows 2003 installation, or quit Setup. Press Enter to select the first option to begin installation. When the licensing dialog box pops up, page down through the licensing agreement and press F8 to agree to the conditions of the license. F8 doesnt show up on the screen until youve paged all the way down to the end of the license. Preparing Disk Partitions Next, Setup shows you the unpartitioned space on the hard disk drives that it detected and asks how you want to set up your partitions and where you want to install Windows Server 2003. If youve worked with NT 4 or DOS disk partitions, what follows should be pretty familiar. You can choose to set up partitions of any size, up to the capacity of a disk drive. I recommend setting up a minimum 10GB partition for the Windows Server 2003 operating system. Installing Windows Server 2003 Software 141 [...]... in this book, your Exchange 20 03 server will not become a part of your DNS domain and will thus not be available to users trying to open their mailboxes, or to other servers trying to send mail to your Exchange server In Chapter 8, youll install a Windows 20 03 stand−alone server and then install Exchange Server 20 03 on it Before installing Windows 20 03 on your soon−to−be Exchange server, you must set... Figure 7.15 shows IIS 4/ Microsoft Transaction Servers MMC Figure 7.16 shows Windows Server 2003s MMC No snap− ins have been installed in the Windows 20 03 MMC Well do that soon Figure 7.15: Microsoft Management Console for Internet Information Server 4 and Microsoft Transaction Server Figure 7.16: Windows Server 2003s Microsoft Management Console Lets focus on the Windows 20 03 MMC shown in Figure 7.16... the Windows 20 03 CD is inserted As I noted earlier, when Windows 20 03 reboots after installation is complete, the Manage Your Server Wizard opens Figure 7.1 shows the wizard To begin configuring your first Windows 20 03 server, click the green button with the arrow on it next to Add or Remove a Role Figure 7.1: The Windows Server 20 03 Manage Your Server Wizard This opens the Configure Your Server Wizard... purchased after your Windows Server 20 03 is up and running If you dont, users and other systems wont be able to connect to the server Computer Name and Administrator Password The wizard next asks you to name your Windows 20 03 server and suggests a name If you like the name, fine If not, change it If youll be running Exchange 20 03 on this server, the name should follow the Exchange Server naming scheme that... this server wont be running Exchange, use whatever naming scheme youve chosen for non Exchange servers Im naming my first server BG01 Following my own advice, this server wont run Exchange 20 03; itll be a domain controller running Active Directory, DHCP, and DNS Thats more than enough for one server The name can be up to 63 characters long If this computer will interact with nonWindows 2000/ 20 03 clients,... internal network Assuming that NetBIOS and WINS are not installed, local computers use the Windows 20 03 DNS to find each other This applies not just to a computer finding, say, an internal web server, but to one Windows 20 03 server finding another server for Windows 2003based interaction So your Windows 20 03 DNS servers have to be able to resolve internal name resolution requests But computers on your network... you need a NetBIOS domain name so that your server can communicate with nonWindows 2000 /20 03 servers such as Windows NT 4 Unless you have strong objections, accept the name offered (see Figure 7.6) 148 Configuring Your First Windows 20 03 Server Figure 7.6: Selecting a NetBIOS domain name using the NetBIOS Name page of the Windows Server 20 03 Configure Your Server Wizard The next wizard page is wonderful... server on which youll install Exchange Server 20 03, read through this section, but dont try to do the hands−on setup work Well set up Microsoft Management Console for your Exchange server in the next chapter Youve just installed some pretty neat software To view the fruits of your labor, you need to use some of the tools that Microsoft provides with Windows Server 20 03 You can find most of these tools... touch your soon−to−be Exchange 20 03 server, which is, of course, a DHCP client in this case Address reservations are important especially when outside servers need to find your Exchange servers address It takes a few minutes to a few days for a new DNS entry to propagate across the Internet So, if your Exchange servers IP address changed every day, servers trying to send mail to the server could be out... point where the Windows 20 03 Configure Your Server Wizard leaves you by default For example, unlike with the Windows 2000 DHCP setup wizard, your Windows 20 03 DHCP server was authorized by default A DHCP server that isnt authorized cant hand out IP addresses You can tell that your DHCP server is authorized by the little up−pointing green arrow on the server icon To unauthorize the server, which you might . single Windows Server 20 03 domain: More Complex Upgrades from Windows NT 4to20 03 and Exchange 5.5to20 03 132 Install Windows Server 20 03 from scratch, creating a new Windows Server 20 03 domain.1 Windows NT 4to20 03 and Exchange 5.5to20 03 134 that you cant do an in−place Exchange 5.5to20 03 upgrade, upgrades from NT 4 to Windows 20 03 are more difficult than Exchange 5.5to20 03 upgrades. Upgrades. Windows NT 4to20 03 and Exchange 5.5to20 03 135 Part 2: Installation Chapter List Chapter 7: Installing Windows Server 20 03 as a Domain Controller Chapter 8: Installing Exchange Server 20 03 136 Chapter