サポートと今すぐチャット
サポートとのチャット

KACE Systems Deployment Appliance 9.2 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 About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

Upload packages for import

Upload packages for import

You can upload packages stored on an external device or server to the KACE Systems Deployment Appliance or Remote Site Appliance (RSA) restore directory, then import the packages to the appliance.

To import packages larger than 1.5GB, place them in the \\[appliance|RSA]_host_name\restore share directory first.
1.
On the left navigation pane, click Settings to expand the section, then click Package Management to display the Package Management page.
2.
Complete one of the following steps:
◦
On the Package Management page, click Upload Packages.
◦
On the Package Management page, click Import KACE SDA Packages On the Import List page that appears, select Choose Action > Upload Package for Import.
3.
On the Import Package page, click Select file to specify the .pkg file to import, or simply drop the file into the indicated area.
4.
Click Import Package.

The appliance adds a copy of the components to the library.

If the package contains drivers, re-cache the drivers. On the left navigation pane, click Library > Drivers, then select Choose Action > Recache Drivers to display the Managing Drivers page.

Import appliance components

Import appliance components

You can import components stored in a different location, a different appliance directly, or to a Remote Site Appliance (RSA), if the package containing the components is smaller than 1.5GB.

If you exported the database, only the Quest KACE Technical Support team can re-import the database back to the appliance.

* 
IMPORTANT: Only system images can be imported to an RSA. Any tasks included with system images imported to the RSA will be removed.
1.
On the left navigation pane, click Settings to expand the section, then click Package Management to display the Package Management page.
2.
Click Import SDA Packages to display the Import List page.
3.
Select the check box next to the package you want to import.
4.
Select Choose Action > Import Selected.
The import process starts. Be sure to allow any import operation to complete before altering any package or database configuration.
* 
NOTE: Depending on the size and number of components in the package, the import process can take several minutes to several hours. Importing images takes longer than exporting images. When you export an image, the appliance locates and packages all of the files associated with that image in to one .pkg file. When the process is reversed, the image files are checked against the appliance image store to ensure that only new files are uploaded.

The new components appear on the Package Management > Import List page.

Package components to export

Package components to export

You can export the components stored on the appliance, such as drivers, network inventory, boot environments, and tasks to a different network location. You can also export system images and user states from a Remote Site Appliance (RSA). This is useful to back up and restore components.

* 
IMPORTANT: Only system images and user states can be exported from an RSA. Any tasks included with system images exported from the RSA will be removed.

You can export the database, but you cannot re-import the database. Exporting components from the appliance is an internal task and cannot run in tandem with other internal tasks, such as re-caching drivers, creating scripted installations, or rebuilding boot environments.

1.
On the left navigation pane, click Settings to expand the section, then click Package Management to display the Package Management page.
2.
Click Export SDA Packages to display the Export List page.
3.
Select only a few components at a time; otherwise, the export cannot complete.
If the package is green, you cannot export it until you change the version number of the package, re-cache the drivers, and save any changes made to the package.

The selected export items are compressed and placed in the \[appliance|RSA]_hostname\restore share directory. A .pkg file is created for each component that you select.

* 
NOTE: While the export is processing, changing any Network, Security, or Date and Time settings causes the appliance to reboot, stop the export process, and lock the Exports feature.
4.
Select Choose Action > Export Selected.
Ensure that export completes before selecting a different export.

The packaging process starts. Exporting packages might take a few minutes to several hours to complete depending on the size of the file. The Status column indicates when each export completes.

* 
NOTE: If the status column shows Completed or Exporting next to each component, but the Currently : status in the upper-right corner displays Idle, contact the Quest KACE Technical Support to access your appliance through the tether and clear the error.

The size of the exported package is smaller than the one on the appliance, and can vary in size due to file export compression and package attachments.

Package file names

Package file names

You can import and export KACE Systems Deployment Appliance or Remote Site Appliance (RSA) components to packages. The following syntax conventions apply to package file names. Follow these guidelines when you import or export appliance packages to quickly find a particular component.

File contents

File name

Pre-installation task

Syntax: PR<ID><Unix_time_stamp>_<microseconds>

Example: PR33_1519839187_5248.pkg

Mid-level installation task

Syntax: MI<ID><Unix_time_stamp>_<microseconds>

Example: MI26_1519792380_3567.pkg

Post-installation task

Syntax: PO<ID><Unix_time_stamp>_<microseconds>

Example: PO17_1519831620_4922.pkg

Database package

Syntax: DB<ID><Unix_time_stamp>_<microseconds>

Example: DB12_1519822800_1546.pkg

KImage

Syntax: KI<ID><Unix_time_stamp>_<microseconds>

Example: KI56_1519827865_4213.pkg

Scripted installation

Syntax: SI<ID><Unix_time_stamp>_<microseconds>

Example: SI59_1519834064_2984.pkg

Driver package

Syntax: DR<ID><Unix_time_stamp>_<microseconds>

Example: DR15_1519823348_3284.pkg

Network inventory package

Syntax: NI<ID><Unix_time_stamp>_<microseconds>

Example: NI36_1519814733_1976.pkg

Custom deployment

Syntax: CU<ID><Unix_time_stamp>_<microseconds>

Example: CU88_1519794461_5889.pkg

Boot environment

Syntax: BE<ID><Unix_time_stamp>_<microseconds>

Example: BE52_1519798711_2802.pkg

Network scan

Syntax: NS<ID><Unix_time_stamp>_<microseconds>

Example: NS37_1519818962_3011.pkg

User State

Syntax: US<ID><Unix_time_stamp>_<microseconds>

Example: US27_1519805822_2846.pkg

Task Group

Syntax: TG<ID><Unix_time_stamp>_<microseconds>

Example: TG16_1519811097_1390.pkg

USMT (User State Migration Tool) Scan template

Syntax: ST<ID><Unix_time_stamp>_<microseconds>

Example: ST39_1519808167_5225.pkg

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択