Carl Webster Accessibility Statement

Carl Webster is committed to facilitating the accessibility and usability of its website, carlwebster.com, for everyone. Carl Webster aims to comply with all applicable standards, including the World Wide Web Consortium’s Web Content Accessibility Guidelines 2.0 up to Level AA (WCAG 2.0 AA). Carl Webster is proud of the efforts that we have completed and that are in-progress to ensure that our website is accessible to everyone.

If you experience any difficulty in accessing any part of this website, please feel free to email us at info@carlwebster.com and we will work with you to provide the information or service you seek through an alternate communication method that is accessible for you consistent with applicable law (for example, through telephone support).

  • Microsoft Active Directory Documentation Script V3.11

    May 27, 2022

    Active Directory, PowerShell

    #Version 3.11 27-May-2022

    • Fixed bug in Function getDSUsers with MaxPasswordAge reported by Danny de Kooker
    • Moved the following section headings so that the error/warning/notice messages had a section heading
      • Domain Controllers
      • Fine-grained password policies

    You can always find the most current script by going to https://www.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 →

    4 Responses to “Microsoft Active Directory Documentation Script V3.11”

    1. Holger Behmann Says:
      February 24, 2023 at 8:17 am

      Hi Carl,

      I’m missing in the context of Fine Grained Password Policies the information aubout the Default Domain Password Policy. I would be nice to have an overview to all Password Policies.

      Holger

      • Carl Webster Says:
        March 25, 2023 at 8:04 am

        Unfortunately, that is beyond the scope of a documentation script.

        Sorry.

        Webster

    2. Kapil Bandlish Says:
      July 27, 2022 at 6:38 am

      Hi Carl,

      I had been using your scripts for long and I absolutely love your work.

      Recently I had been working on a Multi Domain forest and having issues running your Active Directory Health Check and AD documentation scripts. This Domain is poorly designed and I need to figure out all the issues and help fix the domain.

      Most of the times the script will stop in between but when it runs completely it throws an error while saving the file :

      VERBOSE: 7/27/2022 11:14:01 AM:
      WARNING: 7/27/2022 11:14:01 AM: Unable to save the output file, C:\tools\ADHCV2.09\ADHealthCheck.docx
      ProcessDocumentOutput : Unable to save the output file, C:\tools\ADHCV2.09\ADHealthCheck.docx
      At C:\tools\ADHCV2.09\ADHealthCheck_v2.ps1:4342 char:1
      + ProcessDocumentOutput
      + ~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ProcessDocumentOutput

      VERBOSE: 7/27/2022 11:14:01 AM:
      VERBOSE: 7/27/2022 11:14:01 AM: Script started: 07/27/2022 09:04:46
      VERBOSE: 7/27/2022 11:14:01 AM: Script ended: 07/27/2022 11:14:01
      VERBOSE: 7/27/2022 11:14:01 AM: Elapsed time: 0 days, 2 hours, 9 minutes, 14.847 seconds

      I have checked the access on the folder and do not see any issues with it.

      • Carl Webster Says:
        July 27, 2022 at 6:56 am

        This is an error I cannot fix and has been a problem for ten years. Microsoft does not offer PowerShell for Word, so I am stuck using COMObjects. Those objects do not return any useful status information. When I tell Word to Save and Close the file, I have no idea if it worked or not. The only thing I can say to you to try is to start a new PowerShell session and rerun the script.

        Sorry

        Webster