/build/static/layout/Breadcrumb_cap_w.png

KACE SDA "Manual Deployments" stuck in Progress > Manual Deployments log after successful deployment

There is a long list of Manual Deployments that have successfully completed and are not clearing out from the Progress > Manual Deployments log and appearing in the Audit Log. I went to check on a few of the PCs in question to verify this and they are complete. What would cause KACE SDA not to receiving status updates during deployment and reflect the progress appropriately? This is making it difficult to track which deployments were successful and which ones aren't when I am looking through the Progress > Manual Deployments log.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 1 week ago
Red Belt
1

please check, where they stop in the UI (likely on the Run Key) so we can analyze what happened.
I assume that on the client no error is shown and all tasks run through without any error.


Comments:
  • It gets stuck on one of my custom post-installation tasks that removes the Active Directory RSAT tools but completes all the tasks without error. I was experiencing networks issues with some of the computers and the network admin told me work on our network is ongoing. It is probably not getting dhcp ip in time so it can report back to KACE SDA appliance.

    Is there a work around to have the deployment wait until the computer reports back task as complete instead of not notifying SDA its current status? - Steve2 1 week ago
Posted by: Channeler 1 week ago
Red Belt
1

Network issues (unable to resolve SDA hostname at Post Install stage a.k.a. Windows Desktop).

Or the network driver is not working. (Network driver not working for that particular NIC, or the Driver is OK but it's not picking up a valid IP, or is not picking up a valid DNS.)
Or,  OEM images are being used to image these devices.
See:
https://support.quest.com/kb/135252/using-oem-source-media-and-images



Comments:
  • I think it is network issues. I spoke with my net administrator and he said there is work ongoing on our network that may be causing this issue. I will have to report back in a few weeks once the work is done - Steve2 1 week ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ