Changes

Jump to navigation Jump to search
1,015 bytes added ,  01:57, 11 November 2007
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.
*Inventory Tools ?
     −
===ipdiscover bug===
+
Let's hope the next version will come out soon!
We need to confirm that ipdiscover works when the smeserver is the forced client.
+
===ipdiscover-util.pl===
 +
This script used by the web interface do not seem to work too.
   −
I Tried the following:
+
First thing to do is to change the password in this file...
  ipdiscover eth0 10
+
...
{{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}}
+
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.
   −
Here's what I got on my server:
+
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>
  −
<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... But IpDiscover discovers nothing when launched by SME OCS' Agent. There must be a problem here!
     −
Windows Agent don't have this problem...
+
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
 
Cool34000
 
----
 
----
===deployment===
  −
new doc added - Enjoy!
  −
in => Package activation
     −
when you delete a package, ocs complains, but it deletes the files anyway, document later
+
=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
   −
===New RPM version (1-5)===
+
others can work on this cool34000 has done enough
Changelog:
     −
=> Deployment fixed!
+
Stefen
 +
----
 +
Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
   −
Update ASAP and read the new deployment section.
+
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)
   −
By the way, I had some problem using the default certificate untill I fixed DNS issues (I use NO-IP and this free service don't allow wildcards!)
+
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!
   −
This ends with some errors in Apache log file:
+
Of course, more can be done...
[warn] RSA server certificate CommonName (CN) `servername.mydomain.no-ip.com' does NOT match server name!?
  −
Here's how I fixed my problem:
  −
config setprop modSSL CommonName mydomain.no-ip.com  # It would be www.mydomain.no-ip.com if NO-IP had allowed wildcards like dyndns services)
  −
expand-template /home/e-smith/ssl.crt/crt 2> /dev/null
  −
signal-event domain-modify
  −
signal-event email-update
     −
Should we move this to the doc or somewhere else?
+
*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
 
----
 
----
   −
I get this with CAcert, I think it is just a warning, and we can ignore it
+
==glpi==
   −
stephen
+
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