In this chapter, we got into the nuts and bolts of package deployment and remote command execution functionalities of the OCS Inventory NG suite. It's a client-server (agent) model and remote execution is possible via those agents running on every inventoried client computer.
Over the course of this chapter, we learned how to create a package, the kind of steps we need to go through in order to build one. Once a package is done, it needs to be activated. To add a layer of security, the OCS-NG deployment mechanism is secured with HTTP over SSL. The metadata info XML file is retrieved via HTTPS protocol.
While a package is activated, it does not mean it has been deployed yet. As such, we learned how to select the target computers on which an already activated package will be deployed. This technique is called affecting the package on hosts.
Finally, we learned how to generate SSL certificates and get them either signed or self-sign them ourselves. We pondered on a few solutions to get...