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

= Initial situation =

If you want to distribute software to certain Clients, you have the option of building a Client Command and then providing it with parameter values that only apply to this Client Command. With these parameters, you can have various tasks executed within the Client Command without having to create multiple Client Commands. For example, you can use the parameters of the client command to determine whether the software should be installed or uninstalled before execution

6

7

In this case, 7-ZIP (64-bit) is to be installed. To do this, the Package Wizard is used to build the client command. This creates a client command that performs the intended functions and automatically contains the appropriate parameters.

8

9

In a later step, the built client command is transferred to a container that contains the Clients on which 7-ZIP is to be installed.

10

11

12

= Open the package wizard =

13

14

~1. Navigate to the //Client Commands > Create module.//

15

16

2. Go to the ribbon bar under //Package Wizard// and select the desired operating system from Windows, Mac and Linux. In this case, the Windows operating system is selected.

17

18

19

= **Running the package wizard** =

20

21

~1. In the first step, enter a name and, if necessary, a description of the package, e.g. //7-Zip//. Choose the folder in which the Client Command should appear and the installation type. In this case, MSI/MSP files, since the software in question consists of an MSI file. Click //Next >//.

22

23

2. Then add the MSI file via //Add file//. The file path of the MSI file appears. Click //Continue >.//

24

25

3. In the next step, you can specify the execution sequence and, if necessary, integrate a transformation file via drag and drop. In this case, it should be left as it is for execution. Click //Continue >//.

26

27

4. In the last step, you can specify user-defined properties for the package. Click on// Generate// to create the package.

28

29

5. The wizard will then tell you whether the package was successfully generated. If it was not, you will see a red cross under //Status// at the relevant step.

30

31

[[Creating Client Commands in the Package Wizard>>image:Paket Wizard erfolgreich.png||alt="Creating Client Commands in the Package Wizard"]]

32

33

6. To view the parameter values, you have to set the radio button under //Client Command now open in the editor//.

34

35

36

= Editing parameters in CC Editor =

37

38

~1. You can see the client command created in the package wizard in the script.

39

40

[[The client command script shows the created client command>>image:Editor.png]]

41

42

43

2. Navigate to Menu bar > //Properties > Client command specific > Parameter//.

44

45

3. You will see an existing parameter that you can edit to match the action that the software should perform on the clients.

46

47

4. Double-click on the parameter. You can change the German and English names as well as the ACMP Kiosk option.

48

49

[[Editing parameters>>image:Parameter editieren.png]]

50

51

5. You can see the following values under //Combobox Configuration//:

52

53

|**Value**|**Meaning**

54

|Installation|Install the software.

55

|Deinstallation|The software should be uninstalled.

56

|Repair|In the event of a defect, the software will be repaired.

57

|Parking|The software is pre-copied and stored on the client, but not installed.

58

|Unparking|The software is removed from the client on which it was previously stored.

59

60

Use the //Actual Default// value to specify the default value to be passed when the client script is executed.

61

62

63

All default values set here can be overridden at a later date, e.g. when creating a Client Command job, adding to a container or adding a kiosk entry.

6. Click //Save//.

Wiki source code of Transferring specific parameters for software distribution to a Client Command, using 7-ZIP as an example

Navigation

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		3	= Initial situation =
		4
		5	If you want to distribute software to certain Clients, you have the option of building a Client Command and then providing it with parameter values that only apply to this Client Command. With these parameters, you can have various tasks executed within the Client Command without having to create multiple Client Commands. For example, you can use the parameters of the client command to determine whether the software should be installed or uninstalled before execution
		6
		7	In this case, 7-ZIP (64-bit) is to be installed. To do this, the Package Wizard is used to build the client command. This creates a client command that performs the intended functions and automatically contains the appropriate parameters.
		8
		9	In a later step, the built client command is transferred to a container that contains the Clients on which 7-ZIP is to be installed.
		10
		11
		12	= Open the package wizard =
		13
		14	~1. Navigate to the //Client Commands > Create module.//
		15
		16	2. Go to the ribbon bar under //Package Wizard// and select the desired operating system from Windows, Mac and Linux. In this case, the Windows operating system is selected.
		17
		18
		19	= Running the package wizard =
		20
		21	~1. In the first step, enter a name and, if necessary, a description of the package, e.g. //7-Zip//. Choose the folder in which the Client Command should appear and the installation type. In this case, MSI/MSP files, since the software in question consists of an MSI file. Click //Next >//.
		22
		23	2. Then add the MSI file via //Add file//. The file path of the MSI file appears. Click //Continue >.//
		24
		25	3. In the next step, you can specify the execution sequence and, if necessary, integrate a transformation file via drag and drop. In this case, it should be left as it is for execution. Click //Continue >//.
		26
		27	4. In the last step, you can specify user-defined properties for the package. Click on// Generate// to create the package.
		28
		29	5. The wizard will then tell you whether the package was successfully generated. If it was not, you will see a red cross under //Status// at the relevant step.
		30
		31	[[Creating Client Commands in the Package Wizard>>image:Paket Wizard erfolgreich.png\|\|alt="Creating Client Commands in the Package Wizard"]]
		32
		33	6. To view the parameter values, you have to set the radio button under //Client Command now open in the editor//.
		34
		35
		36	= Editing parameters in CC Editor =
		37
		38	~1. You can see the client command created in the package wizard in the script.
		39
		40	[[The client command script shows the created client command>>image:Editor.png]]
		41
		42
		43	2. Navigate to Menu bar > //Properties > Client command specific > Parameter//.
		44
		45	3. You will see an existing parameter that you can edit to match the action that the software should perform on the clients.
		46
		47	4. Double-click on the parameter. You can change the German and English names as well as the ACMP Kiosk option.
		48
		49	[[Editing parameters>>image:Parameter editieren.png]]
		50
		51	5. You can see the following values under //Combobox Configuration//:
		52
		53	\|Value\|Meaning
		54	\|Installation\|Install the software.
		55	\|Deinstallation\|The software should be uninstalled.
		56	\|Repair\|In the event of a defect, the software will be repaired.
		57	\|Parking\|The software is pre-copied and stored on the client, but not installed.
		58	\|Unparking\|The software is removed from the client on which it was previously stored.
		59
		60	Use the //Actual Default// value to specify the default value to be passed when the client script is executed.
		61
		62	{{aagon.infobox}}
		63	All default values set here can be overridden at a later date, e.g. when creating a Client Command job, adding to a container or adding a kiosk entry.
		64	{{/aagon.infobox}}
		65
		66	6. Click //Save//.
		67
		68