Increasing issues with deployments hanging up

[jwood-ok]

It seems that we are having increasing issues these days where deployments, though they have a timeout set, will never time out.  Then, following deployments will get hung up.  Sometimes they seem to free up eventually, but other times not, and deployments in the meantime stack up.

Is there any way to mitigate these issues so that the deployments will just bomb out and go to the next one?  We deploy to a decent amount of laptops and devices that may not always be available, which is fine, but don't want them hanging up everything else.

[DavidPK]

Hi,

I understand your concern — what you’re describing is the classic “zombie deployment session” problem in Lansweeper’s Classic deployment module: a package that never releases its thread because Windows did not return success/failure, so the timeout you specify is not being honored and other deployments queue up.

Here’s how to mitigate this:

Go to Configuration > Deployment Settings and consider:

Lowering Maximum simultaneous deployments per agent.
Increasing the retry interval so retries don’t overlap with fresh jobs.

Make packages “skip gracefully”
Add a “pre-check” step in each package:

Use a simple command that returns quickly if the device is offline, cannot reach the share, or the software is already installed.
Exit code 3010, 0, or a custom success code ensures the package completes, letting the queue move on.

[jwood-ok]

@DavidPK Any other suggestions on accomplishing the pre-check? I think I have any idea, but would like a little bit more detail on how to go about this.

[jwood-ok]

David,

Thanks for the response.  Could you give any more details on the skip gracefully or pre-check.  I realize you put a brief description in there, but a little more detail or another post out there that goes into this would be beneficial.  I could see how what you are describing would be beneficial, just needing a little more direction on how folks have accomplished this.