Archive for March, 2012


Windows Server 8 and Windows Server 2003 – Network Infrastructure…

March 3, 2012




Windows Server 8.

Announced last September, Windows Server 8 updates the code base for Microsoft’s flagship server OS, the current version of which is Windows Server 2008. The beta version will allow administrators to test the OS and offer feedback to Microsoft as it finalizes the software for commercial release. Microsoft did not disclose when the final production-ready version of the OS would be available for purchase.

A major update, Windows Server 8 contains numerous improvements in virtualization, multi-machine management and application hosting capabilities, noted Bill Laing, Microsoft corporate vice president for server and cloud, in a blog post announcing the release.

With virtualization, Windows Server 8 allows administrators to build virtual networks, allowing different business units or customers to share a single physical network while maintaining complete independence from the other virtual networks. Helping in disaster recovery and continuity of operations, another new feature allows file shares to be moved between nodes without stopping the server applications that use these files.

In terms of hosting applications, Windows Server 8 will include a copy of .NET Framework 4.5, which includes new capabilities to run a program concurrently across multiple processor cores. The Web server software IIS (Internet Information Server) has been upgraded to provide better security isolation and to manage more sites per server. The PowerShell command line interface has been strengthened by the addition of 2,300 additional commands.

To run the free beta version, a server will need a 1.4 GHz 64-bit processor, a minimum 512MB of working memory and 32GB on a disk. Users can upgrade to the new beta OS from existing versions of Windows Server 2008 and Windows Server 2008 R2, though they will not be able to upgrade to subsequent releases from this release.

Windows Server 2003 – Network Infrastructure.

Configuring the DHCP Server.

DHCP allows you to automatically assign IP address , subnet masks , and other configuration information to client computers on the local network. When a DHCP server is available , computers that are configured to obtain an IP address automatically adopt an alternate configuration or an Automatic Private IP Addressing (APIPA) address.

Implementing a basic DHCP server requires installing the server ; authorizing the server ; configuring scopes , exclusions , reservations , and options ; activating the scopes ; and finally , verifying the configuration.

Authorizing the Server.

DHCP servers must be authorized if they are to be integrated in Active Directory networks. Only domain controllers and domain member servers participate in Active Directory , and only these server types can become authorized. When your network includes Active Directory domains , the first DHCP server you install on the network must be authorized DHCP server.

Stand alone or workgroup DHCP servers running Microsoft Windows 2000 Server or Windows Server 2003 cannot become authorized in Active Directory networks , but they can coexist with these networks as long as they are not deployed on a subnet with any authorized DHCP servers. (Note , however , that this configuration is not recommended).

Stand alone DHCP servers implemented together with authorized servers are known as rouge servers. When a rogue DHCP server running Windows Server 2003 or Windows 2000 server detects an authorized server on the same subnet , the stand alone server automatically stops its own DHCP Server service and stop leasing IP addresses to DHCP clients.

When the DHCP Server service installed on a domain controller , you can perform the authorization procedure simply by right-clicking the server node in the DHCP console and selecting Authorize. You can use the following procedure  , however to authorize DHCP servers hosted on both domain controllers and member servers.