Thanks

The link below provides instructions for doing this installation on a previous version of Windows. Although there are similarities to a CGI mode install on W2k3, there are certain places where you need to do things slightly differently. Most of the differences are with directory permissions from the windows explorer & other subtle changes within IIS manager control panel. I've tried to summarize some of the steps in brief for you below the link, with any luck the combination of detail information found at this link and the notes I’ve made below might be enough to get you up and running.

http://sawmill.net/cgi-bin/sawmill7/docs/sawmill.cgi?dp+docs.technical_manual.iiscgi

In summary, as long as you have IIS6 Installed, The basics of how to get Sawmill installed in CGI mode are as follows:

Install Sawmill using the pre-packaged windows installer provided as part of the normal distribution. Once Sawmill is installed go into control panels->administrative tools->Services and stop the Sawmill service. You will need to create a “cgi-bin” folder in your webserver directory, and move the “SawmillCL.exe” binary and the “LogAnalysisInfo” folder into that cgi-bin folder within your IIS6 webserver directory. You will also need to create a directory for Sawmill temporary images in that same directory - call it “sawmill”. I have not had time to figure out the minimalist set of permissions to allow for the maximum security on the platform, so currently to get things working I've set up all folders to have write permissions by all users (right click folders in windows explorer, and select security (I think is the menu tab) and modify permissions accordingly for all users & groups. You will also have to load up the IIS 6 manager control panel and change permissions (see the web link about this) & also allow for executables to be run from the cgi-bin directory there’s a pull down to allow “executables” run permissions. I believe there's also a step to set up the "URL" for a particular directory in the IIS manager so that you can resolve this directory from the web browser. The other things to do are to use the IIS control panel and set run Unknown CGI services to "enable" from the main IIS menu (this again is a case where security is compromised and will allow everything CGI to run, with enough time I should be able to figure out a more minimalist approach to permissions here). There are probably a few things I've missed in this quick summary however, that will get you most of the way.

Once you've set this up, you should be able to access your CGI install directly via http://www.yourdomain.com/cgi-bin/SawmillCL.exe (or where ever you've installed the cgi-bin directory in the hierarchy of the website – and created a URL to access it.) If you see a page not found that's bad news, if you see something about not having "permissions" or internal server error (I think error 500) then this is good news because the browser is resolving your install - however, something still needs to be fixed in terms of permissions to get it up and running. If everything goes well you will be prompted for the location of the webserver root directory (the path for the sawmill temporary image folder you've created) and also the URL to get to that directory from the browser. If you get this and successfully see the "sawmill" logo when you submit the information! YOU'VE DONE IT! CONGRATS! From this point forward you will be able to log in and set up profiles.