Windows ISAPI Module Install

1. Checking the version of IIS

1. Select ‘Help’
2. At the bottom of the Help menu, select ‘About Internet Information Services’
3. Check the activated window
4. Check the version of Internet Information Services (Version 7.0-) IIS

2. Checking the OS Bit

1. Right click on Computer to check its properties (it can be checked on control panel-all control panel items-system)
2. Check the version of Windows
3. Check the Bit of OS

3. Install and download Agent

• Refer the instruction of installation https://kuipernet.gitbooks.io/install/content/kuipernet/windows.html

4. Check the application pools.

• In the 32bit OS environment, the application program pool is also 32bit.
• The way to check application program pool in the 64bit OS environment
• Select an application pool.
• Right-click on the application pool you will check.
• Click on advanced settings.
• Check a Bit that is being used with advanced settings.
• If True is selected for the Use 32-bit application, you must apply the 32-bit module file (KPNPlugin32.dll)

5. Create KPNPlugin.dll directory

• Create the folder of KPNPlugin.dll file.
  1. Create a directory for the KPNPlugin.dll file under the kpn_client path
  2. Move KPNPlugin.dll file to the created directory

6. Authorize the created directory

1. right click on the created directory.
2. Select properties.
3. Select security tab on the activated properties information.
4. Select ‘Users’ of usernames.
5. Click on ‘Edit’
6. Select ‘Users’ of usernames.
7. Check Allow all permission
8. Select ‘Ok’

7. Add KPNPlugin.dll mapping

Respective sites(except for FTP) should be mapped as below.

1. Select the web service registered on IIS.
2. Sellect the activated handler mapping on the right.
3. When the Handler Mapping screen is activated, select Add Wildcard Script Mapping on the right.
4. Enter KPNPlugin.dll path
5. name the mapped KPNPlugin.dll
6. Select the OK button
7. Select Edit Feature Permission
8. Make sure Read / Script / Execute check is enabled.
9. If you do not check Read / Script / Execute, the following phenomenon occurs.
   

8. Restart IIS

1. Select the IIS registration name to return to the beginning.
2. Restart IIS by clicking on ‘restart’ in the upper right

9. checklist

• Check if the web server works properly after restarting IIS.

• In case that the image displays ‘x’ or has not been activated, check like below
  
  

  1. Right click on the inactive image to check its properties.
  2. Check the address of the image by properties.
  3. Select the registered IIS services with inactive images.
  4. Select the directory of the enabled image file on properties.
  5. Select the registered KPNPlugin.dll
  6. Select the delete button

• Delete the execute authority of the directory in which KPNPlugin.dll has been delete.

  If you do not remove the execute authority of the directory, you can be damaged in case that malicious file is inserted such as image Web shell. Remove the execute authority of the directory to prevent files such as the image Web shell.
  Remove the execute authority of directory to prevent files such as the image Web shell.

• How to delete the execute authority
  

  1. Select the service in which mapping has been deleted on IIS.
  2. Select the directory in which mapping has been deleted.
  3. Select Edit Feature Permission on the right.
  4. Release script / execute authority on Edit Feature Permission.
  5. Select OK.

11. In Case of Errors

• In case that an error such as 404 occurs(no resources), it is applied the same as Add 7. KPNPlugin.dll mapping of IX.Windows 2012 ISAPI Module Install

Required checklist when an error occurs:
After you register the IIS handler mapping, you must determine the path type. If paths such as local, file are specified in the path type, an error will occur. The path type have to be configured to Unspecified to ensure that it is applied correctly.