The Ntds.dit file grows larger when you install Live Communications Server 2003 (842260)


The information in this article applies to:

  • Microsoft Office Live Communications Server 2003

SYMPTOMS

When you install Microsoft Office Live Communications Server 2003, you notice that the Ntds.dit file grows larger.

Note An Ntds.dit file that is on a Microsoft Windows Server 2003-based computer that is running in a native domain experiences less growth than an Ntds.dit file that is on a Microsoft Windows 2000 Server-based computer.

CAUSE

This problem occurs because of the way that permissions or access control list (ACLs) are applied in the Ntds.dit Active Directory database file. On a Windows 2000 Server-based computer, ACLs are replicated throughout the Active Directory tree. As replication occurs, the Ntds.dit file size increases.

Note In Windows Server 2003-based computers, Ntds.dit replicates only changed ACLs to child objects. Because of this, the growth of the Ntds.dit file is less in Windows Server 2003 than in Windows 2000.

STATUS

This behavior is by design.

MORE INFORMATION

The test domain structure

Microsoft has tested the domain structure in Windows Server 2003 and in Windows 2000 Server to determine the approximate growth that occurs in the Ntds.dit file.

Note All customer deployments are unique. Tests cannot account for all variables and must be viewed as a guide.

Microsoft tested 15 domains. The tests focused on:
  • Domain A (a forest root)
  • Domain B (where Live Communications Server 2003 was installed)
  • Domain C (where there was no installation of Live Communications Server)
The following procedure was used for the domain structure testing.

Note These steps are not intended as detailed step-by-step instructions about how to run these tests in your environment. Each step in this document represents only a brief description of the corresponding step that Microsoft used to obtain the results that are shown here.
  1. Recorded the sizes of the .dit files.
  2. Prepared the enterprise for testing.
  3. Prepared Domain A for testing.
  4. Prepared Domain B (Windows 2000, using mixed mode).
  5. Installed Live Communications Server 2003 on a member server in Domain B.
  6. Added 6,700 users to Domain A by using a script.
  7. Defragmented the following .dit global catalogs:
    1. The Domain C global catalog.

      Note This was to see the difference between a non-defragmented global catalog and a defragmented global catalog on Windows 2000 Server.
    2. The Domain B global catalog.

      Note This was with enabled users already added.
    3. The Domain A global catalog (the forest foot).
  8. Prepared Domain C.

    Note This was where there was no installation of Live Communications Server 2003.
  9. Added 46,000 users to Domain A, to Domain B, and to Domain C by using a script.

    Data Results

    • The Windows 2000 Server global catalog grew by 3.2 kilobytes (KB) per user and by thirteen percent overall.

      Note This global catalog was non-defragmented.
    • The Windows Server 2003 global catalogs grew by 1 KB per user and by seven percent overall.

      Note These global catalogs were non-defragmented
    • The Windows 2000 Server global catalogs grew by 1.4 KB per user and by five percent overall.

      Note These global catalogs were defragmented
    • The Windows Server 2003 domain controller that had users enabled grew by 1.3 KB per user and by three percent overall.
For additional information about how to defragment the Active Directory database, click the following article number to view the article in the Microsoft Knowledge Base:

232122 Performing offline defragmentation of the Active Directory database

Modification Type:MajorLast Reviewed:6/21/2004
Keywords:kbprb KB842260 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.