I have used WinAudit in the past and hadn't realised it was still being actively developed, it looks great with the new features.
I'm really interested in the Database Export feature, however the devices we will typically run WinAudit on will not have any ODBC drivers installed.
I can't see how but is there any way to save the WinAudit reports in a format which could then be opened by WinAudit on another machine and then export to the database?
Or alternatively is there a process for manually inserting the CSV report into the Database?
Also, is there any chance Windows 2000 support will return?
Jun 18, 2015 at 5:28 PM
Edited Jun 18, 2015 at 5:33 PM
Yeah, WinAudit is still going strong, like a general in wartime there's no risk of an untimely demise.
Its not possible to post records to a database when offlne. WinAudit has to create autonumbers/indentity values for primay keys etc. After that a data block is sent over the wire to the database base as a single maxrix raher a set of SQL operations. Likewise,
you cannot open a csv file in Excel and copy into a table. Of course, what WinAudit does could be broken down into steps but that would mean queueing the audit data files gathered from different machines then sending those on to the database. Typically this
is enterprise level functionality such as done by SMS which has a user agent and a service to handle the database processing. I'm not sure that's the direction a small and simple utility like WinAudit should be heading in. A possible solution in this case
would be to have a separate database for each domain/site/network.
ODBC drivers for Access and SQL Server come with Windows. Note, the client machines do not need to have Access installed to post to the database. If your requirements are not too demanding you could try SQL Server Express, its free (https://www.microsoft.com/en-gb/server-cloud/products/sql-server-editions/sql-server-express.aspx
If you are planning to use MySQL or PostgreSQL, then you will have to install their ODBC drivers if you want WinAudit to connect to those.
In terms of Windows 2000, I'm afraid not. We definitely want Visual Studio complier configured for the buffer overflow check (/GS) feature. Newer versions of VS no longer create executables for Win2000. That's the reason for dropping support for Win9X as well.
In the past, we used multiple versions of VS. However, compiler breaking changes (https://msdn.microsoft.com/en-us/library/bb531344.aspx
) mean that it is no longer easy to
build using the same code base with very dissimilar compilers. For Windows 2000, you can of course use the older version found here
. Note, it is no longer supported so there will be no bug fixes or new features.