Line 116: |
Line 116: |
| | | |
| See Section 4.1 in the internal OCS help file. | | See Section 4.1 in the internal OCS help file. |
− | ===OcsAgentSetup.exe=== | + | ===Service use=== |
| Using OCS as a service is what you will probably need. | | Using OCS as a service is what you will probably need. |
| | | |
Line 131: |
Line 131: |
| ---- | | ---- |
| For troubleshooting, look at the log file in ''C:\Program Files\OCS Inventory Agent\COMPUTER_NAME.log'' | | For troubleshooting, look at the log file in ''C:\Program Files\OCS Inventory Agent\COMPUTER_NAME.log'' |
| + | ===Standalone use=== |
| + | You can also make inventories on Windows without installing the service. |
| | | |
− | ===ocsagent.exe===
| + | OCS standalone client is cut into 2 executables: |
− | '''Since version 1-6, this file is no more included directly in the RPM to save bandwidth.''' | + | *''ocsagent.exe'' - This file contains all needed files for the launcher |
| + | *''OcsLogon.exe'' - This file is the standalone executable (launcher) |
| | | |
− | This file only contains files needed by the standalone executable ''OcsLogon.exe''. Files will uncompress in '''''c:\ocs-ng\'''''
| + | Of course, ''ocsagent.exe'' must be uncompressed before launching the standalone executable. |
| | | |
− | There are different ways of using this file...
| + | This can be done by executing directly ''ocsagent.exe'': files will uncompress in ''c:\ocs-ng''. |
− | ====Manual launch====
| |
− | This file can be manually launched on any computer to uncompress needed files. | |
| | | |
− | Procedure is pretty easy: double-clic on ''ocsagent.exe'' to uncompress files! ''ocsagent.exe'' will not be needed anymore (unless you delete ''C:\ocs-ng\'')
| + | You can also import this file into ocs' MySQL database so that the standalone executable can download it if needed. This is documented in [http://wiki.contribs.org/index.php?title=OCS_Inventory_Tools&action=submit#MySQL_importation section MySQL importation]. |
| | | |
− | Go the ''OcsLogon.exe'' section.
| + | The command line is the same as for the service: |
| + | "C:\Path_to_file\OcsLogon.exe" /server:yourdomain.com /np /debug /tag:your_tag |
| + | For easier and faster inventorying, you can also rename this standalone executable to your domain name (don't forget ''.exe''): |
| + | "C:\Path_to_file\yourdomain.com'''.exe'''" /np /debug /tag:your_tag |
| + | |
| + | For troubleshooting, look at the log file in ''C:\ocs-ng\COMPUTER_NAME.log'' |
| + | ---- |
| ====MySQL importation==== | | ====MySQL importation==== |
− | The other method is to import this file in ocs' MySQL database so that the standalone executable can download it. | + | The main advantage of this method is that you can send it by Internet very quickly or even put the standalone executable on a floppy disk as it's only 65KB! How powerful looks your old floppy disk drive now? |
| + | |
| + | 1st thing you need is to copy ''ocsagent.exe'' in '''''/opt/inventory/ocs/ocsreports/files/'''''. |
| | | |
− | The main advantage of this method is that you can send it by Internet very quickly or even put the standalone executable on a floppy disk as it's only 65KB! How powerful looks your old floppy disk drive now?
| + | Installer is locked (install.php), you need to change perms with the following command: |
− | =====Install=====
| + | chmod 660 /opt/inventory/ocs/ocsreports/dbconfig.inc.php |
− | 1st thing you need is to copy this file in '''''/opt/inventory/ocs/ocsreports/files/'''''.
| |
| | | |
− | Then, you need to import this file in the database. Go to http://yourdomain.com/ocs/install.php | + | Then, you can import this file in the database. Go to http://yourdomain.com/ocs/install.php |
| | | |
− | '''Don't use ocs pre-configured account, use an admin account''' - You need [http://wiki.contribs.org/Phpmyadminmulti phpMyAdmin-multi] for that.
| + | Use the pre-configured account 'ocs' for that: |
| [[Image:OCS-installphp.png]]<br> | | [[Image:OCS-installphp.png]]<br> |
| ---- | | ---- |
− | If you get a warning, refresh the page and you should see a successful import. | + | If you get a warning message (cannot alter database), refresh the page and you should see a successful import. |
| [[Image:OCS-installphp-ocsagent.png]]<br> | | [[Image:OCS-installphp-ocsagent.png]]<br> |
| ---- | | ---- |
− | ''ocsagent.exe'' is now in the database. | + | ''ocsagent.exe'' is now in the database! |
− | {{Warning box|install.php will reset ocs password to 'ocs'. Re-apply your changes with following command: | + | {{Warning box|install.php has reset ocs password to 'ocs'. Re-apply your changes with following command: |
| signal-event domain-modify | | signal-event domain-modify |
| + | This will also reset chmod to 440 on ''dbconfig.inc.php'' |
| }} | | }} |
− | You can now use ''OcsLogon.exe'' alone, it will download ''ocsagent.exe'' if needed! | + | You can now use ''OcsLogon.exe'' alone, it will download/update ''ocsagent.exe'' if needed! |
− | =====Update=====
| + | |
− | ''ocsagent.exe'' may be updated. In that case, you should update it in the database too. Then it should deploy the updated ''ocsagent.exe'' next time the standalone executable contacts the server.
| |
− | =====Uninstall=====
| |
| If you want to remove ''ocsagent.exe'' from your database, simply delete the file from the server and redo install.php. This will delete the file from the database. | | If you want to remove ''ocsagent.exe'' from your database, simply delete the file from the server and redo install.php. This will delete the file from the database. |
− |
| |
− | ===OcsLogon.exe===
| |
− | This is the standalone executable. This is the alternate method of running ocs as a service.
| |
− |
| |
− | You must use one of the above method before using it.
| |
− |
| |
− | The command line is the same as for the service:
| |
− | "C:\Path_to_file\OcsLogon.exe" /server:yourdomain.com /np /debug /tag:your_tag
| |
− | For easier and faster inventorying, you can also rename this standalone executable to your domain name:
| |
− | "C:\Path_to_file\yourdomain.com.exe" /np /debug /tag:your_tag
| |
− | ----
| |
− | For troubleshooting, look at the log file in ''C:\ocs-ng\COMPUTER_NAME.log''
| |
| | | |
| ==OCS Agent for Linux== | | ==OCS Agent for Linux== |