Scripts and Other Utilities

All current documentation scripts require PowerShell Version 3 or later and create a Microsoft Word 2010 or 2013 document.

Most documentation scripts have been updated to support Word 2016.

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 either six or seven parts:

  1. ReadMe file
  2. Change Log
  3. Unsigned script with PS1 extension
  4. Unsigned script with TXT extension
  5. Signed script with PS1 extension
  6. Signed script with TXT extension
  7. Sample Software Exclusions file with TXT extension (XenApp scripts only)
Filename Get-ServiceWithAccountNameV1.0.zip
Filesize 29 KB
Version 1.0
Date added May 15, 2017
Downloaded 77 times
Category Miscellaneous
NAME
Get-ServiceWithAccountName.ps1

SYNOPSIS
Find Services using a specific account name on computers in Microsoft Active Directory.

SYNTAX
C:\ScriptTesting\Get-ServiceWithAccountName.ps1 -AccountName <String> [-ComputerName <String>] [-InputFile <String>] [-OrganizationalUnit <String>] [-Folder <String>] [<CommonParameters>]

C:\ScriptTesting\Get-ServiceWithAccountName.ps1 -LiteralAccountName <String> [-ComputerName <String>] [-InputFile <String>] [-OrganizationalUnit <String>] [-Folder <String>] [<CommonParameters>]

DESCRIPTION
By default, builds a list of all computers where "Server" is in the OperatingSystem property unless the ComputerName or InputFile parameter is used.

Process each server looking for Services using a specific StartName.

Builds a list of computer names, Service names, service display names and service start names.

Display the matching 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.