Create a configuration file

You can create your own configuration file or modify an existing one with the configuration tasks that are typically prompted for during an attended scripted installation. The type and name of the file depends on the OS used in the scripted installation. For example, for Microsoft Windows systems, you create or modify an answer file, unattend.xml, while Debian Ubuntu uses a preseed.cfg file.

1.	On the left navigation pane, click Deployments, then click Scripted Installations to display the Scripted Installations page.

2.	Select Choose Action > New to display the Create a Scripted Installation page.

3.	Enter a Name, and select the source files from the Source Media drop-down list, then click Next.

4.	Select which method to use to create the configuration file:

◦	Walk me through creating a <configuration> file for unattended setup: Creates a configuration file using the unattended Installation wizard.

NOTE: The name of the configuration file displayed in these options depends on the target platform. For example, Windows uses an answer file (unattend.xml), while Ubuntu uses a preseed file (preseed.cfg) file.

◦	Upload an existing <configuration> file for unattended setup: Uploads a configuration file for unattended installation.

◦	No <configuration> file; This will be a server-based attended setup: Creates a basic configuration file that requires user input to complete the installation.

5.	Click Walk me through creating a <configuration> file for unattended setup, then click Next.

6.	Windows only. Complete the answer form.

Set the following value in the answer file to disable the Windows 8 animation on login. Setting the value enables you to see the Task Error page on target devices:

◦	EnableFirstLogonAnimation registry key to 0 (zero).

7.	Linux only. In the Configuration step, provide the following information.

Section	Option	Description
Select Preseed Template		Click and select the template that you want to use for this configuration. The list of templates that appear depends on the previously selected platform under Source Media.
Template Data	Root Password	Specify the root password for this configuration. If you want to disable root login for the target system, select Disable root login.
	NOTE: If you choose the server template, this is the only option that appears. All of these options are available with the desktop template.
	User Account	To add a new user account using this method, select Create User Account. Any user accounts that are created this way are granted sudo access. Provide the full name, user name, and password for the account.
	Time Zone	Select the time zone for the target system.
	Time Zone Server	Specify the host name of the applicable time zone server.
	Language	Select the locale for the target system.
	Desktop GUI	Select the graphical user interface that you want to use on the target system: GNOME Desktop Environment, or KDE Desktop Environment, as applicable.   NOTE: For Ubuntu GNOME and KDE desktop deployment, the repository URL must be enabled.

NOTE: The information you provide on this page cannot be changed. If updates are required, you must create a new scripted installation with the desired configuration.

8.	Click Next to display the Pre-installation and Post-installation Tasks page, and add the required pre-installation and post-installation tasks.

9.	Windows only. Select the Task Error Handling option for how you want the appliance to respond to errors.

10.	Click Next.

The Scripted Installation Creation page displays the status.

11.	When the process completes, click Finish.

The Create a Scripted Installation page refreshes and displays the results.

12.

Optional. To view the contents of the answer or configuration file, open the Scripted Installation Detail page for the newly created scripted installation, and under Setup Configuration, click Show. You can make edits to this file, if needed. Any edits you make in the file contents affect only the selected scripted installation.

Deploy the scripted installation from Automated Deployments or as a manual deployment from the KBE Main Menu, which displays on the target device after the target device boots in to the KBE.