Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.11.1 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

Deploy with Reboot or Package dependency


i am searching a way to do deploy a package with one ore more reboots in the middle or if not possible, maybe a "dependend" package deployment.

The goal is to deploy more then one piece of software, but each one needs a reboot for the next and after the last i need a "OK". Because it is a timing problem over a lot of devices, it is very difficult to do every single package round by round alone.

Any ideas? THX!
in OCS Inventory NG server for Unix by (390 points)

4 Answers

+1 vote

yes, copy the contents of each package to the target machine and with a common script execute each package with conditions > If necessary, use flags (a file, a modified registry key, etc.)

For the end of the procedure, a validation by email could do the trick ?
by (32.6k points)
0 votes

Hi steph,

of course we can do the job "outside" OCS... just only start it by OCS... but because of a special situation with the clients, we want to get informed about the progress and the result in a nice central gui smiley

So we also thought about that, but it would be a very complex process to keep in mind which client is in which state. But if there is no other way... we have to go that way.

If it is easy, it is not called IT wink (Hope that translation could be understood laugh)

by (390 points)
+1 vote

the result directly in OCS would be perfect, but as to my knowledge the function does not exist in OCS you will have to request it in the project roadmap.

I already have some ideas to design this function, results and percentage of achievement for each machine in a nice general table, and I can possibly work on it in the next few months... Anyway, it's an nice addition !
by (32.6k points)
0 votes
as Steph statet it is possible to write something into the registry after every step of a client side script.

The registry can be read by ocs-inventory and with dynamic groups you can see which pc sucessfully applied every step.

It will not be in realtime, but should work.

 I think PDQ Deploy has i nice way to manage "steps"

Kind regards

One nice client side script to resume jobs is here

by (22.7k points)
edited by
Powered by Question2Answer