Documentation:WindowsAgent/pl

From OCS Inventory NG
Jump to: navigation, search

Agent OCS Inventory NG w wersji 2.0 dla systemów operacyjnych Windows.

Note: Windows XP nie jest już wspierany w wersjach nowszych niż 2.1.


Note: Agent OCS Inventory NG w wersji 2.0 nie działa z systemami Windows 9X, Windows Millenium lub Windows NT4. W takim przypadku musisz użyć starszej wersji agenta 1.X 4061-1.


Agent OCS Inventory NG dla Windows może uruchamiać się jako usługa Windows automatycznie przy starcie komputera. Może również pracować jako samodzielna aplikacja, która uruchamiany jest poprzez skrypt logowania, politykę GPO Active Directory, planowane zadanie lub skrót w menu Start.


Note: Rekomendujemy użycie Agenta jako usługi, zwłaszcza jeśli planujesz wykorzystywać możliwość zdalnej instalacji pakietów.


Pobierz i rozpakuj najnowszą wersję agenta dla Windows z sekcji Downloads. Ten pakiet zawiera

  • OCS-NG-Windows-Agent-Setup.exe: instaluje Agenta dla systemu Windows jako Usługę systemu Windows lub jako samodzielną aplikację.
  • OcsLogon.exe: instaluje agenta pobierając pliki binarne z Serwera Komunikacyjnego lub uruchamia agenta jeśli jest już zainstalowany. Można zainstalować agenta w wersji jako Usługa systemu Windows lub jako samodzielną aplikację, w zależności od użytych przełączników linii poleceń.


Jaka wersja: Usługa czy Samodzielna ?

Wersja agenta pracująca jako Usługa Windows automatycznie będzie komunikować się z systemem OCS-NG i wykonywać spis oraz instalację pakietów bazując na parametrach ustawionych na serwerze. Wersja jako samodzielna aplikacja używana jest na komputerach które nie mogą się komunikować z serwerem komunikacyjnym lub gdzie wersja usługi nie jest pożądana lub dozwolona.

Jak działa Agent dla Windows ?

Kiedy uruchamiany jest Agent OCS Inventory NG, odpytuje on serwer Komunikacyjny używając protokołu HTTP lub HTTPS. Serwer może odpowiedzieć “nothing” (nie czas na inwentaryzację lub instalację pakietów) i agent kończy pracę. W innym przypadku serwer może odpowiedzieć, że Agent ma do wykonania:

  • Wyślij inwentaryzację: agent zbiera wszystkie parametry komputera i wysyła je przy użyciu protokołu HTTP lub HTTPS do serwera. Serwer zapyta o to tylko jeśli data ostatniej inwentaryzacji jest starsza niż ustalona prze opcję “FREQUENCY”, wyrażoną w dniach (zobacz Managing OCS Inventory NG general options.)
  • Wykryj sieć: Agent skanuje podsieć ze swojego IP w poszukiwaniu aktywnych nasłuchujących urządzeń w sieci, następnie wysyła te informacje używając protokołu HTTP lub HTTPS na serwer. Serwer zapyta o to jedynie jeśli komputer jest wybrany do uruchomienia IPDISCOVERY (zobacz Using IP discovery feature.)
  • Instalacja pakietu: Agent kontaktuje się z serwerem instalacji używając protokołu HTTPS protocol aby pobrać plik informacyjny (plik INFO opisujący pakiet), pobiera poszczególne paczki pakietu z serwera instalacji, odbudowuje pakiet i uruchamia go.
Note: Agent OCS Inventory NG Agent nie nasłuchuje w sieci. Jedynie inicjuje komunikację do serwera, więc nie potrzebuje otwierać portów do komunikacji wychodzącej na firewallu. Jednakże musisz pozwolić na wychodzące połączenia z plików agenta OCS Inventory NG “OCSInventory.exe” i “Download.exe” do Serwera Komunikacyjnego lub Serwera Instalacyjnego przy użyciu protokołu HTTP lub HTTPS.


Za każdym razem kiedy inwentaryzacja jest wykonana, Agent używa i zapisuje pliki konfiguracji przechowywane w katalogu “%ProgramData%\OCS Inventory NG\Agent”. Jest to zwykle katalog

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

Używa on przynajmniej poniższe pliki:

  • ocsinventory.ini: wszystkie parametry konfiguracyjne agenta (adres serwera i dane uwierzytelniające, adres proxy address i dane uwierzytelniające, właściwości usługi...),
  • 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.
Note: YOU MUST STOP “OCS Inventory Service” to make changes on these files, because they are write protected while service is running. As is, only user having Administrator privileges can modify these files.


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.

Note: When the agent is first launched, it will only generate and send an inventory.


How does Windows service work?

Note: You must have Administrator privileges to set up OCS Inventory NG Agent as a service, or you may use OCS Inventory NG Packager to create an installer able to run even if user do not have Administrator privileges. Refer to § Uploading Agent for deployment through launcher “OcsLogon.exe”. or OCS Inventory NG Packager documentation.


  • 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.

Powinienem użyć Agenta w wersji jako usługa systemu Windows czy jako samodzielny program ?

  • Chcesz inwentaryzować komputery nawet gdy nikt nie jest zalogowany ? Użyj agenta pracującego jako usługa.
  • Chcesz wykorzystać możliwość zdalnej instalacji pakietów ? Użyj agenta pracującego jako usługa. Pakiet zostanie ściągnięty w tle i zalogowany użytkownik może kontynuować pracę.
  • Nie chcesz uruchamiać usługi lub nie chcesz aby cokolwiek widniało w rejestrze ? Użyj agenta pracującego jako samodzielny program. Jednakże instalacja pakietów może zająć dłuższą chwilę przy logowaniu się użytkownika.

Innymi słowy rekomendujemy wersję działającą jako Usługa.

Ręczna instalacja Agenta CS Inventory NG Agent dla Windows.

Uruchom “OCS-NG-Windows-Agent-Setup.exe” na computerze klienckim.

Windows Agent 2.0 Setup 0.png

... i kliknij przycisk “Next”

Windows Agent 2.0 Setup 1.png

Przejrzyj licencję i zaakceptuj jej warunki klikając na przycisk “I agree”.

Windows Agent 2.0 Setup 2.png


Wybierz rodzaj instalacji który tobie odpowiada:

  • Network inventory: Computer can reach OCS Inventory NG Server through the network, and so, Agent will be launched using ethier 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).
Windows Agent 2.0 Setup 3.png

Fill in OCS Inventory NG Communication server URL, like http://your_ocs_server_address:your_server_port/ocsinventory. 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").

następnie kliknij przycisk “Next”.

Note: You can use self signed certificate, but certificate CN must equal to server address used by agents for communications. Also, if full path to certificate is not provided, agent will try to load the specified file from its data folder "%ProgramData%\OCS Inventory NG\Agent".


Windows Agent 2.0 Setup 4.png

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.

Windows Agent 2.0 Setup 5.png

By default, OCS Inventory Agent write only few informations 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 informations. Disabling this option does not create shortcut link in "All users" startup menu.
  • Launch inventory just at the end of setup.
Windows Agent 2.0 Setup 6.png

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.

Windows Agent 2.0 Setup 7.png

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

Windows Agent 2.0 Setup 8.png

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 interraction with user
  • /NOSPLASH disable spash screen when installer starts
  • /UPGRADE to deploy new agent through OCS deployement 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
  • /NO_SERVICE to not register OCS Inventory NG Agent into Windows Service Manager. Agent can onlybe 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

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=

Instalacja Agenta przy użyciu programu uruchamiającego OcsLogon.exe poprzez Skrypt Logowania lub politykę GPO w Active Directory.

Program uruchamiający “OcsLogon.exe” jest małym narzędziem mogącym być uruchomionym ze skryptu logowania lub polityki grup GPO Active Directory. Jego działanie polega na uruchomieniu instalatora Agenta, jeśli nie jest on już zainstalowany na komputerze klienta, oraz do uruchomienia Agenta OCS Inventory NG jeśli nie chcesz używać w tym celu usługi systemowej.

  • Aby zdalnie zainstalować Samodzielnego Agenta przy użyciu programu uruchamiającego, najpierw musisz wgrać plik Samodzielnego Agenta “ocsagent.exe” lub “OCSNG-Windows-Agent-Setup.exe” na serwer, przy użyciu Konsoli Administracyjnej.


Note: Refer to § Uploading Agent for deployment through launcher “OcsLogon.exe”.


Launcher “OcsLogon.exe” will try to connect by default to Communication Server using URL http://ocsinventory-ng/ocsinventory.

To use a different URL, you must provide “/SERVER=http[s]://your_server[:your_port]/ocsinventory” command line parameter (strings between [] are optional). For example, if your server uses HTTP protocol, and is located on computer 192.168.1.2 on port 80, you must use “/server=http://192.168.1.2/ocsinventory”. If your server requires HTTPS on port 8443, you must use “/server=https://192.168.1.2:8443/ocsinventory”.

Note: Always use the latest version of OcsLogon.exe. You can get it from the latest package OCSNG-WINDOWS-AGENT_XXXX.zip.


Launcher will first check if OCS Inventory NG Agent is installed, and if not, will contact Communication Server in HTTP/HTTPS to download latest Agent installer and run it on the computer.

Launcher OcsLogon.exe can use the following command line parameters:

  • /PACKAGER setup all-in-one installer “ocspackage.exe” (See Using OCS Packager to create an all-in-one installer to setup agent and server certificate), to install Agent and server certificate even if user does not have Administrator privileges.
  • /GPO tell Launcher that setup file to download is in the same folder as OcsLogon.exe. So, OcsLogon does not try to download setup file from Communication Server, but try to use the one copied in the GPO folder.
  • /URL=http[s]://your_server:port/path_to_file_to_download.exe tell Launcher that setup file is located at provided URL, instead of Communication Server.
  • /DEPLOY=a.b.c.d ensure there is at least the specified version installed. OcsLogon install/upgrade Agent only if installed version is lower than the specified one "a.b.c.d".
  • /FORCE force reinstalling agent, even if the installed version is newer or equal to the specified one. Use it to downgrade version for example. CAUTION, USE THIS OPTION WITH CARE, as Launcher will setup agent each time.
  • /TIMEOUT=x (milliseconds) allow to modify default download timeout of 60 seconds.
  • /UNINSTALL uninstall agent, instead of installing it.

You must also provide standard agent setup command line parameters (see OCS Inventory NG Agent setup command line options for more detail), and at least:

  • /SERVER=http[s]://you_cs_server[:port]/ocsinventory, URL to connect to OCS Inventory NG Communication Server.
  • /NO_SERVICE to not register OCS Inventory NG Agent into Windows Service Manager and so uses standalone agent. Launcher will then launch Agent each time. Otherwise, it will never run Agent, assuming Agent is launched by Windows Service.
Note: Launcher OcsLogon.exe always create a log file “OcsLogon.log” into temporary folder.
  • When launched through a computer GPO, this folder is usually “C:\Windows\Temp”.
  • When launched through a user GPO or login script, this folder is usually “C:\Documents and Settings\User Profile\Local settings\Temp” or “C:\Users\User Profile\AppData\Local\Temp”.


Instalacja lub uruchamianie Agenta poprzez politykę GPO Active Directory.

Note: Rekomendujemy użycie wersji Agenta działającej jako usługa jeśli planowane jest wykorzystanie funkcjonalności zdalnej instalacji usług.


Otwórz narzędzie "Group Policy Manager".

Note: Możesz otworzyć menadżer polityki grup GPO Manager bezpośrednio poprzez wpisanie polecenia gpmc.msc w linii komend.


W lewym panelu wświetl "Group Policy objects" swojej domeny.

GPO Objects.png

Utwórz nową politykę lub wyedytuj istniejącą.

Możesz wykorzystać "Computer policy" (polityka związana z komputerem) lub "User policy" (polityka związana z użytkownikiem). "Computer policy" zostanie zastosowania przy starcie komputera podczas gdy "User policy" zostanie wykonana przy logowania użytkownika.


Wyedytuj stworzoną politykę klikając lewym klawiszem myszy na nazwie polityki i wybierając opcję "Edit"


Note: W naszym przykładzie używamy "Computer policy" oraz skrypt Startup. Adres Serwera Komunikacyjnego to "ocs.mycompany.tld", wybieramy instalację Agenta jako usługi (Service Agent) wykorzystując Packager wszystko-w-jednym instalator "ocspackage.exe" (Patrz Używanie OCS Packager do stworzenia instalatora all-in-one do instalacji agenta i certyfikatów serwera). Jeśli wybierzesz samodzielnego agenta "Standalone Agent", wtedy lepiej wykorzystać "User policy" oraz and skrypt startup, aby umożliwić agentowi uruchomienie za każdym razem kiedy użytkownik się loguje.


Edytor obiektów zasad grup

Rozwiń drzewko "Konfiguracja komputera" widoczne w lewym panelu i przejdź jak pokazano poniżej do opcji "Ustawienia systemu Windows" a później do "Skrypty".

GPO Computer startup script 1.png

Kliknij dwa razy na "Autostart" widoczny w prawym panelu.

GPO Computer startup script 2.png

Kliknij na przycisk "Pokaż pliki..." aby wyświetlić wykonywalne pliki używane przez GPO i skopiuj do tego katalogu pliki programu "Ocslogon.exe" oraz instalatora all-in-one "Ocspackage.exe".

GPO Computer startup script 3.png

Next close “Startup” folder and click “Add” script button, click “Browse” button to select launcher “OcsLogon.exe” , and fill in Launcher parameters, in our example

GPO Computer startup script 4.png

Validate each window to activate Computer Startup script GPO.

GPO Computer startup script 5.png

Update if needed default GPO filters to meet your needs, for example to apply this GPO only to specified Active Directory OU or site.

GPO Activate Filter.png

When computer will start (or when user will login if using User policy), launcher will set up if needed OCS Inventory NG Agent as a service.

Deploying or running Agent through login script.

Note: We recommend using service version of Agent if you plan to use package deployment feature.


Copy files “OcsLogon.exe” to a shared folder somewhere in your network. This folder must be readable by all your users. Then add a call to “OcsLogon.exe” in your users login script.

Here is a sample login script.

Warning: Below code requires additional checking for internal LAN configuration, but is functionally.
@echo of
echo Running system inventory, please wait…
REM Call to OCS Inventory NG Launcher
REM Using shared folder MY_SHARE on server MY_SERVER
REM Using OCS Inventory NG server address ocs.mycompny.tld using HTTP protocol (option /SERVER=)
REM Install stand alone agent without service (option /NO_SERVICE)
REM Ensure that at least Agent version 2.0.0.15 is installed (option /DEPLOY)
REM Configure Launcher and Agent to using HTTP proxy server 192.168.1.2 on port 8080 (option /PROXY_TYPE, /PROXY and /PROXY_PORT)
REM If needed, install agent silently (option /S)
REM As /PACKAGER is not used, this script can only install agent if launched by a user having Administrator rights

\\MY_SERVER\MY_SHARE\OcsLogon.exe /NO_SERVICE /S /SERVER=http://ocs.mycompny.tld/ocsinventory /proxy_type=1 /proxy=192.168.1.2 /proxy_port=8080

echo Done. Thanks a lot.
Sample login script for Windows domain

Put this script named “ocs.bat” for example on your Domain Controller (in the folder “%WINDIR%\SYSVOL\Domain\Scripts” on Windows Controller, where “%WINDIR%” is usually “C:\WINNT” or “C:\Windows”).

Finally, you have to link login script with every users registered in your Samba or Active Directory domain. On Active Directory, you can do this using “Active Directory users and computers” tool, select “Profile” tab in user properties, and fill in “Session startup script”.

AD Users and commputers User logon script.png

When user log in, launcher will set up and/or launch OCS Inventory NG Agent.

Using PSEXEC or "OCS Inventory NG Agent Deployment Tool" to push OCS Inventory NG Agent

PSEXEC from Microsoft (http://download.sysinternals.com/Files/PsTools.zip) is a great and fast way to install the OCS agents on all Windows computers, you can literally setup most of your computers in a few hours (assuming they are all connected to the network, that is).

Note: We've created a graphical tool for Windows, OCS Inventory NG Agent Deployment Tool, which allows you to use PSEXEC more easily. It is able to push agent's installation on up to 10 computers simultaneously, and also to copy the certificate used to authenticate deployement server in OCS Inventory NG data folder.


Some tips:

PSEXEC is best used together with Domain Logon scripts or Active Directory GPO:

  1. Use the PSEXEC to install on all computers that are currently connected to the network (best used during business hours).
  2. Then add a logon script/GPO as described above to install on computers that were offline the next time they connect to the network.
  3. If you really don't want to use logon script/GPO, you can create and monitor a response file to get a list of computers that were not deployed for any reason, and then rerun PSEXEC just for these computers.

PSEXEC Usage examples:

We assume that the agent setup file is called agentsetup.exe and it was placed on a shared folder accessible to all users.

  • Install silently on all computers currently logged in your domain:
psexec \\* -s \\Server\NetLogon\OCS-NG-Windows-Agent-Setup.exe /S /NOSPLASH /SERVER=http://my_ocs_server/ocsinventory 
  • Install silently on a single computer:
psexec \\COMPUTER_NAME -s \\Server\NetLogon\OCS-NG-Windows-Agent-Setup.exe /S /NOSPLASH /SERVER=http://my_ocs_server/ocsinventory
  • Install silently on all computers using the domain administrator credentials:
psexec \\* -s -u Domain\Administrator -p Password \\Server\NetLogon\OCS-NG-Windows-Agent-Setup.exe /S /NOSPLASH /SERVER=http://my_ocs_server/ocsinventory
  • Install silently on specific computers (ALL.TXT is a text file that lists target computer names, one per line), using domain administrator credentials:
psexec @ALL.TXT -s -u Domain\Administrator -p Password \\Server\NetLogon\OCS-NG-Windows-Agent-Setup.exe /S /NOSPLASH /SERVER=http://my_ocs_server/ocsinventory

Generating inventory of a non network connected Windows computer

Run “OCS-NG-Windows-Agent-Setup.exe” on client computer, from an USB stick for example..

Windows Agent 2.0 Setup 0.png

..and click “Next” button

Windows Agent 2.0 Setup 1.png

Validate license agreement by clicking “I agree” button.

Windows Agent 2.0 Setup 2.png

Select Local inventory installation type.

Windows Agent 2.0 Setup Local 1.png

By default, OCS Inventory Agent write only few informations in log files. You may increase this enabling “Verbose log”. You may also specify the TAG value. Last, indicate the folder where you want to store generated inventory file, your usb stick for example:

Windows Agent 2.0 Setup Local 2.png

In local inventory mode, Agent will be installed into a temporary folder (we recommend not changing this folder, it will be automatically deleted at the end of process), Click “Install” button to start process. Agent is installed into temporary folder, launched to generate a ".ocs" inventory file stored in the folder you've specified, and then removed from computer.

Windows Agent 2.0 Setup Local 3.png

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

Windows Agent 2.0 Setup 8.png

This is the interactive process, but it can be scripted using /LOCAL=path_to_folder_where_to_store_ocs_file command line switch.

For example, you can use OCS-NG-Windows-Agent-Setup.exe /S /LOCAL=C:\ to silently generate ".ocs" inventory file into folder c:\.

Once you've transfered generated inventory file, you will be able to import it into the inventory database of OCS Inventory NG Server, through the Administration Console.


OCS Inventory NG Agent for Windows command line options.

OCS Inventory NG Agent version 2.0 or higher includes some command line switches to allow detecting errors.

Once agent is installed, you can run it manually to diagnose problems. Use “C:\Program Files\OCS Inventory Agent\OCSInventory.exe [options]” command line where [options] may be in the following command line switches.

Command Line Options:

Meaning:
/work_dir="path to directory"
Agent must use "path to directory" as working dir (this directory may included configuration file). Default is "%ALLUSERSPROFILE%\Application Data\OCS Inventory NG\Agent" or "%PROGRAMDATA%\OCS Inventory NG\Agent"
/local[="path to folder"]
Agent do not contact communication server, and store inventory in xml compressed .ocs file into folder "path to folder". If no "path to folder" provided, agent assume folder as data folder</nowiki>
/debug[=level]
Generate a very verbose log file "ocsinventory.log" into agent's install folder.
  • 0 => disable verbose logs (default)
  • 1 => enable default verbose logs (default when no level provided provided)
  • 2 => enable debuging logs
/notag
Agent must NOT prompt user for TAG in any case
/tag="my value"
Agent must set "my value" as TAG value
/xml=["path to folder"]
Agent must store inventory in uncompressed xml format into folder "path to folder". If no "path to folder" provided, agent assume folder as data folder
/force
Always send inventory, even if server do not ask for it (use only for debugging purpose !)
/ipdisc="network number"
Agent must launch IP discovery on network "network number" (use only for debugging purpose !)


/ipdisc_lat="number of milliseconds"
Set latency between 2 IP Discover requests to "number of milliseconds"
/fastip
Never wait for latency between 2 IP Discover requests (use only for debugging purpose !)
/hkcu
Search also for software under HKEY_CURRENT_USER registry hive (do not work with service as LocalSystem !)
/uid
Agent must generate a new unique device ID
/server=http[s]://server.domain.tld[:port]/ocsinventory
Agent try to connect to Communication Server address and port Listening on http[s]://server.domain.tld[:port]/ocsinventory
/ssl=0|1
When usng SSL connections:
  • 0 => SSL without certificate validation,
  • 1 => SSL with server certificate validation required (needs CA certificate)
/ca="path_to_cabundle.pem"
Path to CA certificate chain file in PEM format, for server certificate validation
/user=username /pwd=password
Communication Server authentication credentials
/proxy_type=0|1|2|3
Agent proxy use
  • 0 => no,
  • 1 => HTTP proxy,
  • 2 => Socks 4 proxy,
  • 3 => Socks 5 proxy)


/proxy=proxy_address
Proxy server address (without protocol !)
/proxy_port=port
Proxy server port
/proxy_user=username /proxy_pwd=password
Proxy authentication credentials

Sample configuration file "ocsinventory.ini".

[OCS Inventory Agent]
; OCS Inventory NG Agent features
; Enable debugging mode (0 => disabled, 1 => enabled, 2=> trace all) 
Debug=1
; Enable local inventory mode (path to folder to store .ocs file => enabled,
; empty => disabled) 
Local=
; Enable agent scanning HKEY_CURRENT_USER hive for printers and sofware
; (0 => disabled, 1 => enabled) 
HKCU=0
; Disable prompting user for TAG value (0 => prompt allowed, 1 => disabled) 
NoTAG=0
; Force agent launching IpDiscover on specified network (network address => enabled,
; empty disabled)
IpDisc=
; Which communication provider to use
; Name of communication DLL and configuration section to use
; DLL must be in "com" sub directory
ComProvider=ComHTTP.dll

[HTTP]
; OCS Inventory NG Communication Server address and port
; Listening on http[s]://server[:port]/ocsinventory
Server=http://localhost/ocsinventory
; Using SSL connections (0 => SSL without certificate validation,
; 1 => SSL with server certificate validation required)
SSL=0
; Path to CA certificate chain file in PEM format, for server certificate
; validation
CaBundle=D:\Developp\OCS Inventory NG\cacert.pem
; Using authentication on Communication Server (0 => no, 1 => yes)
AuthRequired=0
; Communication Server authentication credentials (encrypted)
User=
Pwd=
; Using proxy (0 => no, 1 => HTTP proxy, 2 => Socks 4 proxy, 3 => Socks 5 proxy)
ProxyType=0
; Proxy address and port
Proxy=
ProxyPort=
; Using proxy authentication (0 => no, 1 => yes)
ProxyAuthRequired=
; Proxy authentication credentials (encrypted)
ProxyUser=
ProxyPwd=

 
[OCS Inventory Service]
; Time to wait in minutes before next agent start
TTO_WAIT=1020
; Number of hour between 2 agent runs
PROLOG_FREQ=5
; Old value of PROLOG_FREQ
OLD_PROLOG_FREQ=10