AD Specs

  • 101 Views
  • Last Post 27 October 2016
kebabfest posted this 27 October 2016

Hi Guys,
I am looking at doing a standard Active Directory Controller specification for a new client. Do people have anything they swear by in terms of memory\CPUs\disk allocation.
I can't find anything about allocation unit size for my SYSVOL volume. I was thinking of 64K.Any thoughts on good\bad things here ?
Also for Azure AD Controllers on the D Drive I am going to put No Caching. Does this seem right to people ?
All thoughts welcome,
Eoin

Order By: Standard | Newest | Votes
gkirkpatrick posted this 27 October 2016

Hi Eoin,

 

Make sure there’s enough memory to cache the entire DIT. It makes the allocation size more-or-less a non-issue as far as directory

access is concerned. This depends on the number of entries in the directory. This article may help:

https://technet.microsoft.com/en-us/library/cc961779.aspx.



 

FWIW, you can another drive to host the DIT. It doesn’t have to be SYSVOL.



 

Azure Active Directory is a cloud service and doesn’t have the notion of a domain controller. When you say “Azure AD Controller”, do

you mean running a domain controller in a VM in Azure? If so, this article provides configuration guidance:



https://azure.microsoft.com/en-us/documentation/articles/active-directory-install-replica-active-directory-domain-controller/

 

Hope this helps,

 

-gil

 

 

 

show

kebabfest posted this 27 October 2016

Hi Gil,
That makes sense. Thanks for your help. Yes I am talking about running a DC in a VM in Azure


show

Close