Windows Server 2008 Administration…..

November 15, 2011

Windows Server 2008 offers two general types of installation : a typical Full server installation and Server Core. Server Core is a stripped down version of Windows Server 2008 that doesn’t include a GUI or any unneeded services. Instead , the server installs only key features that are related  to the role that it supports – for example , Active Directory  ,or Domain Name System (DNS).

One of server’s engineers biggest gripes about the manual Windows Server installation process in the past was that they had to babysit the server as it went through the installation , because they had to key in bits of information at different times throughout the process – license information , componenets to install , and network configuration , for example. Of course , the easy solution to all this is to perform an unattended installation , but for the one offs that require a manual installation , the process was far from being  “set and forget”.

In Windows Server 2008 , this problem has been addressed by reducing the number of interactive steps required to get your server up and running. All the necessary questions for the installation are asked up front , before you begin the actual installation process of copying the files and performing the initial server configuration. By doing this , the installation process no longer has to stop for additional information before it can proceed. Once the server software installation is complete , installation of components and the configuration of the server can proceed under the new integrated management tool called Server Manager.

Minimum System Requirement:-

Processor: Minimum: 1GH

Memory: Minimum: 512MB RAM

Disk Space: Minimum: 8GB

Windows Server 2008 Core: Read-Only DC

 New in Windows Server 2008 is the option to create a read-only domain controller (RODC). To deploy an RODC, the domain controller that holds the PDC emulator operations master role (also known as flexible single master operations or FSMO) for the domain must be running Windows Server 2008. In addition, the functional level for the forest must be Windows Server 2003.

Because the administration of a Server Core is done from the command line only (at least initially), dcpromo must be run with a host of options to promote the Server Core installation to a domain controller (read-only or standard). From the Windows Server 2008 Technical Library, here are the command line options for dcpromo. The options can optionally be specified in an answer file.

So, to create a RODC on a Server Core installation without also installing DNS, the command line would be:

dcpromo /unattend /ReplicaDomainDNSName:<FQDN_of_Domain> /ReplicaOrNewDomain:ReadOnlyReplica /SiteName:<site_name> /InstallDNS:No /DatabasePath:”C:\NTDS” /LogPath:”C:\NTDS” /SysVolPath:”C:\SYSVOL”

Obviously, the paths for the database, logs, and sysvol would need to be changed to the appropriate location for your environment. The bulk of the parameters are pretty self-explanatory, but two need attention called out. First, the /ReplicaOrNewDomain:ReadOnlyReplica parameter is what defines the DC as a RODC. Using /ReplicaOrNewDomain:Replica creates a standard DC in an existing domain. Using /ReplicaOrNewDomain:NewDomain should be pretty obvious, but it does introduce a slew of different required parameters and options. Also, when creating a RODC you must specify the site name using the /SiteName parameter. I’m not sure, but I would assume this is for the enabling of universal group membership caching. So, if you haven’t figured it out, you’ll need to create the site for the RODC in AD DS before you promote the server to a RODC.

Other handy parameters:

  • /ConfirmGC:No – Do not configure the server as a GC (Default is Yes).
  • /CriticalReplicationOnly:Yes – This forces dcpromo to only replicate the critical directory information before rebooting, postpoting the full replication of the remaining AD DS information until after a reboot; can be useful for large directories to speed up the dcpromo process (Default is No).
  • /ReplicationSourceDC:<FQDN_of_DC> – This forces the replication operation to use a specific domain controller.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: