Changes

From SME Server
Jump to navigationJump to search
436 bytes removed ,  01:57, 11 November 2007
Line 2: Line 2:  
There are still some bugs in this RPM... Help us to fix them!
 
There are still some bugs in this RPM... Help us to fix them!
 
==ipdiscover bug==
 
==ipdiscover bug==
===ipdiscover and SME===
+
===ipdiscover on SME===
IpDiscover is not working on SME. We know that. Please use a different client to ipdiscover your networks.
+
IpDiscover is not working on SME. Please use another agent to ipdiscover your networks at the moment.
    
I've opened a [http://forums.ocsinventory-ng.org/viewtopic.php?pid=5684#p5684 thread] on OCS forum.
 
I've opened a [http://forums.ocsinventory-ng.org/viewtopic.php?pid=5684#p5684 thread] on OCS forum.
    +
Let's hope the next version will come out soon!
 
===ipdiscover-util.pl===
 
===ipdiscover-util.pl===
 
This script used by the web interface do not seem to work too.
 
This script used by the web interface do not seem to work too.
Line 14: Line 15:  
  my $dbhost = 'localhost';
 
  my $dbhost = 'localhost';
 
  my $dbuser = 'ocs';
 
  my $dbuser = 'ocs';
  my $dbpwd = 'ocs';
+
  my $dbpwd = 'ocs'; <==
 
  my $db = 'ocsweb';
 
  my $db = 'ocsweb';
 
  my $dbp = '3306';
 
  my $dbp = '3306';
 
The password should be dynamical as this is a perl script. We need to use esmith::ConfigDB or something else to retrieve this value... I was unable to handle that.
 
The password should be dynamical as this is a perl script. We need to use esmith::ConfigDB or something else to retrieve this value... I was unable to handle that.
   −
Also a problem, the script cannot be executed. I try to add script handler for .pl but it didn't worked...
+
Also a problem, the script cannot be executed. I try to add script handler for .pl but it didn't worked... Not sure about how this is working, if someone can help, please do!
 +
 
 +
Cool34000
 +
----
    
==www/ocs/install.php bugs==
 
==www/ocs/install.php bugs==
Line 26: Line 30:  
I took a look on ocsweb database with phpmyadmin before and after using install.php
 
I took a look on ocsweb database with phpmyadmin before and after using install.php
   −
I noticed that ''engine type'' is MyISAM and after using install.php their type is InnoDB!
+
I noticed that a lot of tables' ''engine type'' were ''MyISAM'' and after using install.php their type was ''InnoDB''!
    
So I tried to export a new database (this time with extended parameters), but this new database don't import in ocsweb database: it ends with errors trying to create the 1st table!
 
So I tried to export a new database (this time with extended parameters), but this new database don't import in ocsweb database: it ends with errors trying to create the 1st table!
 +
 +
Help needed!
    
Cool34000
 
Cool34000
 
----
 
----
  −
      
=wiki page=
 
=wiki page=
Line 49: Line 53:     
others can work on this cool34000 has done enough
 
others can work on this cool34000 has done enough
 +
 
Stefen
 
Stefen
 
----
 
----
In fact, that's the way I always used OCS... I don't like to install a service when it's not needed...
+
Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL.
 +
 
 +
I don't like to install a service when it's not needed, so I use the standalone executable. I also don't use OCS deployment feature (I'm using GPOs for that)
    
It is so fast to use against the need of installing the Agent: put OcsLogon.exe in a share folder and simply launch it with a one command line batch script each time a session is opened.
 
It is so fast to use against the need of installing the Agent: put OcsLogon.exe in a share folder and simply launch it with a one command line batch script each time a session is opened.
Line 62: Line 69:  
*Install the Agent silently in a script
 
*Install the Agent silently in a script
 
*Use GPOs (deploy, install, update)
 
*Use GPOs (deploy, install, update)
*...Read the guide!
+
*Create your own ''ocsagent.exe''
 +
People need to read the guide! It's well documented.
   −
Didn't document that... Do we really need to? The command line is really simple, then it's the end-user's job to adapt it to his network and needs.
+
If someone can take some time to document that, it would be nice!
   −
sg
+
Cool34000
---
  −
 
  −
 
  −
@echo off
  −
\\server\share\mydomain.com.exe /np /debug /tag:my_tag
  −
 
  −
that's what we need to know,
  −
 
  −
with this method does deploy work, where does clients cacert.pem go
  −
 
  −
if you can install cacert.pm to netlogon.bat then admin doesn't need to visit clients at all, 
  −
 
  −
sn
   
----
 
----
Yes, those kind of answer are in the manual...
  −
  −
Take a look on the history, I'm fighting with install.php that you want to remove since the begining :D
  −
  −
You can integrate a certificate in ''ocsagent.exe''... But you have to download the packager on their website to create your own ''ocsagent.exe''
  −
  −
That's in the doc ;-)
  −
  −
As I never tested that, it's not documented (don't like to document something I don't know!)
  −
I'll give it a try and add that to the article.
  −
  −
Cool34000
      
==glpi==
 
==glpi==
    
someone who uses this may like to add some more information on how to  use it, some link to more docs at least
 
someone who uses this may like to add some more information on how to  use it, some link to more docs at least
498

edits

Navigation menu