MMC is the primary tool used to administer Windows Server 2003.
A large number of pre- configured MMC are available in the Administrative Tools menu.
3 rd party software often ships with custom MMC add-ons.
You can build MMC for a particular task by creating a custom MMC . You add snap-ins to the console that are relevant to the task. You can then save or discard the console once you are finished with it.
You can use the MMC to administer remote computers within a domain. You add a snap-in with the focus set to the target remote computer.
Windows Server 2003 can host a variety of LAN infrastructure services such as DNS, DHCP, and WINS servers.
Use the Add/Remove Windows Components section of Add/Remove programs in the Control Panel to add services.
When Windows Server 2003 provides these infrastructure services, it must use a static IP address.
Configure a Static IP 1. Open Network Connections from the Control Panel. 2. Right-click Local Area Connection and select Properties. 3. Select Internet Protocol and then click Properties. 4. Select Use the following IP address and enter IP address information.
By default, Windows Server 2003 uses Active Directory Integrated Zones (ADI Zones) which are stored within Active Directory .
ADI Zones can only be hosted on domain controllers . ADI Zones can be replicated to all domain controllers in the domain or forest. Any DNS server hosting an ADI Zones can process updates to that zone.
Only one server can host a primary zone . This server does not need to be a domain controller. Only the server hosting the primary zone can process updates to that zone. The zone data is stored in a zone file.
Any DNS server can host a secondary zone . A secondary zone is a read-only copy of an ADI or primary zone.
A stub zone is an abbreviated zone that contains only a list of name servers for the target zone. Stub zones are read only and are updated by contacting a DNS server hosting the primary zone. Any Windows Server 2003 DNS server can host a stub zone.