Difference between revisions of "Talk:OCS Inventory Tools"

From SME Server

Jump to navigation Jump to search

Latest revision as of 01:57, 11 November 2007

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 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

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

others can work on this cool34000 has done enough

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.

@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)
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

someone who uses this may like to add some more information on how to use it, some link to more docs at least

Retrieved from "https://wiki.koozali.org/index.php?title=Talk:OCS_Inventory_Tools&oldid=6272"

@@ Line 2: / Line 2: @@
 There are still some bugs in this RPM... Help us to fix them!
 ==ipdiscover bug==
-We need to confirm that ipdiscover works when the smeserver is the forced client.
+===ipdiscover on SME===
+IpDiscover is not working on SME. Please use another agent to ipdiscover your networks at the moment.
-I Tried the following:
+I've opened a [http://forums.ocsinventory-ng.org/viewtopic.php?pid=5684#p5684 thread] on OCS forum.
- ipdiscover eth0 10
-{{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}}
-Here's what I got on my server:
+Let's hope the next version will come out soon!
- <IPDISCOVER>
+===ipdiscover-util.pl===
- <H><I>192.168.0.100</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00100.mydomain.com</N></H>
+This script used by the web interface do not seem to work too.
- <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...
+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
 ----
-==deployment deletion bug==
-When you delete a package, ocs complains, but it deletes the files anyway, document later
-Stefen
+==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.
-The only way I was able to reproduce an error on package deletion is when I refreshed the page (as files were already removed, I got an error)
-Could you be more clear on this bug? How did it happened?
+I took a look on ocsweb database with phpmyadmin before and after using install.php
-Cool34000
+I noticed that a lot of tables' ''engine type'' were ''MyISAM'' and after using install.php their type was ''InnoDB''!
-----
-add a package, deploy > activate > click on the red X
+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!
- ERROR: Can't delete directory /opt/inventory/ocs/download/1194511477
-I have documented that you can ignore the error, maybe i should say if you see the error you can ignore?
+Help needed!
-stephen
+Cool34000
 ----
-=future RPM=
-What will be fixed in next RPM release...
-==upload size limit==
- Max allowed packet value is locked at 10M by default on SME.
-Let's delete the mysql custom-template in the future RPM!
-We can modify this value to only affect the ocs directory.
+=wiki page=
-Add the following lines to Apache template:
- <Directory /opt/inventory/ocs/ocsreports>
- ..
- php_admin_value post_max_size $ocs{'MaxUpload'}
- php_admin_value upload_max_filesize $ocs{'MaxUpload'}
-Apply changes:
- config setprop ocs MaxUpload 50M
- expand-template /etc/httpd/conf/httpd.conf
- /etc/init.d/httpd-e-smith condrestart
-==aliases==
-Future RPM will allow to add aliases using 'URL' value to ocs and glpi
- {
-   if (exists $foo{'URL'})
-   { $OUT .= "Alias  /$foo{'URL'}  /opt/foo\n"; }
- }
-==RPM is not a chatroom==
+==5.3.2 Deployment menu==
-Less chat in the install output, just say look at the wiki page, + renamed wiki page
-==events==
+there must be a lot of ways this could be used,
-Don't use signal-event my-own-event: just give all the commands, or use an existing one, we could use domain-modify
+why make everyone think of them themselves when it could be spelled out
-Here's the future createlinks perl script, this is just all we need, I will remove the ones already in place in ''domain-modify'' (i.e. apache should already be expanded+restarted):
+this could be a new page, [[:Application deployment]]
- #!/usr/bin/perl -w
- use esmith::Build::CreateLinks qw(:all);
- # Templates to adjust
- templates2events("/etc/e-smith/sql/init/80ocs_mysql.sql",          qw(domain-modify post-upgrade ));
- templates2events("/etc/e-smith/sql/init/82glpi_mysql.sql",         qw(domain-modify post-upgrade ));
- templates2events("/etc/e-smith/sql/init/84ocs-glpi.sql",           qw(domain-modify post-upgrade ));
- templates2events("/etc/httpd/conf/httpd.conf",                     qw(domain-modify post-upgrade ));
- templates2events("/etc/ocsinventory-agent/ocsinv.conf",            qw(domain-modify post-upgrade ));
- templates2events("/opt/inventory/glpi/config/config_db.php",       qw(domain-modify post-upgrade ));
- templates2events("/opt/inventory/ocs/ocsreports/dbconfig.inc.php", qw(domain-modify post-upgrade ));
- # Services to restart
- safe_symlink("restart", "root/etc/e-smith/events/ocsglpi-update/services2adjust/httpd-e-smith");
- safe_symlink("start",   "root/etc/e-smith/events/ocsglpi-update/services2adjust/mysql.init");
-==save bandwidth==
+this could include other ways to deploy, eg using netlogon.bat
-Create a seperate RPM with the ''guide.pdf'' and make it a dependency of the main RPM. No need to touch the ocs.tar.qz
-==MySQL init scripts ==
+others can work on this cool34000 has done enough
- /etc/e-smith/sql/init/* should only be used one to create the db table, then it is deleted
- httpd.conf and php.ini are in standard events (and are we still changing php.ini?)
- which only leaves three fragments to document in the rare case that something changes
 Stefen
 ----
-Yes, all that goes in /etc/e-smith/sql/init/ is dropped after a successful importation. I know that, I use it this way:
+Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
-*3 templates to dynamically create the DB+User+Password and change OCS' password in GLPI' database. These templates are harmless if re-expanded...
-*2 databases (one for ocs, one for glpi). They are imported ONLY ON NEW INSTALL. These 2 databases are dropped once imported (no need to keep them!)... It also allows me to import the right GLPI database according to ''$LANG''
-So when the RPM runs:
-* 3 files loaded on RPM updates
-* 5 files loaded on RPM install
-Take a look on their name when all 5 files are put in /etc/e-smith/sql/init/ once expanded
-Cool3400
-----
-==RPM strcuture==
+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)
-I'm looking at the src.rpm and it needs to work a different way before this will work, looking...
-stephen
+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!
-==dependencies==
+Of course, more can be done...
-OK, you already have them, just need to check on a clean install what is available
-Another thing to do in time is to add all the requires (to perl dependencies) that are available from existing repos.
+*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.
-Then you can reduce the number of perl rpm in your download the less you are responsible for the better
+If someone can take some time to document that, it would be nice!
-stephen
+Cool34000
 ----
-==ocsagent.exe==
+==glpi==
-I'm not sure this is needed, lets delete it from the server and see if it affects anything before removing from the rpm
- it does generate a warning during the web installer but that is irrelevant to us (from dev in ocs forums)
-stephen
+someone who uses this may like to add some more information on how to  use it, some link to more docs at least
-----
-About ''ocsagent.exe'', it doesn't help you when you've installed the Agent, but if you use the standalone OCSLogon.exe to send inventories, the client will not download needed files. This file is needed!
-By the way, we need to document that: next time the Agent version changes, this file needs to be upgraded too!
-Cool34000
-----

Difference between revisions of "Talk:OCS Inventory Tools"

Latest revision as of 01:57, 11 November 2007

Contents

known bugs

ipdiscover bug

ipdiscover on SME

ipdiscover-util.pl

www/ocs/install.php bugs

wiki page

5.3.2 Deployment menu

glpi

Navigation menu

Page actions

Page actions

Personal tools

Koozali SME Server

Recent activities

Koozali resources

Koozali SME Server wiki

Tools

Search