/build/static/layout/Breadcrumb_cap_w.png

Script not running

I have a VBS script that removes all printers connected to an old print server. The VBscript works locally and will work via KACE SMA on my machine when using my credentials. however, when I target a computer that is not mine it will show up as success but the printers are still there. 

I have tried different options and no luck. Anyone know what could be the issue?


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Golob69 2 years ago
Senior White Belt
0

Hello,
Are you running the vbscript on the remote machine with which account? A local system account, a domain account, the Kace service account?

A2SvHAAAAAElFTkSuQmCC

Can you please share the script execution result logs?

+dH5yzNZmocAAAAASUVORK5CYII=


The fact that the SMA placed the script locally in the directory "C:\ProgramData\Quest\KACE\..." and was able to execute it, even in the event of a failure after execution, the result will be displayed as successful.

The cause could be due to the execution rights of a vbscript on the client machine.


From an anti-virus or UAC parameters of the system to be attached.


A GPO can prevent the execution of Cscript or Wscript.


The script can be called from a batch to increase privileges or disable UAC.

https://stackoverflow.com/questions/11525056/how-to-create-a-batch-file-to-run-cmd-as-administratorBut in your case, I think just a problem of execution right of the vbscript


Do the test deployment with a domain administrator account ?


Best Regards

Golob69

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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