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. |
2. |
3. |
4. |
5. |
6. |
You can rename, replace, remove, or edit K-Images and WIM images.
The System Image 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. For Windows K-Images and WIM images, it also indicates if an image is sysprepped.
You can only edit system images on the appliance that captured them. For example, if you view the details of a system image captured by the KACE SDA, you can edit that image on the System Image Detail page in the KACE SDA Administrator Console, but not in the KACE Remote Appliance Console. If that system image is captured on the KACE SDA and synced to the RSA, the System Image Detail page in the KACE Remote Appliance Console only allows you to review the system image details, but not to edit them. A link appears on this page that allows you to quickly navigate to the System Image Detail in the KACE SDA Administrator Console, and edit the system image, as required.
The Browse Files option is only available for system images.
1. |
2. |
Click Browse Files to open the Browsing Files dialog box to edit the images with the following options: |
▪ |
Click Add Drive to add a partition. The drive name must contain an uppercase letter with a colon at the end. |
◦ |
▪ |
To add a directory, click Add Directory, then type the name of the new directory that you want to add. |
▪ |
▪ |
3. |
When you finish your edits, click Cancel to roll back the changes, or Save to apply the changes to the image. |
4. |
Optional: Under Deploy Options, select Remove local files not in image when restoring the original image to a device, and when files have been added or modified on the device that is not in the original image. |
To import a WIM image, place a copy of the image file to the appliance's Samba clientdrop share.
During a WIM image import, you must specify its OS architecture. The appliance detects if the imported image is sysprepped or not.
NOTE: When the appliance starts importing a system image, if it detects an unattend file, it flags the image as sysprepped. If the image does not include that file, the appliance flags it as not being sysprepped. |
1. |
On the left navigation pane, click Deployments, then click System Images to display the Systems Images page. |
2. |
Select the name of the WIM image file on the Samba clientdrop share. |
4. |
5. |
Optional. When the import is complete, observe the imported image details, and make any changes, as required. |
a. |
On theSystem Images page, in the row containing the imported image, click the Name column to display the System Image Details page. |
c. |
To download the WIM image, in the Wim Management section, in the row containing the partition that you want to download, Actions column, click the Download icon. In the dialog box that appears, specify the name to give to the WIM file. Then click Save. |
NOTE: Like the original WIM image, the replacement image must also be stored in the Samba clientdrop share, in order to be accessible. |
e. |
To review the contents of the log file created during image import, click Show the log for this System Image. |
• |
• |
If not following the above KB articles, use the following guidelines:
• |
• |
If working with a machine that had previously been sysprepped, make sure to delete sysprep_succeeded.tag from windows\system32\sysprep. |
If the image is captured in WIM format, keep at least 60% of the drive space on each partition as free/available.
• |
• |
If you configured a "default" account, ensure to set it to True in the unattend.xml file. The sysprep creator wizard has an option to copy the current profile to the default profile. |
• |
When running sysprep by command line and not the Sysprep Creator/Executor, use the /generalize, /oobe, /shutdown, and the /unattend switches. |
• |
• |
• |
Use CLONEPREP=1 on the .msi Agent install if it is not intended to have the Agent to -check in, and create a KUID until the next reboot. For example: msiexec /i agent.msi HOST=blah CLONEPREP=1 |
◦ |
Use the start /wait command when deploying software through KACE SDA post-installation tasks. |
◦ |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy