• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1510
  • Last Modified:

Windows Server 2008 R2 Core best practices for Domain Controller

Hi,

I'm building a Windows Server 2008 R2 Core domain controller and having trouble finding information on best practices on hard drive requirements specific to Windows Server Core.

http://technet.microsoft.com/en-us/windowsserver/bb414778
 
The System Requirements do not differentiate between Windows GUI and Windows Core. The recommended hard drive size is 40GB. This seems excessive for a domain controller with just 1GB of RAM.

Will 10GB C:\ partition be enough considering it's a VMware VM? I don't want to waste storage on the SAN. Also, regarding other partitions on a domain controller such for NTDS, SYSVOL and Logs. What is best practice for sizing there?

Thanks and I look forward to your responses.


Regards
0
ams_group
Asked:
ams_group
  • 2
1 Solution
 
kevinhsiehCommented:
Why don't you thin provision it? That way you don't waste SAN space. I think that my core RODC takes maybe 5 GB space. If you give it 20 you should be more than fine. If you went with 10 GB you may need to expend it later.

Just leave everything on a single partition. I don't recommend trying to change the locations of the AD DS files.  
0
 
Krzysztof PytkoActive Directory EngineerCommented:
To extend above answer, you may check this articel about "Windows Server 2008 R2 Server Core: Securing the Branch Office Connection" at
http://technet.microsoft.com/en-us/magazine/ff679937.aspx

I would personally make this core DC as Virtual Machine with 20GB HDD :)

Regards,
Krzysztof
0
 
ams_groupAuthor Commented:
Thanks for your response.... I've decided to follow your advice and not use separate partitions and 20GB thin provisioned.

Regarding partitions, there's only around 100 users and computers and agree that it would be more worthwhile in a larger environment.
0
 
kevinhsiehCommented:
I would think that a single partition would be good for up to at least several tens of thousands of users.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now