Changes

Jump to navigation Jump to search
Line 1: Line 1: −
===rename page===
+
=known bugs=
to describe the functions provides
+
There are still some bugs in this RPM... Help us to fix them!
 +
==ipdiscover bug==
 +
===ipdiscover on SME===
 +
IpDiscover is not working on SME. Please use another agent to ipdiscover your networks at the moment.
   −
Inventory and Deployment ?
+
I've opened a [http://forums.ocsinventory-ng.org/viewtopic.php?pid=5684#p5684 thread] on OCS forum.
    +
Let's hope the next version will come out soon!
 +
===ipdiscover-util.pl===
 +
This script used by the web interface do not seem to work too.
   −
===ipdiscover bug===
+
First thing to do is to change the password in this file...
We need to confirm that ipdiscover works when the smeserver is the forced client.
+
...
 +
my $dbhost = 'localhost';
 +
my $dbuser = 'ocs';
 +
my $dbpwd = 'ocs'; <==
 +
my $db = 'ocsweb';
 +
my $dbp = '3306';
 +
The password should be dynamical as this is a perl script. We need to use esmith::ConfigDB or something else to retrieve this value... I was unable to handle that.
   −
I Tried the following:
+
Also a problem, the script cannot be executed. I try to add script handler for .pl but it didn't worked... Not sure about how this is working, if someone can help, please do!
ipdiscover eth0 10
  −
{{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}}
     −
Here's what I got on my server:
+
Cool34000
<IPDISCOVER>
+
----
<H><I>192.168.0.100</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00100.mydomain.com</N></H>
+
 
<H><I>192.168.0.253</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00253.mydomain.com</N></H>
+
==www/ocs/install.php bugs==
<H><I>192.168.0.254</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00254.mydomain.com</N></H>
+
A problem was found in the default imported database. This ends with some ''alter'' errors. This can be fixed by refreshing the web page.
</IPDISCOVER>
+
 
Sounds like it's working for me... But IpDiscover discovers nothing when launched by SME OCS' Agent. There must be a problem here!
+
I took a look on ocsweb database with phpmyadmin before and after using install.php
 +
 
 +
I noticed that a lot of tables' ''engine type'' were ''MyISAM'' and after using install.php their type was ''InnoDB''!
   −
Windows Agent don't have this problem...
+
So I tried to export a new database (this time with extended parameters), but this new database don't import in ocsweb database: it ends with errors trying to create the 1st table!
    +
Help needed!
    
Cool34000
 
Cool34000
 
----
 
----
===deployment howto===
  −
Draft steps for deployment, it works !!
     −
SSL Certificates
+
=wiki page=
Installed a SSL certificate eg. http://wiki.contribs.org/Custom_CA_Certificate
+
 
  −
below fixes the ssl errors as per http://alufis35.uv.es/OCS-Inventory-Package-Deployment.html
  −
this is common, it could be automated, but should we be trusted, probably not ?
     −
wget http://www.cacert.org/certs/root.crt
  −
cp root.crt /home/e-smith/ssl.crt/cacert.pem
  −
add fragment to httpd.conf
  −
{
  −
    #/etc/e-smith/templates/etc/httpd/conf/httpd.conf/35SSL10SSLCACertificateFile
  −
    if (-f '/home/e-smith/ssl.crt/cacert.pem')
  −
    { $OUT = "SSLCACertificateFile /home/e-smith/ssl.crt/cacert.pem"; }
  −
}
     −
copy cacert.pem to the client ocs folder
+
==5.3.2 Deployment menu==
   −
deploying => Activate => activate package
+
there must be a lot of ways this could be used,  
complains that the directory and info files don't exist,
+
why make everyone think of them themselves when it could be spelled out
Just ignore the activate error, the files are visible from clients
  −
 
  −
deployed a file, optional, run a client update, it should show as notified in ocs
     −
in => Package activation
+
this could be a new page, [[:Application deployment]]
when you delete a package, ocs complains, but it deletes the files anyway, document later
      +
this could include other ways to deploy, eg using netlogon.bat
   −
links
+
others can work on this cool34000 has done enough
http://alufis35.uv.es/OCS-Deployment-Tips-and-tricks.html
     −
stephen
+
Stefen
 
----
 
----
Thank you so much for your help Stefen.
+
Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
   −
I'm so happy that deployment works!!! That's really great news!
+
I don't like to install a service when it's not needed, so I use the standalone executable. I also don't use OCS deployment feature (I'm using GPOs for that)
    +
It is so fast to use against the need of installing the Agent: put OcsLogon.exe in a share folder and simply launch it with a one command line batch script each time a session is opened.
 +
@echo off
 +
\\server\share\mydomain.com.exe /np /debug /tag:my_tag
 +
That's all!
   −
A solution was also given on the forum: http://forums.contribs.org/index.php?topic=37359.msg178135#msg178135
+
Of course, more can be done...
   −
It looks easier (no need of CACert). What do you think of the other solution?
+
*Install the Agent silently in a script
 +
*Use GPOs (deploy, install, update)
 +
*Create your own ''ocsagent.exe''
 +
People need to read the guide! It's well documented.
    +
If someone can take some time to document that, it would be nice!
   −
Cool34
+
Cool34000
 
----
 
----
   −
copying the existing .crt didn't work for me, try both ways and find out what works for you,
+
==glpi==
using the existing cert would be simpler, the windows ocs update command produces a good log file in the ocs directory showing any SSL errors
  −
 
  −
setting up a CA Certificate doesn't take long and is 'a good idea'
  −
 
  −
stephen
  −
----
  −
===ParserDetails.ini===
  −
http://bugs.contribs.org/show_bug.cgi?id=3525#c2
     −
charlie said just make it (as you now do), so lets close the open bug
+
someone who uses this may like to add some more information on how to  use it, some link to more docs at least
498

edits

Navigation menu