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

Preparing for capture

Preparing for capture

Follow the best practices for capturing images, such as ensuring that the image is up-to date and that there is enough space on the appliance for the image.

The Quest KACE Support team provides best practices for capturing images. For more information, see, https://support.quest.com/kace-systems-deployment-appliance/kb/121734.

Best practices to prepare for capturing images for deployment:

•
Ensure that there is 20 percent free space on the appliance.
•
Use only the volume license media instead of the OEM media.
•
Create an administrator profile to set up as the default administrator user.
•
Capture a non-sysprepped version of your primary image first in case you have to restore the image to the original device.
•
Sysprep the image.
•
Capture a sysprepped image to the appliance and verify that there is enough space on the appliance for the image.

Capture system images

Capture system images

You can capture images with the KACE Systems Deployment Appliance or remote (RSA) appliances, after you boot the device in to the KACE Boot Environment (KBE).

Run the Sysprep tool on the image to remove any system-specific settings before you boot the device in to the KBE. Quest KACE recommends capturing a non-sysprepped version of your gold image first in case you have to restore the image to the original device.

After the device boots in to the KBE, you can access the built-in VNC remote control software to capture images from remote devices to the KACE Systems Deployment Appliance.

* 
IMPORTANT: Capture of OEM images for purposes of deployment to machines other than the one it is captured from is a violation of Microsoft's Licensing agreement. To create an image for deployment to multiple machines ensure you use Microsoft Volume License Media. Please reference KB 135252 for full details and a link to Microsoft's Licensing brief on re-imaging rights.
1.
Boot the device with the image that you want to capture in to the KBE. From the KBE Main Menu on the device, click Imaging.
* 
TIP: The information appearing at the bottom of this screen provides details about the KACE Systems Deployment Appliance or RSA connected to this KBE, such as its IP address, OS version, architecture, boot mode, Mac address, and other relevant data.
If the device boots in to the hard drive instead of the KBE, boot the device in to the KBE.
2.
Click Capture image of this device.
3.
In Image Name, enter a name that identifies the image on the appliance.
4.
In Image Type, select the type of the image file that you want to create, as required.
5.
If you want to capture the image directly to the server, select Capture directly to server.
When an image is captured locally, it is sent to the server through network sockets. Some network configurations may cause issues when files are transferred this way. Streaming the image directly to the server causes its files to be copied directly to the server share instead of using network sockets.
Only those images captured directly from the server can also be deployed directly from the server.
◦
WIM images captured directly to the server must also be deployed directly from the server. This option cannot be changed on the image detail page.
◦
If you choose not to select this option, and there is not enough disk space locally, the image is streamed directly to the server.
6.
Click Force continue on errors to continue the capture and the upload process even if warnings and fatal errors occur.
7.
Click Include debug output in log to enable debugging level logging and upload the logs to the Appliance Logs page.
Turning on debugging might increase the time it takes to capture and upload the image.
8.
Click Start capture.
◦
A progress bar appears at the bottom of the page, indicating how much progress has been made through the task for each selected partition. You have an option to cancel the capture, if required.
◦
When the capture process is complete, a new system image entry appears on the System Images page in the KACE Systems Deployment Appliance Administrator Console, and also in the Remote Site Console, if the image is captured using an RSA.
◦
If the user subscribed to this UI notification, a notification icon appears in the KACE Systems Deployment Appliance Administrator Console, and also in the Remote Site Console, indicating when the image capture starts, fails, or finishes.
◦
The KACE Systems Deployment Appliance assigns an ID to each captured system image.
* 
TIP: Each system image captured with the KACE Systems Deployment Appliance or its linked RSAs has a unique ID. This allows the appliance to keep track of all the different system images captured with the linked (KACE Systems Deployment Appliance) or remote (RSA) appliances, and to synchronize any images, as you edit them. To find out an ID of a specific system image, hover over the system image name on the System Images page. The ID appears in the bottom-left corner.
* 
NOTE: An image captured on an RSA is only stored on the RSA and does not synchronize. After configuring an image captured from an RSA, on the KACE Systems Deployment Appliance, synchronize that RSA prior to deployment.
Configure the image with all of the required files, tools, and software using a deployment task sequence. You can edit some images or specify their deployment tasks, as required. For more information, see the following topics:
•
Edit a system image
•
Assign tasks to system deployment
.

Create a single partition

Create a single partition

You can add the built-in Create Single Partition pre-installation task to create a single primary partition.

1.
On the left navigation pane, click Library to expand the section, then click Pre-installation Tasks to display the Pre-installation Tasks page.
2.
Select Create Single Partition to display the Pre-installation Task Detail page.
3.
Optional: In Name, change the name to identify the task.
4.
Enter a script to create a partition.
5.
In Notes, add a note to identify the task.
6.
Click Save.
The task is now available to assign to scripted installations, sysprepped system images, and non-sysprepped system image deployments.

Format C drive as NTFS

Format C drive as NTFS

You can add the built-in Format C: as NTFS pre-installation task to format and set the C drive as an NTFS file system.

1.
On the left navigation pane, click Library to expand the section, then click Pre-installation Tasks to display the Pre-installation Tasks page.
2.
Select Format C: as NTFS to display the Pre-installation Task Detail page.
3.
Optional: In Name, change the name to identify the task.
4.
Click Save.
The task is now available to assign to scripted installations, sysprepped system images, and non-sysprepped system image deployments.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation