Line 108: |
Line 108: |
| | | |
| ==OCS Agent for Windows== | | ==OCS Agent for Windows== |
− | Download the latest client software, OCSNG_WIN32_AGENT_1.xx_repack.zip, this contains three alternatives, it is suggested you use OcsAgentSetup.exe. See Section 4.1 in the internal OCS help file. | + | There are 2 differents ways of sending inventories on Windows. Download the latest client software, OCSNG_WIN32_AGENT_1.xx_repack.zip from ocs website. This archive contains 3 executables. |
| | | |
− | Launch the first inventory by typing the following in the 'execute box': | + | See Section 4.1 in the internal OCS help file. |
| + | ===OcsAgentSetup.exe=== |
| + | Using OCS as a service is what you will probably need. |
| + | |
| + | Launch the install of ''OcsAgentSetup.exe'' and provide default settings of the service. |
| + | [[Image:OCS-winagent-setup.png]]<br> |
| + | ---- |
| + | Then launch the first inventory by typing the following in the 'execute box': |
| "C:\Program Files\OCS Inventory Agent\OCSInventory.exe" /server:yourdomain.com /np /debug /tag:your_tag | | "C:\Program Files\OCS Inventory Agent\OCSInventory.exe" /server:yourdomain.com /np /debug /tag:your_tag |
− | Wait a few seconds and go to http://your-server/ocs, you should see your computer's inventory, | + | Wait a few seconds and go to http://your-server/ocs, you should see your computer's inventory. |
− | Or just wait a day for the automatic update.
| + | |
| + | By default, Agent will contact the Server once a day. |
| + | |
| + | You can override this default behaviour in ocs web interface options. Your changes will be applied next time the Agent contacts the Server. |
| + | ---- |
| + | For troubleshooting, look at the log file in ''C:\Program Files\OCS Inventory Agent\COMPUTER_NAME.log'' |
| + | |
| + | ===ocsagent.exe=== |
| + | '''Since version 1-6, this file is no more included directly in the RPM to save bandwidth.''' |
| + | |
| + | This file only contains files needed by the standalone executable ''OcsLogon.exe''. Files will uncompress in '''''c:\ocs-ng\''''' |
| + | |
| + | There are different ways of using this file... |
| + | ====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\'') |
| + | |
| + | Go the ''OcsLogon.exe'' section. |
| + | ====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 then 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 this file in '''''/opt/inventory/ocs/ocsreports/files/'''''. |
| + | {{Incomplete}} |
| + | ===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== |