3,054
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + + + + + − {{Warning box|In development !!!}}+ − + − + − '''none'''+ − − − − − Line 17:
Line 17: + + + + + + + Line 33:
Line 40: − + Line 44:
Line 51: − + Line 52:
Line 59: − + − + − − + + + Line 68:
Line 76: − + Line 116:
Line 124: − + Line 139:
Line 147: − + − + Line 149:
Line 157: − − − − − Line 193:
Line 196: − + Line 243:
Line 246: − + − + Line 251:
Line 254: − + Line 287:
Line 290: − + − + Line 298:
Line 301: − +
→Deploying your packages
{{Languages}}
==Maintainer==
[mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]]
===Version===
{{#smeversion: smeserver-ocsinventory }}
==HowTO==
===Installation===
=Maintainer=
====SME8====
yum install smeserver-ocsinventory --enablerepo=smedev,smetest,smecontribs
=Install=
yum install smeserver-ocsinventory --enablerepo=smedev,smetest,smecontribs -y
then
then
{{Warning box|You must issue first the ocs-update before post-upgrade and reboot}}
{{Warning box|You must issue first the ocs-update before post-upgrade and reboot}}
====SME9====
You must first enabled the [[Remi-ocsinventory]] repository, then
yum install smeserver-ocsinventory --enablerepo=remi-ocsinventory,smecontribs
signal-event ocs-update
or if you prefer to reboot your server, then do
signal-event post-upgrade; signal-event reboot
----
after this you can proceed to normal installation according to [[OCS Inventory#Importing ocsagent.exe in MySQL]] should go to http://YOURDOMAIN/ocs/install.php
after this you can proceed to normal installation according to [[OCS Inventory#Importing ocsagent.exe in MySQL]] should go to http://YOURDOMAIN/ocs/install.php
rm -f /usr/share/ocsinventory-reports/ocsreports/install.php
rm -f /usr/share/ocsinventory-reports/ocsreports/install.php
==Special commands==
===Special commands===
To view OCS configuration, you can type the following at the prompt:
To view OCS configuration, you can type the following at the prompt:
config show ocs
config show ocs
# URL | new alias | | Optionnal aliases for ocs and glpi web interfaces
# URL | new alias | | Optionnal aliases for ocs and glpi web interfaces
=Client Installation=
===Client Installation===
The client side is available [http://www.ocsinventory-ng.org/index.php?page=1-01 on all platforms]. Download the latest client version according to your OS.
The client side is available [http://www.ocsinventory-ng.org/index.php?page=1-01 on all platforms]. Download the latest client version according to your OS.
While you are installing the agent, copy the cacert.pem file, see the SSL section below.
While you are installing the agent, copy the cacert.pem file, see the SSL section below.
==OCS Agent for SME Server==
===OCS Agent for SME Server===
If you want to inventory other SME Servers (without installing the server-side and web interfaces)
If you want to inventory other SME Servers (without installing the server-side and web interfaces)
====for sme8====
yum install ocsinventory-agent ocsinventory-ipdiscover --enablerepo=smetest,epel
yum install ocsinventory-agent ocsinventory-ipdiscover --enablerepo=smetest,epel
{{Warning box|this will issue a warning, which can be ignored, about : rpmts_HdrFromFdno: Entête V3 DSA signature: NOKEY, key ID 00f97f56
{{Warning box|this will issue a warning, which can be ignored, about : rpmts_HdrFromFdno: Entête V3 DSA signature: NOKEY, key ID 00f97f56
Public key for ocsinventory-ipdiscover-1.01-2.el5.remi.i386.rpm is not installed
Public key for ocsinventory-ipdiscover-1.01-2.el5.remi.i386.rpm is not installed
}}
}}
====for sme9====
yum install ocsinventory-agent ocsinventory-ipdiscover --enablerepo=remi-ocsinventory
-----
Then edit ''/etc/ocsinventory-agent/ocsinv.conf'' and modify following lines:
Then edit ''/etc/ocsinventory-agent/ocsinv.conf'' and modify following lines:
OCSSERVER=yourdomain.com
OCSSERVER=yourdomain.com
ocsinventory-agent -s yourdomain.com -t your_tag
ocsinventory-agent -s yourdomain.com -t your_tag
==OCS Agent for Windows==
===OCS Agent for Windows===
There are 2 differents ways of sending inventories on Windows. Download the latest client software, OCSNG_WIN32_AGENT_1.xx_repack.zip from ocs website. This archive contains 3 executables.
There are 2 differents ways of sending inventories on Windows. Download the latest client software, OCSNG_WIN32_AGENT_1.xx_repack.zip from ocs website. This archive contains 3 executables.
This also allows to update files archived in ''ocsagent.exe'' on your clients (can be service or standalone executable).
This also allows to update files archived in ''ocsagent.exe'' on your clients (can be service or standalone executable).
A [http://prdownloads.sourceforge.net/ocsinventory/OCSNG_PACKAGER_1.01.zip?download packager] is available at ocs website. This will allow you to repackage ''ocsagent.exe'' with your own modifications (i.e. an SSL certificate!)
A [https://launchpad.net/ocsinventory-windows-packager/2.1/2.1.1/+download/OCSNG-Windows-Packager-2.1.1.zip packager] is available at ocs website. This will allow you to repackage ''ocsagent.exe'' with your own modifications (i.e. an SSL certificate!)
[[Image:OCS-packager.png]]<br>
[[Image:OCS-packager.png]]<br>
----
----
If you want to remove ''ocsagent.exe'' from your database, simply delete the file from the server and redo install.php. This will delete the file from the database.
If you want to remove ''ocsagent.exe'' from your database, simply delete the file from the server and redo install.php. This will delete the file from the database.
==OCS Agent for Linux==
===OCS Agent for Linux===
Download the generic linux tar.gz, unpack, read the README, and as root, run the setup script.
Download the generic linux tar.gz, unpack, read the README, and as root, run the setup script.
You may required additional perl- packages, use you package management tools to search for the missing dependencies based on the README or the error messages. See Section 4.2 in the internal OCS help file.
You may required additional perl-packages, use your package management tools to search for the missing dependencies based on the README or the error messages. See Section 4.2 in the internal OCS help file.
To run an inventory
To run an inventory
Check the time (will the PC be on) and command given in
Check the time (will the PC be on) and command given in
/etc/cron.d/ocsinventory-client
/etc/cron.d/ocsinventory-client
=OCS Inventory NG Usage=
=OCS Inventory NG Usage=
[[Image:OCS-ipdiscover-step4.png]]<br>
[[Image:OCS-ipdiscover-step4.png]]<br>
----
----
Add you own network/subnet. All fields are mandatory.
Add your own network/subnet. All fields are mandatory.
[[Image:OCS-ipdiscover-step5.png]]<br>
[[Image:OCS-ipdiscover-step5.png]]<br>
----
----
----
----
====Building a deployment packages====
====Building a deployment package====
Deployment packages can be either '''''.zip''''' files (Windows) or '''''tar.gz''''' files (Linux)
Deployment packages can be either '''''.zip''''' files (Windows) or '''''tar.gz''''' files (Linux).
'''Don't try to deploy other file type.'''
'''Don't try to deploy other file type.'''
for an overview see [http://www.ocsinventory-ng.org/index.php?page=package-deployment the ocs website]
for an overview see [http://www.ocsinventory-ng.org/index.php?page=package-deployment the ocs website]
for detail see section 8.3 of the help file,
for detail see section 8.3 of the help file,
for [http://alufis35.uv.es/OCS-Deployment-Tips-and-tricks.html Tips and tricks] see Pablo Iranzo's site
for [http://alufis35.uv.es/OCS-Deployment-Tips-and-tricks.html Tips and tricks] see Pablo Iranzo's site.
[[Image:OCS-buildpackage.png]]<br>
[[Image:OCS-buildpackage.png]]<br>
----
----
Open the desired computer's inventory on click on ''Config'' icon and add a new package
Open the desired computer's inventory on click on ''Config'' icon and add a new package.
[[Image:OCS-deploy-single-pc1.png]]<br>
[[Image:OCS-deploy-single-pc1.png]]<br>
----
----
You should see all activated packages, affect the one you want and confirm changes
You should see all activated packages, affect the one you want and confirm changes.
[[Image:OCS-deploy-single-pc2.png]]<br>
[[Image:OCS-deploy-single-pc2.png]]<br>
----
----
Next time the Agent contacts the server, it is notified of the package, and sometime later should be deployed! As usual, you can manually launch the agent to force the update.
Next time the Agent contacts the server, it is notified of the package, and sometime later should be deployed! As usual, you can manually launch the agent to force the update.
See section 8.1 of the help file to understand how download works
See section 8.1 of the help file to understand how download works.