Wiki source code of Reg-Dateien importieren und exportieren

Last modified by Jannis Klein on 2024/08/13 08:19

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	160
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
2.1	7	= Initial Situation =
1.1	8
2.1	9	You can use the "modify registry value" Client Command module to edit or reset individual registry values. However, if you want to customise or change multiple registry values in a bundle, you can use the Shell Execute Command module to import a registry file.
1.1	10
2.1	11	To do this, you must import a registry file that you have already created or exported. You can export this file from the registry of a sample client and then import it again for all the other clients. This not only saves time, but also ensures that consistent values and parameters are passed.
1.1	12
2.1	13	As well as importing a registry file, you can also export it. Exporting the file allows you to copy the specified keys, entries and values from the local computer and transfer them to another Server or Client. This is useful, for example, if you want to use the operating system settings on other computers.
1.1	14
2.1	15	This use case lists both approaches to importing and exporting a registry file. Both sections can be used independently. Proceed as follows:
1.1	16
2.1	17	= Import Reg file =
1.1	18
2.1	19	== Select script ==
1.1	20
2.1	21	1. Navigate to the //Client Commands// > //Create// module.
	22	1. Click //Add// on the ribbon bar. The Client Command Editor will open and you will need to decide whether it is a console or client script. In this case select Client Script.
1.1	23
2.1	24	== Inserting and customising a Command //Action Group// ==
1.1	25
2.1	26	1. First select the //Miscellaneous// > //Action Group// Command from the Command List. You need this command to structure the script and make it easier to read.
	27	1. Double click on the Command to open it.
	28	1. Enter a name for the action in the Description field, e.g. „Import reg file“.
	29	1. Click //OK//.
	30	The frist Command in row 1 appears.
	31
	32	== To insert and customise a //Download File// ==
	33
	34	1. Navigate back to the command list and select the //File Repository// > //Download File// Command.{{aagon.infobox}}Indent this command, either using the quick selection bar or the CTRL + -> shortcut, so that it appears below the first command (Action group) is displayed. When adding this command, you can also simply drag the command onto the line of the Import Reg file, which will insert it correctly. {{/aagon.infobox}}
	35	1. Open the Command and click on the //General// tab.
	36	1. In the //Description of action// box, enter a name, for example „Download file“.
	37	1. Switch to the //Find file(s)// tab.
	38	1. Click on the icon in the //Select file(s) //field. The File Repository window opens.
	39	1. Upload the previously exported //logging.reg// file to the „Private“ directory. Once the file has been uploaded, mark the file for downloads. To do this, tick the box in front of the file name.
	40	1. Click //Close// to return to the previous window.{{aagon.infobox}}By uploading to the home directory you ensure that the file can only be used for the current Client Command. The reg file you download here will be synchronised to the deployed file repositories.{{/aagon.infobox}}
	41	1. Enter the %PROJECTDIR% variable in the //Memory as// area. This uses a temporary target directory which is automatically cleaned up by the ACMP Client at the end of the Client Command runtime. This means that you do not need to manually remove the files after import.
	42
1.1	43	{{figure}}
	44	(% style="text-align:center" %)
	45	[[image:64_Use Case_Client Command_Reg-Dateien_Download File_708.png]]
	46
	47	{{figureCaption}}
2.1	48	Customised command download file
1.1	49	{{/figureCaption}}
	50	{{/figure}}
	51
2.1	52	9. Click //OK// to display the Command in row 2.
1.1	53
2.1	54	== Inserting and editing the //Shell execute command// ==
1.1	55
2.1	56	1. Load the //Shell execute command// (Processes and Shell) into the script by double-clicking it in the command list, just like the previous commands.
	57	Optional: If you are working with the //Action group// Command, you will need to indent the Shell execute command. This helps with the readability and structure of the client commands. If you have already done this, you can skip this step.
	58	1. Open the //General// tab.
	59	1. Enter a name under the //description of the action//, e.g. „Run Command“.
	60	1. Switch to the //Details// tab.
	61	1. Enter a filename and parameters in the call options.
	62	1. Enter the following information in the fields:
1.1	63
2.1	64	\|Filename\|reg.exe or the file path{{aagon.infobox}}By default, reg.exe is located in the C:\Windows\System32\reg.exe path.{{/aagon.infobox}}
1.1	65	\|Parameter\|import "%PROJECTDIR%logging.reg“
	66
	67	{{figure}}
	68	(% style="text-align:center" %)
	69	[[image:64_Use Case_Client Command_Reg-Dateien_Shell execute command import_708.png]]
	70
	71	{{figureCaption}}
2.1	72	Customised command Shell execute command
1.1	73	{{/figureCaption}}
	74	{{/figure}}
	75
2.1	76	7. Confirm the entries with //OK//.
	77	Line 3 is inserted.
	78	8. Now save the Client Command if you do not want to make any more changes to the content.
1.1	79
2.1	80	If you just want to import a reg file, these three commands are sufficient. Save the Command and proceed with the Client Command phases.
1.1	81
	82	{{figure}}
	83	(% style="text-align:center" %)
	84	[[image:65_Client Command Use Case_Reg import_1350.png\|\|alt="64_Client Command Use Case_Reg export_1350.png"]]
	85
	86	{{figureCaption}}
2.1	87	Client Command Editor: Importing a Reg File
1.1	88	{{/figureCaption}}
	89	{{/figure}}
	90
2.1	91	== Running the Client Command Phases ==
1.1	92
2.1	93	The Client Commands must then go through the [[Test>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command testen.WebHome]], [[Synchronise>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command synchronisieren.WebHome]], [[Release >>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command freigeben.WebHome]]and [[Execute >>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command ausführen.WebHome]]phases before they can be used. Only then can the Reg files be imported.
1.1	94
2.1	95	= Export Reg file =
1.1	96
2.1	97	== Select script ==
1.1	98
2.1	99	1. Navigate to the //Client Commands// > //Create// module.
	100	1. Click //Add //in the ribbon bar The Client Commands Editor will open and you will need to decide whether it is a console or Client Script. In this case select Client Script
1.1	101
2.1	102	== Inserting and customising a Command //Action Group// ==
1.1	103
2.1	104	1. From the Command List, select the //Miscellaneous// > //Action Group// Command.
	105	1. Double click to open the Command..
	106	1. In the //Description of the action// box, type a name, e.g. „Export reg key to reg file“.
	107	1. Click //OK//.
1.1	108
2.1	109	== Inserting and editing a command //Shell execute command// ==
1.1	110
2.1	111	1. From the Command List, select //Processes and Shell// > //Shell Execute command//.
	112	Optional: Note that this command should be indented below the previous one. You can do this using either the CTRL + -> shortcut or the arrows in the toolbar.
	113	1. In the General tab, enter a //description of the action//, e.g. "Run command".
	114	1. Switch to the //Details// tab.
	115	1. Under File name, enter the Reg file to be used for the export, e.g. "reg.exe".
	116	1. Enter the value export for the parameter together with the path HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Aagon\ACMP "C:\Temp\export.reg". The full parameter must therefore be: export HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Aagon\ACMP "C:\Temp\export.reg".
1.1	117
	118	{{figure}}
	119	(% style="text-align:center" %)
	120	[[image:64_Use Case_Client Command_Reg-Dateien_Shell execute command export_708.png]]
	121
	122	{{figureCaption}}
2.1	123	Custom Shell execute command
1.1	124	{{/figureCaption}}
	125	{{/figure}}
	126
2.1	127	6. Confirm your entries with //OK//.
1.1	128
2.1	129	Once you have inserted all the relevant blocks to create an export for a reg file, the Client Command Editor interface should look like this:
1.1	130
	131	{{figure}}
	132	(% style="text-align:center" %)
	133	[[image:65_Client Command Use Case_Reg export_1350.png\|\|alt="64_Client Command Use Case_Reg export_1350.png"]]
	134
	135	{{figureCaption}}
2.1	136	Client Command Editor: Exporting a Reg File
1.1	137	{{/figureCaption}}
	138	{{/figure}}
	139
2.1	140	Save the Client Command if you do not wish to make any further changes to its contents.
1.1	141
	142	== Client Command-Phasen durchlaufen lassen ==
	143
2.1	144	Finally, the Client Command must go through the [[Test>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command testen.WebHome]], [[Synchronise>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command synchronisieren.WebHome]], [[Release >>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command freigeben.WebHome]]and [[Execute>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command ausführen.WebHome]] phases before it can be used. Only then can the Reg files be exported.