AD-COIT: AD-COIT Frequently Asked Questions (FAQ)

AD-COIT Frequently Asked Questions (FAQ):

Where can I download the tool?
The project is hosted over on Sourceforge. You can grab a copy here.

How long will it take to run the script?
It depends on the size of your AD-environment, the number of computer objects in it, how many are online, and your network architecture.

How long will it take assuming 30 computers, with most of them being on-line, and very little AD-clutter in terms of retired computer accounts that remain in AD.
Maybe 5-10 minutes.

Who is the script designed for?
Small-to-Midsized environments.

Will this script work in enterprise environments?
Probably. I've tested it in smaller environments - say, a few hundred clients or less. If you've used it in a medium-to-large environment, email me and let me know about your experience.

When I run the script, it doesn’t report the FSMO role holders. Why?
FSMO role detection uses "DSQUERY" to grab the role-holders. You'll need the "Windows 2003 Admin Pack" installed on the computer that you're executing the script from.

Where can I get DSQUERY/Admin-Pack from?
I't s available for download from the Microsoft download center... http://www.microsoft.com/downloads/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&DisplayLang=en

I can't get any of my computer's to respond, what's going on?
AD-COIT needs to be able to talk to client computers on port 135. If you have a firewall enabled on your clients, you'd need an exception for unsolicited DCOM requests on port 135.

How do I create an exception for this (and other) scripts to run, using Group Policy?
If you're using the Windows Firewall, this can get configured via a Group Policy setting called "Allow Remote Administration Exception" (Open up Group Policy Manager, and go here under your Computer objects OU - Computer Configuration\Administrative Template\Network\Windows Firewall\Domain Profile).