Auto-generate Flow Chart from Java/C++ Codes:

Raptor Flowchart Tutorial For Beginners

Wednesday, March 28, 2012

How to Install Read-Only Domain Controller in Windows Server 2008 Core

copied from: http://www.trainsignal.com/blog/server-2008-install-rodc-read-only-domain-controlle

Installing a Read-Only Domain Controller (RODC) isn’t much different than installing a regular domain controller.

However, there is one important factor to keep in mind. A RODC can only be installed into an existing Active Directory Domain with at least one full (non-read-only) Windows 2008 Server Domain Controller.

The reason is that the RODC is a new feature to Windows 2008 and it needs at least one DC to understand what it is doing in order to function properly.

Once the decision has been made to install a RODC the next decision is whether to install on a full-install or core-install of Windows 2008 Server.

The RODC is primarily aimed at providing additional security on an Active Directory Database for a server that is not physically secured. Installing a RODC on a Core Install of Windows 2008 provides no additional physical security.

It is actually a fair assumption that if someone is savvy enough to break into a stolen server that they also are capable of working most of their tricks from the command-line. So, while a Core Installation does increase security by having a smaller attack footprint, this level of security is separate from that provided by a RODC.

Although, it can be tempting to consider a Core Installation for remote RODC installs to lower the amount of patches and updates that need to be installed. However, it is important to remember that if there is no technical staff on-site, it can be much more difficult to walk someone through any procedures that must be performed locally if the non-technical person has to use the command line.

Installing RODC on a Core Server Install

There is only one way to install RODC role on a Core Server installation. The dcpromo.exe command runs on the GUI-less version of Windows Server 2008.

Using an answer file for the command makes the process much easier than trying to get all the switches just right in the command line.

Installing the Read-Only Domain Controller on Windows Server 2008 - 1

Although there are many settings available depending upon your particular infrastructure, just basic information is required to complete the command:

  • an account with permissions to do what you are trying to do
  • the name of the Site
  • the database and log paths
  • and whether or not to install DNS.

Installing the Read-Only Domain Controller on Windows Server 2008 - 2

Many people will put a “yes” for RebootOnCompletion. If you are doing an actual unattended promotion then that would make sense.

If you are sitting at the console, I prefer to manually reboot the server so that I can take as much time as I want to study what is on the screen if there is an issue.

Regular Installation

On a full install of Windows Servers 2008, there is of course a GUI tool to help with the process. The Active Directory Domain Services Installation Wizard handles the installation of RODC.

Type “dcpromo” at a command prompt to start the wizard. The first screen will ask you whether you want to use an existing forest, or create a new domain in a new forest. Since you must join an existing domain with a RODC, the choice is obvious.

Next you’ll be asked for a username and password. The account must be a member of Domain Admins in order to create a Read-Only Domain Controller.

Next, you’ll choose the site you wish to join.

So far, this is all the same as a regular Domain Controller install. Under “Additional Options” is where you actually choose to make this a Read-Only Domain Controller installation.

Installing the Read-Only Domain Controller on Windows Server 2008 - 3

Next, choose the paths for installing the components, or just click Next to use the defaults. Once the confirmation screen appears, you are all set.

In this case, you might as well check “Reboot On Completion”. Unlike in the command-line environment, here in the GUI-world if something goes wrong you’ll have all the time you want before clicking on OK or Next to analyze what happened.

No comments: