6.1 How to set up OCS properly

To set up OCS properly

the importance of the TAG
managing duplicates

Deployment of agents OCS

It is necessary to plan your deployment of the OCS agents well. With this in mind, you should take into account the following data:

type of platforms (Windows, Linux, Unix, Mac OS X, etc)
the method of deployment (automatic for the workstations, manual on the servers)
the presence of a Windows domain controller with Active Directory
the number of TAGs which will be used

On Unix and Linux there is no automated procedure for deployment of the agent. However, it is possible to use the packages provided by the distributions (if available, for example for Fedora/Redhat/CentOS.)

On Windows it is possible to use an automated deployment scenario to install the agent. Indeed, the OCS project provides an executable named OcsLogon.exe which offers the following functionality:

checks for the installation of the agent
installation and initialization of the agent
update of the agent

Connection OCS/GLPI

GLPI is interfaces natively with OCS Inventory in order to recover its automatic inventory. GLPI can:

incorporate the data of several OCS servers
to go up the material data
to go up the software (with or without OCS dictionary)
reassemble the registry keys of Windows machines

GLPI cannot:

modify the configuration of OCS
update the OCS dictionary
control the deployment of OCS applications

OCS Inventory NG and GLPI are in place, what next?

Now that your system is in place, you can look at:

plugins
how to manage the complete life cycle of a machine