OCS Inventory NG Documentation - OCS Inventory NG

  • View
    8.793

  • Download
    4

Embed Size (px)

Text of OCS Inventory NG Documentation - OCS Inventory NG

OCS Inventory NG:Documentation - OCS Inventory NG

OCS Inventory NG:Documentation - OCS Inventory NGq q

[OCS Inventoiry NG Home] [OCS Inventory NG Forums]

OCS Inventory NG:DocumentationFrom OCS Inventory NGJump to: navigation, searchLanguages: English Espaol Franais

Contents[hide]q

q

q

q

1 Setting up management server. r 1.1 Under Linux Operating System. s 1.1.1 Requirements. s 1.1.2 Installing Communication server required PERL modules. s 1.1.3 Installing Administration console required PHP modules s 1.1.4 Installing management server. s 1.1.5 Configuring management server. s 1.1.6 Upgrading management server. r 1.2 Under Windows Operating System. s 1.2.1 Installing management server. s 1.2.2 Configuring management server. s 1.2.3 Updating security of XAMPP components. s 1.2.4 Upgrading management server. 2 Setting up agent on client computers. r 2.1 Under Windows Operating Systems. s 2.1.1 Which version of Windows Agent must I use ? s 2.1.1.1 How does Windows Agent work ? s 2.1.1.2 How does Windows service work? s 2.1.1.3 Do I have to use service or standalone agent ? s 2.1.2 Manually installing Service version of Agent. s 2.1.3 Manually installing standalone Agent (without service). s 2.1.4 Deploying Agent using launcher OcsLogon.exe through Login Script or Active Directory GPO. s 2.1.4.1 Deploying Agent through Active Directory GPO. s 2.1.4.2 Deploying Agent through login script. s 2.1.5 Agents command line switches r 2.2 Under Linux Operating Systems. s 2.2.1 Requirements. s 2.2.2 Installing the agent interactively. s 2.2.3 Deploying agent through scripted installation without user interaction. s 2.2.4 Agents command line switches 3 Querying inventory results. r 3.1 All computers. r 3.2 TAG / number of PC repartition. r 3.3 Search with various criteria. 4 Administration of OCS Inventory NG. r 4.1 Managing OCS Inventory NG Administration server users. r 4.2 Managing OCS Inventory NG general options. r 4.3 Uploading Agent for deployement through launcher OcsLogon.exe.

http://wiki.ocsinventory-ng.org/index.php?title=OCS_Inventory_NG:Documentation (1 of 91)3/13/2008 9:22:27 AM

OCS Inventory NG:Documentation - OCS Inventory NG

q

q

q q

q

4.4 Using Registry Query feature. 4.5 Managing duplicates computers. r 4.6 Editing administrative information. r 4.7 Editing the label r 4.8 Importing inventory for non network connected computers. s 4.8.1 With Administration server through your web browser s 4.8.2 With Communication server through a Perl script r 4.9 Using software dictionary for GLPI integration. 5 Using IP discovery feature. r 5.1 Introduction. r 5.2 How does it work? s 5.2.1 Retrieving information. s 5.2.2 Election mechanism. s 5.2.3 How do agents work? s 5.2.4 Server tuning r 5.3 Working with results. s 5.3.1 Manage names of your networks. s 5.3.2 Show list of networks s 5.3.3 Show inventoried hosts in the network. s 5.3.4 Show uninventoried network devices. s 5.3.5 Show IPDISCOVER enabled hosts. s 5.3.6 Show known or identified hosts. s 5.3.7 Managing known device types. s 5.3.8 Registering known hosts. s 5.3.9 Scanning an IP address 6 Deploying packages or executing commands on client hosts. r 6.1 How does it work? r 6.2 Requirements. r 6.3 Creating packages. s 6.3.1 Deploying package through Launch command. s 6.3.2 Deploying package through Execute command. s 6.3.3 Command through Execute command. s 6.3.4 Stored package through Store command. r 6.4 Activating package r 6.5 Affecting packages to computers. r 6.6 Unactivating packages. r 6.7 Deployment statistics and success validation. r 6.8 Using SSL certificates in Package deployment. s 6.8.1 Using self signed certificates. s 6.8.1.1 With OCS Inventory NG Server for Linux. s 6.8.1.2 With OCS Inventory NG Server for Windows. s 6.8.2 Using PKI with Certificate Authority. s 6.8.2.1 With OCS Inventory NG Server for Linux. s 6.8.2.2 With OCS Inventory NG Server for Windows. r 6.9 Example: Deploying new version of Service agent for Windows. 7 Management server tuning. 8 Backup/restore of OCS Inventory NG database. r 8.1 Backuping OCS Inventory NG database. r 8.2 Restoring OCS Inventory NG database. 9 Common errors. r 9.1 Troubleshouting agents execution. s 9.1.1 Windows launcher OcsLogon.exe does not download Agent. s 9.1.2 Windows agent does not send inventory to server. s 9.1.3 Linux agent does not send inventory to server. s 9.1.4 Agent HTTP errors.r r

http://wiki.ocsinventory-ng.org/index.php?title=OCS_Inventory_NG:Documentation (2 of 91)3/13/2008 9:22:27 AM

OCS Inventory NG:Documentation - OCS Inventory NG

r

r

r r

9.2 Administration console errors. s 9.2.1 MySQL Max_allowed_packet error. s 9.2.2 MySQL Client does not support authentication protocol. s 9.2.3 PHP Requested content-length. s 9.2.4 Uploads size for package deployment. s 9.2.4.1 upload_max_filesize and post_max_size. s 9.2.4.2 memory_limit. s 9.2.4.3 max_execution_time and max_input_time s 9.2.4.4 Additonal Comments 9.3 Communication server errors. s 9.3.1 I see "Unknown directive PerlRequire...." in Apache log files. s 9.3.2 I see "Can't locate [Perl module name], cannot resolve handler Ocsinventory.pm..." in Apache log files. s 9.3.3 I see "Cannot open log file: ..." in Apache logs. Communication server is not able to write his logs. 9.4 Files and directories permissions under Linux. 9.5 Getting help in forums.

Setting up management server.Management server is made up of 4 main components:

1. 2. 3. 4.

Database server, which stores inventory information Communication server, which handles HTTP communications between database server and agents. Administration console, which allows administrators querying the database server using their favorite browser. Deployment server, which stores all package deployment configuration (require HTTPS!)

These 4 components can be hosted on a single computer or on different computers to allow load balancing. Above 10000 inventoried computers, we recommend using at least 2 physical servers, one hosting database server + Communication server and the other one hosting a database replica + Administration server + Deployement server.

http://wiki.ocsinventory-ng.org/index.php?title=OCS_Inventory_NG:Documentation (3 of 91)3/13/2008 9:22:27 AM

OCS Inventory NG:Documentation - OCS Inventory NG

OCS Inventory NG communication architecture.

NB: If you want to use multiple computers to host OCS inventory NG management server, we recommend that you set it up on Linux servers. OCS Inventory NG server for Windows comes as an integrated package including all required components (apache, perl, php, mod_perl, mysql).

Database server currently can only be MySQL 4.1 or higher with InnoDB engine active.

Communication server needs Apache Web Server 1.3.X/2.X and is written in PERL as an Apache module. Why? Because PERL scripts are compiled when Apache starts, and not at each request. This is better performance-wise. Communication server may require some additional PERL modules, according to your distribution.

Deployment server needs any Web Server with SSL enabled.

Administration console is written in PHP 4.1 (or higher) and runs under Apache Web Server 1.3.X/2.X. Administration console requires ZIP and GD support enabled in PHP in order to use package deployment.

Under Linux Operating System.We assume that you have:q q q q

MySQL database server running somewhere and listening on default port 3306 with TCP/IP communication enabled. Apache Web server installed and running for Communication server and Administration server. PHP and Perl installed and usable by Apache Web server for the Administration console. Perl and mod_perl installed and usable by Apache Web server for the Communication server.

Requirements.q

Apache version 1.3.33 or higher / Apache version 2.0.46 or higher. r Mod_perl version 1.29 or higher. r Mod_php version 4.3.2 or higher. PHP 4.3.2 or higher, with ZIP and GD support enabled. PERL 5.6 or higher. r Perl module XML::Simple version 2.12 or higher. r Perl module Compress::Zlib version 1.33 or higher. r Perl module DBI version 1.40 or higher. r Perl module DBD::Mysql version 2.9004 or higher. r Perl module Apache::DBI version 0.93 or higher. r Perl module Net::IP version 1.21 or higher. r Perl module SOAP::Lite version 0.66 or higher (not mandatory) MySQL version 4.1.0 or higher with InnoDB engine active. Make utility such as GNU make.

q q

q q

NB: OCS Inventory NG Server Setup will check for all these components and will exit if any is missing.

Installing Communication server required PERL modules.The Web communication server requires Apache web server and Perl 5 scripting language and some additional modules for Perl 5 (see Requirements). It acts as an Apache module which handles HTTP OCS Inventory agents' requests to a virtual directory /ocsinventory. You must have root privileges to set required perl modules up.

http://wiki.ocsinventory-ng.org/index.php?title=OCS_Inventory_NG:Documentation (4 of 91)3/13/2008 9:22:27 AM

OCS Inventory NG:Documentation - OCS Inventory NG

It is better for system integrity to use your distribution's precompiled packages when they are available. On Fedora/Redhat like Linux, you can use yum to set required modules up:q q q q q q q

yum install perl-XML-Simple yum install perl-Compress-Zlib yum install perl-DBI yum install perl-DBD-MySQL yum install perl-Apache-DBI yum install perl-Net-IP yum install perl-SOAP-Lite

On Debian like Linux, you can use apt-get to set required modules up:q q q q q q q

apt-get install libxml-simple-perl apt-get install libcompress-zlib-perl apt-get install libdbi-perl apt-get install libdbd-mysql-perl apt-get install libapache-dbi-perl