Changes

From SME Server
Jump to navigationJump to search

OCS Inventory (view source)

Revision as of 20:19, 27 November 2013

6,133 bytes added ,  20:19, 27 November 2013
no edit summary
Line 154: Line 154:        +
=OCS Inventory NG Usage=
 +
Full documentation can be found in the ocs help file, the help icon in ocs interface.
 +
 +
==Access==
 +
OCS Reports' web interface can be reached at http://your-server/ocs
 +
 +
'''Before login, please choose your language (flags on the top right corner)'''
 +
[[Image:OCS_login_page.png]]<br>
 +
Login  : admin<br>
 +
Password: admin
 +
 +
{{Warning box|For security-reasons, change admin's password after your first login, top right icon next to logout!}}
 +
Inventories can be done from WAN but the web interface is only available from inside your network for security reasons by default.
 +
See Sections 5 & 6 in the internal OCS help file for Reporting and Administration help.
 +
 +
==IP discovery==
 +
IP discovery feature allow OCS Inventory NG to discover all network connected devices on the network. For this, Communication server asks a number of most “active” computers running OCS Inventory NG agent to scan for MAC addresses in their sub network at each run. See Section 7 in the internal OCS help file.
 +
 +
===Modifying default behaviour===
 +
You may want to override the default IP Discovery behaviour.
 +
 +
To force a computer to ipdiscover, simply open its inventory. Click on ''Customization'' icon and ''update'' the ipdiscover behaviour.
 +
[[Image:OCS-ipdiscover-step1.png]]<br>
 +
----
 +
Now choose the IP of selected computer and save your changes.
 +
[[Image:OCS-ipdiscover-step2.png]]<br>
 +
----
 +
You should now see your modifications.
 +
 +
[[Image:OCS-ipdiscover-step3.png]]<br>
 +
At this point, ipdiscover will run next time with the agent!
 +
 +
'''Manually launch the inventory to force ipdiscover''' or wait a day for the next inventory.
 +
----
 +
===Adding networks and devices categories===
 +
Now click on ''Security'' and go to ''Config''
 +
[[Image:OCS-ipdiscover-step4.png]]<br>
 +
----
 +
Add you own network/subnet. All fields are mandatory.
 +
[[Image:OCS-ipdiscover-step5.png]]<br>
 +
----
 +
We can also add categories. Let's do that! Click on 'Network devices types'
 +
[[Image:OCS-ipdiscover-step6.png]]<br>
 +
----
 +
 +
===Usage===
 +
Go back to ''Security'' and click on ''Network information''. Now that your network is created, you should see ipdiscover working...
 +
 +
Click on ''non-inventoried'' devices.
 +
[[Image:OCS-ipdiscover-step7.png]]<br>
 +
----
 +
Now all you have to do is registering new devices!
 +
[[Image:OCS-ipdiscover-step8.png]]<br>
 +
----
 +
[[Image:OCS-ipdiscover-step9.png]]<br>
 +
----
 +
 +
==Deploying packages==
 +
OCS Inventory NG includes package deployment feature on client computers. From the central management server, you can upload packages which will be downloaded through HTTP/HTTPS and launched by agent on client computer. See Section 8 in the internal OCS help file.
 +
 +
'''This feature is LAN ONLY'''
 +
 +
===SSL certificate===
 +
Deployment feature uses SSL to authenticate Agents.
 +
 +
To allow the Agent to authenticate with the Server, you need to '''copy the ''cacert.pem'' file in your agents' installation directory'''
 +
 +
This file is located in '''''/home/e-smith/ssl.crt/'''''
 +
 +
====Using default cacert.pem====
 +
If the file ''/home/e-smith/ssl.crt/cacert.pem'' can not be found, the RPM install will create it by copying your original SME certificate into this file. This is a quick and a simple method.
 +
 +
Copy the '''''cacert.pem''''' file in your agents' installation directory. Skip to next section!
 +
 +
====Using a custom certificate====
 +
If you've followed this [http://wiki.contribs.org/Custom_CA_Certificate howto] to create a valid certificate, you can use this certificate with OCS Deployment feature.
 +
 +
Download cacert.org certificate with the following command:
 +
wget http://www.cacert.org/certs/root.crt
 +
And replace the old file with the following command:
 +
cp root.crt /home/e-smith/ssl.crt/cacert.pem
 +
Copy this file into your agents' installation directory.
 +
 +
===Deployment menu===
 +
Open OCS' web interface and click on Deployment icon.
 +
[[Image:OCS-deployment-menu.png]]<br>
 +
----
 +
 +
====Building a deployment packages====
 +
Deployment packages can be either '''''.zip''''' files (Windows) or '''''tar.gz''''' files (Linux)
 +
 +
'''Don't try to deploy other file type.'''
 +
 +
There are many options to deploy packages,
 +
for an overview see [http://www.ocsinventory-ng.org/index.php?page=package-deployment the ocs website]
 +
for detail see section 8.3 of the help file,
 +
for [http://alufis35.uv.es/OCS-Deployment-Tips-and-tricks.html Tips and tricks] see Pablo Iranzo's site
 +
[[Image:OCS-buildpackage.png]]<br>
 +
----
 +
After creating the deployment package, you should get this successful screen:
 +
[[Image:OCS-success-build.png]]<br>
 +
----
 +
 +
====Activating deployment packages====
 +
Once a package is added, you need to activate it.
 +
[[Image:OCS-activate-package1.png]]<br>
 +
----
 +
Provide paths to download folder. As this feature is LAN ONLY, provide internal name or IP address for both fields.
 +
 +
Be careful, this path will be resolved by the agent (value ''localhost'' forbidden here!)
 +
 +
[[Image:OCS-activate-package2.png]]<br>
 +
----
 +
Don't pay attention to the warning messages when activating, Just click Yes.
 +
[[Image:OCS-activate-package3.png]]<br>
 +
----
 +
You can also ignore any warning messages when deleting a package, the package is removed.
 +
 +
====Activated deployment packages====
 +
Here you will be able to see activated packages...
 +
[[Image:OCS-activated-package.png]]<br>
 +
 +
===Deploying your packages===
 +
All should be ready to go now!
 +
 +
The final step is to affect the created package to computers...
 +
 +
Here's a quick howto for deploying the package ''on a single computer''.
 +
 +
To learn how to deploy on multiple computers, see section 8.5 of the help file.
 +
 +
 +
Open the desired computer's inventory on click on ''Config'' icon and add a new package
 +
[[Image:OCS-deploy-single-pc1.png]]<br>
 +
----
 +
You should see all activated packages, affect the one you want and confirm changes
 +
[[Image:OCS-deploy-single-pc2.png]]<br>
 +
----
 +
Back at Config page, you should now see affected packages and their states.
 +
[[Image:OCS-deploy-single-pc3.png]]<br>
 +
----
 +
Next time the Agent contacts the server, it is notified of the package, and sometime later should be deployed! As usual, you can manually launch the agent to force the update.
 +
 +
See section 8.1 of the help file to understand how download works
     
Unnilennium
Super Admin, Wiki & Docs Team, Bureaucrats, Interface administrators, Administrators
3,254

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/22516"

Navigation menu