Actually the AD mapper tool mentioned before is quite good. You don't need to install Visio on a machine in the domain. Just a machine that you control - you can authenticate/provide credentials to connect to the domain.
Cheers Ken -----Original Message----- From: Ajay Kulsh [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 January 2008 11:24 PM To: NT System Admin Issues Subject: Re: Documenting a Windows domain Let me once again answer my own question: Best tool to dump AD information is a script. Multiple scripts are available at: http://www.microsoft.com/technet/scriptcenter/scripts/default.mspx?mfr=true Jay ----- Original Message ----- From: "Ajay Kulsh" <[EMAIL PROTECTED]> To: "NT System Admin Issues" <[email protected]> Sent: Thursday, January 24, 2008 2:28 AM Subject: Re: Documenting a Windows domain -- a subjecting propostion? > > Thanks but I will not be able to install Visio in that domain. > > I am using "SrvInfo" tool to gather information about servers. > GPMC creates nice report about GPOs. > But using "csvde -f" command gives information about AD but that file has > too verbose to be useful. > > Are there some other tools that dump AD and other network information? > Thanks. > > Jay > > ----- Original Message ----- > From: "Free, Bob" <[EMAIL PROTECTED]> > To: "NT System Admin Issues" <[email protected]> > Sent: Wednesday, January 23, 2008 4:25 PM > Subject: RE: Documenting a Windows domain -- a subjecting propostion? > > > > admap will get you a good start. Ooops...that's the 'old' name :-) > > ADTD will get you a good start....it has selectable levels of detail, > which you choose really depends on the complexity of your environment > and the intended audience. Once you have the topology mapped, you can > add other stuff to your heart's content. > > It's a free D/L from MS now but it does require VISIO. > > http://www.microsoft.com/downloads/details.aspx?FamilyID=cb42fc06-50c7-4 > 7ed-a65c-862661742764&DisplayLang=en > > > > -----Original Message----- > From: Ajay Kulsh [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 23, 2008 4:12 PM > To: NT System Admin Issues > Subject: Documenting a Windows domain -- a subjecting propostion? > > I have been told to document a Windows 2003 domain -- without > instructions on what to include. > > I am thinking of listing all DCs, sites, connectors, > servers-and-their-applications, user and group names, group membership > and GPOs. > > Any suggestions on what else I should include and if there is a tool to > do this? Thanks. > > Jay > > So. Pasadena > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
