Use ocspackager

Содержание:

Manual

Prerequisite

Using OCS Inventory Packager is the fastest way to deploy and setup the OCS Inventory NG Agent
on stand alone or domain integrated computers. It is based on the NSIS script and RemCom tools.
It generates a file called ocspackage.exe based on your parameters, which allows a one click and/or
a silent user install.

In this document a number of assumptions are made:

We assume that you know the domain or local administrative account of your computers.
You should also know how to generate or obtain a certificate file.
You are familiar with common Windows administrative tasks.

Usage

Download the Packager and the latest Windows agent from our website.

Prepare your certificate (needed for software remote deployment).

Launch OcsPackager.exe and accept the License agreement.

The following window will appear:

“Files and Options” group box:

On the Exe File line, select your freshly downloaded OcsAgentSetup.exe program.
This entry is required !
On the Certificate file line, select your cacert.pem file.
The other files line allows additional files to be specified which will be copied to your install folder.
On line you should enter all the needed options for the Ocs Agent setup
program (e.g. /server=http://my_server/ocsinventory:8181 /S). Do not forget to specify the
/S option for a silent installation.
The Label line will create a label file containing your user prompt. The first time
OcsInventory.exe starts, a popup using this prompt will be shown. The user entered value is called the TAG.

“Install will run under account” group box:

On User line, enter the local admin account or a domain administrative account. On Active Directory
domains, use “@” to separate the user from the domain name (e.g. administrator@my.domain.com).
On a NT4 domain use the “domain\user” syntax.
Be careful when entering the password. It will not be validated at this point !

You should have something like this:

Click the button.

Select the destination folder and Click .

At this point windows will briefly appear to generate ocspackage.exe.

You can now test ocspackage.exe by launching it under a normal user account
(no administrative privileges).

A brief Ocs Inventory popup may show indicating the ocspackage.exe has been created.
A log file named ocspackage.log is created at install time.

Using static groups

Static groups of computers corresponds to the result of a various criteria search. For example,
if you make a various criteria search which search all computers having Firefox, then all the
computers that meet these criteria at this moment can be added to a static group. The content
of a static group won’t change until you manually add/remove computers to this group, even using
another various criteria search.

Create a static group

To create a static group of computers, you have to make a various criteria search first.
Click on «Search with various criteria», select your parameters, and click on «Search» button.
In the result table, check the computers you want to add to the static group (you can click on
«the page» to select all the computers). Click on Groups at the bottom of the result table and select if you want to add what you selected (checkboxes) or for the request itself.

Now add informations in several fields:

Name : enter the name of the group here
Description: add a description of the group here (optional)

Now, you can view your new static group, as described before, by clicking «Groups» and «Static groups» tab.

Installation

Installing a plugin on your server(s) occurs in 3 steps:

Installation of the extension package on the Administration server’s filesystem;
Activation of the extension via the Administration console;
Installation of the extension for the Communication server.

Once the plugin is installed on your server(s) you still have to deploy an agent-part on all your agents.

Plugin installation on filesystem

First download the extension here:

Github : https://github.com/PluginsOCSInventory-NG

Plugin site : https://plugins.ocsinventory-ng.org/

Then, place the downloaded zip file in the folder of your Administration server and unzip it.

You may delete the zip file after it is unzipped.

Plugin activation

Log into your Administration console and go to the «Extensions» tab.

Select the plugin and click on «Install».

Logout and login for finish the web installation.

You can now proceed with the installation on your Communication server.

Scripted communication server installation

To install your plugin on the Communication server, the may be used.

On your Administration server, go to the
folder, and execute the script with sudo:

Enter the path to your Administration server’s folder:

Don’t forget the last slash

After, the script will present you all the plugins that can be installed.
Select the number of the plugin that you want to install:

Now there are two specific cases:

OCS Comuunication server is on the same server.
OCS Communication server is on an other server.

In the case where your Communication server is on an another server, you need to enter
the server’s informations:

In both case, you will have to enter the path of your Communication server’s configuration directory:

The script will copy all the needed files into your Communication server’s configuration directory.

Server installation without script

To install plugins without the script, log into your Communication server and go to the configuration
directory (By default «/etc/ocsinventory-server/»).

There, create a new directory into «perl/Apache/Ocsinventory/Plugins/» with the name of the plugin :

Next, place the Map.pm file inside.

Finally, place the plugin’s configuration file into the «plugins/» folder.

Plugin deployment

Now that your Administration and Communication servers support your plugin, you need to deploy the agent part on you clients.

The plugin’s agent part is usualy located in the subfolder of your plugin’s zip file.

So, find this folder back and create a zip file containing all the files in this folder.

Then, create a deployment package with the action as explained in
Deploying packages or executing commands on client hosts

Specify as the path where the files need to be copied on the agents.

Configuration of Agent

By clicking on configuration standard button of Android (different depending on the device),
4 menus are available:

Configuration : Access to agent configuration
About : About OCS Inventory NG agent installed
Import configuration : Import a configuration file if present in directory ocs
Export configuration : Export the configuration to backup or using on others devices

General Configuration of agent

TAG : Cathegory TAG in OCS
DEBUG : possible to generate a trace file in the ocslog.txt agent directory
AUTOMATIC : define if agent works as a service or a standalone application
DEPENDING ON NETWORK STATUS : Define using mobile internet connection or Wifi
INVENTORY FREQUENCY : define frequency between 2 inventories (in hours)
WAKE FREQUENCY : define time between 2 verifications of time since last inventory
CACHE : possible to recordd inventory cache on device
CACHE LIFETIME : define cache timelife (in minutes)
SYSTEM SOFTWARE : Exclude or include software like clock
USERAGENT COMPATIBILITY : Active this option for old OCS Inventory Server under 2.X
HIDE NOTIFICATION : Show off or on the notification from OCS android agent

Configuration concerning server

SERVER URL : define URL address of OCS Inventory NG server(By default:
).

`Note: If your OCS Inventory NG server listens on an other port than classic port, you have to define it in serveur URL.
Example :
SSL CONTROL : possible to active and desactive SSL control.
BASIC AUTHENTIFICATION : define if server needs authentification. If yes, you have to define
Login and Password.
HTTP PROXY : define if agent use a proxy. If yes, you have to define Address and
port of proxy server.

Introduction

Open Computer and Software Inventory NG Packager is an application designed to prepare automated
single “Click” end-user installation packages for windows. It also allows use an alternative user
account to perform any kind of scripted task. This Packager is based on the NSIS script and RemCom
utilities open source projects.

OCS Inventory NG Packager is GPL software.

i.e. free to use & copy (see http://www.opensource.org).

OCS Inventory is also Open Source! This means that if you want to modify the sources you can! However,
if you want to change the source code and distribute the changed software, you must provide the source
to your updates as well, as required by the GPL license terms.

Система OCS Inventory NG

Решение OCS Inventory NG (OCSNG, Open Computers and Software Inventory New Generation, ocsinventory-ng.org) позволяет произвести инвентаризацию комплектующих и программного обеспечения, установленных на компьютерах в локальной сети, и отслеживать их изменения, периодически получая данные о конфигурации систем. Еще одной полезной функцией является возможность удаленной установки программ и выполнения команд. Для сбора информации на клиентские компьютеры устанавливается программа-агент.
Агент доступен практически для всех версий Windows от 95 до 2k8R2, Linux, Mac OS X, *BSD, Solaris, IBM AIX и HP-UX. Все собранные данные агенты отправляют на сервер управления (management server) в виде XML-потока, сжатого при помощи библиотеки Zlib. Для передачи используется стандартный протокол HTTP/HTTPS, поэтому проблем с firewall’ом обычно не возникает. При помощи агентов реализована функция «IP discovery», которая помогает находить все сетевые и периферийные устройства, работающие в локалке, в том числе те, на которые нельзя установить агента (свитчи, принтеры, web-камеры и т.д.) Агенты сканируют сеть в поисках подобных устройств и отправляют сведения о них на сервер для анализа.

Версия для Windows написана на C++, *nix вариант — на Perl и С.

Серверная часть OCSNG включает в себя четыре компонента, которые необязательно должны быть установлены на одном сервере. Это СУБД (MySQL) для сбора данных, а также вебсервер, который может играть одну из трех ролей:

Служба связи — обеспечивает связь по протоколу HTTP между сервером базы данных и программами-агентами (Apache 1.3.X/2.X с интегрированным Perl, в Debian/Ubuntu пакет libapache-dbi-perl);
Служба развертывания — хранение установочных файлов программ-агентов (любой веб-сервер с поддержкой SSL);
Консоль управления — просмотр собранных данных в браузере (веб-сервер с поддержкой PHP с ZIP и GD).

Серверная часть OCSNG может быть установлена на компьютер, работающий под управлением Win2k/XP/2k3, Linux, *BSD, Solaris, IBM AIX и MacOS X.

Установка плагинов

Ссылки на скачивание лучше брать с GitHub, так как на официальном сайте встречаются старые версии. Устанавливать будем на примере Office Pack. Этот плагин позволяет получать ключи от Microsoft Office.

Для установки нам понадобится положить скачанный плагин в . Приступим.

Далее в веб-интерфейсе нашего сервера открываем Plugins —> Plugins Manager, выбираем скачанный плагин и жмем Install. После успешной установки рестартуем демон Apache.

Осталось скачать плагин на компьютере с установленным агентом и распаковать файлик (он лежит в ) в .

В трее ищем наш агент, нажимаем правой кнопкой мыши и выбираем Run OCS Inventory NG Agent now.

Проверяем результат!

Viewing groups

To views the groups you created, click on the menu Inventory toolbar and then groups.

You can see three tabs:

Dynamic Groups tab : to view the list of dynamic groups
Static Groups tab : to view the list of static groups
Server Groups tab : to view the list of redistribution server groups

When you click on a group name, you go to the group page. In the top,
you can see various informations about the group:

Group name
Creation date
Query (the SQL query corresponding to the various criteria search parameters for dynamics groups)
Description

You can edit the description and the group name by clicking on update.

If you click on «All computers (cached)», you can see all the computers members of the group.

Manually installing OCS Inventory NG Agent for Windows.

Run “OCS-NG-Windows-Agent-Setup.exe” on client computer..

..and click “Next” button

Validate license agreement by clicking “I agree” button.

Select the installation type you want:

Network inventory: Computer can reach OCS Inventory NG Server through the network, and so,
Agent will be launched using either a Windows Service, or a Logon/GPO script.
Local inventory: Computer is not connected to a network, or will never be able to reach
OCS Inventory NG Server. You can generate an inventory of this computer and save to file to be imported
later on server (see chapter Generating inventory of a non network connected Windows computer below).

Fill in OCS Inventory NG Communication server URL, like

. You can also specify https if your server is SSL enabled to secure communication.
If you’ve protected your Communication Server access with credentials, you must specify credentials
agent will use to authenticate (these credentials will be encrypted to be stored into configuration file).
If you’re aware of server certificate validation when using HTTPS protocol, either for sending inventory
or deploying package, you can disable it. However, this is a security flaw! We do not recommend disabling
certificate validation because Agent does not authenticate server. With certificate validation enabled,
you must specify path to Certificate Authority root certificate (default uses
«%ProgramData%\OCS Inventory NG\Agent\cacert.pem»). Then click “Next” button.

If needed, select proxy type to use to connect to Communication Server, proxy address and port, and
proxy credentials if required (these credentials will be encrypted to be stored into configuration file).
Agent support HTTP, SOCKS 4 and SOCKS 5 proxies.

By default, OCS Inventory Agent write only few information in log files. You may increase
this enabling “Verbose log”. You may also disable TAG question, or specify the TAG value. Last,
indicate which level of system integration you need:

Do not register service using LocalSystem account (i.e, use standalone agent, which must be launched manually or using login script).
Do not configure OCS Inventory NG Systray Applet to start automatically when user log in. This applet allows user to manually run agent, or to display inventory information. Disabling this option does not create shortcut link in «All users» startup menu.
Launch inventory just at the end of setup.

Choose destination folder, “C:\Program Files\OCS Inventory Agent” by default
(“C:\Program Files (x86)\OCS Inventory Agent” under Windows 64 bits), and click “Install” button.

Click “Finish” button to close OCS inventory NG Agent Setup.

This is the interactive installation setup. However, this process requires that you launch it under
all your computers. Hopefully, this installation can be scripted.

OCS Inventory NG Agent for Windows Setup command line options

Service Agent setup «OCS-NG-Windows-Agent-Setup.exe» may be called with some command line parameters:

/S to run the installer in silent mode, no interaction with user
/NOSPLASH disable splash screen when installer starts
/NO_SERVICE to not register OCS Inventory NG Agent into Windows Service Manager. Agent can only be launched manually or through a script/GPO.
/NO_SYSTRAY to not create a shortcut into «All Users» startup folder to start systray applet when user log in.
/NOW to launch inventory just after setup
/NOSOFTWARE to ignore software installed
/D to install ocsinventory agent in an another directory (default %PROGRAMFILES%\ocs inventory agent)
/UPGRADE to deploy new agent through OCS deployment feature. Because you upgrade agent using agent itself to run the upgrade, it is needed to notify the installer (which terminates agent’s processes) to specify the result in order to send it back to the server next time agent will run.

Also, you can pass to the installer the following agent’s command line parameters
(see agent’s options below for more detail):

/SERVER=
/USER=
/PWD=
/SSL=
/CA=
/PROXY_TYPE=
/PROXY=
/PROXY_PORT=
/PROXY_USER=
/PROXY_PWD=
/DEBUG=
/NOTAG
/TAG=
/D=

Deploying or running Agent through Active Directory GPO

To deploy the agent using GPO we recommand you to create a standalone packager with all your configuration already provisionned. See using OCS Packager to create an all-in-one installer to setup agent and server certificate

After creating a packager, you will need to store it at a place where all your users have access to.

Then create a GPO that trigger on user login. You will have a create a script that call the packager executable and trigger the installation on the computer.

Here is a sample script:

Configuring Unix Unified Agent

Prerequisites

To be able to make SNMP using OCS Unified Unix agent, you have to install Net::SNMP perl module. You can find more information in the page Unix agent.

Copying SSL certificate file

To allow Unix Unified agent to download snmp_com.txt file using HTTPS, you have to copy SSL certificate file (as cacert.pem) in your OCS server configuration directory in your basevardir directory.

Your OCS server configuration directory is a directory created automatically using your OCS server URL (http:__ocsinventory-ng_ocsinventory for example).

For example, if your basevardir parameter is /var/lib/ocsinventory-agent/ and your OCS server URL is , so you have to copy your cacert.pem certificate file in /var/lib/ocsinventory-agent/http:__ocsinventory-ng_ocsinventory directory.

Scans informations using debug mode

To see more informations about SNMP scan, you can launch ocsinventory-agent using debug mode, like this:

You will see an debug output about SNMP scan like this:

In this example, you can see that the agent scanned an equipment and the data related to your SNMP data model configuration.

Using OCS Inventory NG Packager for MacOSX

Download OCS MacOSX Packager for MacOSX from OCS Inventory NG website download page
(),
unzip the file and double click Ocsinventory_MacOSX_Packager.app.

First of all, choose an OCS MacOSX installer package path by clicking the Browse button.

Set your custom OCS MacOSX agent configuration by choosing serveral options:

Http or https for OCS MacOSX agent communication to OCS server («http» by default).
OCS server server name («ocsinventory-ng» by default).
OCS MacOSX agent TAG value (optional).
Log file path for OCS MacOSX agent («/var/log/ocsng.log» by default).
Activate or Unactivate OCS MacOSX agent debug mode for logs (activated by default).
Activate or Unactivate OCS MacOSX agent packages download feature (activated by default).
Activate or Unactivate OCS MacOSX agent lazy mode (inactivated by default).
Periodicity for OCS MacOSX agent to be launched by Launchd daemon (5 hours by default).
Activate or Unactivate OCS MacOSX agent launch at Launchd daemon start (activated by default).
Activate or Unactivate OCS MacOSX agent launch, using Launchd daemon, after OCS agent installation
(unactivated by default)

You can set a certificate file path using the Browse Button (mandatory if you activate OCS MacOSX
agent packages download feature). Certificate file must be named as «cacert.pem».

Once you set your custom configuration, click on Next button to validate configuration.

If you do not set a path for OCS MacOSX installer package, you will have this warning:

If you activate OCS MacOSX agent packages download feature without specifying a certificate file path,
you may have this warning:

Set export options for generated package:

Choose an export path by clicking on the Browse button
Specify a custom filename if needed («ocspackage.pkg» by default)

If you do not set a export path, you will have this warning:

If you already have a same named file in export path, you will have this warning:

When your custom OCS MacOSX agent installer has been generated, you will have this message:

A custom OCS MacOSX agent installer file has been created in export path you set in last window.

Pushing OCS Inventory NG agent for Windows setup

Click on button of Agent Deployment Tool main window to start deploying on Windows computers. You can choose to deploy Agent on

all Windows computers within the specified IP range,
a list of manually selected computers: select them in the network neighborhood using button
«Browse Network», or specify them using UNC notation (\Computer_name or \IP_Address) or
select multiple computers into Active Directory using button «Browse AD»,
or import them from a file (file have to contain one IP or computer name by line)

Click button.

Select Windows Agent installer file to push,
Select optional plugin files to copy into plugins directory of the agent,
Select additional files to copy into Agent’s data folder, like certificate file,
Enter OCS Inventory NG server URL

or
or
or ,
Check Enable verbose log to activate OCS Inventory Agent logs (same as /DEBUG parameter)
Check Do not register service if you do not wish to use service for launching Agent
(same as /NO_SERVICE parameter)
Check Do not register Systray applet autostart if you do not wish to display OCS icon into Systray
(same as /NO_SYSTRAY parameter)
Check Force inventory just after setup to force inventory launch after OCS agent installation
(beware to OCS server load if you install a lot of computers at the same time !)
Enter additional parameters in Other options for Agent (/HKCU for example)
Check Change Agent setup directory to modify OCS Inventory agent installation directory
Other Commandline options will also work, for all Options see below.

and click button

Provide credentials of an Administrator account on remote computers with associated
password and click button.

You are now ready to process. Choose the number of computers to push installation simultaneously
(up to 10 computers) using the slider and click button.

Agent Deployment Tool will first check if remote computer is up and running Windows OS,
copy installation files to remote computer through administratibe shares,
uses PSEXEC to execute installation on remote computer and display logs into listbox.

If Agent Deployment Tool encounter errors on one or more computers, it will prompt you to save
the list of failed computers into a CSV file, and you will be able to import this file later to restart
installation process on these computers.

You can stop at any time the process using “Stop” button and also, when deployment is finished,
save logs to a file using “Save logs” button.

Система инвентаризации Myzci

Многие, кто пробовал систему инвентаризации zCI (zci.sf.net), находили ее довольно удачным решением, но ей не хватало возможности заносить данные вручную и локализованного интерфейса.

Конечно, это не критические моменты, но есть и другие мелочи. Например, нельзя удалить устройство через веб-интерфейс — необходимо вручную составить SQL-запрос на очистку данных из таблиц. Система инвентаризации MyZCI (sf.net/projects/myzci) является форком zCI. Разработкой занимается Юрий Винник, он довел zCI до нужных кондиций: интерфейс переведен на русский и украинский языки, добавлены новые поля в таблицы (например, размещение компьютера) и упрощено управление.

Для работы MyZCI потребуется любой вебсервер с поддержкой PHP (с PECL, PHP Extension Community Library) и MySQL.

Распаковываем архив myzci-1.2.1.zip в корневой каталог веб-сервера и в файле zciconfig.php указываем параметры доступа к MySQL:

Чтобы создать таблицы в БД, используем скрипт mysqlscript.sql, находящийся в каталоге engine. Записи внутри нужно привести в соответствие с данными:

Локализация интерфейса производится установкой переменной “$Lang” в значение “ru” в файле langconfig.php.

Для сбора информации в Windows-системе используется Windows Script Host, в Linux — lshwclient на Java. Все компоненты находятся в подкаталоге add-ons и engine. Здесь же лежат MS Windows Scripting Host 5.6 и MS WMI Core 1.5, которые необходимы для работы клиентской части в Win95/98/NT4. Перед развертыванием в файлах takedata.js и lshwclient.java следует изменить значение переменной MyZCIpath и MyZCIserver, чтобы она указывала URL сервера.

Процесс настройки клиентской части на конечных системах упрощен. Так, скрипт install.sh, используемый при установке в Linux, проверяет наличие пакетов lshw, jdk и read-edid (инфа о мониторе) и при их отсутствии выдает пояснительное сообщение. Далее происходит сборка Java-клиента и установка задания cron. После развертывания MyZCI нужно подключиться к серверу с удаленной системы и зарегистрировать компьютер, нажав соответствующую ссылку на главной странице. Информация о новой системе должна появиться в базе MyZCI. Скачиваем с главной страницы архив с клиентской частью и запускаем установщик.

После чего скрипты начнут отсылать данные на сервер. Интерфейс предельно прост и позволяет выводить детальную информацию о железе, вносить и редактировать данные о компьютерах, группировать, искать системы по определенному критерию (например, тип видеокарты и монитор), отслеживать изменения.

Меню администратора позволяет определять статус (закреплен, аренда) и местонахождение системы.

Enabling computer’s group feature

To be able to use computer groups, you must first enable its feature.

To do so, go to your management server’s configuration menu, and select the «Groups» configuration screen:

There, set the «ENABLE_GROUPS» parameter to «ON», and adjust the other parameters if needed.

The available parameters are:

ENABLE_GROUPS: Enable or disable the computer’s group feature;
GROUPS_CACHE_OFFSET: This setting is used to add a random number of seconds to the «GROUPS_CACHE_REVALIDATE»
to avoid computing many groups in the same process. See hereunder for more information;
GROUPS_CACHE_REVALIDATE: To avoid excessive load on servers where a large number of dynamic groups is being
used, groups’ membership is cached and refreshed at regular interval. This setting specify the interval,
in seconds, at which dynamic groups’ cached data is refreshed. This interval is actualy increased at run time
by a random number of seconds chosen between O and «GROUPS_CACHE_OFFSET» to avoid all dynamic groups being
refreshed at the same time.

Which version: Service or Standalone ?

The Windows service version will automatically communicate with the OCS-NG system and perform inventories
and package deployment based on parameters set on the server. The standalone client is used for computers
that cannot communicate with the server, or where the service version is not wanted or allowed.

How does Windows Agent work ?

When the OCS Inventory NG Agent is launched, it queries the Communication server using the HTTP
or HTTPS protocol. The server can answer “nothing” (not time for an inventory and no package to deploy),
and the agent stops. Otherwise, the server may answer that Agent has to:

Send an inventory: the agent retrieves all computer properties and sends them using HTTP
or HTTPS protocol to the server. The server ask this only if the last inventory date in the database
is older than the general option “FREQUENCY”, specified in days (see
.)
Discover the network: Agent scans his IP subnet for active devices listening on the network,
then sends these data using HTTP or HTTPS protocol to the server. The server ask this only if the
computer is elected to run IPDISCOVERY (see
Using IP discovery feature.)
Deploy a package: Agent contacts the deployment server using the HTTPS protocol to get the information file (file INFO which describes the package), downloads package fragments from the deployment server, rebuilds the package and launches it.

Since OCS Inventory Agent 2.6, it’s possible to deploy package greater than 4GB.
However, the deployment of such package may cause latency in machines on which it’s deployed.

Each time an inventory is done, the Agent uses and writes configuration files stored into folder
“%ProgramData%\OCS Inventory NG\Agent”. This directory is usually

C:\Documents and Settings\All Users\Application Data\OCS Inventory NG\Agent under Windows 2000, XP and 2003.
C:\ProgramData\OCS Inventory NG\Agent under Windows Vista, 2008, Seven and 2008 R2.

It uses at least the following files:

ocsinventory.ini: all configuration parameters for the agent (server address and credentials,
proxy address and credentials, service properties…),
ocsinventory.dat: computer unique identity file, based on MAC address and hostname,
last_state: last inventory state, to detect changes between 2 inventory,
history: package deployment history,
All log files created by OCS Inventory NG Agent.

When launched for the first time, OCS Inventory NG agent will prompt user for the TAG value
(if this feature is enabled). Help text displayed in the dialog-box is the one you have entered
in Configuring management server. User may enter this value, or leave it blank (you will be able
to update this value through the Administration server).

Then (or otherwise if TAG feature is not enabled), it will do the inventory and send inventory
results to Communication server using HTTP or HTTPS.

How does Windows service work?

OCS Inventory NG Agent “OCSInventory.exe” is launched by service “OcsService.exe” every PROLOG_FREQ hours.
It keeps trace of the countdown in seconds in file “ocsinventory.ini” (value TTO_WAIT), so it is the time
of EFFECTIVE run.
The number of hours to wait is randomized at install time and each time PROLOG_FREQ is changed in
Administration Console.
It allows not having all agents contacting Communication Server at the same time. The randomization
is between 0 and PROLOG_FREQ (10 hours by default). You can adjust these parameters considering your
server load using Administration Console.

When service launch agent, it call without parameter, so agent uses parameters specified in file “ocsinventory.ini”.

As you can see, Service is only a launcher which will run Agent regularly, even if nobody logs in the computer.

Do I have to use service or standalone agent ?

You want to have computers inventoried, even if nobody log in ? Use Service version.
You want to use package deployment feature ? Use service version. As is, package will be downloaded
in background, and logged in user can continue to work.
You do not want to set service up or have anything appears in the registry ? Use standalone version.
However, deployment of package may take a long time when users log in.

In other words, we recommend using service version.

Configuring SNMP scan

General options

To manage SNMP general options in Web Interface, go to menu, click on and go to the tab.

This is the SNMP configuration options available:

SNMP: activate or deactivate SNMP scan feature. If this option is OFF, no SNMP scans will be made by any OCS agent
SNMP_MIB_DIRECTORY: set the server MIBs folder path

Manage SNMP communities

To be able to scan a SNMP device, you must use SNMP community. SNMP community can be viewed as authentication informations to be allowed to scan SNMP devices. SNMP community is created by 2 informations:

SNMP version : it is the SNMP version supported by the SNMP device(s) (can be version 1, version 2, version 2c etc…)
SNMP community name : it is the community name you set in your SNMP device(s). For many SNMP devices, the default SNMP community name is public.

If you set your own SNMP communities in your SNMP devices, you have to add it in OCS Inventory configuration. OCS agent will received informations about this communities and will try to scans SNMP devices using every SNMP communities you set in administration console. SNMP communites informations are directly added in database.

To manage SNMP communities in Web Interface, go to menu, click on and go to the tab.

You can now add a new SNMP communities using the button. A new screen is displayed :

You have to set a community name and a SNMP version (using the drop list).

To delete a SNMP community, click on the red cross
To modify a SNMP community, click on the edit icon

Configuring SNMP data model to scan

SNMP scan is now based on a dynamic data model, which mean that the database model and inventory will be adapted depending on the queried device.

To configure SNMP scan data model, read the documentation Managing SNMP on Web Console.

Electing computer(s) to be able a SNMP scan

To be able an Agent to scan its network using SNMP (without waiting for an Ipdiscover automatic election), you may have to set its custom parameters at computer side or at groups side.

Configuring computer custom parameters

To make a single Agent to scan its network using SNMP, you have to set it in its custom parameters. First, go to its page and click on . Then, click on the tab.

If no network address appears in IPDISCOVER option, you have to set it manually using the drop list
You can enable/disable a computer to make SNMP scans using SNMP_SWITCH option. By default, global configuration parameter is taken, corresponding to the Default radio button.

Click on the button to save your modifications.

Configuring groups custom parameters

To make a multiple Agents to scan its network using SNMP, you have to set it in group custom parameters.
First, click the menu and . Select the group that you want to be able to a SNMP scan. At the bottom of the customization page click on .
Then, click on the tab.

The configuration parameters are the same that a single computer.

Click on the button to save your modifications.

Installing and configuring OCS Inventory NG Agent Deployement tool

To install OCS Inventory NG Agent Deployment Tool, download zip archive from
our download page.

Uncompress the zip file and run OCS-NG-Agent-Deployment-Tool-Setup.exe on a Windows Computer.

Click button

Validate license agreement by clicking button

Choose destination folder, C:\Program Files\OCS Inventory Agent Deployement Tool” by default
(“C:\Program Files (x86)\OCS Inventory Agent Deployment tool under Windows 64 bits),
and click button

Choose start menu folder, OCS Inventory NG\Agent Deployement Tool by default,
and click button.

Click button to close OCS inventory NG Agent Deployment Tool Setup.
Setup can start the tool for you if you the box Start OCS Inventory NG Agent Deplyment Tool is checked

Click on button of Agent Deployment Tool main window to display settings.

You have to provide path to:

Microsoft SysInternals PsExec.exe tool (click on the link to open your browser with SysInternals
Home page and download PsTools suite from here).
PuTTY.exe SSH and Pscp.exe tools (click on the link to open your bowser with PuTTY Home page
and donwload tools from here).

Click button to save changes.