Installation

Installation of Inventory Pro involves setting up the SQL Server database, running the installation package for the Desktop application, and optionally enabling the Mobile application and REST API. The public documentation below focuses on the steps an administrator needs to complete safely without exposing internal deployment tooling.

:::tip[Quick Start]

1. Database — Restore the .bak via SSMS and map the application login.
2. Desktop — Update install.xml, run run.bat → Option 1.
3. Mobile (optional) — Run Mobile run.bat → Option 1.
4. Secure — Bind SSL certificate in IIS, log in, change the default admin password. :::

Prerequisites

Ensure you have local administrative rights on the application server and the required SQL Server credentials before beginning installation.

The installation package enables the required Windows and IIS features automatically and installs the supporting runtime components needed by Inventory Pro. No manual IIS configuration is required before running the installer.

Installation Overview

Database Setup

The database can be restored manually in SQL Server Management Studio or with guided assistance from CISS.

Manual Setup (SSMS)

1. Extract the backup

Extract the provided .bak file from the installation package.

2. Enable Mixed Mode Authentication

1. Open SQL Server Management Studio and connect to your instance.
2. Right-click the server name and choose Properties.
3. Open the Security page.
4. Select SQL Server and Windows Authentication mode.
5. Apply the change and restart the SQL Server service (this is always required for the change to take effect).

3. Create the application login

Run a script similar to the following in a new query window:

CREATE LOGIN [YourUserName]
WITH PASSWORD = N'YourSecurePassword',
DEFAULT_DATABASE = [master];

:::caution[Security] By default, SQL Server enforces password complexity and expiration policies for SQL logins. Keep these defaults enabled unless your environment has a specific service-account standard that requires otherwise. Where possible, prefer Windows Authentication over SQL authentication for stronger credential management. :::

4. Restore the database

1. Right-click Databases and choose Restore Database.
2. Select Device and browse to the extracted backup file.
3. Name the restored database according to the guidance in your CISS installation package.

5. Link the database user

After restore, map the orphaned database user to your new login:

USE [YourDatabaseName];
ALTER USER [YourUserName] WITH LOGIN = [YourUserName];

Note: The application login requires db_owner on the application database. Do not grant sysadmin or server-level permissions beyond what is needed for this single database.

Assisted or automated setup

Some installation packages include CISS-managed automation for SQL Server Express setup and validation. Those support tools are not published on the public website. If you need an automated installation workflow, contact CISS Support for the package appropriate to your environment.

Remote database server

If SQL Server runs on a separate server:

• Configure SQL Server to listen on a non-default port and disable the SQL Server Browser service. Using a non-standard port reduces exposure to automated scanning.
• Open only the chosen SQL port from the application server to the database server — do not allow broad inbound access.
• Verify connectivity with Test-NetConnection -ComputerName <sql-server> -Port <your-port> from the application server before running the installer.
• Record the chosen port in your installation notes; the installer will ask for it during database configuration.

Desktop Application

Installer configuration

Before running the installer, review the install.xml file in the installation package. Typical values include an installation root, the Desktop folder name, the primary site URL, HTTPS preference, authentication options, the SQL Server host, and the restored database name.

:::caution[Security] After a successful installation, secure or remove install.xml from the server. It contains the database server name and configuration details that should not remain in an accessible location on a production system. :::

Example structure:

<?xml version="1.0" encoding="utf-8"?>
<Configuration>
  <root>[InstallDrive]:\InventoryPro</root>
  <installFolder>Desktop</installFolder>
  <domainName>inventorypro.example.com</domainName>
  <siteName>Default Web Site</siteName>
  <requireSSL>true</requireSSL>
  <enableActiveDirectory>false</enableActiveDirectory>
  <enableEmail>false</enableEmail>
  <databaseServer>your-sql-server</databaseServer>
  <databaseName>your_inventorypro_database</databaseName>
</Configuration>

Run the installer

1. Extract the installation package.
2. Open the extracted folder and run run.bat.
3. Select the appropriate menu option.

:::caution[Backup Before Upgrading] Always take a full database backup before running an update (Option 2). Use SQL Server Management Studio or your scheduled backup process to create a .bak file you can restore if the upgrade encounters issues. :::

For a first-time deployment, run Option 1 and then review the validation results.

IIS Application Pool notes

The installer configures the required application pools automatically. If you need to reconfigure them manually:

Unattended installation

The installation package also supports unattended execution for staged deployments, but the automation entry points depend on the package provided for your environment. Use the guidance supplied with your installation package for unattended rollouts.

Dual instance support

To run two instances on the same server, create a second configuration file in the installation root with a different install folder, site name, and database target.

Installation validation

After installation, the validator checks the installation path, required registrations, application startup state, and general connectivity.

Mobile Application

The Mobile application is installed after the Desktop application and shares the same Inventory Pro site.

Install

1. Extract the Mobile installation package.
2. Run run.bat and select the install option.
3. Wait for setup to complete.

The installer places the Mobile application inside the Inventory Pro installation and configures the IIS application settings needed to run it.

Mobile configuration

Review the Mobile application’s configuration after installation and confirm:

• Database connectivity
• HTTPS enforcement
• Page sizing and scanner behavior
• Session and login rules required by your environment

The installer manages the connection string key automatically. Do not rename configuration keys manually after deployment.

REST API

The REST API is an optional component that enables programmatic access for third-party integrations, reporting tools, and automation scripts. It is deployed as a separate IIS application alongside the Desktop site.

The REST API is not included by default — contact CISS to enable it for your installation. For details on endpoints, authentication, and usage, see REST API Documentation.

Configuration

After installation, review the application configuration and confirm the items required for your environment:

• Database connection settings
• Primary site URL and HTTPS enforcement
• Authentication method
• Session and password policy
• Email delivery settings
• Export or document-processing folders

Upgrading? If your existing SQL connection settings still reference sqloledb or sqloledb.1, update them to msoledbsql during the upgrade review.

Post-Installation

SSL certificate setup

If your organization does not already manage certificates centrally, install a certificate for the site before enabling production access.

1. Configure DNS for the production hostname.
2. Install the certificate in IIS.
3. Add the HTTPS binding to the site.
4. Confirm that HTTPS is enforced in the application configuration.

Verify installation

After installation:

1. Open the Desktop site URL configured during installation.
2. Log in with the initial administrator credentials. On a fresh installation, these are set during the database provisioning step and supplied in your installation package documentation. If you restored from a CISS-provided backup, the default administrator account and temporary password are included in the package readme.
3. Change the administrator password immediately.
4. Review the core system settings before users begin transacting.

Note: The Database Setup, Desktop Application, and Configuration sections above are installation-time steps. The checklist below can be reviewed again later on a running system.

Initial configuration checklist

Additional configuration

Deployment

Desktop, Mobile, and Database deployment automation is handled through internal CISS operations tooling and is not published on the public website. If you need a deployment package for a sandbox, staging, or production environment, contact CISS Support.

Troubleshooting

Common issues

Connection errors or missing provider

• Confirm the SQL driver installation completed successfully.
• Verify the SQL Server is reachable from the application server.
• Review the configured connection settings.

Application registration issues

• Re-run the installer or validator.
• Confirm the required IIS settings are enabled.
• Review the validation output for any missing components.

Site will not start

• Check for hostname or binding conflicts in IIS.
• Confirm the chosen site URL resolves to the correct server.
• Review firewall and certificate configuration.

Document or export issues

• Restart IIS if a service restart is required.
• Confirm the configured export folder exists and is writable.
• Re-run validation if supporting components appear unavailable.

Session or login problems

• Review session timeout and lockout settings.
• Check IIS application pool idle timeout settings.
• Confirm cookies and HTTPS settings match your environment.

Mobile app connectivity problems

• Confirm the Mobile application was installed successfully.
• Review its connection settings.
• Verify that the certificate and IIS configuration cover the Mobile application path.

Validation

Use the installer’s built-in Validate option after installation or repair work. If validation still reports errors, contact CISS Support with the validation output and the installation log.

Log files

Support

For installation assistance, contact CISS with:

• The installation log
• Screenshots of any error messages
• Server OS version and SQL Server version
• Validation output when available

:::tip[Related] Learn about deployment options and security: System Architecture | Pricing & Editions :::