498
edits
Changes
From SME Server
Jump to navigationJump to searchDeploying packages section expanded
==Deploying packages==
==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.
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, see section 8.3 of the help file.
[[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 names for both fields!
[[Image:OCS-activate-package2.png]]<br>
----
Don't pay attention to the warning message when activating.
[[Image:OCS-activate-package3.png]]<br>
----
====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 will contact the server, the package should be deployed! As usual, you can manually launch the agent to force the update.
See section 8. of the help file to understand how download works
=GLPI Usage=
=GLPI Usage=
