Rollout Templates

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.

4

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]].

6

7

The Rollout Template overview displays all available Rollout Templates in a table format, including all values.

8

9

= Add Rollout Template =

10

11

To add a new rollout template, click the //Add// button in the //Rollout Templates// section of the ribbon bar.

12

13

A wizard will open. On the first page of the wizard, enter a name for the template and, optionally, a description.

14

15

You then have several options:

16

17

* **Rollout template can be selected on the client**

18

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.

20

21

* **Create a new ACMP Client**

22

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.

24

25

* **Create a certificate for the ACMP Gateway**

26

27

28

This option is available starting with ACMP version 6.2.

29

30

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.

32

33

Then click //Next >.//

34

35

[[Add Rollout Template>>image:67_OS Deployment_Rollout Template_969.png]]

36

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]].

38

39

(% style="text-align:center" %)

40

[[image:XWiki.Images.WebHome@hmfile_hash_0aaa2c28.png||alt="19.1 - Rollout Template konfigurieren" height="595" width="786"]]

41

Configure the Rollout Template

42

43

44

We recommend using a Windows image without the ACMP Agent installed for OS Deployment.

45

46

47

If an ACMP Agent is already installed, various errors may occur:

48

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

51

52

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.

54

55

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.

57

58

The jobs should execute during the Rollout process after the operating system has been installed.

59

60

61

Please note that Job Collections are executed in the specified order. The top Job Collection is processed first.

62

63

64

[[Add jobs to the Rollout Template>>image:Rollout Template_Job Collections.png||data-xwiki-image-style-alignment="center" height="608" width="800"]]

65

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.

68

69

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.

71

72

73

[[Add driver to Rollout Template>>image:Rollout Template_Treiber.png||data-xwiki-image-style-alignment="center" height="608" width="800"]]

74

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.

76

77

(% style="text-align:center" %)

78

[[image:XWiki.Images.WebHome@hmfile_hash_e707036b.png||alt="19.2 - File Repository Status" height="446" width="590"]]

79

File Repository Status

80

81

82

When deploying an operating system image in VMware Workstation, make sure to select the “Thick” option for partitioning.

83

84

85

Click //Done// to exit creating the Rollout Template. You can now [[perform the Rollout>>doc:||anchor="HPerformaRollout"]].

86

87

= Perform a Rollout =

88

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.

90

91

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”.

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.

97

98

99

To use a Rollout Template for a rollout, you have the following options.

100

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.

104

105

106

[[image:65_Rollout Template_Rollout Übersicht_883.png||data-xwiki-image-style-alignment="center"]]

107

108

109

Client selected for Rollout

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.

114

115

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.

117

118

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.

Please note that if you use number profiles, you will no longer be able to change the computer name manually.

124

125

126

You can access three wizards via the menu.

127

128

|(((

129

[[image:rollouttemplate_assigntoallclients.png||alt="RolloutTemplate_AssignToAllClients" data-xwiki-image-style-alignment="center" height="32" width="32"]]

130

)))|(((

131

Opens a wizard for selecting a Rollout Template, which is then assigned to all selected Clients.

132

)))

133

|(((

134

[[image:XWiki.Images.WebHome@productkey.png||alt="ProductKey" data-xwiki-image-style-alignment="center" height="32" width="32"]]

135

)))|(((

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.

137

)))

138

|(((

139

[[image:rollouttemplate_generatecomputernames.png||alt="RolloutTemplate_GenerateComputerNames" data-xwiki-image-style-alignment="center" height="32" width="32"]]

140

)))|(((

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.

142

)))

143

144

== Assign a Rollout Template to all clients ==

145

146

Open the wizard to assign Rollout Templates. The selected Rollout Template will be assigned to all Clients, overwriting any prior items.

147

148

149

If you set a filter before starting the wizard, the Rollout Template will be assigned only to the Clients that are displayed.

150

151

152

(% style="text-align:center" %)

153

[[image:XWiki.Images.WebHome@hmfile_hash_0040b52a.png||alt="20.2 - Template zuweisen" height="387" width="607"]]

154

Select a Rollout Template for all Clients

155

156

== Assign a product key to all clients ==

157

158

ÜThis wizard allows you to assign a product key to all clients, regardless of the product key specified in the Rollout Template.

159

160

161

If you set a filter before starting the wizard, the product key will be assigned only to the Clients that are displayed.

162

163

164

(% style="text-align:center" %)

165

[[image:XWiki.Images.WebHome@hmfile_hash_640428fb.png||alt="20.3 - Produktschlüssel zuweisen" height="474" width="675"]]

166

Select product keys for all Clients

167

168

== Generate Computer Names ==

169

170

This wizard helps you assign unique computer names during the Rollout.

171

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.

173

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.

175

176

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.

[[image:65_Rollout Template_Computernamen generieren_623.png||data-xwiki-image-style-alignment="center"]]

182

183

184

Generate computer names

[[image:65_Rollout Template_Nummernprofile_689.png||data-xwiki-image-style-alignment="center"]]

190

191

192

Assign a number profile

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.

198

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		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.
		4
		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]].
		6
		7	The Rollout Template overview displays all available Rollout Templates in a table format, including all values.
		8
		9	= Add Rollout Template =
		10
		11	To add a new rollout template, click the //Add// button in the //Rollout Templates// section of the ribbon bar.
		12
		13	A wizard will open. On the first page of the wizard, enter a name for the template and, optionally, a description.
		14
		15	You then have several options:
		16
		17	* Rollout template can be selected on the client
		18
		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.
		20
		21	* Create a new ACMP Client
		22
		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.
		24
		25	* Create a certificate for the ACMP Gateway
		26
		27	{{aagon.versionierungsbox}}
		28	This option is available starting with ACMP version 6.2.
		29	{{/aagon.versionierungsbox}}
		30
		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.
		32
		33	Then click //Next >.//
		34
		35	[[Add Rollout Template>>image:67_OS Deployment_Rollout Template_969.png]]
		36
		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]].
		38
		39	(% style="text-align:center" %)
		40	[[image:XWiki.Images.WebHome@hmfile_hash_0aaa2c28.png\|\|alt="19.1 - Rollout Template konfigurieren" height="595" width="786"]]
		41	Configure the Rollout Template
		42
		43	{{aagon.infobox}}
		44	We recommend using a Windows image without the ACMP Agent installed for OS Deployment.
		45	{{/aagon.infobox}}
		46
		47	If an ACMP Agent is already installed, various errors may occur:
		48
		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
		51
		52	{{aagon.infobox}}
		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.
		54	{{/aagon.infobox}}
		55
		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.
		57
		58	The jobs should execute during the Rollout process after the operating system has been installed.
		59
		60	{{aagon.infobox}}
		61	Please note that Job Collections are executed in the specified order. The top Job Collection is processed first.
		62	{{/aagon.infobox}}
		63
		64	[[Add jobs to the Rollout Template>>image:Rollout Template_Job Collections.png\|\|data-xwiki-image-style-alignment="center" height="608" width="800"]]
		65
		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.
		68
		69	{{aagon.warnungsbox}}
		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.
		71	{{/aagon.warnungsbox}}
		72
		73	[[Add driver to Rollout Template>>image:Rollout Template_Treiber.png\|\|data-xwiki-image-style-alignment="center" height="608" width="800"]]
		74
		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.
		76
		77	(% style="text-align:center" %)
		78	[[image:XWiki.Images.WebHome@hmfile_hash_e707036b.png\|\|alt="19.2 - File Repository Status" height="446" width="590"]]
		79	File Repository Status
		80
		81	{{aagon.infobox}}
		82	When deploying an operating system image in VMware Workstation, make sure to select the “Thick” option for partitioning.
		83	{{/aagon.infobox}}
		84
		85	Click //Done// to exit creating the Rollout Template. You can now [[perform the Rollout>>doc:\|\|anchor="HPerformaRollout"]].
		86
		87	= Perform a Rollout =
		88
		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.
		90
		91	{{aagon.infobox}}
		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”.
		93	{{/aagon.infobox}}
		94
		95	{{aagon.warnungsbox}}
		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.
		97	{{/aagon.warnungsbox}}
		98
		99	To use a Rollout Template for a rollout, you have the following options.
		100
		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.
		104
		105	{{figure}}
		106	[[image:65_Rollout Template_Rollout Übersicht_883.png\|\|data-xwiki-image-style-alignment="center"]]
		107
		108	{{figureCaption}}
		109	Client selected for Rollout
		110	{{/figureCaption}}
		111	{{/figure}}
		112
		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.
		114
		115	{{aagon.infobox}}
		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.
		117	{{/aagon.infobox}}
		118
		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
		121
		122	{{aagon.infobox}}
		123	Please note that if you use number profiles, you will no longer be able to change the computer name manually.
		124	{{/aagon.infobox}}
		125
		126	You can access three wizards via the menu.
		127
		128	\|(((
		129	[[image:rollouttemplate_assigntoallclients.png\|\|alt="RolloutTemplate_AssignToAllClients" data-xwiki-image-style-alignment="center" height="32" width="32"]]
		130	)))\|(((
		131	Opens a wizard for selecting a Rollout Template, which is then assigned to all selected Clients.
		132	)))
		133	\|(((
		134	[[image:XWiki.Images.WebHome@productkey.png\|\|alt="ProductKey" data-xwiki-image-style-alignment="center" height="32" width="32"]]
		135	)))\|(((
		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.
		137	)))
		138	\|(((
		139	[[image:rollouttemplate_generatecomputernames.png\|\|alt="RolloutTemplate_GenerateComputerNames" data-xwiki-image-style-alignment="center" height="32" width="32"]]
		140	)))\|(((
		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.
		142	)))
		143
		144	== Assign a Rollout Template to all clients ==
		145
		146	Open the wizard to assign Rollout Templates. The selected Rollout Template will be assigned to all Clients, overwriting any prior items.
		147
		148	{{aagon.infobox}}
		149	If you set a filter before starting the wizard, the Rollout Template will be assigned only to the Clients that are displayed.
		150	{{/aagon.infobox}}
		151
		152	(% style="text-align:center" %)
		153	[[image:XWiki.Images.WebHome@hmfile_hash_0040b52a.png\|\|alt="20.2 - Template zuweisen" height="387" width="607"]]
		154	Select a Rollout Template for all Clients
		155
		156	== Assign a product key to all clients ==
		157
		158	ÜThis wizard allows you to assign a product key to all clients, regardless of the product key specified in the Rollout Template.
		159
		160	{{aagon.infobox}}
		161	If you set a filter before starting the wizard, the product key will be assigned only to the Clients that are displayed.
		162	{{/aagon.infobox}}
		163
		164	(% style="text-align:center" %)
		165	[[image:XWiki.Images.WebHome@hmfile_hash_640428fb.png\|\|alt="20.3 - Produktschlüssel zuweisen" height="474" width="675"]]
		166	Select product keys for all Clients
		167
		168	== Generate Computer Names ==
		169
		170	This wizard helps you assign unique computer names during the Rollout.
		171
		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.
		173
		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.
		175
		176	{{aagon.infobox}}
		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.
		178	{{/aagon.infobox}}
		179
		180	{{figure}}
		181	[[image:65_Rollout Template_Computernamen generieren_623.png\|\|data-xwiki-image-style-alignment="center"]]
		182
		183	{{figureCaption}}
		184	Generate computer names
		185	{{/figureCaption}}
		186	{{/figure}}
		187
		188	{{figure}}
		189	[[image:65_Rollout Template_Nummernprofile_689.png\|\|data-xwiki-image-style-alignment="center"]]
		190
		191	{{figureCaption}}
		192	Assign a number profile
		193	{{/figureCaption}}
		194	{{/figure}}
		195
		196	{{aagon.infobox}}
		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.
		198	{{/aagon.infobox}}

Wiki source code of Rollout Templates