Changes

Jump to navigation Jump to search
102 bytes added ,  20:24, 10 May 2021
m
Line 1: Line 1: −
 
+
{{Languages}}
 
==Maintainer==
 
==Maintainer==
 
[mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]]
 
[mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]]
 +
===Version===
 +
{{#smeversion: smeserver-ocsinventory }}
    
==HowTO==
 
==HowTO==
Line 67: Line 69:  
====for sme9====
 
====for sme9====
 
  yum install ocsinventory-agent ocsinventory-ipdiscover --enablerepo=remi-ocsinventory
 
  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
Line 122: Line 124:  
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>
 
----
 
----
Line 148: Line 150:  
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  
Line 194: Line 196:  
[[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>
 
----
 
----
Line 244: Line 246:  
----
 
----
   −
====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.'''
Line 252: Line 254:  
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>
 
----
 
----
Line 288: Line 290:       −
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>
 
----
 
----
Line 299: Line 301:  
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.
     
3,054

edits

Navigation menu