Installing the Columbus Inventory Scanner on Mac OS
You will need to customise the ColumbusInventoryScanner.tar file before continuing to ensure that the parameters are set for you environment.
If you are deploying to the same configuration to multiple devices it may be beneficial to customize the ColumbusInventoryScanner.tar file beforehand. A guide on how to build a custom *.tar file can be found here.
The prepared *.tar file will have the following folder structure:
Ensure that the following two files have been checked and modified to correspond with your environment:
Cis.prv – This is the hash file used by the scanner agent to talk back to the server, details on how to exchange this file can be found in this KB
ColumbusInventoryScanner.cfg – This is configuration file used to modify settings for the scanner agent, details on how to modify this can be found in this KB
To install the scanner agent onto the Mac please follow these steps.
Deploy the ColumbusInventoryScanner.tar and the setup.sh file to the /OPT/CIS/ directory on the Apple Mac
Run the included setup.sh script as SUDO using the following command:
sudo sh setup.sh –headless
In this instance the “--headless” switch prevents local user confirmation to allow for remote deployment, further details on additional available switches can be found in the Setup.sh script and are detailed in this article.
Once the setup.sh script has been run the Columbus Inventory Scanner will perform an initial scan using the settings in the config file. During this scan additional files will be downloaded from the Spider Data Collector server.
The output results of the last scan can be found in the ‘Output’ folder and the scanner agent will create a *.tar file once completed and will upload this to the Spider Data Collector.
A log file is created during execution, the ColumbusInventoryScanner.log file is stored in the ‘log’ folder.
Temp files are deleted after each scan, further information will be appended to the log file accordingly.
The Columbus Inventory Scanner will then run automatically on the Apple Mac according to the schedule in the configuration file.
Apr 19, 202305:37 AM - edited Apr 28, 202308:05 AM