Installing IIS to Support the Velocity Web Services Client (VWSC)

Owned by Anand Rajaraman
Last updated: Nov 13, 2024 by Emmanuel Morales
13 min read

..Before installing and using the Velocity Web Services Client, you must first install Microsoft’s Internet Information Services (IIS) on your Velocity Server, Velocity Workstation, or dedicated IIS Server.

The Velocity Web Services Client is an optional feature. If your organization isn’t comfortable providing remote access to your physical access control system, do not install IIS or the Velocity Web Services Client.

For details about the Windows versions supported by recent Velocity releases, please refer to Step 4 in the Introduction topic below.

The details for installing IIS to support the Velocity Web Services Client vary somewhat for each version of Windows; this information is provided in the appropriate version of the Velocity Web Services Client Installation Guide and Release Notes. For your convenience, this topic provides procedures for installing IIS on Windows 10\11 Pro, Windows Server 2016, 2019, and 2022.

System Requirements

This version of the Velocity Web Services Client requires the following components:

  • A physical access control system with various hardware components controlled by Velocity 3.8.6

  • The Velocity Web Services Client software

  • A Web Server running Microsoft’s Internet Information Services (IIS) (version 6.0 or later)

  • For optimal performance, use a personal computer or tablet with a modern web browser. Recommended browser versions are:

    • Google’s Chrome (64-bit): Minimum version 118.0; recommended version 124.0 or later

    • Microsoft’s Edge (64-bit): Minimum version 117.0; recommended version 120.0 or later

    • Mozilla’s Firefox (64-bit): minimum version 119.0; recommended version 124.0 or later

    • Apple’s Safari (64-bit): Minimum version 17.0; recommended version 17.4 or later

Hirsch recommends using Google Chrome (64-bit) with a device display resolution of 1280 x 720 px. At lower resolutions, parts of large dialogs, such as Credential Properties, may not be fully visible.

Microsoft Internet Explorer is no longer supported.

Prerequisites

The Velocity Web Services Client can be installed during a new Velocity installation or separately after the Velocity installation. After installing this client, you must also perform a few configuration and setup tasks.

Installing Microsoft’s Internet Information Services (IIS)

Before installing and using the Velocity Web Services Client, you must first install Microsoft’s Internet Information Services (IIS) on your Velocity Server, Velocity Workstation, or dedicated IIS Server. 

The table below lists the supported Windows versions for each of these system roles.

System Role

The Windows versions supported by Velocity 3.8.6

System Role

The Windows versions supported by Velocity 3.8.6

Velocity Server or Dedicated IIS Server

  • Windows Server 2022

  • Windows Server 2019

  • Windows Server 2016

Velocity Standalone Workstation

  • Windows Server 2022

  • Windows Server 2019

  • Windows Server 2016

  • Windows 11 Pro

  • Windows 10 Pro

Installing IIS on Windows 10 Pro

  1. Open the Control Panel and click on Programs.

  2. Under Programs and Features, select Turn Windows Features on or off.

  3. In the Windows Features dialog, expand the folders for .NET Framework 3.5 (includes .NET 2.0 and 3.0), the .NET Framework 4.7 Advanced Services, and Internet Information Services to view the available options.

  4. Select the following features to install IIS and additional IIS Management features.

    • .NET Framework 3.5 (includes .NET 2.0 and 3.0)

      • Windows Communication Foundation HTTP Activation

      • Windows Communication Foundation Non-HTTP Activation

    • .NET Framework 4.7 Advanced Services

      • ASP.NET 4.7

      • WCF Services

        • TCP Port Sharing

    • Internet Information Services

      • Web Management Tools

        • IIS 6 Management Compatibility

          • IIS 6 Management Console

          • IIS 6 Scripting Tools

          • IIS 6 WMI Compatibility

          • IIS 6 Metabase and IIS 6 configuration compatibility

        • IIS Management Console

      • World Wide Web Services

        • Application Development Features

          • .NET Extensibility 3.5

          • .NET Extensibility 4.7

          • ASP.NET 3.5

          • ASP.NET 4.7

          • ISAPI Extensions

          • ISAPI Filters

          • WebSocket Protocol

      • Common HTTP Features

        • Default Document

        • HTTP Errors

        • Static Content

      • Performance Features

        • Static Content Compression

  1. Click OK and wait a few moments for the features to install.

  2. When prompted, restart your PC to apply the changes.

Installing IIS on Windows 11 Pro

  1. Open the Control Panel and click on Programs.

  2. Under Programs and Features, select Turn Windows Features on or off.

  3. In the Windows Features dialog, expand the folders for the .NET Framework 4.8 Advanced Services, and Internet Information Services to view the available options.

  4. Select the following features to install IIS and additional IIS Management features.

    • .NET Framework 4.8 Advanced Services

      • ASP.NET 4.8

      • WCF Services

        • TCP Port Sharing

    • Internet Information Services

      • Web Management Tools

        • IIS 6 Management Compatibility

          • IIS 6 Management Console

          • IIS 6 Scripting Tools

          • IIS 6 WMI Compatibility

          • IIS 6 Metabase and IIS 6 configuration compatibility

        • IIS Management Console

        • IIS Management Scripts and Tools

      • World Wide Web Services

        • Application Development Features

          • .NET Extensibility 3.5

          • .NET Extensibility 4.8

          • ASP.NET 3.5

          • ASP.NET 4.8

          • ISAPI Extensions

          • ISAPI Filters

          • WebSocket Protocol

        • Common HTTP Features

          • Default Document

          • Directory Browsing

          • HTTP Errors

          • Static Content

        • Performance Features

          • Static Content Compression

  5. Click OK and wait a few moments for the features to install.

  6. When prompted, restart your PC to apply the changes.

Installing IIS on Windows Server 2016

  1. Open Control Panel.

  2. Locate and click on the “Turn Windows Features on or off” link.

  3. In the resulting Server Manager window, click the Features item (in the left pane) and click the Add Features link.

  4. In the resulting Add Roles and Features Wizard, provide the necessary information and click Next on each of the first few pages.

  5. On the Select server roles page of the wizard, check [√]the Web Server (IIS) role, and click Next.

  6. In the resulting dialog that asks ‘Add features that are required for Web Server (IIS)?’, check[√] the option to ‘Include management tools (if applicable),’ and click the Add Features button.

  7. On the Select features page of the wizard, check [√]the following options (as shown in the screen capture), and click Next.

    • .NET Framework 3.5 Features

    • .NET Framework 3.5 Features > .NET Framework 3.5 (includes .NET 2.0 and 3.0)

    • .NET Framework 4.6 Features > ASP.NET 4.6

    • .NET Framework 4.6 Features > WCF Services > TCP Port Sharing

  8. Read the displayed information on the wizard's resulting Web Server Role (IIS) page and click Next.

  9. On the wizard's resulting Select role services page, check [√] the following options (as shown in the subsequent screen capture), and click Next.

    • Web Server

    • Web Server > Common HTTP Features

    • Web Server > Common HTTP Features > Default Document

    • Web Server > Common HTTP Features > Directory Browsing

    • Web Server > Common HTTP Features > HTTP Errors

    • Web Server > Common HTTP Features > Static Content

    • Web Server > Common HTTP Features > HTTP Redirection

    • Web Server > Health and Diagnostics

    • Web Server > Health and Diagnostics > HTTP Logging

    • Web Server > Performance

    • Web Server > Performance > Static Content Compression

    • Web Server > Security

    • Web Server > Security > Request Filtering

    • Web Server > Application Development

    • Web Server > Application Development > .NET Extensibility 3.5

    • Web Server > Application Development > .NET Extensibility 4.6

    • Web Server > Application Development > ASP.NET 3.5

    • Web Server > Application Development > ASP.NET 4.6

    • Web Server > Application Development > ISAPI Extensions

    • Web Server > Application Development > ISAPI Filters

    • Management Tools

    • Management Tools > IIS Management Console

    • Management Tools > IIS 6 Management Compatibility

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Management Console

    • Management Tools > IIS 6 Management Compatibility > IIS 6 Scripting Tools

    • Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility

    • Management Tools > IIS Management Scripts and Tools

  10. On the wizard's resulting Confirm installation selections page, check [√] the option to ‘Restart the destination server automatically if required, and review the displayed information to determine whether it is correct.

    • If something is not correct, click Previous to return to the previous page and make the necessary changes.

    • If everything is correct, click Install.

      Progress messages on the Installation progress page of the wizard are displayed until the installation is complete.

  11. Verify that the Web Server (IIS) role was installed in the Server Manager window. You can then close the Server Manager window and the Control Panel.

Installing IIS on Windows Server 2019

  1. Open Control Panel.

  2. Locate and click on the Programs and Features link.

  3. Once in the Programs and Features window, click on the Turn Windows Features on or off link.

  4. In the resulting Server Manager window, click the Dashboard item (in the left pane), and click the Add roles and features link.

  5. In the resulting Add Roles and Features Wizard | Before you Begin, click Next.

  6. Select Role-based or feature-based installation in the Add Roles and Features Wizard | Installation Type, and click Next.

  7. In the resulting Add Roles and Features Wizard | Server Selection, select a server from the server pool and click Next.

  8. In the resulting Add Roles and Features Wizard | Server Roles, select Web Server (IIS).

  9. In the resulting dialog that asks Add features that are required for Web Server (IIS)?, check the option to Include management tools (if applicable), and click the Add Features button, then click Next.

  10. On the Select features page of the wizard, check the following options (as shown in the screen capture), and click Next.

    • .NET Framework 3.5 Features

    • .NET Framework 3.5 Features > .NET Framework 3.5 (includes .NET 2.0 and 3.0)

    • .NET Framework 4.7 Features

    • .NET Framework 4.7 Features > .NET Framework 4.7 (Installed)

    • .NET Framework 4.7 Features > WCF Services > TCP Port Sharing (Installed)

  11. In the resulting Add Roles and Features Wizard | Web Server Role (IIS), read the displayed information, and click Next.

  12. On the wizard's resulting Select role services page, check the following options (as shown in the subsequent screen capture), and click Next..

    • Web Server

      • Web Server > Common HTTP Features

      • Web Server > Common HTTP Features > Default Document

      • Web Server > Common HTTP Features > Directory Browsing

      • Web Server > Common HTTP Features > HTTP Errors

      • Web Server > Common HTTP Features > Static Content

      • Web Server > Common HTTP Features > HTTP Redirection

      • Web Server > Health and Diagnostics

      • Web Server > Health and Diagnostics > HTTP Logging

      • Web Server > Performance

      • Web Server > Performance > Static Content Compression

      • Web Server > Security

      • Web Server > Security > Request Filtering

      • Web Server > Application Development

      • Web Server > Application Development > .NET Extensibility 3.5

      • Web Server > Application Development > .NET Extensibility 4.7

      • Web Server > Application Development > ASP.NET 3.5

      • Web Server > Application Development > ASP.NET 4.7

      • Web Server > Application Development > ISAPI Extensions

      • Web Server > Application Development > ISAPI Filters

    • Management Tools

      • Management Tools > IIS Management Console

      • Management Tools > IIS 6 Management Compatibility

      • Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility

      • Management Tools > IIS 6 Management Compatibility > IIS 6 Management Console

      • Management Tools > IIS 6 Management Compatibility > IIS 6 Scripting Tools

      • Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility

      • Management Tools > IIS Management Scripts and Tools

  13. On the wizard's resulting Confirm installation selections page, check the option to Restart the destination server automatically if required, and review the displayed information to determine whether it is correct.

    • If something is not correct, click the Previous button to make the necessary changes

    • If everything is correct, click the Install button

  14. Progress messages on the Installation progress page of the wizard are displayed until the installation is complete.

  15. Verify that the Web Server (IIS) role was installed in the Server Manager window and then close the Server Manager window and the Control Panel.

Installing IIS on Windows Server 2022

  1. Open Control Panel.

  2. Locate and click on the Programs and Features link.

  3. Once in the Programs and Features window, click on the Turn Windows Features on or off link.

  4. In the resulting Server Manager window, click the Dashboard item (in the left pane), and click the Add roles and features link.

  5. In the resulting Add Roles and Features Wizard | Before you Begin, click Next.

  6. Select Role-based or feature-based installation in the Add Roles and Features Wizard | Installation Type, and click Next.

  7. In the resulting Add Roles and Features Wizard | Server Selection, select a server from the server pool, and click Next.

  8. In the resulting Add Roles and Features Wizard | Server Roles, select Web Server (IIS).

  9. In the resulting dialog that asks Add features that are required for Web Server (IIS)?, check the option to Include management tools (if applicable), and click the Add Features button, then click Next.

  10. On the Select features page of the wizard, check the following options (as shown in the screen capture), and click Next.

    • .NET Framework 3.5 Features

    • .NET Framework 3.5 Features > .NET Framework 3.5 (includes .NET 2.0 and 3.0)

    • .NET Framework 4.8 Features

    • .NET Framework 4.8 Features > .NET Framework 4.8 (Installed)

    • .NET Framework 4.8 Features > WCF Services > TCP Port Sharing (Installed)

  11. In the resulting Add Roles and Features Wizard | Web Server Role (IIS), read the displayed information, and click Next.

  12. On the wizard's resulting Select role services page, check the following options (as shown in the subsequent screen capture), and click Next.

    • Web Server

      • Web Server > Common HTTP Features

      • Web Server > Common HTTP Features > Default Document

      • Web Server > Common HTTP Features > Directory Browsing

      • Web Server > Common HTTP Features > HTTP Errors

      • Web Server > Common HTTP Features > Static Content

      • Web Server > Common HTTP Features > HTTP Redirection

      • Web Server > Health and Diagnostics

      • Web Server > Health and Diagnostics > HTTP Logging

      • Web Server > Performance

      • Web Server > Performance > Static Content Compression

      • Web Server > Security

      • Web Server > Security > Request Filtering

      • Web Server > Application Development

      • Web Server > Application Development > .NET Extensibility 3.5

      • Web Server > Application Development > .NET Extensibility 4.8

      • Web Server > Application Development > ASP.NET 3.5

      • Web Server > Application Development > ASP.NET 4.8

      • Web Server > Application Development > ISAPI Extensions

      • Web Server > Application Development > ISAPI Filters

      • Web Server > Application Development > WebSocket Protocol

    • Management Tools

      • Management Tools > IIS Management Console

      • Management Tools > IIS 6 Management Compatibility

      • Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility

      • Management Tools > IIS 6 Management Compatibility > IIS 6 Management Console

      • Management Tools > IIS 6 Management Compatibility > IIS 6 Scripting Tools

      • Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility

      • Management Tools > IIS Management Scripts and Tools

  13. On the wizard's resulting Confirm installation selections page, check the option to Restart the destination server automatically if required, and review the displayed information to determine whether it is correct.

    • If something is not correct, click the Previous button to make the necessary changes

    • If everything is correct, click the Install button

  14. Progress messages on the Installation progress page of the wizard are displayed until the installation is complete.

  15. Verify that the Web Server (IIS) role was installed in the Server Manager window and then close the Server Manager window and the Control Panel.

Configuring the Network Port used by the Default IIS Web Site

The Velocity Web Services Client works like a typical Web page and connects to Microsoft’s IIS using the HTTP protocol. The default network port is 80, which some other programs might already be using.

If you want to use a network port other than the 80, you can perform the following steps to configure the network port used by the default IIS Web site to communicate with the Velocity Web Services Client.

  1. From your Windows Server Start menu (on the computer where IIS and the Velocity Server are installed), select Administrative Tools > Internet Information Services (IIS) Manager

  2. In the Connections pane of the Internet Information Services (IIS) Manager window, expand the computer name, expand Sites, and then click on Default Web Site

  3. In the Actions pane (under Edit Site), click on Bindings

  4. In the resulting Site Bindings dialog, click the HTTP entry, and then click on Edit

  5. In the resulting Edit Site Bindings dialog, enter the desired value (such as 8080) for the Port, and click OK

  6. Close the Site Bindings dialog

  7. In the Actions pane of the Internet Information Services (IIS) Manager window (under Manage Web Site), click Stop, and then Start

Ensuring that the Network Port used by the Default IIS Web Site is Allowed Through Your Firewalls

Because the Velocity Web Services Client communicates across a shared network (instead of a dedicated physical security network), you will have to work with your network administrator to ensure that the network port used by the Default IIS Web Site is allowed through your firewalls. Some networks use the software firewall provided with Microsoft Windows, others use a software firewall provided by a different vendor (as shown in the following image), and high-security networks include hardware firewalls.

Because the firewalls on a network can vary so much, we cannot provide a detailed procedure for your specific network.  But the following example for the Windows 10 Pro Firewall should help illustrate the general process.

  1. Open the Control Panel, and click on the Windows Firewall link.

  2. Click on the Advanced settings link (in the left column).

  3. In the resulting Windows Firewall with Advanced Security window, click on Inbound Rules (in the left pane), and then click on New Rule… in the Actions pane.

  4. Select the Port option on the Rule Type page of the resulting New Inbound Rule Wizard, and then click Next.

  5. On the Protocol and Ports page, select the TCP option, select the Specific local ports option, enter the desired value (such as 8080), and click Next.

  6. On the Action page, click Next to accept the default selection.

  7. On the Profile page, click Next to accept the default selections.

  8. On the Name page, enter the required name in the Name field, optionally enter a description in the Description field, and click Finish.
    This allows the Network Port used by the Default IIS Web Site through your Firewalls