Active Directory on Windows Server 2008 Requirements

by Daniel Petri - January 7, 2009 Printer Friendly Version The process of installing an Active Directory domain in Windows Server 2008 is quite simple, but some beginners or IT professionals that have never had a chance to get their hands on AD installations and that are not familiar with its requirements might stumble across a few pitfalls.

Also see Configure and customize SharePoint Workspace 2010

Monitor VMware with Microsoft System Center

Find out how you can get scalable, fault tolerant and agentless VMware monitoring directly in System Center with the Veeam nworks Management Pack. Protect your investments in Microsoft System Center Manage physical and virtual from one console Eliminate the costs of an additional monitoring framework Learn more about the nworks Management Pack here So, what do we need in order to successfully install Active Directory on a Windows Server 2008? Here is a quick list of what you must have:

An NTFS partition with enough free space An Administrator's username and password The correct operating system version A NIC Properly configured TCP/IP (IP address, subnet mask and - optional - default gateway) A network connection (to a hub or to another computer via a crossover cable) An operational DNS server (which can be installed on the DC itself) A Domain name that you want to use Brains (recommended, not required...)

After you have all the above go ahead and read my "Installing Active Directory on Windows Server 2008" article.

An NTFS Partition

To successfully install AD you must have at least one NTFS formatted partition. Back in older operating systems this was something that you actually had to tell people about, because *some* administrators had servers that did not have their partitions formatted with NTFS. Nowadays, NTFS is the only way to go in Windows-based servers, but I will nevertheless put it on the writing, just to make sure. This partition is where the SYSVOL folder is placed, and usually, that is the C:' partition, but for large AD deployments, this could very well be a different partition. To convert a partition (C:) to NTFS type the following command in the command prompt window:
convert c:/fs:ntfs

Free space on your disk

You need at least 250mb of free space on the partition you plan to install AD on. Of course you'll need more than that if you plan to create more users, groups and various AD objects.

Local Administrator's username and password

Remember, only a local Administrator (or equivalent) can install the first domain and thus create the new forest. Other installation scenarios such as adding additional (replica) DCs require either Domain Admin permissions, or, in case of new domains in the same tree or in new trees Enterprise Admins permissions.

The right operating system version - Windows Server 2008 Standard, Enterprise or Data Center
Duh... however, note that you CAN install Active Directory on Server Core versions. Please read my "Understanding Windows Server 2008 Server Core" and "Installing Active Directory on Windows 2008 Server Core" articles for more information on Server Core.

IP Configuration
While it is possible to install Active Directory on a server that has a dynamically-assigned IP address, it doesn't make much sense to do so. It's much better to configure the server with a manual and dedicated IP address. If you do not use a dedicated IP address, DNS registrations may not work and Active Directory functionality may be lost. If the computer is a multihomed computer, the network adapter that is not connected to the Internet can host the dedicated IP address. The Active Directory domain controller should point to its own IP address in the DNS server list to prevent possible DNS connectivity issues. To configure your IP configuration, use the following steps:

Note: IP addresses can be also configured from the Command Prompt by using the NETSH command, but I will not describe that procedure here. 1. Right-click Network, and then click Properties.

If you do not have the Network icon visible on your desktop, use Control Panel. 2. In the Control Panel'Network and Sharing Center window, click on the manage Network Connections link on the left.

Note: You can get to the same window by typing NCPA.cpl in the run command.

3. In the Control Panel'Network Connections window, right-click Local Area Connection, and then click Properties.

4. Click Internet Protocol version 4 (TCP/IPv4), and then click Properties.

Note: You can also configure the TCP/IPv6 properties, but you do NOT have to, and frankly, unless you require TCP/IPv6 functionality, I'd simply ignore it or disable it. More on that, in a future article. 5. Make sure you have a static and dedicated IP address. If you don't need Internet connectivity through this specific NIC you can use a Private IP range such as 192.168.101.0 with a Subnet Mask of 255.255.255.0.

6. The next step is not required, but I usually recommend checking that the correct configuration is in place. Click Advanced, and then click the DNS tab. The DNS information should be configured as follows: Configure the DNS server addresses to point to the DNS server. This should be the computer's own IP address if it is the first server or if you are not going to configure a dedicated DNS server.

Have you tried Forefront for Exchange?

If the Append these DNS suffixes (in order) option is selected for the resolution of unqualified names, the Active Directory DNS domain name should be listed first, at the top of the list. Verify that the information in the DNS Suffix for this connection box is the same as the Active Directory domain name. Make sure that the Register this connection's addresses in DNS check box is selected.

Active Network Connection Required During Installation

The installation of Active Directory requires an active network connection. When you attempt to use DCPROMO.exe to promote a Windows Server 2008 computer to a domain controller that doesn't have a connected and active NIC, you will receive the following error message:

And after hitting Next, this error will appear: Active Directory Domain Services Installation Wizard The TCP/IP networking protocol must be properly configured. Complete the configuration before you proceed. This problem can occur if the network cable is not plugged into a hub or other network

device.

(Screenshot of a connected NIC)

(Sample of a disconnected or un-plugged network cable) To resolve this problem, plug the network cable into a hub or other network device. While highly improbable that the network connection status would be disconnected in a server that is about to be deployed in a production environment, this could be the case when building the server for testing purposes. If network connectivity is not available and this is the first

domain controller in a new forest, you can finish DCPROMO.exe by installing Microsoft Loopback Adapter.

DNS Configuration
A DNS server that supports Active Directory DNS entries (SRV records) must be present for Active Directory to function properly. In my Windows 2000/2003 versions of the Active Directory installation tips I recommended to manually install and configure DNS prior to running DCPROMO. However, in Windows Server 2008, and when installing the FIRST Domain Controller in the Active Directory domain, I tend to recommend that you allow the DCPROMO wizard to automatically build the proper DNS services and configuration.

Client Connections
When considering Internet connectivity, it is recommended (and in most cases, this is the proper and most-used configuration) that the client computers connect to the Internet through a NAT device (i.e. a Router that translates private IP addresses to one public one, and allows connectivity through one ISP-assigned IP address). This prevents any issues that may arise if clients obtain an IP address from your Internet service provider (ISP). In Small Office or Home Office (SOHO) scenarios, this can be achieved by using a second network adapter on the server connected to a hub. You can use NAT and Routing on the server to isolate the clients on the local network. The clients should point to the domain's INTERNAL DNS server, and NOT to the ISP's DNS server, to ensure proper DNS connectivity. The internal DNS server's forwarder will then allow the clients to access DNS addresses on the Internet.

Do not use Single-Label domain names

As a general rule, Microsoft recommends that you register DNS domain names for internal and external namespaces with Internet authorities. This is true for Windows 2000/2003 and for Windows Server 2008. This includes the DNS names of Active Directory domains, unless such names are sub-domains of names that are registered by your organization name, for example, "corp.example.com" is a sub-domain of "example.com". When you register DNS names with Internet authorities, it prevents possible name collisions should registration for the same DNS domain be requested by another organization, or if your organization merges, acquires or is acquired by another organization that uses the same DNS names. DNS names that don't include a period ("dot", ".") are said to be single-label (for example, com, net, org, bank, companyname) and cannot be registered on the Internet with most Internet authorities.

Installing Active Directory on Windows Server 2008

by Daniel Petri - January 8, 2009 Printer Friendly Version

Microsoft Active Directory provides the structure to centralize the network management and store information about network resources across the entire domain. Active Directory uses Domain Controllers to keep this centralized storage available to network users. In order to configure a Windows Server 2008 machine to act as Domain Controller, several considerations and prerequisites should be taken into account, and several steps should be performed. In this article I will guide you through these prerequisites and steps of creating a new Windows Server 2008 Domain Controller for a new Active Directory domain in a new forest.

Monitor VMware with Microsoft System Center

Find out how you can get scalable, fault tolerant and agentless VMware monitoring directly in System Center with the Veeam nworks Management Pack. Protect your investments in Microsoft System Center Manage physical and virtual from one console Eliminate the costs of an additional monitoring framework
Learn more about the nworks Management Pack here

Considerations when Installing a new Windows Server 2008 forest

When you install AD to create the first domain controller in a new Windows Server 2008 forest, you must keep the following considerations in mind:

You must make forest and domain functional level decisions that determine whether your forest and domain can contain domain controllers that run Windows 2000 Server, Windows Server 2003, or both. To read more about forest and domain functional levels please refer to the links below. Domain controllers running the Microsoft Windows NT Server 4.0 operating system are NOT supported with Windows Server 2008. Servers running Windows NT Server 4.0 are NOT supported by domain controllers that are running Windows Server 2008, meaning you MUST have additional DCs running Windows 2000/2003 to support older NT 4.0 servers. The first Windows Server 2008 domain controller in a forest must be a global catalog server and it cannot be an RODC.

Considerations when Installing a new Windows Server 2008 domain in an existing Windows 2000/2003 forest

When you install AD to create the first domain controller in a new Windows Server 2008 domain, you must keep the following considerations in mind:

Before you create a new Windows Server 2008 domain in a Windows 2000/2003 forest, you must prepare the forest for Windows Server 2008 by extending the schema (that is, by running ADPREP /forestprep). To read more about ADPREP please refer to the links below or my "Windows Server 2008 ADPREP" article. You must make domain functional level decisions that determine whether your domain can contain domain controllers that run Windows 2000 Server, Windows Server 2003, or both. To read more about forest and domain functional levels please refer to the links below. I recommend that you host the PDC emulator operations master role in the forest root domain on a domain controller that runs Windows Server 2008. For more information about FSMO Roles, please read my "Understanding FSMO Roles in Active Directory" and "Transferring FSMO Roles" articles.

General considerations
Make sure you read and follow the requirements described in my "Active Directory on Windows Server 2008 Requirements" article.

Installing Active Directory Domain Services (AD-DS)

In Windows Server 2008, unlike previous server operating Systems, there is an additional step that needs to be taken before running DCPROMO to promote the server to Domain Controller and installing Active Directory on it. This step is the installation of Active Directory Domain Services (AD-DS) role on the server. In fact, the AD-DS role is what enables the server to act as a Domain Controller, but you will still need to run DCPROMO the regular way. AD-DS can be installed in one of 3 methods:

Method 1 Server Manager/Initial Configuration Tasks

Roles can and should be added from Server Manager (but they can also be initiated from the Initial Configuration Tasks wizard that auto-opens the first time you log on to the server).
1. Open Server Manager by clicking the icon in the Quick Launch toolbar, or from the Administrative Tools folder. 2. Wait till it finishes loading, then click on Roles > Add Roles link.

3. In the Before you begin window, click Next.

4. In the Select Server Roles window, click to select Active Directory Domain Services, and then click Next.

5. In the Active Directory Domain Services window read the provided information if you want to, and then click Next.

6. In the Confirm Installation Selections, read the provided information if you want to, and then click Next.

7. Wait till the process completes.

8. When it ends, click Close.

9. Going back to Server Manager, click on the Active Directory Domain Services link, and note that there's no information linked to it, because the DCPROMO command has not been run yet.

10. Now you can click on the DCPROMO link, or read on. 1. To run DCPROMO, enter the command in the Run command, or click on the DCPROMO link from Server Manager > Roles > Active Directory Domain Services.

2. Depending upon the question if AD-DS was previously installed or not, the Active Directory Domain Services Installation Wizard will appear immediately or after a short while. Click Next.

Note: The Advanced features of DCPROMO will be discussed in a future article.

Also see System Center Essentials 2010 - Configuring and Managing

3. In the Operating System Compatibility window, read the provided information and click Next.

4. In the Choosing Deployment Configuration window, click on "Create a new domain in a new forest" and click Next.

5. Enter an appropriate name for the new domain. Make sure you pick the right domain name, as renaming domains is a task you will not wish to perform on a daily basis. Click Next.

Note: Do NOT use single label domain names such as "mydomain" or similar. You MUST pick a full domain name such as "mydomain.local" or "mydomain.com" and so on. The wizard will perform checks to see if the domain name is not already in use on the local network.

6. Pick the right forest function level. Windows 2000 mode is the default, and it allows the addition of Windows 2000, Windows Server 2003 and Windows Server 2008 Domain Controllers to the forest you're creating. Read my "Understanding Windows Server 2008 Active Directory Domain and Forest Functional Levels" article for more information on that.

7. Pick the right domain function level. Windows 2000 Native mode is the default, and it allows the addition of Windows 2000, Windows Server 2003 and Windows Server 2008 Domain Controllers to the domain you're creating.

Note: If you select "Windows Server 2008" for the forest function level, you will Not be prompted to pick a domain function level. Read more about domain and forest function levels on my "Understanding Windows Server 2008 Active Directory Domain and Forest Functional Levels" article.
8. The wizard will perform checks to see if DNS is properly configured on the local network. In this case, no DNS server has been configured, therefore, the wizard will offer to automatically install DNS on this server.

Note: The first DCs must also be a Global Catalog. Also, the first DCs in a forest cannot be a Read Only Domain controller.
9. It's most likely that you'll get a warning telling you that the server has one or more dynamic IP Addresses. Running IPCONFIG /all will show that this is not the case, because as you can clearly see, I have given the server a static IP Address. So, where did this come from? The answer is IPv6. I did not manually configure the IPv6 Address, hence the warning. In a network where IPv6 is not used, you can safely ignore this warning.

10. You'll probably get a warning about DNS delegation. Since no DNS has been configured yet, you can ignore the message and click Yes.

11. Next, change the paths for the AD database, log files and SYSVOL folder. For large deployments, carefully plan your DC configuration to get the maximum performance. When satisfied, click Next.

12. Enter the password for the Active Directory Recovery Mode. This password must be kept confidential, and because it stays constant while regular domain user passwords expire (based upon the password policy configured for the domain, the default is 42 days), it does not. This password should be complex and at least 7 characters long. I strongly suggest that you do NOT use the regular administrator's password, and that you write it down and securely store it. Click Next.

13. In the Summary window review your selections, and if required, save them to an unattend answer file. When satisfied, click Next.

14. The wizard will begin creating the Active Directory domain, and when finished, you will need to press Finish and reboot your computer.

Note: You can automate the rebooting process by checking the Reboot on Completion checkbox. To automate domain controller installations, you can use an answer file or you can specify unattended installation parameters at the command line. More on that in my "Creating an Unattend Installation File for DCPROMO in Windows Server 2008" article. Note: As written in my "Installing Active Directory on Windows 2008 Server Core" article, configuring a Windows Server 2008 Server Core machine REQUIRES you to perform an automated installation of Active Directory on that server, as there is NOT DCPROMO GUI on Server Core. Your server now acts as a Domain Controller. Make sure you properly back it up. You can test functionality by using AD management tools such as Active Directory Users and Computers, examine the Event Logs, services and folders and shares that have been created.
Links

AD DS Installation and Removal Step-by-Step Guide

Method 2 Servermanagercmd.exe
Servermanagercmd.exe is the command prompt equivalent of the Add Roles and Add Features wizards in Server Manager. Through the use of various command line options, you can quickly and easily add or remove features and roles to or from your server, including the AD-DS role. To install AD-DS by using Servermanagercmd.exe, simply enter the following command in the Command Prompt window:
Servermanagercmd.exe I ADDS-Domain-Controller

Let the command run and when it finishes, AD-DS will be installed on the server.

Method 3 Letting DCPROMO do the job

Oh yes. If you forget to install AD-DS or simply want to skip clicking on some windows, you can run DCPROMO from the Run command and before it is executed, the server will check to see if the AD-DS binaries are installed. Since they are not, they will auto-install.

After you complete the Add Roles Wizard, either click the link to start the Active Directory Domain Services Installation Wizard, or close Server Manager and manually run DCPROMO from the Run command.

Running DCPROMO
After installing the AD-DS role, we need to run DCPROMO to perform the actual Active Directory database and function installation. Note: This guide assumes this is the first Domain controller in the forest, thus creating a new domain in a new forest. For a guide on how to add additional Domain Controllers to existing domains, please read my upcoming "Installing Additional Windows Server 2008 Domain Controllers in your Existing Active Directory Domain" article.

Raising Windows Server 2008 Active Directory Domain and Forest Functional Levels
by Daniel Petri - January 8, 2009 Printer Friendly Version When the first Windows Server 2008based Domain Controller is deployed in a domain or forest, the domain or forest operates by default at the lowest functional level that is possible in that environment, meaning Windows 2000 Native Mode. This allows you to take advantage of the default Active Directory features while running versions of Windows earlier than Windows Server 2008. When you raise the functional level of a domain or forest, a set of advanced features becomes available.

Monitor VMware with Microsoft System Center

Find out how you can get scalable, fault tolerant and agentless VMware monitoring directly in System Center with the Veeam nworks Management Pack. Protect your investments in Microsoft System Center Manage physical and virtual from one console Eliminate the costs of an additional monitoring framework Learn more about the nworks Management Pack here Make sure you read my "Understanding Windows Server 2008 Active Directory Domain and Forest Functional Levels" article for more info about domain and forest function levels. Note: In the Windows Server 2008 version of DCPROMO, when you install a new domain in a new forest, you are prompted for the function level of your choice. Therefore, it may very well be that a brand new installation of Active Directory will not hold the "default" domain or forest function levels.

Raising Domain Function Levels

To activate new domain features that available in Windows Server 2008, all domain controllers in the domain must be running Windows Server 2008. After this requirement is met, the administrator can raise the domain functional level to Windows Server 2008. Important Raising the domain functional levels to Windows Server 2008 is a nonreversible task and prohibits the addition of Windows 2000based or Windows Server 2003based Domain Controllers to the environment. Any existing Windows 2000based or Windows Server 2003based Domain Controllers in the environment will no longer function, and in fact, the upgrading wizard will not allow you to continue with the operation. Before raising functional levels to take advantage of advanced Windows Server 2008 features, ensure that you will never need to install domain controllers running Windows 2000-based or Windows Server 2003based Domain Controllers in your environment. Membership in Domain Admins, Enterprise Admins, or equivalent, is the minimum required to complete this procedure. In order to raise the domain functional level:

1. Log on the PDC Emulator of the domain with domain administrator credentials. Note: The PDC Emulator is usually the first DC in the domain. 2. Open Active Directory Users and Computers by clicking Start > All Programs > Administrative Tools, and then click Active Directory Users and Computers (you can also perform this action from the Active Directory Domains and Trusts snap-in). 3. In the console tree, right-click the domain node and then click Raise Domain Functional Level.

4. Under Select an available domain functional level, do one of the following: Click Windows Server 2003, and then click Raise to raise the domain functional level to Windows Server 2003. or Click Windows Server 2008, and then click Raise to raise the domain functional level to Windows Server 2008.

5. Read the warning message, and if you wish to perform the action, click Ok.

6. You will receive an acknowledgement message telling you that the operation was completed successfully. Click Ok.

7. You can check the function level by performing step 3 again and viewing the current function level.

Note: The current domain functional level appears under Current domain functional level in the Raise Domain Functional Level dialog box. The level increase is performed on the PDC Emulator FSMO and requires the domain administrator.

Also see What are the capabilities of Exchange Online?

Raising Forest Function Levels

To activate new forest features that available in Windows Server 2008, all domain function levels in the forest must be running in Windows Server 2008 mode. After this requirement is met, the administrator can raise the forest functional level to Windows Server 2008. Note that domains that are set to the domain functional level of Windows Server 2003 will automatically be raised to Windows Server 2008 at the same time that the forest functional level is raised to Windows Server 2008. Important Raising the forest functional levels to Windows Server 2008 is a nonreversible task and prohibits the addition of Windows 2000based or Windows Server 2003based Domain Controllers to any of the domains in the environment. Any existing Windows 2000based or Windows Server 2003based Domain Controllers in the environment will no longer function, and in fact, the upgrading wizard will not allow you to continue with the operation. Before raising functional levels to take advantage of advanced Windows Server 2008 features, ensure that you will never need to install domain controllers running Windows 2000-based or Windows Server 2003based Domain Controllers in your environment. Membership in Enterprise Admins, or equivalent, is the minimum required to complete this procedure. In order to raise the forest functional level: 1. Log on to the PDC Emulator of the forest root domain with a user account that is a member of the Enterprise Administrators group. 2. Open Active Directory Domains and Trusts by clicking Start > All Programs > Administrative Tools, and then click Active Directory Domains and Trusts. 3. In the console tree, right-click Active Directory Domains and Trusts, and then click Raise Forest Functional Level.

4. Under Select an available forest functional level, do one of the following: Click Windows Server 2003, and then click Raise to raise the forest functional level to Windows Server 2003. or Click Windows Server 2008, and then click Raise to raise the forest functional level to Windows Server 2008.

5. Read the warning message, and if you wish to perform the action, click Ok.

6. You will receive an acknowledgement message telling you that the operation was completed successfully. Click Ok.

7. You can check the function level by performing step 3 again and viewing the current function level.

Note: To raise the forest functional level to Windows Server 2008, you must upgrade (or demote) all existing Windows 2000 or Windows Server 2003 Domain Controllers in your forest. If you cannot raise the forest functional level, you can click Save As in the Raise Forest Functional Level dialog box to save a log file that specifies which domain controllers in the forest still must be upgraded from older operating systems.