Changes

Jump to navigation Jump to search
1,381 bytes added ,  01:57, 11 November 2007
Line 1: Line 1: −
see history for old info !
+
=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.
 +
 +
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
 
----
 
----
   −
Thanks for cleaning this up!
+
=wiki page=
 +
 
 +
 
   −
Your comments are on my todo's list ;-)
+
==5.3.2 Deployment menu==
   −
Can you confirm that ipdiscover works on your install?
+
there must be a lot of ways this could be used,
 +
why make everyone think of them themselves when it could be spelled out
   −
As I used 3 PCs to get ipdiscover info, I didn't test only with SME enabled.
+
this could be a new page, [[:Application deployment]]
   −
Try the following:
+
this could include other ways to deploy, eg using netlogon.bat
ipdiscover eth0 10
  −
{{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}}
     −
Here's what I got on my server:
+
others can work on this cool34000 has done enough
<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
+
Stefen
 
----
 
----
ipdiscover looks to be working here also, maybe it was operator error ?
+
Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
   −
Draft steps for deployment
+
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)
   −
Installed a cacert certificate eg. http://wiki.contribs.org/Custom_CA_Certificate
+
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.
  copy the domain.crt from cacert to cacert.pem in the client ocs folder
+
  @echo off
(this is the public key right ??)
+
\\server\share\mydomain.com.exe /np /debug /tag:my_tag
 +
That's all!
   −
deploying => Activate => activate package
+
Of course, more can be done...
complains that the directory and info files don't exist,
  −
I think we should just ignore the activate error, the files are visible from clients
     −
deployed a file, optional, run a client update and it is now aware of the update
+
*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.
   −
in => Package activation
+
If someone can take some time to document that, it would be nice!
when you delete a package, ocs complains, but it deletes the files anyway, document later
+
 
ERROR: Can't delete directory /opt/inventory/ocs/download/1194356189
+
Cool34000
stephen
   
----
 
----
 +
 +
==glpi==
 +
 +
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