If you use multiple IP addresses, you can register each with a DNS server, allowing multiple companies or departments to use one system running multiple Web servers. Many sites that you have accessed on the Internet are served from only one of many virtual servers residing on a UNIX or Windows system.
For example, IIS 7.0 and Apache Server are designed to support multiple Web server scenarios ranging from simple Web sites on a corporate intranet to large ISP Web farms. Strictly speaking, all Web servers are considered virtual; even if you are running only one Web server, IIS and Apache treat it as the primary virtual server.

Just as you need to monitor physical computers, you also need to monitor virtual machines (VMs). Everything you have learned in this lesson applies to VMs. To monitor a virtual machine running Windows, you can still use Server Manager, Computer Management, Event Viewer, Performance Monitor, and all of the other tools. Since a single host can have many virtual servers, you need to make sure that one virtual computer does not use all of the resources that would take away from the other machines.
Server Manager, introduced in the first release of Windows Server 2008, provides server management based on server roles such as Active Directory Domain Services, Domain Name System (DNS), and Dynamic Host Configuration Protocol (DHCP). In Server 2012, Server Manager has a tile-based, modern interface. In addition to managing the local server, Server Manager now supports multiserver management. Most administrative tasks can now be performed through the updated Server Manager utility. These tasks include deploying features and roles remotely to physical and virtual servers. Server Manager now integrates other management tools such as RDS, IPAM (Internet protocol address management), Hyper-V, and file and storage management. Administrators can use the enhanced Server Manager dashboard as a centralized launching point for most server management tools.