Computer Audit Tool

[llewxam]

I'd like to start by saying that this is not a network discovery tool, I keep wishing that it was and maybe through WMI I could accomplish that some day, but this tool is fast enough to execute that no users have ever minded a 10 second interruption in their workday as of yet. (I know some tools exist on the forum for domain environments, but many offices are workgroup and I have had no luck in using those...)

Now that I have stated what it is not, what this tool does is gathers the following information:

• The computer's name
• The operating system, architecture, service pack level, and COA
• The local users
• If MS Office is installed, gathers the version(s) and COA
• The CPU name and speed
• Installed RAM, free RAM, and swap file info
• Local drive letters, labels, total and free space, and percent full
• Network drive letters, their UNC path, total and free space, and percent full
• The computer's IP address
• Optional notes, such as "front desk PC" or "runs slow", whatever is helpful to know later

All of that is bundled in to a CSV file, with the options of creating a new CSV for each machine named the same as the computer's name, an append mode that you can name after the site, or the cool part - there is an option to create a customized agent. In the customized mode, you pre-define the site name and a network path accessible by all machines, and the script will create a new customized script with those details hardcoded and compile it for you! Then all you have to do is get on to any networked pc and browse to the path, run the agent, and in 2 seconds you're done with that machine.

Please pay attention to the files required to compile at the top of the script - I know it is a long list but only 2 are required to be downloaded from the forum, the rest are in the AutoIt install folder in Includes or aut2exe folders. I could have included the paths in the code, but found this was just.....nicer (for me).

I have found this to be very helpful, and I even had one client thank me for doing it, as he realized the value of me having all of that information if he had a problem. Hopefully there are some other field techs out there, or folks in charge of their office's IT needs, who can also benefit from this. Another benefit for field techs is that with this list you can easily review it later and then call them up a few days later to tell them what upgrades they need and get a re-visit

Enjoy

Ian

EDIT: Updated code to include a couple bug fixes

Audit Tool.au3

Edited May 23, 2012 by llewxam

[CesarL]

Looks good, but when executing shows:

Line 5248 (File ""):

Error: Duplicate function name.

Using Latest version: v3.3.8.1

Edited May 9, 2012 by CesarL

[CesarL]

Looks good, but when executing shows:

Line 5248 (File ""):

Error: Duplicate function name.

Used WinAPIEx_3.6_3380 instead of WinAPIEx_3.7_3361 and the build worked fine.

[CesarL]

Looks good, but when executing shows:

Line 5248 (File ""):

Error: Duplicate function name.

Used version WinAPIEx_3.6_3380 instead of WinAPIEx_3.7_3361 and the build worked fines now.

[lgvlgv]

i dont have #include <LocalAccounts.au3> is this file missing?

[Chimaera]

If you had read the top of the Audit Tool au3 you would have found this

Requirements:

WinAPIx.au3 (Yashied)

LocalAccount.au3 (engine)

[lgvlgv]

Thx, i mist the Localaccount

[BrewManNH]

The line to include LocalAccount.au3 has a typo in it, it should be #include <LocalAccount.au3> it currently says #include <LocalAccounts.au3>

[llewxam]

OOOOPS, I'll look at that shortly. I think there is also a minor glitch in the custom agent where a quote is misplaced. I will repost when these items have been corrected.

Ian

[llewxam]

I, for reasons unknown, had LocalAccount and copied it as LocalAccounts, which is why I had no problems. Silly, sorry about that, it has been changed in the code. I also found the issue with adding quotes at the wrong time in the compiled agent on enumerating network mapped drives.

Ian

[llewxam]

Code updated, I was finding many servers were crashing before it finished, thought it might have been related to not having Office installed but it turned out to be the _AccountEnum function of LocalAccount. I included a check to make sure there was a result, now it doesn't crash.

Ian