../thumbnail_Inspect%20Word%20Transparent.png

Inspect System Installation

 

 

 

1st October 2026


1. Introduction

This document outlines the technical requirements and configuration steps required to prepare your environment for the installation of Inspect.


It covers the setup of user access, shared folders, SQL Server databases and permissions, property and owner data, map data, and network configuration. Completing these requirements before installation will help ensure that the Inspect Test and Production environments can be configured and deployed smoothly.


Where example names, domains, folders, database names, or port numbers are provided, these can be adjusted to suit your organisation's existing IT standards.

If you have any questions about these requirements or require assistance with any of the configuration steps, please contact us and we will be happy to assist.

2. Active Directory Group

Please create an Active Directory (AD) group for Inspect users and assign all required users to this group.

For example:

  • client_domain\InspectGroup
  • This group will be used to manage access to the Inspect folders, database, and Inspect Service.

3. Inspect Desktop Folders

Please create separate folders for the Test and Production environments.

For example:

  • Test: Inspect_Test

  • Production: Inspect_Prod

Each environment should contain the following subfolders:

InstallationFiles

  • Used to store the Inspect Desktop installation files.

  • The Inspect AD group requires Read permission.

Data 

  • Used to store Inspect data files.

  • The Inspect AD group requires Read/Write permission.

Example folder structure:

  • Inspect_Test\InstallationFiles — Read permission

  • Inspect_Test\Data — Read/Write permission

  • Inspect_Prod\InstallationFiles — Read permission

  • Inspect_Prod\Data — Read/Write permission

4. Inspect Databases

Please create separate databases for the Test and Production environments.

For example:

  • Test: InspectTest

  • Production: InspectProd

The Inspect AD group requires Read/Write access to both databases.

At least one Inspect user should also have database owner (db_owner) permissions. This user will be responsible for running database migrations when required.

A database migration is automatically performed when Inspect Desktop is launched for the first time after a new version is installed. Therefore, after new installation files are deployed, a user with the required database permissions should launch Inspect Desktop first.

5. SQL Server Permissions

Inspect database users must also be granted permission to view the SQL Server state, as this is required by the Inspect licensing mechanism.

Example:

GRANT VIEW SERVER STATE TO 'client_domain\InspectGroup'
6. Property and Owner Data

Property and owner data will need to be exported from your property management system.

Please export the data in the format described in the attached Inspect CSV Import Specifications document. Please use the version attached to this email, as it contains a recent update.

Once the data has been exported from Synergy, please send it through to us and we will review it before importing it into Inspect.

7. Map Data

Inspect requires map data including:

  • Property cadastre data in Shapefile format

  • Satellite/aerial imagery in ECW format

The required map data can be obtained from Landgate.

We will provide additional instructions on how to convert the ECW imagery into MBTiles format for use with Inspect.

8. Inspect Service Port Configuration

Inspect Desktop runs a local Inspect Service on each machine where the application is installed.

A Windows administrator will need to reserve the required HTTP URL so that the service can be started by non-administrator users.

Example command:

netsh http add urlacl url=http://+:80/ user=client_domain\InspectGroup 
Supported port numbers are:
  • 80 — default

  • 591

  • 8008

  • 8080

By default, Inspect uses TCP port 80.

The system administrator will also need to configure Windows Firewall on each machine where Inspect Desktop is installed. This can be done by either:

Adding an inbound TCP firewall rule for the selected Inspect port; or

Allowing the Inspect Desktop application through Windows Firewall.