Difference between revisions of "Talk:OCS Inventory Tools"

From SME Server
Jump to navigationJump to search
(New RPM -5)
(New RPM -5 released)
Line 36: Line 36:
 
charlie said just make it ([http://bugs.contribs.org/show_bug.cgi?id=3464 as you now do]), so lets close opened bugs
 
charlie said just make it ([http://bugs.contribs.org/show_bug.cgi?id=3464 as you now do]), so lets close opened bugs
  
===Next RPM version===
+
===New RPM version (1-5)===
Quick sumarry of what will change on the next release...
+
Changelog:  
====New Apache template====
 
As suggested by Stefen:
 
  
Content of '''''/etc/e-smith/templates/etc/httpd/conf/httpd.conf/35SSL10SSLCACertificateFile'''''
+
=> Deployment fixed!
 
# OCS Inventory NG Certificate
 
{
 
    if (-f '/home/e-smith/ssl.crt/cacert.pem')
 
      { $OUT = "SSLCACertificateFile /home/e-smith/ssl.crt/cacert.pem"; }
 
    else
 
      { $OUT = "# File /home/e-smith/ssl.crt/cacert.pem not present, deployment will not be possible"; }
 
}
 
 
====Specification File====
 
I've added following code in the '''''.spec''''' file in the '''%post''' section
 
if [ ! -e /home/e-smith/ssl.crt/cacert.pem ]; then
 
  cp /home/e-smith/ssl.crt/$SRVNAME.$DOMAIN.crt /home/e-smith/ssl.crt/cacert.pem
 
fi
 
''$SRVNAME'' and ''$DOMAIN'' are already gathered with following code in the '''''.spec''''' file:
 
DOMAIN=$(/sbin/e-smith/db configuration get DomainName)
 
SRVNAME=$(/sbin/e-smith/db configuration get SystemName)
 
  
By the way, I had some problem using the certificate untill I fixed DNS issues (I use NO-IP and this free service don't allow wildcards!)
+
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:
 
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!?
 
  [warn] RSA server certificate CommonName (CN) `servername.mydomain.no-ip.com' does NOT match server name!?
 
Here's how I fixed my problem:
 
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)
+
  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
 
  expand-template /home/e-smith/ssl.crt/crt 2> /dev/null
 
  signal-event domain-modify
 
  signal-event domain-modify
 
  signal-event email-update
 
  signal-event email-update
 
 
{{Note box|I have some problem uploading the new release (1-5) at contribs.org right now but the RPM is ready...}}
 
  
  
 
Cool34000
 
Cool34000
 
----
 
----

Revision as of 01:01, 8 November 2007

rename page

to describe the functions provides

Inventory and Deployment ?


ipdiscover bug

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

I Tried the following:

ipdiscover eth0 10
Important.png 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... 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

new doc added - Enjoy!

in => Package activation

when you delete a package, ocs complains, but it deletes the files anyway, document later

ParserDetails.ini

http://bugs.contribs.org/show_bug.cgi?id=3525#c2

charlie said just make it (as you now do), so lets close opened bugs

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


Cool34000