-
Microsoft Active Directory Documentation Script Update Version 2.21
November 11, 2018
#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
Webster is a Sr. Infrastructure Consultant for Conversant Group 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.
6 Responses to “Microsoft Active Directory Documentation Script Update Version 2.21”
Leave a Reply
- For HTML output, reverted the output Hardware and Service functions back to using $rowdata = @()
September 29, 2019 at 6:00 am
Yes I cant get the script to save the output?
September 29, 2019 at 7:16 am
I would do a full online repair of Office.
Webster
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
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.
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.
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.