You can rename, duplicate, remove, or edit scripted installations.
The Scripted Installation Detail page allows you to view the image settings, add a boot action, download the log files for the image, and set the options for how the appliance responds to errors.
The Installation Plan enables you to create a task sequence by adding the available pre-installation, mid-level, and post-installation tasks to run in the order that you place the tasks for the deployment.
1. |
On the left navigation pane, click Deployments, then click Scripted Installations to display the Scripted Installations page. |
2. |
3. |
4. |
a. |
Next to Config XML, click Show, and review the file contents that appear. The contents of the file are read only. |
b. |
a. |
Next to Task XML, click Show, and review the file contents that appear. The contents of the file are read only. |
b. |
7. |
8. |
When you finish your edits, click Cancel to roll back the changes, or Save to apply the changes to the image. |
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. |
3. |
◦ |
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. |
6. |
Windows only. Complete the answer form. |
◦ |
EnableFirstLogonAnimation registry key to 0 (zero). |
7. |
Specify the root password for this configuration. If you want to disable root login for the target system, select Disable root login. | ||||
| ||||
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. | ||||
Select the graphical user interface that you want to use on the target system: GNOME Desktop Environment, or KDE Desktop Environment, as applicable. |
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. |
11. |
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. |
For Volume licenses, enter the MAK (Multiple Activation Key) or KMS (Key Mgt System) setup key. | |
Windows 10 only. Windows 10 ISO images include all Windows editions. Click this field and select the Windows Edition that you want to install. |
Disables the automatic login of the administrator account after the specified number of boots. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center