/build/static/layout/Breadcrumb_cap_w.png

K1000: Old script keeps running

About a year ago I create an online Kscript to install a shared printer which I over deployed because my smart label criteria was messed up.  After we caught the problem I had it over deployed to about 100 to many computers world wide.  We stopped it by removing the smart label from the scripts "Deploy to".

The KScript is very simple.  It is just On Success run a batch file and the batch file text is:

 

rundll32 printui.dll,PrintUIEntry /ga /n \\MyPrintServer\SharedPrinter
net stop spooler
ping 127.0.0.1 > nul
net start spooler

We keep manually deleting this printer, but it keeps coming back.  I tried to check the C:\Programdata\Dell\Kace folders for to see if maybe the batch file is downloaded or stuck or something, but I do not see it.

I deleted the printer again and ran "runkbot 4 0" and even "1 0" thru "6 0" and the printer does not show, but tomorrow it will show up again.  How do I permanantly get rid of this?


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: jegolf 11 years ago
Red Belt
1

Look at the inventory of a machine in question and check the Scripting Logs section. It will list all scripts targeted to that machine. See if something stands out there...


Comments:
  • I think I solved my own question. The "/ga" installs for all user so even if you are an admin and you delete the printer, it comes back. You have to undo the command with "/gd" - JordanNolan 11 years ago
    • Good catch! - jegolf 11 years ago

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