PC Info Tool v2r6

Have you ever looked at a system in Spiceworks inventory, and not been able to get current data? Would you like to be able to troubleshoot a system in real time? See what services or processes are running? End a few of them? See if CPU or memory load is running hot? Or perhaps get the CPU temp on a remote system? And would you like all that in a GUI? Well now you can!

Copy and save the script below as a *.ps1. You do not need to change your Powershell execution policy. You just need to have admin rights to the target PC, .NET must be installed, and the Firewalls (both source and target) must be off or configured to allow WMI connections.

Place the following *.bat file script in the same directory and launch to run the Powershell script.
Line 1: @echo off
Line 2: Powershell.exe -sta -executionpolicy remotesigned -WindowStyle Hidden ".\yourscriptname.ps1"
Line 3: pause

(note: there should only be 3 lines in the *.bat file. @echo, Powershell, and pause. Darn text wrapping....)

Let me know what you think. If you would like to see additional info, let me know. See the Revision History, and the Known Issues section for additional info.

Latest release is 2r6, which includes a Toolbox option check box. This allows you to run the script against the local PC without needing to fill in the System Name field. Also included, is a checkbox to toggle between Imperial and Metric units for CPU temp.

Source Code

This script has not been checked by Spiceworks. Please understand the risks before using it.

Screenshots

10 Comments

Just posted version 2 revision 4.
Changes this release:
- Added Last reboot time.
- Added method of pulling last Windows update. Note: as this process can take 5 to 40 seconds, depending on network speeds, I have set this up as a button, that is only available once the initial data pull has been accomplished.
- Also modified the focus so that any button (except Exit) will now return focus to the System Name text box.

Mark,
thanks for your comment. actually i was trying to edit my previous comment before but i couldn't. the script work fine like a charm through "Quest power GUI 3.8" application.
if i tried to run it directly it wont and will give me the error above. but its ok! i convert it through "Quest power" to EXE so it run independently.
Well done and thanks for the Script. keep up the good work .

I just modified the write-up after a fellow Spicehead reported problems with the 3 line script. The original write-up for Line 2 should have read:
Powershell.exe -sta -executionpolicy remotesigned -WindowStyle Hidden ".\yourscriptname.ps1"
It seems these blocks take anything inside of '<>' and skip them. :) I have corrected Line 2 to indicate that a file name needs to be included.
Hopefully this clears up any confusion for launching the powershell script in default execution policy mode.

Mark,
Great job! This is awesome. If I wanted to run it on a local machine with zero user input, what do I need to change so it would automatically load the local machine name and populate the fields?
Thanks!
Rob T.
USAF (Ret)

Per your request, Rob!
Version 2 rev 5 now includes a Toolbox Option checkbox. Check this box and you no longer need to fill in the System Name field. Instead, the script will use the computer name you are running the script on.
Great feature request. As always, user feedback is welcome.