Windows Computer Profiler

Tag: windows Author: enriqre Date: 2009-08-30

We create a lot of internal tools in order to work with the data we use. Occasionally we'll run into a problem with one of those tools on a designer or artists computer and will need to spend considerable time on there computer to try and diagnose where the problem may be coming from.

This creates problems because while a programmer is trying to diagnose an issue on the user's computer the user is unable to continue with their work. What we'd like to be able to do instead is run an app that will generate a report that a programmer can look at on their own machine in order to at least rule out some of the more common and obvious problems.

Example information we'd need would be all the environment variables, registry info and installed applications. Is there a decent existing tool that will accomplish this or would it be better to just roll our own?

Best Answer

Start > All Programs > Accessories > System Tools > System Information


Start > Run "msinfo32"


File > Export

and you can take the file back to your desk.


Good answer. Something new everyday!
On Windows XP Start->Run "msinfo32"
@Bas, Thanks! I dereferenced the wrong shortcut file. Fixed. For the record: Start > Run "helpctr" also provides access to the same information. Click "Use Tools to view your computer information and diagnose problems", then "Advanced System Information", then "View detailed system information (Msinfo32.exe)".

Other Answer1

Using Windows Powershell setting up a script that can provide the needed information should be relatively easy. The script center is a great starting place to learn Powershell. If you like to listen to podcasts I would recommend The Powerscripting podcast.


+1 - the script center was the link I was oiginally looking for before posting my answer. Good answer.

Other Answer2

This probably should be on, since it deals with an end user's configuration and is not necessarily a programming issue.

That said, I would think that you should be able to write a WMI script to cover this.

You'd want to start here