Difference between revisions of "Talk:OCS Inventory Tools"
(→new RPM (1-7): delete) |
|||
Line 31: | Line 31: | ||
Cool34000 | Cool34000 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
Revision as of 23:23, 10 November 2007
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.
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
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 engine type is MyISAM and after using install.php their type is 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!
Cool34000
wiki page
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.
sg ---
@echo off \\server\share\mydomain.com.exe /np /debug /tag:my_tag
that's what we need to know,
with this method does deploy work, where does clients cacert.pem go
if you can install cacert.pm to netlogon.bat then admin doesn't need to visit clients at all,
sn
Yes, those kind of answer are in the manual...
Take a look on the history, I'm fighting with install.php that you want to remove since the begining :D
You can integrate a certificate in ocsagent.exe... But you have to download the packager on their website to create your own ocsagent.exe
That's in the doc ;-)
As I never tested that, it's not documented (don't like to document something I don't know!) I'll give it a try and add that to the article.
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