08-30-2024 03:37 PM
Hello,
some scripts deployements with batch or powershell scripts seems not working anymore after upgrade to last version of lansweeper. I can see others in this forum with this issue. Is there any workaround to resolve this issue?
thank you!
Enrico
11-13-2024 12:33 PM - edited 11-13-2024 12:37 PM
With the latest version the issue seams solved.
10-30-2024 11:12 AM
Same issue here.
Using current logged on is impossible as this scripts has to run with elevated priviledges.
09-30-2024 09:11 PM
I'm also seeing the same error on deployments.
10-02-2024 03:06 PM
Dear,
There is currently an ongoing issue in 11.4.1.4 with deployments, which may occur when using "scanning credentials" to deploy a package. In that case, the wrong credential is passed, and the package is deployed by the system account.
As a workaround for now, you could try using "Currently logged on" instead. Depending on your package, this could indeed have an impact, but it could work.
We apologize for the inconvenience this is causing. We are prioritizing this to get it solved as soon as possible.
10-24-2024 05:33 PM
Has there been any movement on this. Using the "Currently logged on" option does not work in a secured environment where general users do not have access to the file locations nor installation rights.
Thank you
10-31-2024 01:55 PM
Dear,
Our development team is working on this at the moment. We should be close to a fix now. Once this is completely tested and approved, we hope to solve this soon in the next release.
Again, we apologize for the inconvenience this is causing for the customers who heavily rely on the deployment feature.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now