/build/static/layout/Breadcrumb_cap_w.png
10/09/2018 177 views

We have a KACE K2100s SDA, that we just recently upgraded to version 6.0.425.  We also have a linked K1100s appliance running version 6.4.119927.  Since upgrading the SDA, we can no longer create system images.  When booting from the PXE KBE, when we attempt to create a new system image, two command prompt windows briefly appear, and then a popup saying "Start Capture Failed" appears. 

 

A google search for the error brought me to https://support.quest.com/kace-systems-deployment-appliance/kb/231271 .  Since our SDA doesn't have an RSA, I thought that was odd, but I went ahead and followed the recommended steps.  In the SDA Web Interface, I went to Settings->KACE Linking, and changed the "Host Name:" from the server DNS name to the IP address.  I then went to Settings->Manage Linked Appliances, clicked on the IP address of the linked K1100s appliance, and changed the "Host Name:" from the K1100s' server DNS name to its IP address.  After saving these changes and restarting the SDA, we still get the error when creating system images

 

The system images we've created in the past have been sysprepped UEFI Windows 10 Enterprise v1803 x64, with a small S drive and a larger C drive.  We have no problems deploying those system images we've previously created using the SDA.  We just can't create any new, updated ones at this point.

 

The KBE we're using was created using the latest version of the KBE Manipulator and the Windows10 v1803 Deployment Toolkit.  The SDA is located on a different subnet than the clients.  We use Inflobox DHCP for IP address management on both subnets. 

 

A few minutes after the "Start Capture Failed' error appears, a single log file appears in \\K2100s\petemp that shows just this:

 

2018-10-09 10:35:18-0500 [info] Items processed: 6 (23.83 GB)

2018-10-09 10:35:18-0500 [info] Items transferred: 1 (12.0 MB)

2018-10-09 10:35:18-0500 [info] Hashstore Client-end [1]

2018-10-09 10:35:18-0500 [info] Copy completed successfully

2018-10-09 10:35:18-0500 [info] Deploy Image - Start

2018-10-09 10:35:18-0500 [info] ...Creating temp dir: [C:\K2_2018-10-09_10-35-18]

2018-10-09 10:35:18-0500 [info] ...Deploy Directory: C:\

2018-10-09 10:35:18-0500 [info] ...Image File: C:\K2_2018-07-06_13-05-08\C.wim

2018-10-09 10:35:18-0500 [info] ...Image Dir: C:\K2_2018-07-06_13-05-08\

2018-10-09 10:35:18-0500 [info] ...Temp Directory: C:\K2_2018-10-09_10-35-18

2018-10-09 10:35:19-0500 [info] ...Deploying...

 

 

Since we can't update any of our images, we are stuck.  This same error occurs when trying to create a new system image of the non-UEFI system image, too.  Has anyone seen this error message before (and possibly found a solution for it)?


Thanks

2 Comments   [ + ] Show comments

Comments

  • I think you need to log a support call
  • make sure you have enough space on the SDA to harvest that Image.

    make sure your source system , has enough space to create a copy of itself, OR, try enabling Capture Directly to server option
    • Thanks for the response. I get the same "Start Capture Failed" error message when capturing directly.

There are no answers at this time