Talk:OCS Inventory Tools
known bugs
There are still some bugs in this RPM... Help us to fix them!
ipdiscover bug
ipdiscover and SME
IpDiscover is not working on SME. We know that. Please use a different client to ipdiscover your networks.
I've opened a thread on OCS forum.
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.
We need to lower rights on this file (should not be visible to anyone)
Also a problem, the script cannot be executed. I try to add script handler for .pl but it didn't worked...
www/ocs/install.php bugs
New doc, enjoy!
=> Do we really need an admin account? Why can't we use ocs' one?
If you encounter any problem with files insertion, try setting the global max_allowed_packet mysql value to at least 2M in your server config file.
How to set this value for ocs only?
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
future RPM
What will be fixed in next RPM release...
MaxUpload
Default value will raise to 100M (OpenOffice ready)
secure install.php
Need to modify the existing template-metadata for dbconfig.inc.php:
UID="root" GID="www" PERMS=0440
www/ocs/install.php is no more possible. To use install.php, you have to chmod to 460 this file. Else, you'll get this message:
ERROR: can't write in directory (on dbconfig.inc.php), please set the required rights in order to install ocsinventory (you should remove the write mode after the installation is successfull)
After using
signal-event domain modify
perms will be reseted to read value and password reapplyied :-)
I think this close the problem.
dependencies
just supply the .tar.gz
add all the dependacies in smeserver-inventory-tools to make sure the user has installed them
wiki page
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!
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
In fact, that's the way I always used OCS... I don't like to install a service when it's not needed...
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)
- ...Read the guide!
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.
glpi
someone who uses this may like to add some more information on how to use it, some link to more docs at least
