Difference between revisions of "Talk:OCS Inventory Tools"

From SME Server

Latest revision as of 00: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
@@ Line 22: / Line 26: @@
 ==www/ocs/install.php bugs==
-Quick howto for ocsagent.exe MySQL importation. BETA
+A problem was found in the default imported database. This ends with some ''alter'' errors. This can be fixed by refreshing the web page.
-First, you need to import the file in the database. Go to www/ocs/install.php and relaunch the install (this is harmless) '''with an mysql admin account''' (I use phpmyadmin so this is ''admin'')
+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''!
-If you get a warning, refresh and you should see a successful import. ''ocsagent.exe'' is now in the database. Actually, to allow download, OCS need to authenticate... That's why this file is in the database in binary code!
+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!
-Once imported, the file should be deletable... But I need to verify that. Next time the agent version changes, then an update will be needed!
+Help needed!
-So, file is imported '''but the install reseted password to 'ocs''''
+Cool34000
-You need to apply changes:
- signal-event domain-modify
-=> Why  do we need really an admin account? Why can't we use ocs?
- 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?
-=> install.php is needed, as you now know. But the file can be renamed or secured when not needed ;-)
 ----
-Here's 3 screenshot already taken that I will use for the article when all of this will be clear.
+=wiki page=
-Install.php
-[[Image:OCS-installphp.png]]<br>
-----
-Default MaxUpload can be seen here & ocsagent.exe not present
-[[Image:OCS-installphp-warning.png]]<br>
-----
-ocsagent.exe present - successful import
-[[Image:OCS-installphp-ocsagent.png]]<br>
-----
-=future RPM=
-What will be fixed in next RPM release...
-==MaxUpload==
+==5.3.2 Deployment menu==
-Default value will raise to 100M (OpenOffice ready)
-==/download==
+there must be a lot of ways this could be used,
-Now that we know that the activation warning can be skipped, can we delete in ocs Apache template:
+why make everyone think of them themselves when it could be spelled out
- <Directory /opt/inventory/ocs/download>
-   Options None
- -  Options +Indexes
- -  Options +Includes
-   AllowOverride None
-   order deny,allow
-   deny from all
-   allow from { $localAccess }
-   php_admin_value open_basedir /opt/inventory/ocs/download:/tmp
- </Directory>
-This will disallow files from being viewable (but still accessible for ocs?)
-This would be more secure if it works! Need to test that!
+this could be a new page, [[:Application deployment]]
-==dependencies==
+this could include other ways to deploy, eg using netlogon.bat
-change the install method to install the  perl dependencies that are available from existing repos.
-Then you can reduce the number of perl rpms in your download the less you are responsible for the better
+others can work on this cool34000 has done enough
- yum localinstall smeserver-inventory-tools* --enablerepo=dag --enablerepo=extras
+Stefen
-stephen
 ----
-Is this just a doc issue or do I need to change the Requires?  DOCUMENTATION, CHANGE THE INSTALL COMMAND
+Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
-All needed deps are should be in ''extras'' and mostly in ''dag''
+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)
-Here's the actual list of Requires in the .spec file (edit if 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.
-  - Requires:  e-smith-base  SN - NOT NEEDED IF YOU HAVE BELOW
+  @echo off
-  - Requires:  e-smith-release >= 7              # Note: SME >8 may need a fix if it uses mod_perl >=2  (could be good to test and be ready!)
+  \\server\share\mydomain.com.exe /np /debug /tag:my_tag
-  + DON'T WE HAVE SMESERVER-RELEASE >=7 ? CHECK, rpm -q ...
+That's all!
- Requires:  mod_perl >= 1.99_16-4
- Requires:  monitor-edid >= 1.11-1            #ocs Agent
- Requires:  ocsinventory-ipdiscover >= 1.01-2 #ocs Agent => will remove this one as it's already a dependency of ocsinventory-agent
- Requires:  ocsinventory-agent >= 0.0.6-1     #ocs Agent
-  Requires:  perl-Apache-DBI >= 0.9901-2.2
-  Requires:  perl-Archive-Tar >= 1.23-3.99_2
- Requires:  perl-Compress-Zlib >= 1.42-1
- Requires:  perl-Crypt-OpenSSL-Bignum >= 0.03-1.2
- Requires:  perl-Crypt-OpenSSL-RSA >= 0.21-1.2
- Requires:  perl-IO-Socket-SSL >= 1.01-1
- Requires:  perl-IO-Zlib >= 1.04-2
- Requires:  perl-Mail-DomainKeys >= 0.21-2
- Requires:  perl-MIME-Lite >= 3.01-2.2
- Requires:  perl-Net-IP >= 1.23-1
- Requires:  perl-Net-Jabber >= 2.0-1.2
- Requires:  perl-Net-XMPP >= 1.0-1.2
- Requires:  perl-SOAP-Lite >= 0.69-1
- Requires:  perl-XML-SAX >= -0.12-7
- Requires:  perl-XML-Simple >= 2.14-4
- Requires:  perl-XML-Stream >= 1.22-1.2
- Conflicts: smeserver-ocs_inventory_ng  # old RPM version, here for safety!
- Conflicts: smeserver-glpi              # old RPM version, here for safety!
-=> fresh 7.1 final CD install - no updates
+Of course, more can be done...
-=> dag added to yum repos (disabled and invisible)
+*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.
-=> removed all perl dependencies:
+If someone can take some time to document that, it would be nice!
-A lot are missing... The RPM installed but I got an error trying to contact the server!
 Cool34000
 ----
-Add the dependacies and use the new yum command with --enablerepo.....
+==glpi==
+someone who uses this may like to add some more information on how to  use it, some link to more docs at least

Difference between revisions of "Talk:OCS Inventory Tools"

Latest revision as of 00: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