Installing the Software

All components of the OctoSAM Software come as a .zip archive that you can extract to a location on the filesystem. Recommended and pre-configured filesystem location for the Server components is D:\OctoSAM\Server

Installation for production environments is supported on Windows domain member servers only. The software can be installed on Windows 10 or Windows 11 (64bit only) for testing and development. Installation on Windows domain controllers is not supported.

The OctoSAM Windows GUI can also be installed via the OctoSAM.msi file for compatibility with earlier versions, especially if you have distributed the GUI to client machines.

Prerequisites

Microsoft .NET

See release notes for information about required .NET runtime versions.

Service Accounts

The OctoSAM Inventory Windows services require a Windows service account with the following privileges:

Read/Write access to parts of the file system that you configure for log files and .scan file processing
At least Read/Write and Bulk Import access rights to the central OctoSAM Inventory database
Read access to Active Directory for user and computer objects (Offline import of Active Directory Information is also supported).

CPU and Memory Resources

As a rule of thumb, you can use the Microsoft recommended hardware specifications for Windows 2016 Server and SQL Server 2016 and add:

32 GB RAM + additional 8 GB of RAM to SQL Server for each 10,000 computers

2 vCPU / cores or better to SQL Server for each 10,000 computers

8 GB of RAM for the import service (regardless of the size of the database)

2 vCPU / cores for the import service

Tip

Plan for additional resources if you want to run the OctoSAM GUI (at least 8 GB RAM and 1 vCPU per concurrent user) on the same machine.

Plan for additional resources if you want to run ad-hoc query tools or the Microsoft SQL Management Studio on the same machine.

Disc Space

Disc Performance: We recommend high-performance storage subsystems such as solid state disk arrays. Disc performance is usually the limiting factor that defines overall throughput of the OctoSAM applications.
Database: We recommend 30 GB per 1000 machines depending on configured retention times for history data. Make sure your transaction log settings are big enough for the high transaction volume that is to be expected from inventory scan import.
Log Files: All OctoSAM Inventory server components write log files through the (Serilog)[https://serilog.net/] logging framework. Designate a directory on a local file system for logging.; Log file disc space requirements depend on the configured log levels, we recommend to reserve at least 50 GB for log data.; Detailed configuration of the serilog framework is not part of this documentation.

Tip

Make sure that all service accounts have write permission to the configured log directory.

Scan File Archive: It’s highly recommended to archive the collected scan files after import. Required disc space for scan file archiving is approx. 100 KB per scan.; 1000 Machines with on average 1 scan per day result in 100 MB per day, 30 GB per year. The Import Service automatically archives processed scan files into a directory hierarchy.

Tip

Make sure that the import service account has write write permission to the configured archive directories.

Scanner, Scan File Collection, Central Scanner Configuration Files: Disc space for these operations is best placed on a highly available storage cluster system. The scanner is usually started by group policy settings or a login script, so the executable and its configuration file should be always available.