GroupWise Mailbox Audit Log to CSV Converter


The GroupWise Mailbox Audit is a nice feature, but it is time consuming to read through the entire log to find the information you need.

This is a VB script that parses the GW Check logs and converts them to a CSV file containing the PO.DOMAIN, userID, Last GW account activity, and license type.

This way you can open it up in a spreadsheet or import it into a database. This makes it easy to find inactive accounts and clean them up. It is also useful if you need to know which users use the Full or Limited (Web access, pop3, imap) GroupWise license.

NOTE: Instructions are also contained in the script as comments.

Copy the logs to a common directory such as c:\gwaud. The mailbox audit log can be created from the stand alone GWCheck or from the one in ConsoleOne. The audits can also be configured as automated scheduled POA events.

Each post office will have a gwcheck.log that will need to be saved in c:\gwaud as a different name. You can call it anything as long as it has a .LOG extension. It may be a good idea to name it YOURPONAME.LOG so you can tell if you have all your PO logs.

Copy the GWAUD.VBS script to the same directory as the logs. Go to a command prompt and change to that directory. Then type GWAUD.VBS to run the script.

The script will read *.LOG in that directory and create one combined CSV file. This script was run on Windows XP but should run on any Windows platform that has VB scripting installed.

The command prompt will appear shortly indicating that the script completed. You will have a gwaudit.CSV file containing the users, PO.DOMAIN, date, and license type. There will also be a GWerr.csv file containing users where GWcheck encountered errors processing their DB if any.

If errors are found, you should correct the PO UserDB errors, run the GWCheck Audit again, and run the GWAUD.VBS script again to get accurate results.

If the account has no activity date and time, 1/1/2000 1:01 will show up as the date. If you intend to delete inactive accounts, please read TID 10069532 and TID 10071572 to understand what activity causes the time to be stamped in the user's DB.

This script was written quickly with no error checking, but it is something you should find useful.


How To-Best Practice
Comment List
    Hi This would be an awesome tool if it work properly,
    the problem I'm experiencing is as follows :

    I have run the vb script for my one po with 1664 users. completes fine.

    when reading the csv file i see that the date field is a bit wonkey, some dates appear 06/23/08 time and other dates appear 2006/23/08 ...