Difference between revisions of "Talk:OCS Inventory Tools"

From SME Server
Jump to navigationJump to search
Line 22: Line 22:
  
 
==www/ocs/install.php bugs==
 
==www/ocs/install.php bugs==
''ocsagent.exe'' is not needed if you plan to use the Agent as a service...
+
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'')
 +
 
  
This file allows you to make inventories of computers '''without''' having the Agent installed.
+
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!
  
Once installed in ocs, you can use the standalone executable ''OCSLogon.exe'' to inventory a single computer without having to install the service (better control for logon scripts and think of what you can do with a simple USB key!)
+
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!
  
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'')
+
So, file is imported '''but the install reseted password to 'ocs''''
  
After a 1st warning, refresh and the agent.exe should import itself in mysql database. Not sure about what is does, the only thing I've noticed is that ocsweb's database grows of 1.5MB after this!!! So I guess the file is imported in mysql, this is really strange but it do the job!
+
You need to apply changes:
 +
signal-event domain-modify
  
Once imported, the file should be deletable...
 
  
Forgot this: '''www/ocs/install.php will reset default password to 'ocs' => reapply changes'''
 
signal-event domain-modify ;-)
 
  
I think the 1st error screen can be fixed, maybe with raising the good value, mysql tries to import 1.5MB, this is huge!
+
=> 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?
 +
----
  
 +
Here's 3 screenshot already taken that I will use for the article when all of this will be clear.
  
=> Verified! Here's how it works:
+
Install.php
*rename ocslogon.exe into yourdomain.com.exe
 
*on a computer without the Agent, launch:
 
c:\your_path\yourdomain.com.exe /np /debug /tag
 
*Server sends ocsagent.exe and unzip needed files in c:\ocs-ng
 
*client can inventory himself, then send his inventory.
 
  
 +
[[Image:OCS-installphp.png]]<br>
 
----
 
----
why not just have all the files on the USB key or Disk in the first place ?
+
Default MaxUpload can be seen here & ocsagent.exe not present
But if this is how it works then just document it
+
[[Image:OCS-installphp-warning.png]]<br>
 
+
----
Do we really have use install.php, can you just put the ocsagent.exe in /files.
+
ocsagent.exe present - successful import
I only used it looking for errors long ago,
+
[[Image:OCS-installphp-ocsagent.png]]<br>
install.php probably should be deleted, as the rpm does the setup
 
 
 
stephen
 
 
----
 
----
  

Revision as of 23:10, 9 November 2007

known bugs

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.

I Tried the following:

ipdiscover eth0 10
Important.png Note:
Usage : ipdiscover [iface name] [latency in ms]


Here's what I got on my server:

<IPDISCOVER>
<H>192.168.0.100<M>00:xx:xx:xx:xx:xx</M><N>pc-00100.mydomain.com</N></H>
<H>192.168.0.253<M>00:xx:xx:xx:xx:xx</M><N>pc-00253.mydomain.com</N></H>
<H>192.168.0.254<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...

Cool34000


www/ocs/install.php bugs

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)


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!

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!

So, file is imported but the install reseted password to 'ocs'

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?


Here's 3 screenshot already taken that I will use for the article when all of this will be clear.

Install.php

OCS-installphp.png


Default MaxUpload can be seen here & ocsagent.exe not present File:OCS-installphp-warning.png


ocsagent.exe present - successful import OCS-installphp-ocsagent.png


RPM 1-6

RPM sent, these dependencies are giving me headaches! -> going to bed

- Removed useless MySQL custom-template
- Removed ocsagent.exe and guide.pdf
- Upload limit fixed
- 'MaxUpload' DB entry added to set dynamically max upload file size (default still at 10M)
- Events moved to domain-modify
- 2 new 'url' types added for ocs' virtual locations
- Uninstall script now also deletes new DB values + logs + old inventories
- Improved Apache templates to allow adding aliases for both web interfaces
- RPM runs silently :'(

future RPM

What will be fixed in next RPM release...

MaxUpload

make the default bigger say 100M to allow for OpenOffice

Admin occasionally uploading files to OCS will be OK

dependencies

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

yum localinstall smeserver-inventory-tools* --enablerepo=dag --enablerepo=extras 

stephen


Is this just a doc issue or do I need to change the Requires? DOCUMENTATION, CHANGE THE INSTALL COMMAND

All needed deps are should be in extras and mostly in dag

Here's the actual list of Requires in the .spec file (edit if needed):

 - Requires:  e-smith-base  SN - NOT NEEDED IF YOU HAVE BELOW
 - 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!)
 + DON'T WE HAVE SMESERVER-RELEASE >=7 ? CHECK, rpm -q ...
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

=> dag added to yum repos (disabled and invisible)

=> removed all perl dependencies:

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