Ok - I've been emailing Mike a few times, and I have an audit.vbs I'd like for some of the high-end users (and moderators) to take a look at.
I needed to modify this because I felt that I shouldn't have to have multiple audit.vbs files for different configurations. For example, I use the same audit.vbs to run against a dynamic OU that is being populated with computers daily and then again at a different time during the day where it will query a static list of servers.
I'm not totally done with it, as I'm not sure how far to go with the command-line switches...let me know - should I just mimic all the audit.conf settings?
Am I crazy, should I have even done this?
Basically, I added some command-line switches:
computer: (computername)
user: (domain\username)
password: (password)
config: (name of .conf file to use, ex. "x:\path\config.con")
list: (path of computer list to run against, ex. "x:\path\computerlist.txt")
*if you have spaces in the either the config or computer list paths, use quotes...
I added a section that had some default configuration parameters, which get superseded by the command-line switches (i.e. if you downloaded and ran the file without having access to the config files).
I also told audit.vbs to automatically default to its own directory if no path was specified for the audit.conf files (using strScriptPath).
I couldn't get this post to take the code, so I've uploaded to my own website. Download it and give it a try:
*updated to 2.3 on 12/13/07*
http://www.vbshf.com/vbshf/forum/forums ... mentid=355