How do I get a copy of the IISLogs component?
Visit IISLogs evalution webpage
What is IISLogs?
This component will help administrators and developers easily manage log files created to Internet
Information Server 5.0 and 6.0. The component will provide configurable options compressing files
using ZIP, and/or just deleting files after a configurable setting based on time. One of the benefits
will help maintain and conserve precious disk space on servers.
What platforms will IISLogs run on?
Windows XP Professional, Windows 2000 and Windows 2003
What version of .NET Framework needed to run?
.Net Framework 1.1
What .NET language will this be written in?
Currently there is a VB.NET version, a C# version is under development
What will this component do to the logfiles?
Based on a configurable time setting, it will zip and/or delete files
Will IISLogs monitor multiple directories?
Yes, it can monitor multiple directories or a single directory, the preference is yours.
Can I do this same option with VBScript, pkzip or winzip?
How much will IISLogs cost?
IISLogs is priced per machine ($29.95 for 1 - 25 computers) ($24.95 for 26 > computers).
Enterprise, educational and volume licensing also available (contact [email protected] for more details).
Pricing is the same for Stand-Alone EXE or Windows Service Version.
Will IISLogs component run as a Windows Service or a stand-alone EXE?
There are three versions (A stand-alone EXE and a Windows Service) - both of these are full versions.
A third version is a stand-alone EXE (IISLogs Lite Version).
Will IISLogs component require running as an Administrator credentials?
This still has to be worked out for configuration, the default setting is targeted NOT to require
running as an Administrator. It will require permissions to to the directories that Store Internet
Information server and related log files. Will IISLogs record logging information to central SQL Server?
This is being considered, all current logging information is stored in a configurable log directory
located on the local machine. Future enhancements will consider this option.
What are the main *features* of IISLogs?
There are many options to configure IISLogs, each option provides their own configurable settings
to provide flexibility. The first option will allow for monitoring one or more specific
directories (c:wwwLogsw3svc1mySite). An additional option will monitor entire directory structures.
Either option will ZIP and/or Delete
files based on configured settings. IISLogs can be setup to JUST ZIP files and/or delete files in
the same directory structure. What we mean by directory structures? This is simple, by default,
Internet Information Server puts web log files in %SystemRoot%System32Logfiles directory with
several sub-directories below. There could be sub-directories for FTP, SMTP and WWW services;
they might be named such as (MSFTPSVC1, SMTPSVC1, W3SVC1, W3SVC2 etc.).
This option provides to monitor all of these sub-directories. If your running many websites
on the same server, you might have configured IIS to store these log files in a different directory
(IE D:wwwlogs). IISLogs can monitor custom directory structures also.
The second feature is to monitor the directories associated with the Microsoft SMTP Service.
If your web applications use this functionality, these directories fill up with un-needed files.
This feature is simple; it deletes files after a certain configurable date. This SMTP feature
is effective in helping keep those directories free of 1000’s of bad emails and old files.
The third feature is similar to the SMTP option; it will monitor specific directories and
delete files based on its own configured setting. Why does IISLogs have this option when
it can be setup in the first option? First of all, this option monitors just single
directories not entire directory structures like the first option does. There are
occasions where certain directories need to have different retention periods that other
directory structures. This option provides for this very situation.
File Naming Options allows for someone to control what the ZIP file is named.
This is available in both the Stand-Alone and Windows Service version.
Does IISLogs read the IIS metabase to get any IIS settings?
Yes, using the IISLogsGUI, part of the IISLogs suite, has a feature called EasyConfig that
will read the metabase and automatically configure the required specific Directories.
Can I turn off detail logging?
Yes, this will greatly reduce the need to receive a daily email on what happened on that particular machine.
This is only recommended if you want IISLogs to run and not be notified about what is happening on the machine.
Will IISLogs run if I *JUST* copy the directory to another server w/o first running the setup.exe?
Yes, you can just copy the directory to another server without running the setup.exe as long as a few
things are done. IISLogs is designed to be very easy to distribute and setup on many computers w/o manually
installing on every machine. 1 - The server getting the files copied to is setup the same or similiar.
the biggest thing is where the Log files are stored. From experience, shops with a lot of web servers
typically store their web logs files in a central directory (such as D:Logfiles or D:wwwlogs).
2 - Below the InstallDirOfIISLogslogsPolicyAgreements directory is copied too.
This is a security mechanism built into IISLogs to insure the administrator has thought through
the configuration. IISLogs won't ZIP or Delete files w/o these files being present.
3 - The IISLogs.exe.config has the appropriate log file paths on the target server.
If you have further questions how to automate distribution of IISLogs w/o having to manually
install on every machine, please contact [email protected]Can I edit the IISLogs.exe.config using notepad?
Yes except for the MailUID and and MailPWD values which ONLY can be done through IISLogsGUI.
These values are stored in a encrypted format.
How do I unzip or uncompress several zip files so I can re-run my stats program like Deep Matrix or Web Trends?
Use the built-in Windows 2003/XP to hightlight and compress all ZIP files residing in the log file directories.
If your using Windows 2000, you can use WINRAR or WINZIP to highlight and unzip/uncompress the files.