I GET MESSAGE"sid POOL EXHUST" when i try add any object TO AD

When you install the Administration Tools Pack on a computer that is running Windows XP Professional x64 Edition, the Active Directory Users and Computers MMC snap-in file (Dsa.msc) is installed in the %windir%\Syswow64 folder. Additionally, the computer's file system maps the Active Directory Users and Computers MMC snap-in to the following path: DriveLetter:\%windir%\Syswow64\Dsa.mscHowever, the Active Directory Domains and Trust MMC snap-in incorrectly specifies the path of the Active Directory Users and Computers MMC snap-in as follows: DriveLetter:\%windir%\System32\Dsa.mscWhen the computer's file system tries to locate the Dsa.msc file from within the Active Directory Domains and Trust MMC snap-in, Mmc.exe is run. Mmc.exe is run because the Dsa.msc file is associated with Mmc.exe. When Mmc.exe is run, it uses the following path to locate Dsa.msc: DriveLetter:\%windir%\System32\Dsa.msc DomainPathAfter the Mmc.exe command is run, the Active Directory Domains and Trust MMC snap-in tries to locate the Dsa.msc file. Because the Dsa.msc file does not exist in the %windir%\System32 folder, the error message that is mentioned in the "Symptoms" section is generated.

To resolve this problem, manually copy the Dsa.msc file from the %windir%\Syswow64 folder to the %windir%\System32 folder.

Your hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:

http://www.microsoft.com/windowsxp/64bit/default.mspx (http://www.microsoft.com/windowsxp/64bit/default.mspx) For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site:http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx

If active Directory is not in administrative tools then it is likely that the machine is not configrued as a domain controller. You will need to add this as a role through server manager. Once configured as a domain controller Active Directory will appear under admin tools

The resolution and workaround to solve the error is as below.

1. Login to the Windows 2003 domain controller, and delete the computer account object from the Active Directory by using Microsoft Management Console (MMC) which you can always access from “Manage Your Server”.
2. Log-in to the PC workstation as local administrator. If you cannot logon as local administrator, try to unplug the network cable and logon to the computer by using a domain administrator user that used to logon on the PC before, by using cached logon credentials feature.
3. Go to Control Panel, then click on System icon, then go to Computer Name tab.
4. Unjoin the computer from the domain by clicking on “Change”. You should see that Domain button is now selected. Remember your domain name in the text box. Select (Click) on “Workgroup” to remove the computer from the domain, and put any workgroup name in the text box (e.g. workgroup).
5. Click OK to exit.
6. Restart the computer (optional)
7. Go back to the Control Panel, launch System properties and then go to Computer Name tab, and click on “Change”.
8. Rejoin the domain by uncheck the Workgroup button and select (check) Domain button, and put in the domain name noted above into the text box.
9. Click OK to exit.
10. Reboot the PC.

This should solve the unable to logon to domain error, without changing or losing the user profiles on AD.

Is there a running Domain Controller present? If so DNS info is often stored in Active Directory (A.D. Inegrated DNS Zone).  If this is the case you can just connect a server to the network, join the domian (verify DNS settings in TCI/IP config is pointing to Domain Controller) and then installm DNS from Add/Remove windows components.  Zone data should replicate from AD to new DNS server, to verify open DNS console and look for resource records relevent to the domain.

if u edit settings in active directory and editing the rools

bake up your setting

and remove active directory

them stup it agien

Active Directory think of it has management system for all network LAN PCs in your domain. You can add users to certain enterprise groups, you can disable accounts, push and pull software application better then you can in SMS domain. I use to to clone user accounts or create new user groups. Very easy to learn. To install on Server requires a domain, DNS. If you're using Windows Server 2003 and setup the server to manage active directory all the options for the installation process will appear for installation. There are a lot of info online and in books if you need more info. There are training classing offer at MS Solutions Centers.

Dear , friend


Active Directory (AD) is a technology created by Microsoft that provides a variety of network services,

Active directory is a directory service used to store information about the network resources across a domain and also centralize the network.


DNS stands for Domain Name Server. These are the servers that match up a fully qualified domain with the proper IP address. This is necessary because computers only understand the IP address for your domain (eg- 123.45.678.90).

An application directory partition is represented by a domainDNS object with an instanceType attribute value of DS_INSTANCETYPE_IS_NC_HEAD combined with DS_INSTANCETYPE_NC_IS_WRITEABLE. This domainDNS object represents the application directory partition root (NC head), and is named similar to a regular domain partition, for example, "DC=dynamicdata,DC=fabrikam,DC=com", which corresponds to a DNS name of "dynamicdata.fabrikam.com". An application directory partition can, therefore, be instantiated anywhere a domain partition can be instantiated. There is no NetBIOS name associated with an application directory partition.

It is possible to nest application directory partitions, that is, an application directory partition can have child application directory partitions. Searches with subtree scope rooted at an application directory partition head will generate continuation references to the child application directory partitions.

An application directory partition replica can only be created on a domain controller that is running on Windows Server 2003 and later and only while the Domain-Naming FSMO role is held by a Windows Server 2003 and later domain controller. In a mixed forest that has both Windows Server 2003 domain controllers and down-level domain controllers (Windows 2000 domain controllers or Windows NT 4.0 primary domain controllers), an attempt to create an application directory partition replica on a down-level domain controller will fail.

An application directory partition also has a corresponding crossRef object in the Partitions container of the configuration partition. The crossRef can be pre-created manually before creating the domainDNS object. The pre-created crossRef object must have the attribute values shown in the following table or the partition creation will fail. If the crossRef object does not exist, the Active Directory server will create one when the application directory partition is created.

Active Directory (AD) is a technology created by Microsoft that provides a variety of network services, including:

• LDAP-like[1][2] directory services
• Kerberos based authentication
• DNS based naming and other network information

using the same database, for use primarily in Windows environments. Active Directory also allows administrators to assign policies, deploy software, and apply critical updates to an organization. Active Directory stores information and settings in a central database. Active Directory networks can vary from a small installation with a few hundred objects, to a large installation with millions of objects (though not easily [3]).
Active Directory was previewed in 1996, released first with Windows 2000 Server edition, and revised to extend functionality and improve administration in Windows Server 2003. Additional improvements were made in both Windows Server 2003 R2 and Windows Server 2008.
Active Directory was called NTDS (NT Directory Service) in older Microsoft documents. This name can still be seen in some AD binaries.
There is a common misconception that Active Directory provides software distribution. Software distribution is run by a separate service that uses additional proprietary schema attributes that work in conjunction with the LDAP protocol. Active Directory does not automate software distribution, but provides a mechanism by which other services can provide software distribution.