How to follow up a deployment task

[servicedesk]

Today a workmate deployed a package using a report with 20 targets with a 12 hours retry if the pc is offline.

At the deployment log started to appears errors like

"Result: Deployment ended: This action is only valid for products...Stop(Failure)" due step "X"

So I fix it on the fly and started to appear:

Result: Deployment ended: The operation completed successfully. Stop(Success)

All fine until here, then I noticed that the deployment was being re-deployed on machines that were succesfully deployed... now the computers are offline but lansweeper is keeps retrying, giving offline errors.

I think that my workmate re-deployed the task and thats why is keeping retrying again and again, but I'm not sure.

Can I see somewhere in Lansweeper, the status of a "deployment task" ?

Thanks

[Bert_D]

Currently there is no page that has the information you are requesting.
What i would recommend, is a quick and dirty fix: restarting your Lansweeper service.
Restarting will release all memory, actively stopping the current deployments.

If that didn't do the trick, you will need to:
a: Wait till everything is done deploying. (but I'm guessing that, since your here, you don't wanna do that )
b: Do some SQL work

If you are going for option b, you need to look up the ID of the package you are deploying.
For this you can use SQL server manager or, if you are using SQL compact, the Lansweeper report builder.

Select tsysPackages.PackageName, tsysPackages.PackageID As ID From tsysPackages

Now that you have the required ID, you can delete the configuration that is causing your deployment to (re)start.

Delete from tsyspackageschedule where packageID = 'FILL_ID_HERE'

If using SQL Compact, be aware that you need to execute/paste the delete part of the SQL code under configuration >> database scripts.
(Do note that this is normally not recommended! Always double-check your syntax!)

And you're done!

You might even have time to spare to tell your workmate to never ever deploy an untested package again.

Happy fixing!

Bert