498
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − see history for old info !+ + + + + − rpm -3 installs fine, deploy=>builds ok, /downloads is accessible+ − a minor point, I suggest you add /downloads to accounts db as a url next rpm+ + + − deploying => + + + + + + + + − + − i installed a cacert certificate as per the contribs howto, + − + − copied the domain.crt to cacert.pem in the client ocs folder − deployed a file, run a client update and it is now aware of the update, so we now wait+ + − impatient people see http://forums.ocsinventory-ng.org/viewtopic.php?id=1079+ − stephen+ − ---- − Thanks for cleaning this up!+ − Your comments are on my todo's list ;-)+ + + − Can you confirm that ipdiscover works on your install?+ − As I used 3 PCs to get ipdiscover info, I didn't test only with SME enabled. − Try the following: − ipdiscover eth0 10 − {{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}} − Here's what I got on my server:+ − <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> − <H><I>192.168.0.254</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00254.mydomain.com</N></H> − </IPDISCOVER> − Sounds like it's working for me... − Cool34000+ − ----+ − looks to be working here also, maybe it was operator error ? − [root@kiwi more]# ipdiscover eth0 10 − <IPDISCOVER> − <H><I>192.168.35.2</I><M>00:0b:ad:a0:0a:2d</M><N>pc-00002.dom.net</N></H> − <H><I>192.168.35.3</I><M>00:0d:88:44:fc:fd</M><N>ap.dom.net</N></H> − <H><I>192.168.35.233</I><M>00:0f:20:fd:e1:e7</M><N>pc-00233.dom.net</N></H> − <H><I>192.168.35.242</I><M>00:0e:08:da:e7:e1</M><N>pc-00242.dom.net</N></H> − </IPDISCOVER> − prompt client to call home+ − ocsinventory-client.pl -debug − DOWNLOAD: <?xml version='1.0' encoding='ISO-8859-1'?>+ − <REPLY> − <OPTION> − <NAME>IPDISCOVER</NAME> − <PARAM IPDISC_LAT="100">192.168.35.0</PARAM> − </OPTION> − <OPTION> − <NAME>DOWNLOAD</NAME> − <PARAM FRAG_LATENCY="10" PERIOD_LATENCY="0" TIMEOUT="30" ON="1" TYPE="CONF" CYCLE_LATENCY="60" PERIOD_LENGTH="10" /> − <PARAM ID="1194355263" CERT_PATH="INSTALL_PATH" PACK_LOC="2321.net/download" CERT_FILE="INSTALL_PATH/cacert.pem" TYPE="PACK" NFO_LOC="2321.net/download" /> − <PARAM ID="1194356189" CERT_PATH="INSTALL_PATH" PACK_LOC="2321.net/download" CERT_FILE="INSTALL_PATH/cacert.pem" TYPE="PACK" INFO_LOC="2321.net/download" /> − </OPTION> − <RESPONSE>SEND</RESPONSE> − <PROLOG_FREQ>24</PROLOG_FREQ> − </REPLY> − − DOWNLOAD: Writing config file. − DOWNLOAD: Retrieving info file for 1194355263 − DOWNLOAD: Initialize ssl layer... − DOWNLOAD: Connect to server: 2321.net/download... − DOWNLOAD: Starting SSL connection... − 28948: callback: ssl connect! + − deploy stalls, with this error/warning on server+ − # tail /var/log/httpd/error_log + − could not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.5/XML/SAX+ − − hide warning ? with − touch /usr/lib/perl5/vendor_perl/5.8.5/XML/SAX/ParserDetails.ini − still waiting...+ − ---- − − We need to build this file! − touch /usr/lib/perl5/vendor_perl/5.8.5/XML/SAX/ParserDetails.ini+ − perl -MXML::SAX -e "XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()" + − chmod 0444 /usr/lib/perl5/vendor_perl/5.8.5/XML/SAX/ParserDetails.ini + + − Here's the content of generated file:+ − [XML::SAX::PurePerl] − http://xml.org/sax/features/namespaces = 1 − No more warning! :-D+ + + + + + + + +
Talk:OCS Inventory Tools (view source)
Revision as of 01:57, 11 November 2007
, 01:57, 11 November 2007→ipdiscover bug
=known bugs=
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.
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.
First thing to do is to change the password in this file...
...
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 think we should just ignore the activate error, the files are visible from clients
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!
Cool34000
----
==www/ocs/install.php bugs==
A problem was found in the default imported database. This ends with some ''alter'' errors. This can be fixed by refreshing the web page.
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''!
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
----
=wiki page=
==5.3.2 Deployment menu==
there must be a lot of ways this could be used,
why make everyone think of them themselves when it could be spelled out
this could be a new page, [[:Application deployment]]
this could include other ways to deploy, eg using netlogon.bat
others can work on this cool34000 has done enough
Stefen
----
Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
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)
I found this [http://perl-xml.sourceforge.net/faq/#parserdetails.ini link]
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!
Of course, more can be done...
*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!
Cool34000
Cool34000
----
----
==glpi==
someone who uses this may like to add some more information on how to use it, some link to more docs at least