Talk:OCS Inventory Tools
ipdiscover bug
We need to confirm that ipdiscover works when the smeserver is the forced client.
I Tried the following:
ipdiscover eth0 10
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
deployment howto
Draft steps for deployment, it works !!
SSL Certificates Installed a SSL certificate eg. http://wiki.contribs.org/Custom_CA_Certificate below fixes the ssl errors as per http://alufis35.uv.es/OCS-Inventory-Package-Deployment.html this is common, it could be automated, but should we be trusted, probably not ?
wget http://www.cacert.org/certs/root.crt cp root.crt /home/e-smith/ssl.crt/cacert.pem add fragment to httpd.conf { #/etc/e-smith/templates/etc/httpd/conf/httpd.conf/35SSL10SSLCACertificateFile if (-f '/home/e-smith/ssl.crt/cacert.pem') { $OUT = "SSLCACertificateFile /home/e-smith/ssl.crt/cacert.pem"; } }
copy cacert.pem to the client ocs folder
deploying => Activate => activate package complains that the directory and info files don't exist, Just ignore the activate error, the files are visible from clients deployed a file, optional, run a client update, it should show as notified in ocs
in => Package activation when you delete a package, ocs complains, but it deletes the files anyway, document later
links http://alufis35.uv.es/OCS-Deployment-Tips-and-tricks.html
stephen
Thank you so much for your help Stefen.
I'm so happy that deployment works!!! That's really great news!
A solution was also given on the forum: http://forums.contribs.org/index.php?topic=37359.msg178135#msg178135
It looks easier (no need of CACert). What do you think of the other solution?
Cool34
copying the existing .crt didn't work for me, try both ways and find out what works for you, using the existing cert would be simpler, the windows ocs update command produces a good log file in the ocs directory showing any SSL errors
setting up a CA Certificate doesn't take long and is 'a good idea'
stephen
ParserDetails.ini
http://bugs.contribs.org/show_bug.cgi?id=3525#c2
charlie said just make it (as you now do), so lets close the open bug
