-
Microsoft Active Directory Documentation Script Update Version 2.15
June 26, 2017
While working on a project with my PowerShell and AD mentor, Michael B. Smith, he needed some additions made to the script. He also made a couple of other suggestions I implemented.
#Version 2.15 released 26-Jun-2017
- Added new parameter MaxDetails:
- This is the same as using the following parameters:
- DCDNSInfo
- GPOInheritance
- HardWare
- IncludeUserInfo
- Services
- This is the same as using the following parameters:
- Fixed wrong loop variable for CA
- Removed code that made sure all Parameters were set to default values if for some reason they did exist or values were $Null
- Reordered the parameters in the help text and parameter list so they match and are grouped better
- Replaced _SetDocumentProperty function with Jim Moyle’s Set-DocumentProperty function
- Updated Function ProcessScriptEnd for the new Cover Page properties and Parameters
- Updated Function ShowScriptOptions for the new Cover Page properties and Parameters
- Updated Function UpdateDocumentProperties for the new Cover Page properties and Parameters
- Updated help text
If you are running domain controllers on Windows Server 2016, make sure you update RSAT installed on the computer running the script.
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
Webster is a Sr. Solutions Architect for Choice Solutions, LLC and specializes in Citrix, Active Directory and Technical Documentation. Webster has been working with Citrix products for many years starting with Multi-User OS/2 in 1990.
View all posts by Carl WebsterSubscribe
Subscribe to our e-mail newsletter to receive updates.
2 Responses to “Microsoft Active Directory Documentation Script Update Version 2.15”
Leave a Reply
- Added new parameter MaxDetails:
September 12, 2017 at 9:18 am
Hi Carl
Thanks for your script, it’s been very useful to document customer environments.
There’s an idea I’ve been thinking about, would it be possible to run it from a computer non domain joined against a specific forest/domain?
I went through your code but was unable to find anyway to introduce the credentials used to start the script with. The reason why is simple, sometimes it is difficult to have a PC with Office client installed on customers environment.
Share your thoughts and keep up your good work!
Cheers
September 12, 2017 at 9:49 am
You have NEVER needed Word to run the AD doc script. The script has generated HTML output since day 1.
I will look at what it will take to add credentials as parameters.
Webster