The OC Scanner can be deployed in four different ways:
- Agentless Multiple Scanners
- Agentless Single Scanner
- Agent-Based Scanners
- Hybrid
Further information can be found in the Onboarding section under Deployment Approaches.
The deployment of OC Scanner is straightforward. You will need to put the following two files in any subfolder of your choice on the server you want to deploy OC Scanner. By convention, we recommend creating a subfolder C:\oc_scanner and place the following two files in there:
- InventoryScan.exe file (the OC Scanner application)
- Related scan file
Based on the deployment approach you chose for OC Scanner, the related scan file can be different. Here a quick overview:
Agent-based scanner
By convention for agent-based scans, you deploy together with OC Scanner the related agent.cfg scan file.
Agentless single scanner
For the agentless single scanner approach, you simply deploy the created scan file with the OC Scanner.
Agentless multiple scanners
The agentless multiple scanners approach is the most used deployment type by customers. There are some restrictions in naming the scan file and some rules to follow. In the agentless multiple scanner approach, the OC Scanner needs a connection towards the OC Configurator API server to get its original scan file.
The original scan file needs to be named by the FQDN name of the server, where OC Scanner is deployed. When you deploy OC Scanner, you don’t copy the original scan file with it. You are copying a “proxy” scan file called “remote.cfg”, which is taking care to pick up from the central OC Configurator API server the correct original scan file of OC Scanner. For further information about the configuration part, please click here.