This project is read-only.
After installing Filter.NET, and after creating your managed filters its time to register Filter.NET in IIS. Filter.NET is installed at %SYSTEMROOT%\Filter.NET\[version], the location where you can find the tool to register Filter.NET with IIS. The tool is called filter_regiis.exe with the following syntax:

c:\Windows\Filter.NET\v1.0.1>filter_regiis.exe

Administration utility (1.0.1) to install and uninstall Filter.NET on the local machine.

Usage: filter_regiis.exe -i [-s <path>] | -u
-i            Install Filter.NET at global or site scope
-s <ID>       Install Filter.NET at the specified site ID.
-u            Uninstall Filter.NET.


Using filter_regiis with -i only will install the native ISAPI Filter at global scope (/LM/W3SVC). Using -i with -s <ID> will install the native ISAPI Filter at site scope (/LM/W3SVC/ID). Tipically, one would install Filter.NET at global scope like this (output on a WinXP):

C:\WINDOWS\Filter.NET\v1.0.1>filter_regiis.exe -i
ACL: Adding (R)ead, (E)xecute for IIS_WPG in C:\WINDOWS\Filter.NET\v1.0.1 ...
     Account IIS_WPG does not exist, and is ignored.
ACL: Adding (R)ead, (E)xecute for ASPNET in C:\WINDOWS\Filter.NET\v1.0.1 ... Done
IIS: Add ISAPI Filter Filter.NET_v1.0.1 to /LM/W3SVC ... done
IIS: Wait 30s for IIS to stop ... stopped
IIS: Wait 30s for IIS to start ... running


Remember that IIS_WPG was only added in Windows 2003, hence the warning message on the output. The output on a Windows 2003 should be like this:

C:\WINDOWS\Filter.NET\v1.0.1>filter_regiis.exe -i
ACL: Adding (R)ead, (E)xecute for IIS_WPG in C:\WINDOWS\Filter.NET\v1.0.1 ... Done
ACL: Adding (R)ead, (E)xecute for ASPNET in C:\WINDOWS\Filter.NET\v1.0.1 ... Done
IIS: Add ISAPI Filter Filter.NET_v1.0.1 to /LM/W3SVC ... done
IIS: Wait 30s for IIS to stop ... stopped
IIS: Wait 30s for IIS to start ... running


Last edited Sep 4, 2007 at 12:20 AM by thalm, version 3

Comments

No comments yet.