cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Keyline
Engaged Sweeper

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

6 REPLIES 6
SIA_URM
Engaged Sweeper II

With the latest version the issue seams solved.

SIA_URM
Engaged Sweeper II

Same issue here.

Using current logged on is impossible as this scripts has to run with elevated priviledges.

Spamhater0071
Engaged Sweeper

I'm also seeing the same error on deployments.

FrankSc
Lansweeper Tech Support
Lansweeper Tech Support

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.

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 

FrankSc
Lansweeper Tech Support
Lansweeper Tech Support

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.