Wiki source code of Rollout Templates

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

version	line-number	content
1.1	1	{{aagon.floatingbox/}}
	2
63.1	3	A Rollout Template is used to create a standardized template for a rollout with ACMP. In the templates, you can select the components and configure them to suit different rollout scenarios.
1.1	4
63.1	5	A Rollout Template includes an [[operating system>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Betriebssysteme.WebHome]], a [[answer files>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Antwortdateien.WebHome]], a [[Boot Image>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Boot Images.WebHome]], and optionally a [[product key>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Produktschlüssel.WebHome]].
1.1	6
63.1	7	The Rollout Template overview displays all available Rollout Templates in a table format, including all values.
1.1	8
63.1	9	= Add Rollout Template =
5.1	10
63.1	11	To add a new rollout template, click the //Add// button in the //Rollout Templates// section of the ribbon bar.
1.1	12
63.1	13	A wizard will open. On the first page of the wizard, enter a name for the template and, optionally, a description.
1.1	14
63.1	15	You then have several options:
1.1	16
63.1	17	* Rollout template can be selected on the client
1.1	18
63.1	19	If a Rollout Template is marked as interactive, it can be selected when rolling out a machine via a physical boot medium, provided that no other template has been assigned to the system yet.
58.1	20
63.1	21	* Create a new ACMP Client
58.1	22
63.1	23	This option is primarily intended for physical boot media used, for example, in a rollout environment where the same network adapter is always used.
58.1	24
63.1	25	* Create a certificate for the ACMP Gateway
58.1	26
	27	{{aagon.versionierungsbox}}
63.1	28	This option is available starting with ACMP version 6.2.
58.1	29	{{/aagon.versionierungsbox}}
	30
63.1	31	This option allows you to automatically create a client certificate for the ACMP Gateway during the Rollout. This is particularly useful for laptops used outside the company network—such as when working from home or in the field.
58.1	32
63.1	33	Then click //Next >.//
58.1	34
63.1	35	[[Add Rollout Template>>image:67_OS Deployment_Rollout Template_969.png]]
16.1	36
63.1	37	The next step is to configure the Rollout Template. To do this, select an [[operating system>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Betriebssysteme.WebHome]], a [[answer files>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Antwortdateien.WebHome]], the edition, the [[Boot Image>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Boot Images.WebHome]], and the [[product key>>doc:ACMP.610.ACMP-Solutions.OS Deployment.Windows Deployment.Produktschlüssel.WebHome]].
3.2	38
1.1	39	(% style="text-align:center" %)
27.1	40	[[image:XWiki.Images.WebHome@hmfile_hash_0aaa2c28.png\|\|alt="19.1 - Rollout Template konfigurieren" height="595" width="786"]]
63.1	41	Configure the Rollout Template
1.1	42
	43	{{aagon.infobox}}
63.1	44	We recommend using a Windows image without the ACMP Agent installed for OS Deployment.
1.1	45	{{/aagon.infobox}}
	46
63.1	47	If an ACMP Agent is already installed, various errors may occur:
1.1	48
63.1	49	* The client's computer name will actually be displayed incorrectly until the Rollout is finished and the computer scanner has re-inventoried the client
	50	* Post deployment is not executed and the Rollout is not finished
1.1	51
	52	{{aagon.infobox}}
63.1	53	Please note that a valid product key is required for both the Windows 10 Education Edition and the Windows 10 Multiple Edition. It is not possible to deploy these editions without a valid product key.
1.1	54	{{/aagon.infobox}}
	55
63.1	56	In the third step, you can specify the [[Job Collections>>doc:ACMP.610.ACMP-Solutions.Jobs.Job Collections.WebHome]] to be integrated into the Rollout Template. Alternatively, you can create a new Job Collection.
3.2	57
63.1	58	The jobs should execute during the Rollout process after the operating system has been installed.
60.1	59
	60	{{aagon.infobox}}
63.1	61	Please note that Job Collections are executed in the specified order. The top Job Collection is processed first.
60.1	62	{{/aagon.infobox}}
	63
63.1	64	[[Add jobs to the Rollout Template>>image:Rollout Template_Job Collections.png\|\|data-xwiki-image-style-alignment="center" height="608" width="800"]]
3.2	65
63.1	66	In the next step, you can choose whether to lock the computer during the Rollout. By default, the computer can be unlocked with a password during the Rollout. You can also disable this option.
	67	In the next step, select the driver packages to install. The selected driver packages are not integrated into the operating system’s Install.wim file; instead, they are integrated into the operating system—which has already been copied to the target computer’s disk—during installation via Windows Update. This integration takes place before the system is started for the first time.
3.2	68
1.1	69	{{aagon.warnungsbox}}
63.1	70	During setup, Windows automatically integrates all drivers specified in the Rollout Template. These drivers are downloaded from the available file repositories, which can result in higher network traffic and longer installation times if there are many drivers. Therefore, please verify in advance that all drivers are fully available in the repository you are using.
1.1	71	{{/aagon.warnungsbox}}
	72
63.1	73	[[Add driver to Rollout Template>>image:Rollout Template_Treiber.png\|\|data-xwiki-image-style-alignment="center" height="608" width="800"]]
5.1	74
63.1	75	In the final step, you can view the status of the file repositories and the synchronization status. If you notice that not all required templates have been synchronized in a full manner to the file repository, you can use the option //Synchronize all templates with the $Name$ file repository// to perform the synchronization.
1.1	76
	77	(% style="text-align:center" %)
27.1	78	[[image:XWiki.Images.WebHome@hmfile_hash_e707036b.png\|\|alt="19.2 - File Repository Status" height="446" width="590"]]
1.1	79	File Repository Status
	80
	81	{{aagon.infobox}}
63.1	82	When deploying an operating system image in VMware Workstation, make sure to select the “Thick” option for partitioning.
1.1	83	{{/aagon.infobox}}
	84
63.1	85	Click //Done// to exit creating the Rollout Template. You can now [[perform the Rollout>>doc:\|\|anchor="HPerformaRollout"]].
4.1	86
63.1	87	= Perform a Rollout =
1.1	88
63.1	89	You can apply a saved Rollout Template to all clients that have not been decommissioned and for which a MAC address has been stored.
1.1	90
	91	{{aagon.infobox}}
63.1	92	During the Rollout, we use Windows Autologon multiple times. To ensure that the network is ready, we set the “SyncForegroundPolicy” flag in the registry under “HKLM\Software\Policies\Microsoft\Windows NT\CurrentVersion\Winlogon”.
1.1	93	{{/aagon.infobox}}
	94
	95	{{aagon.warnungsbox}}
63.1	96	If you have explicitly disabled the “Always wait for the network at computer startup and logon” setting in Group Policy, the “SyncForeGroundPolicy” flag we set will be overridden, which may result in errors.
1.1	97	{{/aagon.warnungsbox}}
	98
63.1	99	To use a Rollout Template for a rollout, you have the following options.
1.1	100
63.1	101	* Execute a Query and select the Clients on which you want to perform a rollout. Right-click to open the context menu. In the context menu, select Rollout.
	102	* Execute a Query and select the Clients on which a Rollout is to be performed. Now navigate to the Rollout Templates and, while holding down the left mouse button, drag the selected Clients onto the Rollout Template to be used.
	103	* Navigate to the Rollout Templates and select the Rollout Template you want to use. Now select Rollout from the ribbon and add one or more Clients to the Rollout Template. If you have already selected Clients in a Query, they will be added directly to the Rollout Template.
1.1	104
	105	{{figure}}
3.2	106	[[image:65_Rollout Template_Rollout Übersicht_883.png\|\|data-xwiki-image-style-alignment="center"]]
1.1	107
	108	{{figureCaption}}
63.1	109	Client selected for Rollout
1.1	110	{{/figureCaption}}
	111	{{/figure}}
	112
63.1	113	In this window, you can specify a Rollout Template and a product key for the client. The computer description is taken from the specified client but can be customized.
1.1	114
	115	{{aagon.infobox}}
63.1	116	If a product key has been specified in the Rollout Template, it is automatically entered when the Rollout Template is selected. You can override the product key to be used for the Rollout.
1.1	117	{{/aagon.infobox}}
	118
63.1	119	To include additional clients in the Rollout, select the Add Clients command ([[image:XWiki.Images.WebHome@client_add_zoom25.png\|\|alt="Client_Add" height="15" width="15"]]). In the window that opens, execute a Query and select the client you want to add. If necessary, remove an existing client using the Remove Selected Client command ([[image:XWiki.Images.WebHome@client_delete_zoom25.png\|\|alt="Client_Delete" height="16" width="16"]]). You can also create number profiles within the Rollout to ensure the automatic generation of computer names.
	120
1.1	121
	122	{{aagon.infobox}}
63.1	123	Please note that if you use number profiles, you will no longer be able to change the computer name manually.
1.1	124	{{/aagon.infobox}}
	125
63.1	126	You can access three wizards via the menu.
1.1	127
	128	\|(((
27.1	129	[[image:rollouttemplate_assigntoallclients.png\|\|alt="RolloutTemplate_AssignToAllClients" data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	130	)))\|(((
63.1	131	Opens a wizard for selecting a Rollout Template, which is then assigned to all selected Clients.
1.1	132	)))
	133	\|(((
27.1	134	[[image:XWiki.Images.WebHome@productkey.png\|\|alt="ProductKey" data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	135	)))\|(((
63.1	136	This wizard is optional. If you do not use a key in a Rollout Template, you can use this wizard to assign a product key to the client immediately before the rollout.
1.1	137	)))
	138	\|(((
27.1	139	[[image:rollouttemplate_generatecomputernames.png\|\|alt="RolloutTemplate_GenerateComputerNames" data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	140	)))\|(((
63.1	141	If you want to roll out multiple clients, ACMP can help you name the computers. This involves using a prefix and/or suffix in combination with a continuous number. This is done via the number profiles.
1.1	142	)))
	143
63.1	144	== Assign a Rollout Template to all clients ==
1.1	145
63.1	146	Open the wizard to assign Rollout Templates. The selected Rollout Template will be assigned to all Clients, overwriting any prior items.
1.1	147
	148	{{aagon.infobox}}
63.1	149	If you set a filter before starting the wizard, the Rollout Template will be assigned only to the Clients that are displayed.
1.1	150	{{/aagon.infobox}}
	151
	152	(% style="text-align:center" %)
27.1	153	[[image:XWiki.Images.WebHome@hmfile_hash_0040b52a.png\|\|alt="20.2 - Template zuweisen" height="387" width="607"]]
63.1	154	Select a Rollout Template for all Clients
1.1	155
63.1	156	== Assign a product key to all clients ==
1.1	157
63.1	158	ÜThis wizard allows you to assign a product key to all clients, regardless of the product key specified in the Rollout Template.
1.1	159
	160	{{aagon.infobox}}
63.1	161	If you set a filter before starting the wizard, the product key will be assigned only to the Clients that are displayed.
1.1	162	{{/aagon.infobox}}
	163
	164	(% style="text-align:center" %)
27.1	165	[[image:XWiki.Images.WebHome@hmfile_hash_640428fb.png\|\|alt="20.3 - Produktschlüssel zuweisen" height="474" width="675"]]
63.1	166	Select product keys for all Clients
1.1	167
63.1	168	== Generate Computer Names ==
1.1	169
63.1	170	This wizard helps you assign unique computer names during the Rollout.
1.1	171
63.1	172	To do this, enter a starting and ending range and specify the number of leading zeros. Name prefixes and suffixes complete the computer names to be generated. When you switch input fields, a preview of the first generated computer name is displayed.
59.1	173
63.1	174	After clicking //Generate//, the new computer names are created using the number profiles, and the window closes. Therefore, if you need to make changes in either of the two windows, you must switch between the sections before exiting your work there.
59.1	175
1.1	176	{{aagon.infobox}}
63.1	177	Please note that the computer name is generated based on the computer name profile being used. This means that you cannot manually change the computer name as long as you are using a computer name profile. This ensures that the ACMP Server assigns unique names.
1.1	178	{{/aagon.infobox}}
	179
	180	{{figure}}
3.2	181	[[image:65_Rollout Template_Computernamen generieren_623.png\|\|data-xwiki-image-style-alignment="center"]]
1.1	182
	183	{{figureCaption}}
63.1	184	Generate computer names
1.1	185	{{/figureCaption}}
	186	{{/figure}}
	187
	188	{{figure}}
3.2	189	[[image:65_Rollout Template_Nummernprofile_689.png\|\|data-xwiki-image-style-alignment="center"]]
1.1	190
	191	{{figureCaption}}
63.1	192	Assign a number profile
1.1	193	{{/figureCaption}}
	194	{{/figure}}
	195
	196	{{aagon.infobox}}
63.1	197	If the number specified at the end of the range is smaller than the number of Clients selected for the Rollout, computer names will be generated only for the specified number (from top to bottom). For all subsequent computers, the current computer name will be used.
1.1	198	{{/aagon.infobox}}