Before installing and using the Velocity Web Services Client, you must first install Microsoft’s Internet Information Services (IIS) on your Velocity Workstation, Velocity Server, 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 look at 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; that 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 Pro, Windows Server 2016, and Windows Server 2019.
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 version 3.8.5 of the Hirsch Velocity security management system software
The optional Velocity Web Services Client
A Web Server running Microsoft’s Internet Information Services (IIS) (version 6.0 or later)
A personal computer, tablet computer, or smartphone running a relatively current Web browser such as:
Google’s Chrome minimum version is 45.0 but recommended is 110.0
Microsoft’s Edge minimum version is 18.0 but recommended is 110.0
Mozilla’s Firefox minimum version is 34.0 but recommended is 110.0
Apple’s Safari minimum version is 10.0, but it is recommended to be 16.0
Identiv recommends using Google’s Chrome browser with a device display resolution of 1024 x 768. (At a lower resolution, you will not be able to see part of an extensive dialog such as Credential Properties) .
Microsoft Internet Explorer is no longer supported.
Prerequisite
The optional Velocity Web Services Client can be installed either as part of a full Velocity 3.8.5 installation or separately after the Velocity installation. After installing this client, you must also perform a few configuration and setup tasks.
To install the Velocity Web Services Client, you must be logged into Windows using an account with administrator privileges, and you must know the name and password of the Velocity Services account (specified during the Velocity installation).
The Velocity Web Services Client must only be installed on your server. If you want to install and use this optional client, you must first install Microsoft’s Internet Information Services (IIS). The installer checks your system to see whether all prerequisites have been met.
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 standalone Workstation, Velocity Server, or dedicated IIS Server. The following table shows which versions of Windows are supported by Velocity 3.8.5 for those computer roles.
System Role | The supported version of Windows by Velocity 3.8.5 |
|---|---|
Velocity Server |
|
Velocity Standalone Workstation |
|
The following procedures are for installing IIS on Windows 10, Windows 11, Windows Server 2016, Windows Server 2019 and Windows Server 2022.
Installing IIS on Windows 10
Open Control Panel.
Locate and click on the “Turn Windows Features on or off” link.
In the resulting Windows Features dialog, expand the .NET Framework 3.5 (includes .NET 2.0 and 3.0), the .NET Framework 4.7 Advanced Services, and the Internet Information Services folders to reveal the available options.
Check [√]the following set of options, and then click OK. (Most of these options are shown in the subsequent screen capture.)
.NET Framework 3.5 (includes .NET 2.0 and 3.0)
.NET Framework 3.5 (includes .NET 2.0 and 3.0) > Windows Communication Foundation HTTP Activation
.NET Framework 3.5 (includes .NET 2.0 and 3.0) > Windows Communication Foundation Non-HTTP Activation
.NET Framework 4.7 Advanced Services > ASP.NET 4.7
NET Framework 4.7 Advanced Services > WCF Services > TCP Port Sharing
Internet Explorer 11
Internet Information Services > Web Management Tools > IIS 6 Management Compatibility
Internet Information Services > Web Management Tools > IIS 6 Management Compatibility > IIS 6 Management Console
Internet Information Services > Web Management Tools > IIS 6 Management Compatibility > IIS 6 Scripting Tools
Internet Information Services > Web Management Tools > IIS 6 Management Compatibility > IIS 6 WMI Compatibility
Internet Information Services > Web Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase and IIS 6 configuration compatibility
Internet Information Services > Web Management Tools > IIS Management Console
Internet Information Services > World Wide Web Services > Application Development Features > .NET Extensibility 3.5
Internet Information Services > World Wide Web Services > Application Development Features > .NET Extensibility 4.7
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 3.5
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.7
Internet Information Services > World Wide Web Services > Application Development Features > ISAPI Extensions
Internet Information Services > World Wide Web Services > Application Development Features > ISAPI Filters
Internet Information Services > World Wide Web Services > Application Development Features > Web Socket Protocol
Internet Information Services > World Wide Web Services > Common HTTP Features > Default Document
Internet Information Services > World Wide Web Services > Common HTTP Features > HTTP Errors
Internet Information Services > World Wide Web Services > Common HTTP Features > Static Content
Internet Information Services > World Wide Web Services > Performance Features > Static Content Compression
Enabling the WebSocket Protocol option manually in IIS increases the efficiency of the web application.
5. Close the Control panel.
Installing IIS on Windows 11
Click on the Search icon given on the Windows 11 Taskbar.
Enter features and select the option “Turn Windows features on or off“.
This will open the Window Features dialog to enable the different in-built options of Windows 11 including the Internet Information Services (IIS).
From the list of the options, click the box given for Internet Information Services Web Management Tools-> World Wide Web Services to select them.
This installs IIS along with other IIS Management Console Application features.
Click on the OK button.
Wait for a few seconds for the features to get installed and then a dialog asks you to restart your PC.Reboot your system for the changes to occur.
Installing IIS on Windows Server 2016
Open Control Panel.
Locate and click on the “Turn Windows Features on or off” link.
In the resulting Server Manager window, click the Features item (in the left pane) and click the Add Features link.
In the resulting Add Roles and Features Wizard, provide the necessary information and click Next on each of the first few pages.
On the Select server roles page of the wizard, check [√]the Web Server (IIS) role, and click Next.
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.
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
Read the displayed information on the wizard's resulting Web Server Role (IIS) page and click Next.
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
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.
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
Open Control Panel.
Locate and click on the ‘Programs and Features' link.
Once in the Programs and Features window, click on the “Turn Windows Features on or off” link.
In the resulting Server Manager window, click the Dashboard item (in the left pane), and click the Add roles and features link.
In the resulting Add Roles and Features Wizard | Before you Begin, click Next.
Select Role-based or feature-based installation in the Add Roles and Features Wizard | Installation Type, and click Next.
In the resulting Add Roles and Features Wizard | Server Selection, select a server from the server pool and click Next.
In the resulting Add Roles and Features Wizard | Server Roles, select Web Server (IIS).
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.
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)
In the resulting Add Roles and Features Wizard | Web Server Role (IIS), read the displayed information, and click Next.
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
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.
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 2022
Open Control Panel.
Locate and click on the ‘Programs and Features' link.
Once in the Programs and Features window, click on the 'Turn Windows Features on or off link.
In the resulting Server Manager window, click the Dashboard item (in the left pane), and click the Add roles and features link.
In the resulting Add Roles and Features Wizard | Before you Begin, click Next.
Select Role-based or feature-based installation in the Add Roles and Features Wizard | Installation Type, and click Next.
In the resulting Add Roles and Features Wizard | Server Selection, select a server from the server pool and click Next.
In the resulting Add Roles and Features Wizard | Server Roles, select Web Server (IIS).
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.
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)
In the resulting Add Roles and Features Wizard | Web Server Role (IIS), read the displayed information, and click Next.
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
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.
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.
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.
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.
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.
In the Actions pane (under Edit Site), click on Bindings.
In the resulting Site Bindings dialog, click the HTTP entry, and then click on Edit.
In the resulting Edit Site Bindings dialog, enter the desired value (such as 8080) for the Port, and click OK.
Close the Site Bindings dialog.
In the Actions pane of the Internet Information Services (IIS) Manager window (under Manage Web Site), click Stop, and 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 7 Firewall should help illustrate the general process.
Open the Windows 10 Control Panel, and click on the Windows Firewall link.
Click on the Advanced settings link (in the left column).
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.
Select the Port option on the Rule Type page of the resulting New Inbound Rule Wizard, and then click Next.
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.
On the Action page, click Next to accept the defaults.
On the Profile page, click Next to accept the defaults.
On the Name page, enter the required Name, optionally enter a Description, and click Finish.
This allows the Network Port used by the Default IIS Web Site through your Firewalls.