Difference between revisions of "Talk:OCS Inventory Tools"
(→rename page: checked, ok for me) |
|||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===ipdiscover bug=== | ===ipdiscover bug=== | ||
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. |
Revision as of 01:06, 8 November 2007
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
When you delete a package, ocs complains, but it deletes the files anyway, document later
Stefen
The only way I was able to reproduce an error on package deletion is when I refreshed the page (as files were removed, I got an error)
Could you be more clear on this bug?
Cool34000
New RPM version (1-5)
Changelog:
=> Deployment fixed!
Update ASAP and read the new deployment section.
By the way, I had some problem using the default certificate untill I fixed DNS issues (I use NO-IP and this free service don't allow wildcards!)
This ends with some errors in Apache log file:
[warn] RSA server certificate CommonName (CN) `servername.mydomain.no-ip.com' does NOT match server name!?
Here's how I fixed my problem:
config setprop modSSL CommonName mydomain.no-ip.com # It would be www.mydomain.no-ip.com if NO-IP had allowed wildcards like dyndns services) expand-template /home/e-smith/ssl.crt/crt 2> /dev/null signal-event domain-modify signal-event email-update
Should we move this to the doc or somewhere else?
Cool34000
I get this with CAcert, I think it is just a warning, and we can ignore it
stephen