Requirements and Compatibility

Signature System Requirements

To find a complete list of system requirements across all the Signature modules, refer to System Requirements.

Signature Version Compatibility

• Signature 18.03b05 or higher
• Signature 2018 R3
• Signature 2016 R3 SP2
• MobileTech 8.5.57 or higher for XOi Deep Linking
• Building Optimization Broker 1.3 or higher
• Signature Agent 2.4.39 or higher
• Map2BOB 1.1.16 or higher

Device Compatibility

Schedule is not designed to perform on smaller form-factors, like a tablet computer or smartphone.

Incompatibility

WebDav is an optional IIS Feature that is not currently compatible with the Schedule services. 

It is our recommendation not to install WebDav as one of the features installed on IIS as a prerequisite feature for Schedule.  It is an optional feature and not needed for Schedule and could potentially cause problems.

If WebDav is a needed feature for other IIS websites installed (other than WennSoft software), we recommend that WebDav is removed from the Handler Mappings and Modules features for the particular IIS Site that Schedule is installed on.

1. Open the Internet Information Services (IIS) Manager.
2. Navigate the Default Web Site.
3. Double-click to open Handler Mappings.
4. Right-click WebDav and select Remove.
5. Select Default Web Site.
6. Double-click to open Modules.
7. Right-click WebDav and select Remove. 
8. Perform IISRESET from elevated CMD prompt.

Install the .NET Core 3.1 Windows Server Hosting bundle

1. Install the .NET Core Windows Server Hosting bundle on the hosting system. The bundle installs the .NET Core Runtime, .NET Core Library, and the ASP.NET Core Module. The module creates the reverse proxy between IIS and the Kestrel server. If the system doesn't have an Internet connection, obtain and install the Microsoft Visual C++ 2015 Redistributable before installing the .NET Core Windows Server Hosting bundle. Important! If the hosting bundle is installed before IIS, the bundle installation must be repaired. Run the hosting bundle installer again after installing IIS.
2. Restart the system or execute net stop was /y followed by net start w3svc from a command prompt. Restarting IIS picks up a change to the system PATH made by the installer.

Obtain a Mapping API Key

If you will be using the Mapping feature, you will also need to obtain a Google or Bing Mapping API key:

• Google Maps: https://cloud.google.com/maps-platform/pricing/ You will need the Maps JavaScript API (Maps > Dynamic Maps), Directions API (Routes > Directions), and Geocoding (Places tab). Geocoding is required for setting coordinates.
• Bing Maps: https://www.microsoft.com/en-us/maps/licensing/options