Changes for page Transferring specific parameters for software distribution to a Client Command, using 7-ZIP as an example

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (0 modified, 1 added, 0 removed)
  • prio.WebHome[0]

Details

Page properties

Content

...	...	@@ -65,4 +65,29 @@
65	65
66	66	6. Click //Save//.
67	67
68		-
	68	+= Running Client Command phases =
	69	+
	70	+The client command can now be pushed through the //Test,// //Synchronise,// //Release// and //Execute// phases.
	71	+
	72	+Transferring parameters within a container to client commands
	73	+
	74	+~1. Go to //Client// //Management// > //Container//.
	75	+
	76	+2. Select the container that contains the clients on which the actions are to be executed or create a new one. If you create a new container, remember to add the clients to it.
	77	+
	78	+3. Select the //Jobs// tab in the workspace and then click //Add// in the ribbon bar to attach a job to the container.
	79	+
	80	+4. A new window will open. Under //Type of Job//, select the //Client Command// job and then, below that, double-click to select the Client Command that was just created, in this case the// 7-Zip// Client Command.
	81	+
	82	+5. The CC appears in the list under //Available Client Commands//. Click on the Client Command to display the parameters below it. The parameters now show fixed parameters, which every CC has and which cannot be configured by the user, and variable parameters, which can be added, deleted and configured by the user. In this use case, for example, these were added in advance by the package wizard in the client command.
	83	+
	84	+[[Create Client Command Job>>image:CC Job.png||height="824" width="1303"]]
	85	+
	86	+
	87	+6. Choose action from the values that should be applied when executing the CC, in this case //Install.//
	88	+
	89	+7. Then click //OK//.
	90	+
	91	+8. Then select a start condition.
	92	+
	93	+You have now attached a Client Command job to the container, which enables execution with 7-ZIP on the desired Clients. You can use the parameter //action that is applied when the Client Command is executed// to individually decide whether it should be installed, uninstalled, repaired, parked or unparked.

prio.WebHome[0]

priorisierung-66

...	...	@@ -1,0 +1,1 @@
	1	+140