•If the Web Server Role is enabled on the host machine, remove the Role before installation. Instructions on how to configure this setting can be found in the Hanwell EMS Installation Manual, Doc. No. IM5995.

When installing the A version, the install disk needs to install to the C:\ drive.

The Customer should provide a backup System, with Microsoft SQL integration, appropriate to their data protection requirements.

•Ellab strongly recommends the use of an appropriately rated Uninterruptable Power Supply (UPS), with automatic shutdown technology.

Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022

•Server Edition must be Standard or above1.

•Server Core Mode is not supported.

1 Windows Server Essentials editions can be configured to run W900A or W906A; however, Ellab recommends against this and will only provide support by arrangement prior to installation at additional cost.

Table 1

Processor		2.5GHz or faster minimum cores 2+
RAM		8GB
Hard Disk Drive:	Physical Machine	250GB (SSD Recommended)
	Virtual Machine	80GB minimum 250GB recommended
Network		1GB Ethernet Network Port

Note:

EMS W900A or W906A must NOT be installed on a Domain Controller. SQL Server Security Restrictions mean that the installation will usually fail.

Windows 10 or 11 Pro or Enterprise

Note:

EMS will not run-on Windows 10 or 11 Home or Mobile due to the lack of Network access rights and components.

Table 2

Processor	2.5GHz or faster minimum cores 2+
Ram	8GB
Hard-drive	250GB
Network	1GB Ethernet Network Port

.Net Pre-requisites

EMS install requires both .Net 3.5.1 and .Net 4.5 frameworks.

The installer includes bootstrappers for the .Net 3.5 4.5 Frameworks which will install automatically throughout the install process.

However, on machines running Windows Server operating systems, the customer must enable .Net 3.5.1 manually on the Server prior to EMS installation.

See Hanwell EMS Installation Manual, Doc. No. IM5995 for information on checking and enabling .Net 3.5.1 on server-based Systems.

Browser Compatibility

The EMS System is scalable, browser based, with an SQL database, and used through a browser.

The Host machine and Client machines MUST have one of the browsers below installed:

•Internet Explorer 10 or 11.

•Microsoft Edge (Windows 10). Version 42 or later.

•Google Chrome Version 72 or later.

•Mozilla Firefox Version 65 or later.

Note:

Other browsers generally work with EMS but are not guaranteed to be fully compatible; earlier versions of Internet Explorer do not support all EMS features.

Server/Computer Details

The following needs to be in place and checked by your IT department:

•Server/Computer where W900A or W906A is to be installed IS NOT a Domain Controller.

•Server/Computer IS NOT hosting a Web Server such as IIS or Apache1.

•Server IS NOT hosting a Database Server, other than Microsoft SQL2.

•If hosting a Microsoft SQL Database Server, the version of Microsoft SQL is 2014 or later.EMS ONLY supports versions of Microsoft SQL from 2014 onwards. If using EMS MobileApp, Microsoft SQL 2014 onwards.

•Server is up to date with latest Windows updates.

•If antivirus software is installed on the server/computer this may need to be disabled duringinstallation.

1 Ellab DOES NOT support EMS use in a mixed Webserver Environment and EMS should not be installed in such an environment.

2 Ellab Recommends against running EMS in a mixed Database Server environment.

Existing Microsoft SQL Instances

•If the target server does NOT have an existing Microsoft SQL Server instance and you do not wish to use/have an appropriate Microsoft SQL Server available on the LAN, you will require either EMS W900A / W906A and can move onto Section 5.

•If there is an existing Microsoft SQL Server, on the target server or LAN, that you wish touse for EMS, you will require either EMS W900B / W906B.

In any case, DO NOT attempt to install EMS W900A / W906A on a machine with an existing Microsoft SQL Server instance, unless the SQL was installed as part of a previous W900A / W906A installation; SQL Express will be installed during W900A / W906A installation, DO NOT install SQL prior to installation.

Our Installation Team will ensure that you have the correct version.

EMS W900B / W906B

If ordering EMS W900B / W906B, your IT will have to provide our installation team with the following information:

•SQL Server Name.

•Instance Name or Port Number, if used.

•SQL Version.

Note:

EMS and the EMS Mobile App ONLY support versions of Microsoft SQL from 2014 onwards.

Existing Microsoft SQL Server Requirements

•The installing User’s Windows login must have a System Admin role on the SQL Instance.

•It is helpful if the SQL Server Browser Service is running during EMS install and EMSConfig Utility operation.

•SQL Server Management Studio (SSMS) must be installed.

User Credentials

If EMS W900B / W906B is to operate a Microsoft SQL Server running on a separate machine, then EMS will require Windows domain login credentials to operate.

The Login used for EMS MUST have password set to Never Expire, otherwise, the Service Account that serves the data from the Application Server to the Database will stop working when the Password expires.

This login MUST not be the login used to install EMS; using the same login causes database creation to fail (and would in any case result in a worse security situation post install, as the EMS Services would be left running as Administrator on the local System and as an SQL Administrator on the SQL Server).

Customers should not add this EMS System login to their SQL Server. The login will be added automatically during EMS installation (allowing the installation to add the EMS Service logins to the SQL Server gives the best security situation, because the Service login will only be granted access to the databases created for EMS, with the minimum roles required to operate the System).

Ellab recommends that customers create a Network User login specifically for the EMS System.

TCP/IP Ports and Addresses

•If the Customer wishes to connect to remote SR2, CR3 or CR2 USB units where no intranetis in place, then the Customer must ensure that all Firewalls are configured to allow connections between the remote networks over the requisite TCP/IP Ports. See Table 3 below.

•There are no IANA registered Port Numbers for EMS; instead, it uses unassigned PortNumbers.

See: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml (As of 4/10/201).

•If a conflict arises on the host machine, EMS TCP/IP Ports can be configured duringinstallation.

For the majority of Systems, the Default Ports will suffice.

•Where Port Numbers need to be changed, care should be taken to avoid well known andassigned Port Numbers; consult the IANA website and do not use Port Numbers below1024.

If Port Numbers are altered, make a note of any changes and then modify the matchingservice data during database configuration.

Where Hardware Services are installed on distributed machines, Port Numbers can beshared amongst the distributed machines.

•The EMS IP Address / Hostname and Port Number can be set during installation of theHardware Services.

This must match the address of the EMS Server and the Data Service Port No. set for theHardware Services during initial System Configuration.

•The Hardware Service Command Listening Ports will be automatically updated by the DataService when each Hardware Service initially makes contact; therefore, these can bealtered without manually updating the database.

•The Debug Ports are solely used by the Service Debug Viewer for Ellab maintenancepurposes; therefore, again, these can be altered without modifying the database.

Debug Port Numbers are altered by editing the Hardware Services setup.xml file, found inthe service’s Common Application Data Folder.

Table 3

Service	Data	Protocol	Incoming or Outgoing	Debug
EMSSR2Service	10992	TCP (Out)	Out	11002
EMSDataService	10991 (DB set) (DB set)	n/a	n/a	11004
EMS WCF Connection	8083	n/a	n/a	n/a
EMSArchiveService	8082	n/a	n/a	11010
iSense/CR3 GPRS (CR2 GPRS) – Hanwell Remote Data Service	8081	TCP (Out)	Out	n/a
W900A/B Installation – Remote Management Tool (SQL Connection)	80 (HTTP) 443 (HTTPS)	TCP (In)	In	n/a
SQL Service SQL Browser Service	1433 1434	TCP (In) UDP (In)	In	n/a
ARB Module, SMS Module, IceSpy Bases	10997	TCP (In)	In	n/a

Notes:

•If one of the Ports included above is unavailable, please provide an alternative in the Alternate column.

•For Firewall rules purposes, the SQL Ports require TCP and UDP, all other Ports are TCP.

•See EMS Install Manual for full details when installing EMS.

•The Customer MUST enable inbound connections for the above Ports on any server firewall prior to installation. If using iSense orCR3 GSM (CR2GPRS), the Customer MUST also enable outbound connections on Port 8081 on server and corporate firewall(s)prior to installation.

•EMS WCF and Debug Connections are local to the EMS Server.

Potential Installation Issues

•Some antivirus programs may detect a false positive on the EMS Installer.

➢If this happens, you should disable your antivirus program during the installation process.

•If installation of the EMS Server Components is interrupted or fails for any reason, you should perform a complete removal of the EMS Server Components, before attempting a re-installation.

➢Follow the procedure described in EMS Server Removal to completely remove any existing EMS Server Components.

•The existing Microsoft SQL Server must be a version from 2012 onwards.