Installing Hyper-V on Windows Server 2008 R2

To install Hyper-V on Windows Server 2008 R2 you can use one of the following approaches. Note that all methods require a reboot after completion.

Method #1 - Through the GUI

Probably the easiest for this specific role. I would use this method.
1. Open Server Manager, wait for it to load.
2. Click on "Roles", wait for it to load.

3. On the "Before you begin" page, click "Next".

4. In the "Select Server Roles" page, click to select the Hyper-V role. Click "Next".

5. Click "Next".

6. Select all the Network Interface Cards (NICs) that you wish to assign for the Virtual Machines. Make sure you leave one NIC un-selected for host management. If you only have one NIC, select it, but make a note that it is best to have at least 2 NICS - one for the host and one for the VMs. These settings can be changed later.

7. In the "Confirm Installation Selections" page click "Install".

8. One finished, you will need to reboot the server. Click on the "Close" button, and then click "Yes" when you are prompted to reboot the server.

9. When the server reboots, log back into the server and the Server Manager should automatically load and resume the installation process.

After about a minute, you should see a message telling you that Hyper-V has installed successfully. Click "Close" to complete the wizard.

Note: Make sure you do not forget to enable the CPU Virtualization Mode and the Execute Disable bit. Again, read my Prepare Your Windows Server 2008 R2 for Hyper-V Role article. If you fail to do so, you will receive an error when attempting to start a VM.

Method #2 - Using the Command Prompt

Using the servermanagercmd.exe command is easy, and only requires 3 words... A reboot is required at the end of the installation (which can also be added to the command, making it 4 words...). However, Hyper-V network connections will need to be changed after the installation.
1. Open a Command Prompt window with elevated permissions.

2. Type:

servermanagercmd -i Hype-V

If you want to automatically reboot the server when the installation is finished, type:

servermanagercmd -i Hyper-V -restart

Easy and simple. This is probably why Microsoft decided to deprecate the usage of servermanagercmd.exe

Method #3 - Using PowerShell

In Windows Server 2008 R2, PowerShell is installed by default. However, in order to install roles with it, you need to import the Server Manager module.
1. Open a PowerShell window and type:

Import-Module servermanager

2. Once imported, type:

Add-WindowsFeature Hyper-V

If you want to automatically reboot the server when the installation is finished, type:

Add-WindowsFeature Hyper-V -restart

Easy and simple, but here too, Hyper-V network connections will need to be changed after the installation.

Read More

Windows Server 2008

Windows Server 2008 (sometimes abbreviated as "Win2K8"^[2]or "W2K8") is one of Microsoft Windows' server line of operating systems. Released to manufacturing on February 4, 2008, and officially released on February 27, 2008, it is the successor to Windows Server 2003, released nearly five years earlier. A second release, named Windows Server 2008 R2, was released to manufacturing on July 22, 2009.^[3]Like Windows Vista and Windows 7, Windows Server 2008 is based on Windows NT6.x.

History

Originally known as Windows Server Codename "Longhorn", Microsoftchairman Bill Gates announced its official title (Windows Server 2008) during his keynote address at WinHEC16 May 2007.^[4]
Beta 1 was released on 27 July 2005, Beta 2 was announced and released on 23 May 2006 at WinHEC 2006 and Beta 3 was released publicly on 25 April 2007.^[5]Release Candidate 0 was released to the general public on 24 September 2007^[6]and Release Candidate 1 was released to the general public on 5 December 2007. Windows Server 2008 was released to manufacturing on 4 February 2008 and officially launched on 27 February 2008.^[7]

Features

See also: Features new to Windows Vista

Windows Server 2008 is built from the same code base as Windows Vista; therefore, it shares much of the same architecture and functionality. Since the code base is common, it automatically comes with most of the technical, security, management and administrative features new to Windows Vista such as the rewritten networking stack(native IPv6, native wireless, speed and security improvements); improved image-based installation, deployment and recovery; improved diagnostics, monitoring, event logging and reporting tools; new security features such as BitLocker and ASLR(address space layout randomization); improved Windows Firewall with secure default configuration; .NET Framework 3.0technologies, specifically Windows Communication Foundation, Microsoft Message Queuing and Windows Workflow Foundation; and the core kernel, memory and file system improvements. Processors and memory devices are modeled as Plug and Play devices, to allow hot-pluggingof these devices. This allows the system resources to be partitioned dynamically using Dynamic Hardware Partitioning; each partition has its own memory, processor and I/O host bridge devices independent of other partitions.^[8]

Server Core

Default user interface for Server Core. Because Windows Explorer is removed from Server Core, programs such as Notepad use the Windows NT 3.x-style file dialog.

Windows Server 2008 includes a variation of installation called Server Core. Server Core is a significantly scaled-back installation where no Windows Explorer shell is installed. All configuration and maintenance is done entirely through command-line interface windows, or by connecting to the machine remotely using Microsoft Management Console. However, Notepad and some control panel applets, such as Regional Settings, are available.
Server Core does not include the .NET Framework, Internet Explorer, Windows PowerShell or many other features not related to core server features. A Server Coremachine can be configured for several basic roles: Domain controller/Active Directory Domain Services, ADLDS (ADAM), DNS Server, DHCP server, file server, print server, Windows Media Server, IIS 7 web server and Hyper-Vvirtual server. Server Core can also be used to create a cluster with high availability using failover clustering or network load balancing.
Andrew Mason, a program manager on the Windows Server team, noted that a primary motivation for producing a Server Core variant of Windows Server 2008 was to reduce the attack surface of the operating system, and that about 70% of the security vulnerabilities in Microsoft Windows from the prior five years would not have affected Server Core.^[9]

Active Directory roles

Active Directory roles are expanded with identity, certificate, and rights management services. Active Directory, until Windows Server 2003, allowed network administrators to centrally manage connected computers, to set policies for groups of users, and to centrally deploy new applications to multiple computers. This role of Active Directory is being renamed as Active Directory Domain Services (ADDS).^[10]A number of other additional services are being introduced, including Active Directory Federation Services (ADFS), Active Directory Lightweight Directory Services (AD LDS), (formerly Active Directory Application Mode, or ADAM), Active Directory Certificate Services (ADCS), and Active Directory Rights Management Services (ADRMS). Identity and certificate services allow administrators to manage user accounts and the digital certificates that allow them to access certain services and systems. Federation management services enable enterprises to share credentials with trusted partners and customers, allowing a consultant to use his company user name and password to log in on a client's network. Identity Integration Feature Pack is included as Active Directory Metadirectory Services. Each of these services represents a server role.

Failover Clustering

Main article: Failover Clustering

Windows Server 2008 offers high-availability to services and applications through Failover Clustering. Most server features and roles can be kept running with little to no downtime.
In Windows Server 2008 and Windows Server 2008 R2, the way clusters are qualified changed significantly with the introduction of the cluster validation wizard.^[11]The cluster validation wizard is a feature that is integrated into failover clustering in Windows Server 2008 and Windows Server 2008 R2. With the cluster validation wizard, an administrator can run a set of focused tests on a collection of servers that are intended to use as nodes in a cluster. This cluster validation process tests the underlying hardware and software directly, and individually, to obtain an accurate assessment of how well failover clustering can be supported on a given configuration.
Note: This feature is only available in Enterprise and Datacenter editions of Windows Server.

Self-healing NTFS

In Windows versions prior to Windows Vista, if the operating system detected corruption in the file system of an NTFS volume, it marked the volume "dirty"; to correct errors on the volume, it had to be taken offline. With self-healing NTFS, an NTFS worker thread is spawned in the background which performs a localized fix-up of damaged data structures, with only the corrupted files/folders remaining unavailable without locking out the entire volume and needing the server to be taken down. The operating system now features S.M.A.R.T.detection techniques to help determine when a hard disk may fail.^[12]

Hyper-V

Hyper-V architecture

Main article: Hyper-V

Hyper-V is hypervisor-based virtualization software, forming a core part of Microsoft's virtualization strategy. It virtualizes servers on an operating system's kernel layer. It can be thought of as partitioning a single physical server into multiple small computational partitions. Hyper-V includes the ability to act as a Xenvirtualization hypervisor host allowing Xen-enabled guest operating systems to run virtualized.^[13]A beta version of Hyper-V shipped with certain x86-64editions of Windows Server 2008, prior to Microsoft's release of the final version of Hyper-V on 26 June 2008 as a free download. Also, a standalone version of Hyper-V exists; this version supports only x86-64 architecture.^[14]While the IA-32 editions of Windows Server 2008 cannot run or install Hyper-V, they can run the MMC snap-in for managing Hyper-V.

Windows System Resource Manager

Main article: Windows System Resource Manager

Windows System Resource Manager (WSRM) is integrated into Windows Server 2008. It provides resource management and can be used to control the amount of resources a process or a user can use based on business priorities. Process Matching Criteria, which is defined by the name, type or owner of the process, enforces restrictions on the resource usage by a process that matches the criteria. CPU time, bandwidth that it can use, number of processors it can be run on, and allocated to a process can be restricted. Restrictions can be set to be imposed only on certain dates as well.

Server Manager

Server Manager is a new roles-based management tool for Windows Server 2008.^[15]It is a combination of Manage Your Server and Security Configuration Wizard SCW from Windows Server 2003. Server Manager is an improvement of the Configure my server dialog that launches by default on Windows Server 2003 machines. However, rather than serve only as a starting point to configuring new roles, Server Manager gathers together all of the operations users would want to conduct on the server, such as, getting a remote deployment method set up, adding more server roles etc., and provides a consolidated, portal-like view about the status of each role.^[16]

Other features

Other new or enhanced features include:

Core OS improvements

• Fully multi-componentized operating system.
• Improved hot patching, a feature that allows non-kernel patches to occur without the need for a reboot.
• Support for being booted from Extensible Firmware Interface (EFI)-compliant firmware on x86-64 systems.
• Dynamic Hardware Partitioning
• Support for the hot-addition or replacement of processors and memory, on capable hardware.

Active Directory improvements

• Read-only domain controllers (RODCs) in Active Directory, intended for use in branch office or other scenarios where a domain controller may reside in a low physical security environment. The RODC holds a non-writeable copy of Active Directory, and redirects all write attempts to a Full Domain Controller. It replicates all accounts except sensitive ones.^{[citation needed][clarification needed]} In RODC mode, credentials are not cached by default. Moreover, only the replication partner of the RODC needs to run Windows Server 2008.^{[clarification needed]} Also, local administrators can log on to the machine to perform maintenance tasks without requiring administrative rights on the domain.^{[citation needed]}
• Restartable Active Directory allows ADDS to be stopped and restarted from the Management Console or the command-line without rebooting the domain controller. This reduces downtime for offline operations and reduces overall DC servicing requirements with Server Core. ADDS is implemented as a Domain Controller Service in Windows Server 2008.

Policy related improvements

• All of the Group Policy improvements from Windows Vista are included. Group Policy Management Console (GPMC) is built-in. The Group Policy objects are indexed for search and can be commented on.^[17]
• Policy-based networking with Network Access Protection, improved branch management and enhanced end user collaboration. Policies can be created to ensure greater Quality of Service for certain applications or services that require prioritization of network bandwidth between client and server.
• Granular password settings within a single domain - ability to implement different password policies for administrative accounts on a "group" and "user" basis, instead of a single set of password settings to the whole domain.

Disk management and file storage improvements

• The ability to resize hard disk partitions without stopping the server, even the system partition. This applies only to simple and spanned volumes, not to striped volumes.
• Shadow Copy based block-level backup which supports optical media, network shares and Windows Recovery Environment.
• DFS enhancements - SYSVOL on DFS-R, Read-only Folder Replication Member. There is also support for domain-based DFS namespaces that exceed the previous size recommendation of 5,000 folders with targets in a namespace.^[18]
• Several improvements to Failover Clustering (High-availability clusters).^[19]
• Internet Storage Naming Server (iSNS) enables central registration, deregistration and queries for iSCSI hard drives.

Protocol and cryptography improvements

• Support for 128- and 256-bit AES encryption for the Kerberos authentication protocol.
• New cryptography (CNG) API which supports elliptic curve cryptography and improved certificate management.
• Secure Socket Tunneling Protocol, a new Microsoft proprietary VPN protocol.
• AuthIP, a Microsoft proprietary extension of the IKE cryptographic protocol used in IPsec VPN networks.
• Server Message Block 2.0 protocol in the new TCP/IP stack provides a number of communication enhancements, including greater performance when connecting to file shares over high-latency links and better security through the use of mutual authentication and message signing.

Miscellaneous improvements

• Windows Deployment Services replacing Automated Deployment Services and Remote Installation Services. Windows Deployment Services (WDS) support an enhanced multicast feature when deploying operating system images.^[20]
• Internet Information Services 7 - Increased security, Robocopy deployment, improved diagnostic tools, delegated administration.
• Windows Internal Database, a variant of SQL Server Express 2005, which serves as a common storage back-end for several other components such as Windows System Resource Manager, Windows SharePoint Services and Windows Server Update Services. It is not intended to be used by third-party applications.
• An optional "Desktop Experience" component provides the same Windows Aero user interface as Windows Vista, both for local users, as well as remote users connecting through Remote Desktop.

Removed features

See also: Features removed from Windows Vista

• The Open Shortest Path First (OSPF) routing protocol component in Routing and Remote Access Service was removed.^[21]
• Services for Macintosh, which provided file and print sharing via the now deprecated AppleTalk protocol, has been removed. Services for Macintosh were removed in Windows XP from client operating systems but were available in Windows Server 2003.^[21]
• NTBackup is replaced by Windows Server Backup, and no longer supports backing up to tape drives.^[22] As a result of NTBackup removal, Exchange Server 2007 does not have volume snapshot backup functionality; however Exchange Server 2007 SP2 adds back an Exchange backup plug-in for Windows Server Backup which restores partial functionality.^[23] Windows Small Business Server and Windows Essential Business Server both include this Exchange backup component.^[24]
• The POP3 service has been removed from Internet Information Services 7.0.^[25] The SMTP (Simple Mail Transfer Protocol) service is not available as a server role in IIS 7.0, it is a server feature managed through IIS 6.0.
• NNTP (Network News Transfer Protocol) is no longer part of Internet Information Services 7.0.

Editions

Most editions of Windows Server 2008 are available in x86-64 and IA-32 versions. Windows Server 2008 for Itanium-based Systems supports IA-64processors. Microsoft has optimized the IA-64 version for high-workload scenarios like database servers and Line of Business (LOB) applications. As such it is not optimized for use as a file server or media server. Microsoft has announced that Windows Server 2008 is the last 32-bit Windows server operating system.^[26]Windows Server 2008 is available in the editions listed below,^[27]similar to Windows Server 2003.

• Windows Server 2008 Standard (IA-32 and x86-64)
• Windows Server 2008 Enterprise (IA-32 and x86-64)
• Windows Server 2008 Datacenter (IA-32 and x86-64)
• Windows HPC Server 2008 (Codenamed "Socrates") (replacing Windows Compute Cluster Server 2003)
• Windows Web Server 2008 (IA-32 and x86-64)
• Windows Storage Server 2008 (Codenamed "Magni") (IA-32 and x86-64)
• Windows Small Business Server 2008 (Codenamed "Cougar") (x86-64) for small businesses
• Windows Essential Business Server 2008 (Codenamed "Centro") (x86-64) for medium-sized businesses^[28] (Discontinued) ^[29]
• Windows Server 2008 for Itanium-based Systems
• Windows Server 2008 Foundation (Codenamed "Lima")

Server Core is available in the Web, Standard, Enterprise and Datacenter editions. It is not available in the Itanium edition. Server Coreis simply an alternate installation option supported by some of the editions, and not a separate edition by itself. Each architecture has a separate installation DVD. The 32-bit version of Windows Server 2008 Standard Edition is available to verified students for free through Microsoft's DreamSparkprogram.

Service Packs

Microsoft occasionally releases service packs for its Windows operating systems to fix bugs and also add new features.

Service Pack 2

Because Windows Server 2008 is based on the Windows NT 6.0 Service Pack 1 kernel, the RTM release is considered to be Service Pack 1; accordingly, the first service pack is called Service Pack 2. Announced on October 24, 2008,^[30]this service pack contains the same changes and improvements as the Windows Vista Service Pack 2, as well as the final release of Hyper-V 1.0, and an approximate 10% reduction in power usage.
The first SP2 beta build was sent out in October 2008, a public beta arrived in December 2008, and an RC-escrow build was given to testers in January 2009. Windows Vista and Windows Server 2008 share a single service pack binary, reflecting the fact that their code bases were joined with the release of Server 2008. On May 26, 2009, Service Pack 2 was ready for release. It is now available in Windows Update.

Windows Server 2008 R2

Main article: Windows Server 2008 R2

A second release, Windows Server 2008 R2, was released on October 22, 2009.^[31]Retail availability began September 14, 2009.^[32]Windows Server 2008 R2 reached the RTM milestone on July 22, 2009.^[33]Like Windows 7, it is built on Windows NT 6.1. New features include new virtualization features, new Active Directory features, IIS 7.5, and support for 256 logical processors. Support for 32-bit-only processors (IA-32) has been removed. On July 22, 2009, Microsoft officially announced that they had released both Windows Server 2008 R2 and Windows 7 to manufacturing. Windows Server 2008 R2 was generally available for download from MSDN and Technet on August 19 and for retail purchase from October 22, 2009.

System requirements

System requirements for Windows Server 2008 are as follows:

Source:www.wikipedia.org

Read More

Monitoring Windows Server 2008 R2 with SNMP

So you have a new Windows Server 2008 R2 installed and now you’d like to start gathering statistics about how it’s performing. The SNMP protocol is a great way to get started. In this tutorial I will install the SNMP agent service on a Windows server and configure it to allow queries from a SNMP based management server. On the management server I will use a tool named Cacti that can collect this SNMP information and generate graphs from it in a fairly easy way. I will assume that you have a server with Cacti already set up. If not, details on how to set up an instance of Cacti on a CentOS Linux server can be found here.


 
Install and Configure Windows SNMP Agent
Okay first of all let’s install the Windows SNMP agent service.
Start Server Manager.

Scroll down to the Features Summary section and click Add Features.

Under Features open up SNMP Services and check SNMP Service. Click Next.

Click Install at the confirmation screen, then click Close when the install is complete.

Now it is time to configure the SNMP Service. Back in the Server Manager in the left pane open up Configuration and select Services. In the middle Services pane scroll down and double click the SNMP Service.

Click the Agent tab and enter your Contact and Location information. Click Apply.

For now we’ll skip any configuration in the Traps tab. This should only be necessary if you want to configure the SNMP agent to notify our monitoring server of any events without the monitor soliciting the information.
In the Security tab under Accepted Community Names click Add.

We’ll only be reading information (and not setting parameters) on the SNMP agent so keep Read Only and type a Community Name. Using a name other than “public” will help keep unauthorized clients from reading SNMP information from the agent but this is still not completely secure. Click OK.

Now click the second Add button under Accept SNMP Packets.

Type the IP address or hostname of the Cacti management server and click Add.

Make sure that “Accept SNMP packets from these hosts” is still selected, then click OK.

Read More

Components of a Server Computer

The hardware components that a typical server computer comprises are similar to the components used in less expensive client computers. However, server computers are usually built from higher-grade components than client computers. The following paragraphs describe the typical components of a server computer.

Motherboard

The motherboard is the computer's main electronic circuit board to which all the other components of your computer are connected. More than any other component, the motherboard is the computer. All other components attach to the motherboard.
The major components on the motherboard include the processor (or CPU), supporting circuitry called the chipset, memory, expansion slots, a standard IDE hard drive controller, and input/output (I/O) ports for devices such as keyboards, mice, and printers. Some motherboards also include additional built-in features such as a graphics adapter, SCSI disk controller, or a network interface.

Processor

The processor, or CPU, is the brain of the computer. Although the processor isn't the only component that affects overall system performance, it is the one that most people think of first when deciding what type of server to purchase. At the time of this writing, Intel had four processor models designed for use in server computers:

• Itanium 2: 1.60GHz clock speed; 1–2 processor cores

• Xeon: 1.83–2.33GHz clock speed; 1–4 processor cores

• Pentium D: 2.66-3.6GHz clock speed; 2 processor cores

• Pentium 4: 2.4-3.6GHz clock speed; 1 processor core

Each motherboard is designed to support a particular type of processor. CPUs come in two basic mounting styles: slot or socket. However, you can choose from several types of slots and sockets, so you have to make sure that the motherboard supports the specific slot or socket style used by the CPU. Some server motherboards have two or more slots or sockets to hold two or more CPUs.

The term clock speed refers to how fast the basic clock that drives the processor's operation ticks. In theory, the faster the clock speed, the faster the processor. However, clock speed alone is reliable only for comparing processors within the same family. In fact, the Itanium processors are faster than Xeon processors at the same clock speed. The same holds true for Xeon processors compared with Pentium D processors. That's because the newer processor models contain more advanced circuitry than the older models, so they can accomplish more work with each tick of the clock.

The number of processor cores also has a dramatic effect on performance. Each processor core acts as if it's a separate processor. Most server computers use dual-core (two processor cores) or quad-core (four cores) chips.

Memory

Don't scrimp on memory. People rarely complain about servers having too much memory. Many different types of memory are available, so you have to pick the right type of memory to match the memory supported by your motherboard. The total memory capacity of the server depends on the motherboard. Most new servers can support at least 12GB of memory, and some can handle up to 32GB.

Hard drives

Most desktop computers use inexpensive hard drives called IDE drives (sometimes also called ATA). These drives are adequate for individual users, but because performance is more important for servers, another type of drive known as SCSI is usually used instead. For the best performance, use the SCSI drives along with a high-performance SCSI controller card.
Recently, a new type of inexpensive drive called SATA has been appearing in desktop computers. SATA drives are also being used more and more in server computers as well due to their reliability and performance.

Network connection

The network connection is one of the most important parts of any server. Many servers have network adapters built into the motherboard. If your server isn't equipped as such, you'll need to add a separate network adapter card.

Video

Fancy graphics aren't that important for a server computer. You can equip your servers with inexpensive generic video cards and monitors without affecting network performance. (This is one of the few areas where it's acceptable to cut costs on a server.)

Power supply

Because a server usually has more devices than a typical desktop computer, it requires a larger power supply (300 watts is typical). If the server houses a large number of hard drives, it may require an even larger power supply

Read More

Installing and Configuring DNS

The Active Directory Installation wizard offers to install DNS if the wizard does not detect a proper DNS zone configuration during the installation of Active Directory. However, you should not rely on the wizard for these tasks. Many bug reports have been submitted regarding installation bases that relied on the wizard. Also keep in mind that the Active Directory Installation wizard does not install a reverse lookup zone.

The Windows 2000 DNS service can coexist with or migrate other DNS services, including the popular Berkeley Internet Name Domain (BIND) DNS service. One great place to find BIND information is the Internet Software Consortium Web site. To migrate from BIND, you must transfer the BIND zone and boot files to the Microsoft DNS service.
Windows 2000 DNS can also upgrade or coexist with Windows NT 4.0 DNS servers.
For the exam, you should know how to configure DNS for Active Directory. Here is the procedure.

1. Click Start --> Settings --> Control Panel.

2. Double-click Add/Remove Programs and then click Add/Remove Windows Components.

3. In Components, select Networking Services and then click Details.

4. In Subcomponents of Networking Services, select the Domain Name System (DNS) check box, click OK, and then click Next.

5. In Copy Files From, type the full path to the Windows 2000 distribution files and then click OK.

To host Active Directory, you must properly configure DNS with a zone for the Active Directory namespace. You should create both zone types for a proper DNS implementation for your Active Directory namespace — that is, a forward lookup zone and a reverse lookup zone. Read on to discover how.

Creating a forward lookup zone

To create a forward lookup zone:

1. Click Start --> Programs --> Administrative Tools --> DNS.

Windows 2000 launches the DNS Microsoft Management Console, from which you can perform your DNS administration.

2. Expand the DNS server.

3. Right-click the Forward Lookup Zone folder and choose New Zone.

4. Click Next to continue when the New Zone wizard appears.

The wizard takes the pain out of DNS administration.

5. Ensure that Standard Primary is selected and click Next.

6. Ensure that Forward Lookup Zone is selected and click Next.

7. At the New Zone page, type the name of your zone (for example, fordummies.com) and click Next.

8. Select Create a New File With This File Name and click Next.

9. Click Finish.

Creating a reverse lookup zone

To create a reverse lookup zone:

1. Click Start --> Programs --> Administrative Tools --> DNS.

2. Expand the DNS server.

3. Right-click your server and choose New Zone.

4. Click Next to continue when the New Zone wizard appears.

5. Ensure that Standard Primary is selected and click Next.

6. Ensure that Reverse Lookup Zone is selected and click Next.

7. Ensure that Network ID is selected, type your network ID in the Network ID field, and click Next.

8. Select Create a New File With This File Name and click Next.

9. Click Finish.

As far as Active Directory is concerned, your DNS server is almost ready. You should now configure the forward and reverse lookup zones for dynamic updating so that you do not get stuck creating all the records required for Active Directory yourself!

Read More