• Microsoft Active Directory Documentation Script Update Version 2.21

    November 11, 2018

    Active Directory, PowerShell

    #Version 2.21 released 11-Nov-2018

    • For HTML output, reverted the output Hardware and Service functions back to using $rowdata = @()
      • Using $rowdata = New-Object System.Collections.ArrayList did not always work, which is weird

    You can always find the most current script by going to https://carlwebster.com/where-to-get-copies-of-the-documentation-scripts/

    Thanks

    Webster






    About Carl Webster

    Carl Webster is an independent consultant specializing in Citrix, Active Directory, and technical documentation. Carl (aka “Webster”) serves the broader Citrix community by writing articles (see CarlWebster.com) and by being the most active person in the Citrix Zone on Experts Exchange. Webster has a long history in the IT industry beginning with mainframes in 1977, PCs and application development in 1986, and network engineering in 2001. He has worked with Citrix products since 1990 with the premiere of their first product – the MULTIUSER OS/2.

    View all posts by Carl Webster →

    8 Responses to “Microsoft Active Directory Documentation Script Update Version 2.21”

    1. Thomas Chiteri Says:
      September 1, 2020 at 5:58 am

      Hi Carl,
      I am running the ADDS_Inventory_V2 to document my AD. The script runs just fine but its unable to write the outpout word file in the script folder. I am running Ms Office 365. Below is the error code:

      WARNING: 09/01/2020 13:29:52: Unable to save the output file, D:\ps\ISUZU.LOCAL.docx
      ProcessDocumentOutput : Unable to save the output file, D:\ps\ISUZU.LOCAL.docx
      At D:\ps\ADDS_Inventory_V2_Signed.ps1:16525 char:1
      + ProcessDocumentOutput
      + ~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ProcessDocumentOutput

      Kindly help.

      Reply

    2. jeremiah Says:
      September 29, 2019 at 6:00 am

      Yes I cant get the script to save the output?

      Reply

    3. Dhinesh Subramaniam Says:
      February 5, 2019 at 4:54 am

      Hi Carl,

      Any Idea of critical services on AD can be captured along with Health Check?

      Could you also please provide the link where you have the latest AD updated scripts, As I am not able to open the link provided on the top?

      Regards,
      Dhinesh

      Reply

      • Carl Webster Says:
        February 5, 2019 at 2:40 pm

        All scripts can be found at https://carlwebster.com/downloads

        From the script help text:

        .PARAMETER Services

        Gather information on all services running on domain controllers.

        Services that are configured to automatically start but are not running will be
        colored in red.

        Used on Domain Controllers only.

        This parameter requires the script be run from an elevated PowerShell session
        using an account with permission to retrieve service information (i.e. DomainAdmin).

        Selecting this parameter will add to both the time it takes to run the script and
        size of the report.

        This parameter is disabled by default.

        Reply

    4. Jason Says:
      December 28, 2018 at 3:09 am

      Hi Carl , with regard to the AD Documentation Script is there a way I can direct the Script to a specific Domain within a multi domain environment? i.e… if I want to only get information on child domain only… great website love the information you provide.

      Reply

      • Carl Webster Says:
        December 28, 2018 at 12:57 pm

        PS C:\ScriptTesting> get-help .\ADDS_Inventory_V2.ps1 -full


        -ADDomain
        Specifies an Active Directory domain object by providing one of the following
        property values. The identifier in parentheses is the LDAP display name for the
        attribute. All values are for the domainDNS object that represents the domain.

        Distinguished Name

        Example: DC=tullahoma,DC=corp,DC=labaddomain,DC=com

        GUID (objectGUID)

        Example: b9fa5fbd-4334-4a98-85f1-3a3a44069fc6

        Security Identifier (objectSid)

        Example: S-1-5-21-3643273344-1505409314-3732760578

        DNS domain name

        Example: tullahoma.corp.labaddomain.com

        NetBIOS domain name

        Example: Tullahoma

        If both ADForest and ADDomain are specified, ADDomain takes precedence.

        Required? false
        Position? named
        Default value
        Accept pipeline input? false
        Accept wildcard characters? false

        ————————– EXAMPLE 3 ————————–

        PS C:\PSScript >.\ADDS_Inventory_V2.ps1 -ADDomain child.company.tld

        Will use all default values.
        HKEY_CURRENT_USER\Software\Microsoft\Office\Common\UserInfo\CompanyName=”Carl
        Webster” or
        HKEY_CURRENT_USER\Software\Microsoft\Office\Common\UserInfo\Company=”Carl Webster”
        $env:username = Administrator

        Carl Webster for the Company Name.
        Sideline for the Cover Page format.
        Administrator for the User Name.
        child.company.tld for the AD Domain.

        ComputerName defaults to the value of $Env:USERDNSDOMAIN, then the script queries for
        a domain controller that is also a global catalog server and will use that as the
        value for ComputerName.

        Reply

    Leave a Reply