Talk:OCS Inventory Tools

We need to confirm that ipdiscover works when the smeserver is the forced client

As I used 3 PCs to get ipdiscover info, I didn't test only with SME enabled.

Try the following:

ipdiscover eth0 10

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

Cool34000

---

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 to httpd.conf
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

stephen

---