Scripts and Other Utilities
All downloads are now on Citrix ShareFile.
Please ignore the Filename displayed for the download. WordPress is showing the ShareFile link and not the filename of the download.
If you get an invalid or expired link, email me email@example.com and let me know and I will get the link updated to one that never expires.
All current documentation scripts require PowerShell Version 3 or later and create a Microsoft Word 2010, 2013, or 2016/2019/Word O365 document.
Most documentation scripts will also create formatted text and HTML output so Microsoft Word is not required.
*****All scripts perform best with PowerShell Version 5*****
Each documentation script has up to seven parts:
- ReadMe file
- Change Log
- Unsigned script with PS1 extension
- Unsigned script with TXT extension
- Signed script with PS1 extension
- Signed script with TXT extension
- Sample Software Exclusions file with TXT extension (XenApp 6.x scripts only)
Note: Version 1.x of this script is specific to XenApp 6.5
Gets the average, minimum and maximum Group Policy processing time on computers in Microsoft Active Directory.
C:ScriptTestingGet-GPOTimeV2.ps1 [-ComputerName <String>] [-InputFile <String>] [-OrganizationalUnit <String>] [-Folder <String>] [<CommonParameters>]
By default, builds a list of all computers where "Server" is in the OperatingSystem property unless the ComputerName or InputFile parameter is used.
The script must be run from an elevated PowerShell session.
Process each server looking in the Microsoft-Windows-GroupPolicy/Operational for all Event ID 8001.
Displays the Avergage, Minimum and Maximum processing times.
All events where processing time is 0 are ignored. A 0 time means a local account was used for login.
Display the results on the console and creates two text files, by default, in the folder where the script is run.
Optionally, can specify the output folder.
Unless the InputFile parameter is used, needs the ActiveDirectory module.
The script has been tested with PowerShell versions 2, 3, 4, 5, and 5.1.
The script has been tested with Microsoft Windows Server 2008 R2, 2012, 2012 R2, and 2016 and Windows 10 Creators Update.
There is a bug with Get-WinEvent and PowerShell versions later than 2 or culture other than en-US, the Message property is not returned.
There are two work-arounds:
1. PowerShell.exe -Version 2
2. Add this line to the script:
[System.Threading.Thread]::CurrentThread.CurrentCulture = New-Object "System.Globalization.CultureInfo" "en-US"