Terms you'll need to understand:
Techniques you'll need to master:
Windows Server 2003 can have any number of different roles in the enterprise. The system could be deployed as a domain controller and, in that role, can also function as an Operations Master or a Global Catalog server. It could also be set up as a file server, a print server, or an application server, which includes setting the system up as an Internet Information Services (IIS) version 6 server. By installing it with the Post Office Protocol version 3 (POP3) and Simple Mail Transfer Protocol (SMTP) services, it could be set up as a mail server. You could also enable Terminal Services, configure the server as a streaming media server, or configure Routing and Remote Access Service (RRAS). The system could also be set up as a Domain Name System (DNS) server, a Dynamic Host Configuration Protocol (DHCP) server, or a Windows Internet Naming Service (WINS) server. For the most part, this chapter reviews some DNS material as an overview and preparation for Exam 70-293: Planning and Maintaining a Microsoft Windows Server 2003 Network Infrastructure. Regardless of which role you choose, you should carefully plan your server deployments so that those systems run only the services necessary for the server to perform its job. For example, there is usually no reason to enable RRAS on a file server or to install the NWLink protocol and bind it to the network adapters when NWLink is not needed on the network. |