Difference between revisions of "Talk:OCS Inventory Tools"
From SME Server
Jump to navigationJump to searchm |
(Fixing initial msg about ipdiscover) |
||
| Line 1: | Line 1: | ||
| − | We need to confirm that ipdiscover works when the smeserver is the forced client | + | We need to confirm that ipdiscover works when the smeserver is the forced client. |
| − | + | I Tried the following: | |
| − | |||
| − | |||
ipdiscover eth0 10 | ipdiscover eth0 10 | ||
{{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}} | {{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}} | ||
| Line 13: | Line 11: | ||
<H><I>192.168.0.254</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00254.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> | </IPDISCOVER> | ||
| − | Sounds like it's working for me... | + | 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 | Cool34000 | ||
---- | ---- | ||
| − | |||
| − | |||
Draft steps for deployment, it works !! | Draft steps for deployment, it works !! | ||
| Line 53: | Line 52: | ||
stephen | stephen | ||
---- | ---- | ||
| − | |||
Thank you so much for your help Stefen. | Thank you so much for your help Stefen. | ||
Revision as of 12:41, 7 November 2007
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
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
