We recommend installing the server components in a folder structure under a base folder named
The installation media contains a script
create_folder_structure.ps1 under Support/Install/Scripts that creates the recommended folder structure and network share.
For a fresh install, extract the installation archive to a temporary folder, adjust and execute the
By convention, copy the installation archive to the Install/Delivery folder in the newly created folder structure. This helps to find the installation archive if you
later require additional artifacts.
The Server folder contains the Server software. If updating an existing installation, make sure all services and other applications are stopped. Extract the installation archive and replace the Server folder in the OctoSAM base directory with the one from the installation archive.
It's recommended that you rename the existing Server folder to Server_OLD or similar. Do not just copy a new Server Folder over the existing one as this may lead to leftover files. Leftover files from earlier installations may impact the functionality and/or stability of the OctoSAM Server software.
The Server folder and its subfolders also may contain configuration files. These files should only be altered if advised by Octosoft. A viable scenario to alter such files might be to enable additional diagnostics. If you modify files within the Server structure you have to manually re-apply the changes after each software update (if required).
The easiest way to collect your scan files is to configure the scanner in such a way that the scan files are all written to a central share. For simple installations, define a hidden share called OctoSAM$ on your storage system. Place the following folders in that share:
- (read-only for all users except OctoSAM administrators) to hold octoscan2.exe and its configuration file.
- (read/write for all users) to accept scan files from all users/computers in the network.
create_folder_structure.ps1 creates the OctoSAM$ share with simple default configuration..
The Import Service reads only complete files from configured import folders. When copying files to the central share, you therefore don't have to apply any fancy copy and rename strategy.
We recommend to place the Bin folder with the Octoscan2 executable and the Data folder on the same network share. That way, the Group Policy Engine on the client takes care of potential network startup timing issues.
OctoSAM Inventory uses standard .net 5.0 configuration appsettings.json files for all server components and the GUI.
All server components can be configured through a single appsettings.json file located in a configurable folder that
is referenced via the
create_folder_structure.ps1 configures the environment variable
The installation media provides documented template configuration files in the Directory
within the Server folder.