Script to Harvest Windows Server\Client System Details

PowerShell Help
1

I’m a support analyst\help desk technician by trade.

Here’s a little PowerShell script cobbled together over the years to harvest details of Windows client and\or server platforms:

GitHub - Pendraig/System-Inventory: PowerShell Script to Harvest Windows Server\Client System Information

Edit Note: Changed the original link from my personal OneDrive to Public GitHub. Props to TonyD for the suggestion. :slight_smile: This repository contains a readme, sample results, the actual text file I send to or share with clients as well as the script (.ps1) file itself.

I use this script as part of my diagnostic process to streamline information gathering, minimize redundant communications, and enhance case note documentation. Saves me a buttload of time by eliminating guesswork about system architecture and reducing unnecessary communications to obtain details I should have had in the first place!

The script will extract, format, and write the following data elements into a text file named ‘System Inventory - .txt’ saved in the logged-on user’s Downloads folder:

  • OS Details
  • OEM Serial Number
  • GPU specs
  • Storage Capacity
  • Optional Windows Features or Server Roles (contingent upon platform)
  • ISP Details & External IP Addresses (both IPv4 & IPv6)
  • Antivirus details
  • PowerShell & .NET Framework versions
  • Browser URL associations - ‘What did you say your default browser was?’
  • Critical & Error events over the past 24 hours
  • Updates & Hotfixes

So, how exactly do I use the script? Real basic:

  1. Share the script with the client
  2. Walk them through running the script
  3. Retrieve the results (if remotely assisting) or have the client send the System Inventory.txt file to me via email
  4. Post the client’s system inventory as an internal case note in whatever ITSM\CRM platform (SalesForce, ServiceNow, Remedy, etc) my shop is using
  5. Diagnose, reproduce, and fix the client’s issue

Would appreciate any suggestions and\or constructive criticism offered.

2

Just a heads up … most of corporate america blocks OneDrive live access.

3

Safest place available to host the text files in question. I normally send the relevant text file directly to the user in question either by email or direct transfer (Bomgar, WebEx, etc). :wink:

Didn’t think folks would appreciate slogging through 434 lines of code had I posted same here originally. Would be happy to share the script as a text file upon request.

4

How about Github ?? I do believe that is a common method.

6

What about PSGallery? You can publish a script as well.

7

GitHub has much wider exposure, more flexibility and better security (IMO).