To install/uninstall WebKnight on the local or remote machine you can use the file install.vbs/uninstall.vbs from the setup folder. This method will install WebKnight as a global filter on the selected host or localhost.

Manual installation as a global filter in IIS:

  1. Copy all the files in the Setup folder to a local folder on the server (e.g. C:\Program Files\AQTRONIX WebKnight).
  2. Open the IIS snap-in.
  3. Right-click the server name (not the site name) (in IIS 6 right-click Web Sites) under Internet Information Services in the MMC, and then select Properties.
  4. Verify that WWW Service is displayed in the Master Properties drop-down list, and click the Edit button. For IIS 6 go to next step.
  5. Choose the ISAPI Filters tab, and then click the Add button.
  6. In the Filter Properties window, type WebKnight, and enter the full path to WebKnight.dll in the Executable box.
  7. Select OK to close each dialog.
  8. Review any settings of WebKnight, by running config.exe that you copied locally.
  9. Restart IIS.

 

Manual installation as a site filter in IIS:

  1. Copy all the files in the Setup folder to a local folder on the server (e.g. C:\Program Files\AQTRONIX WebKnight\W3SVC1). Note: it is important to have a unique folder for each WebKnight installation!
  2. Open the IIS snap-in.
  3. Right-click the site name (not the server name) under Internet Information Services in the MMC, and then select Properties.
  4. Choose the ISAPI Filters tab, and then click the Add button.
  5. In the Filter Properties window, type WebKnight, and enter the full path to WebKnight.dll in the Executable box.
  6. Select OK to close each dialog.
  7. Review any settings of WebKnight, by running config.exe that you copied locally. (Make sure global filter capabilities are disabled: uncheck ‘Is Installed As Global Filter’)
  8. For IIS 6 you need to make sure that each site for which you installed WebKnight as a site filter, has its own application pool. This is because only one instance of WebKnight can be run in any application pool. By default all sites are run in the DefaultAppPool and can only contain one instance of WebKnight, so you can only have one site filter, unless you specify a different application pool for any additional site on which you are running WebKnight as a site filter.
  9. Restart IIS.

 

If you want to import your settings from urlscan, you can do that by copying the file urlscan.ini to the WebKnight directory. Delete WebKnight.xml (or rename it) and your settings from urlscan.ini will be imported in a new WebKnight.xml file when you restart your web server. This can be useful if you experienced problems with your urlscan installation and you had to customize the settings of urlscan and want to keep using these settings. If you want to load the default settings again, you can do that by deleting the files WebKnight.xml and urlscan.ini in the directory WebKnight and a new WebKnight.xml will be made with the default settings when you restart your web server.

Post By Editor (2,827 Posts)

Website: →

Connect