Talk:OCS Inventory Tools

thanks for the new rpm, deploy > build now works (uploads to downloads)

deploy > activate fails, currently you can't see www/download, you need to edit the httpd fragment. eg.

Alias /download /opt/inventory/ocs/download
<Directory /opt/inventory/ocs/download>
   Options None
   Options +Indexes
   Options +Includes
   AllowOverride None
   order deny,allow
   deny from all
   allow from 127.0.0.1 192.168.35.0/255.255.255.0
 php_admin_value open_basedir /opt/inventory/ocs:/tmp
</Directory>

now you can see it but activate still fails !@#$

Snoble 01:21, 5 November 2007 (MST)

I also get stuck when I try to activate a package: I'm getting warnings about information files and fragments not being present at https://myserver/download/123456789 and at http://myserver/download/123456789

Of course files and fragments are at the good place and reachable...

This is really weird because according to the guide.pdf, files can be placed on any https capable apache server in ./download/123456789 and accessible at https://fileserver/download/123456789

I get a 403 error page at http://myserver/download but if I put an empty index.html file inside the folder and I can see now a blank page at http://myserver/download

So this folder is now reachable for sure with your fixes...

There is also this section about "https certificate" in guide.pdf at sections 8.2 & 8.8.1. I didn't create the needed cacert.pem file, did you?

I've successfully tested ipdiscover. As I only have 3 computers for testings, I forced ipdiscover on 2 computer and they discovered my router and my Wifi AP :-)

I've added back stephen's improvements (ocs ng setions)

Cool34000

I've added force discover on the server, ran another inventory and it found nothing else the guide isn't very clear, if you can document this in a few steps it may help

i get the same error on deply > activate I haven't copy the certificate yet, I don't think that is needed until the next step of deploying to the PC

Snoble 13:43, 5 November 2007 (MST)

OK, I will document the ipdiscover with a few pics ASAP... Anyway, this is pretty easy: force ipdiscover behaviour in OCS web console for a computer (force scan on it's own IP)

Manually launch an inventory on the computer you've set, this will force the ipdiscovery. A few min later it was done!

By the way, I've made a quick list of needed Perl modules... I just gathered needed modules in OCS Server+Agent+IPDiscovery readmes. It should work on all SME versions:

yum install perl'(Apache::DBI)'
yum install perl'(Archive::Tar)'
yum install perl'(Compress::Zlib)'
yum install perl'(Crypt::OpenSSL::Bignum)'
yum install perl'(Crypt::OpenSSL::RSA)'
yum install perl'(DBI)'
yum install perl'(DBD::Mysql)'
yum install perl'(Digest::MD5)'
yum install perl'(IO::Socket::SSL)'
yum install perl'(IO::Zlib)'
yum install perl'(Mail::DomainKeys)'
yum install perl'(MIME::Lite)'
yum install perl'(Net::IP)'
yum install perl'(Net::Jabber)'
yum install perl'(Net::SSLeay)'
yum install perl'(Net::XMPP)'
yum install perl'(SOAP::Lite)'
yum install perl'(LWP)'
yum install perl'(XML::Simple)'
yum install perl'(XML::Stream)'

Some RPMs are not in standard repos, I used DAG to find them... I don't know if this can be useful to anyone.

Cool34000