|
Not disagreeing with you Matt – we’re all just in a
guess mode without RM providing more information. I love those posts to lists
where the original poster never get’s back the questions being posted to
his questions… Anyways – I just made the point that his DIT size is not
small for a company not running Exchange. The number of users given was just an
example – more likely 100k vs. 5k users… And naturally most “corporate”
environments then have a similar amount of computer accounts and a strongly
varying number of groups (totally depends on group model being used). And even if
his AD already included Exchange we couldn’t easily tell how large his
environment is, simply because there are so many dependencies. That’s why
I gave those numbers using assumptions – certainly nothing to take as a fixed
value. Heck, we don’t even know his DC version (Win2003 single
instance storage of ACE has a huge impact on DIT size) or if he has disabled
Distributed Link Tracking (DLT), which adds a ton of garbage to every DC. Provided
you have sufficient file servers in your AD and are happily moving data around between
the servers (or between volumes), DLT alone can eat up many hundred meg of your
AD DIT. Did he defrag or not? Etc. /Guido From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Matt Hargraves I'm not sure what else he's
running on his DC. He might be running complex intrusion detection
software, DNS, WINS, etc.... On 8/1/06, Grillenmeier, Guido
<[EMAIL PROTECTED]>
wrote: Richard doesn't seem to be too
keen on giving us further details – too bad. But not sure why you – Matt
- are talking about "breaking 1.25 GB" with respects to the 32-bit
capabilities. By default 32-bit Win2003 DCs can cache a DIT up to approx.
1.5GB, which grows to 2.6-2.7GB using the /3GB switch (provided sufficient
physical memory). But irrespective of these
limitations, I'd argue you should move to Win2003 64bit DC anyways if you can.
For example if you are doing a hardware refresh at the same time. It is cheaper
(meaning you can support more memory for less licensing costs) and it will give
you much more room to grow for the future. 64bit drivers for x64 server
hardware are no longer an issue and even other important add-ons and management
tools such as AV and Backup etc. are catching up quickly. So try not to use the
32bit WinOS versions for AD DCs, even if they still handle the load today
– you'll do yourself a favor by moving to 64bit DCs as soon as you can.
Time to learn all those little quirks and challenges around handling this OS.
This way you'll be best prepared for when you really need to use 64bit
Windows for other applications. /Guido From: [EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED]] On Behalf Of Matt Hargraves Subject: Re: [ActiveDir] Exchange rollout - How much
larger does NTDS.DIT become? I guess the gist of what everyone is saying can
be summed up with the following: On 7/29/06, joe < [EMAIL PROTECTED]> wrote: To further add to this, it depends
considerably on how populated you want your GAL to be. Some people just let the
mandatory Exchange attributes get populated, others want the GAL to be the one
stop shop for info on employees so everything goes into the GAL which means
everything goes into AD. -- O'Reilly Active Directory Third
Edition - http://www.joeware.net/win/ad3e.htm
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Grillenmeier, Guido Subject: RE: [ActiveDir] Exchange rollout - How much larger
does NTDS.DIT become? Assuming this is after defrag,
650MB without Exchange is quite a large AD – guess you'd be close to 100k
users in your forest, if you've used the "standard" attributes of the
objects in AD (and haven't added stuff like thumbnail pictures to your
users…). After adding the Exchange schema
mods, the DIT shouldn't grow substantially, since AD doesn't use any space for
unused attributes – and the Exchange attributes for your object won't be
filled magically, until you mail-enable them. But once they are filled, it will
impact your AD (e.g. E2k3 adds 130 attributes to the Public Information
property set used by user class objects) It is very tough to make a guess
at the actual size you'd have with a fully deployed Exchange, but if you do
mail-enable the majority of your users (i.e. give them Exchange mailboxes) and
add DLs etc. and assuming my guess with 100k users is in the right ballpark
your AD DIT would easily grow to 3-5 GB. /Guido From: [EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED]] On Behalf Of RM NTDS.DIT is currently 650megs. Once Exchange has been fully deployed,
any guesses as to how much larger it will become? Just looking for a
ballpark figure... thx, RM |
- RE: [ActiveDir] Exchange rollout - How much larger doe... Grillenmeier, Guido
