Tchater maintenant avec le support
Tchattez avec un ingénieur du support

KACE Systems Deployment Appliance 9.0 Common Documents - Administrator Guide

About the KACE Systems Deployment Appliance Getting started Using the Dashboard Configuring the appliance Setting up user accounts and user authentication Configuring security settings Preparing for deployment Managing device inventory Using labels Creating a Windows or Linux Boot Environment Managing drivers Capturing images Capturing user states Creating scripted installations Creating a task sequence Automating deployments Performing manual deployments Managing custom deployments Managing offline deployments Imaging Mac devices About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

View the components assigned to a label

View the components assigned to a label

You can view the components assigned to a label.

1.
Go to the page for the component to which you want to view the label.
2.
Select View by > Label, and click the label name under that group.

The components assigned to that label display in the list.

Creating a Windows or Linux Boot Environment

Create a Windows boot environment
Create a Linux boot Environment
Update Windows drivers
Set new KBE as default for the appliance
Hide boot environments from the PXE boot menu
Best practices: Create a KACE Boot Environment (KBE) for Windows

You can create a KACE Boot Environment (KBE) for Windows systems using the KACE Media Manager. For Linux systems, when you upload a Linux source media, the appliance automatically creates a Linux boot environment.

For Windows boot environments, install the Windows ADK and the KACE Media Manager on the Administrator device where you installed the appliance. The Windows ADK provides network card drivers that the KBE requires to boot target devices. Target devices must be on the same network as the appliance.

You can import a KBE from a different location, by exporting the KBE from a different appliance, and saving the exported .pkg file to the appliance restore directory. See Import appliance components.

* 
NOTE: The KBE for Windows contains fonts for most scripts, such as Latin, Greek, and Cyrillic. If you add Asian fonts after you build the KBE, the appliance requires that you rebuild the KBE. By default, the embedded font support in the KBE is disabled. You can enable font support using the language options on the Language page.

Create a Windows boot environment

Create a Windows boot environment

You can use the KACE Media Manager to create a Windows KACE Boot Environment (KBE) or a NetBoot environment to boot devices to capture images and to deploy operating systems.

Download and install the KACE Media Manger. See Download and install the KACE Media Manager. For more information about this tool, see About the Media Manager.
1.
Run the Media Manager from Start > All Programs > Quest > KACE Media Manager.
2.
In Media Manager, in the left pane, click General Settings.
The General Settings page appears on the right.
* 
NOTE: This page appears by default if this is the first time you run the Media Manager.
3.
On the General Settings page, in the SDA Hostname field, enter the IP address of the appliance.
4.
In the SDA IP Address field, enter the IP address segments of the appliance.
5.
In the SDA Samba Share Password field, enter the password. This password must match the password that you entered in the SDA Samba Share Password field on the General Settings page.
* 
NOTE: If you change the Samba share password on the General Settings page, all Windows boot environments are automatically updated to use the new password.
6.
In the WAIK or WADK Path field, provide the path to the applicable Windows AIK or ADK files. For example:
◦
WinPE 10 Win10 x86 ADK C:\Program Files\Windows Kits\10
◦
WinPE 4 Win8 x64 ADK C:\Program Files(x86)\Windows Kits\8.1

If you installed the Windows ADK somewhere else, browse to and select the correct path.

7.
In Media Manager, in the left pane, click Create KBE.
The Create KBE page appears on the right.
8.
On the Create KBE page, on the General tab, in Name, review the KBE name. This automatically-generated string identifies the KBE on the appliance. You can update the KBE name, if needed.
When you upload the KBE to the appliance, the process first verifies that the name is unique on the appliance. If there is already a KBE with the same name on the appliance, an error message appears, instructing you to change the KBE name. The process creates the KBE only after a successful verification of the provided KBE name.
9.
In Architecture, select the KBE architecture you are booting in to, for example 32-bit or 64-bit.
10.
Set the language for your region from the Language drop-down list.
11.
Before you start the upload, update the WinPE related drivers necessary to boot the target device in to the KBE. See Update Windows drivers.
12.
Click Upload KBE.
The new KBE appears on the Boot Environments and Source Media pages.
Set the new KBE as the default.

Create a Linux boot Environment

Create a Linux boot Environment

When you upload a Linux source media, the appliance automatically creates a Linux boot environment.

1.
Specify the source media used to install the OS during deployment, such as CD-ROM or network install. To do that, open the Boot Environment Detail page for this KBE, and select the appropriate PXE Initrd File option.
2.
Specify one or more package repositories associated with this OS. To do that, open the Source Media Detail page associated with this KBE, and under Package Repositories, specify the URLs, as required.
3.
Optional. To save Linux packages used during the installation to the appliance, on the General Settings page (KACE Systems Deployment appliance only), or Remote Site Settings page (Remote Site Appliance only), under Linux Repository Cache Options, select Enable Repository Caching. Selecting this option speeds up deployments and decreases overall bandwidth usage in organization with a high number of managed devices.

The name of the newly created Linux boot environment is the same as the name of the Linux source media with the BE suffix. For example, if you upload a Linux source media called CentOS, the appliance assigns CentOS BE as the boot environment name.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation