Wiki source code of Boot Templates

Last modified by Sabrina V. on 2026/06/11 06:06

version	line-number	content
2.1	1	{{aagon.floatingbox/}}
	2
10.1	3	In the Boot Templates section, you can manage your bootable environments (Boot Images) that can be deployed via PXE. You can use these for various actions:
2.1	4
10.1	5	* You can securely delete storage devices and hard drives
	6	* You can boot customized PE/Linux images (e.g., for diagnostic or automation tasks)
	7	* You can execute manufacturer or third-party Boot Images on Clients
2.1	8
10.1	9	[[Overview- Boot Templates>>image:Boot Templates_Übersicht.png\|\|alt="Übersicht - Boot Templates"]]
2.1	10
10.1	11	= Workspace Functions =
2.1	12
10.1	13	The following functions are available in the ribbon bar and via the context menu:
4.1	14
10.1	15	\|=Icon \|=Description
4.1	16	\|(((
10.1	17	Add (Boot Templates)
4.1	18	)))\|(((
10.1	19	Opens the drop-down menu to select the new boot template to be added.
4.1	20	)))
	21	\|(((
10.1	22	Edit (Boot Templates)
4.1	23	)))\|(((
10.1	24	Opens the properties of the selected template.
4.1	25	)))
	26	\|(((
10.1	27	Delete (Boot Templates)
4.1	28	)))\|(((
10.1	29	Deletes the selected template. Any linked Boot Images are not affected.
4.1	30	)))
	31	\|(((
10.1	32	Duplicate (Boot Templates)
4.1	33	)))\|(((
10.1	34	Creates a copy of the template, including settings.
4.1	35	)))
	36	\|(((
10.1	37	Assign (Boot Templates)
4.1	38	)))\|(((
10.1	39	Opens a dialog to assign the selected boot template to a Client for execution or to remove a Client’s assignment.
4.1	40	)))
	41	\|(((
10.1	42	Add (Ordner)
4.1	43	)))\|(((
10.1	44	Adds a folder for the structured storage of boot templates.
4.1	45	)))
	46	\|(((
10.1	47	Edit (Ordner)
4.1	48	)))\|(((
10.1	49	Opens the folder properties.
4.1	50	)))
	51	\|(((
10.1	52	Delete (Ordner)
4.1	53	)))\|(((
10.1	54	Deletes the selected folder. Subfolders are also deleted.
4.1	55	)))
	56	\|(((
10.1	57	Download from server
4.1	58	)))\|(((
10.1	59	Downloads the selected custom boot template from the OSD Setup Repository and copies it to local storage.
4.1	60	)))
	61	\|(((
10.1	62	Upload
4.1	63	)))\|(((
10.1	64	Uploads the selected custom boot template from local storage to the OSD Setup Repository.
4.1	65	)))
	66	\|(((
10.1	67	Delete
4.1	68	)))\|(((
10.1	69	Deletes the selected boot template from local storage.
4.1	70	)))
	71	\|(((
10.1	72	Open in folder
4.1	73	)))\|(((
10.1	74	Opens the file directory on local storage where the downloaded custom boot template file was copied.
4.1	75	)))
	76
	77	(% class="wikigeneratedid" %)
10.1	78	In the workspace, you can see the folder structure containing the available boot templates. The column view displays various pieces of info about the boot templates.
4.1	79
10.1	80	\|=Column\|=Description
4.1	81	\|(((
10.1	82	Type
4.1	83	)))\|(((
10.1	84	Type of boot template, e.g., Wipe (delete) or Custom (user-defined/third-party image).
4.1	85	)))
	86	\|(((
10.1	87	Description
4.1	88	)))\|(((
10.1	89	Free-form text describing the boot template.
4.1	90	)))
	91	\|(((
10.1	92	Sync Status
4.1	93	)))\|(((
10.1	94	Sync status of the deployment to the deployed file repositories.
4.1	95	)))
	96	\|(((
10.1	97	Image Name
4.1	98	)))\|(((
10.1	99	Reference name of the underlying Boot Image that is loaded during PXE boot.
4.1	100	)))
	101	\|(((
10.1	102	Size
4.1	103	)))\|(((
10.1	104	Size of the referenced Boot Image.
4.1	105	)))
	106
10.1	107	= Running Boot Templates on Clients =
4.1	108
10.1	109	To execute a boot template on one or more clients, you must create an assignment between the boot template and the clients.
7.1	110
10.1	111	1. Select the desired boot template.
	112	1. Click the //Assign// button on the ribbon bar.
	113	1. In the dialog that opens, click the //Add Clients// button.
	114	1. Execute a query in the query window that opens.
	115	1. Select the clients to be assigned to the boot template.
	116	1. In the query window that opens, click the //Done// button.
	117	1. If necessary, configure the settings for waking up the clients.
	118	1. Click the //Apply// button to execute the boot template on the added clients.
7.1	119
	120	{{aagon.warnungsbox}}
10.1	121	Depending on the settings, the execution of a boot template may occur immediately and cannot be undone.
7.1	122	{{/aagon.warnungsbox}}
	123
10.1	124	One or more jobs have now been created to execute the boot template. You can track the progress of the execution in the [[Job monitor>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome\|\|anchor="HJobmonitor"]].
7.1	125
10.1	126	= Edit Bootloaders in Custom Boot Templates =
7.1	127
10.1	128	When creating custom boot templates, the bootloader files are uploaded from your local memory to the OSD Setup Repo. Therefore, you cannot edit the bootloader files for an existing custom boot template directly in ACMP; instead, you must download them from the Server, edit them locally, and then upload them again. To do this, follow these steps:
7.1	129
10.1	130	1. Select the desired custom boot template whose bootloader files you want to edit.
	131	1. Click the //Load from Server// button in the ribbon bar.
	132	1. Click the //Open in Folder// button in the ribbon bar.
	133	1. Open the bootloader file you want to edit with a program of your choice.
	134	1. Make your edits and save the file.
7.1	135
10.1	136	1. {{aagon.infobox}}The bootloader file must not be saved under a different name or in a different directory.{{/aagon.infobox}}
	137	1. Return to the ACMP Console and click the //Upload// button on the ribbon bar.
	138	1. Select whether you want the file to be deleted from your local storage.
	139	1. The bootloader file has now been uploaded back to the OSD Setup Repository.
7.1	140
	141