I’d look at the whitespace to determine when to offline defrag a DC. You can enable the associated event which will tell you the amount of whitespace by setting the registry key HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\6 Garbage Collection to 1 instead of 0 (which is the default). Regkey might be likely – just typed it from hard.

This will give you an event every time when garbage collection runs (every 12 hrs) and tell you the amount of whitespace in the DB.

Whatever needs to be loaded should perform better when smaller.

I’ve heard that a DC on x64 will perform better than on 32-bit, since it’s very likely you already have some of the newer servers with x64 I’d just give it a try for one DC yourself.

Gruesse - Sincerely,

Ulf B. Simon-Weidner

Profile & Publications: http://mvp.support.microsoft.com/profile="">
Weblog: http://msmvps.org/UlfBSimonWeidner
Website: http://www.windowsserverfaq.org

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Coffman
Sent: Thursday, June 29, 2006 10:59 PM
To: [email protected]
Subject: [ActiveDir] NTDS.DIT Size

Our AD (NTDS.dit) is at 1.7GB (approx. 250,000 users).

Should an offline defrag be performed at a regular interval?

Some articles I read only say it is only worthwhile if you are running low on space. We have plenty of drive space and RAM.

At what point should the AD be moved to 64 bit?

Thanks,

Josh

RE: [ActiveDir] NTDS.DIT Size

Reply via email to