498
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: − + − + + Line 14:
Line 15: − + − + + + + Line 26:
Line 30: − + + + − − =new RPM (1-7)= − New RPM uploaded! Wait for miror sync... − − Changelog: − - Fix security issue on dbconfig.inc.php - We now use root:www 440 − - Fix perms on ocsreports folder and ipdiscover-util.pl (750 for both) − - Fix problem while importing ocsagent.exe into MySQL with ocs user − - MaxUpload limit raised to 100M by default (new install only) − Update ASAP! − − ''install.php'' is no more a problem with this new RPM, install.php will not be usable untill security is put back to 660 in ''dbconfig.ini.php'' − − The problem while importing ''ocsagent.exe'' is fixed by setting max_allowed_packet to 2M (this value is not set by default). − − Wiki needs to be updated... Will do the needed modifications later in the evening. − − Enjoy! − − Sylvain − ---- − =future RPM= − ==dependencies== − just supply the .tar.gz − − add all the dependacies in smeserver-inventory-tools to make sure the user has installed them − I didn't use this screenshot finally... Can you delete it? (I don't have the right to do that) − Image:OCS-installphp-warning.png − ==split page== − I'd like to move somethings to a sub page and just show the most likely options − − 4.2.2 ocsagent.exe − − 4.2.3 OcsLogon.exe − − in time, 3.3.1 Old RPMs version − 5.2.1 Modifying default behaviour − Ok, let's do this! Line 85:
Line 53: + − In fact, that's the way I always used OCS... I don't like to install a service when it's not needed...+ + + Line 98:
Line 69: − + + − Didn't document that... Do we really need to? The command line is really simple, then it's the end-user's job to adapt it to his network and needs.+ + + +
Talk:OCS Inventory Tools (view source)
Revision as of 00:57, 11 November 2007
, 00:57, 11 November 2007→ipdiscover bug
There are still some bugs in this RPM... Help us to fix them!
There are still some bugs in this RPM... Help us to fix them!
==ipdiscover bug==
==ipdiscover bug==
===ipdiscover and SME===
===ipdiscover on SME===
IpDiscover is not working on SME. We know that. Please use a different client to ipdiscover your networks.
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.
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===
===ipdiscover-util.pl===
This script used by the web interface do not seem to work too.
This script used by the web interface do not seem to work too.
my $dbhost = 'localhost';
my $dbhost = 'localhost';
my $dbuser = 'ocs';
my $dbuser = 'ocs';
my $dbpwd = 'ocs';
my $dbpwd = 'ocs'; <==
my $db = 'ocsweb';
my $db = 'ocsweb';
my $dbp = '3306';
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.
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...
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==
==www/ocs/install.php bugs==
I took a look on ocsweb database with phpmyadmin before and after using install.php
I took a look on ocsweb database with phpmyadmin before and after using install.php
I noticed that ''engine type'' is MyISAM and after using install.php their type is InnoDB!
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!
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
----
----
=wiki page=
=wiki page=
==5.3.2 Deployment menu==
==5.3.2 Deployment menu==
others can work on this cool34000 has done enough
others can work on this cool34000 has done enough
Stefen
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)
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.
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.
*Install the Agent silently in a script
*Install the Agent silently in a script
*Use GPOs (deploy, install, update)
*Use GPOs (deploy, install, update)
*...Read the guide!
*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
----
==glpi==
==glpi==
someone who uses this may like to add some more information on how to use it, some link to more docs at least
someone who uses this may like to add some more information on how to use it, some link to more docs at least