/build/static/layout/Breadcrumb_cap_w.png

KBScriptrunner.exe has no effect

Has anyone encountered a situation where machines refuse to check in (seemingly randomly - no particular model)? I've tried uninstalling and reinstalling the KBOX client, forcing an update from Computers : Detail Item page, and of course, running KBScriptrunner.exe

What would be a good list of troubleshooting steps to follow to pinpoint the problem?

Thanks--

David

0 Comments   [ + ] Show comments

Answers (7)

Posted by: airwolf 14 years ago
Red Belt
1
http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=3&id=713&artlang=en

I've got a handful (20 or so) of my ~1700 clients that have the same issue. I'm assuming it's just some goofy client system issue (not KBOX related). I've had a KACE ticket in on this for a while, and so far I haven't been able to resolve the issue even with assistance from KACE.

In your case, the KB article may help.
Posted by: GillySpy 14 years ago
7th Degree Black Belt
1
You could run the agent debugger (updated for 5) to see if anything is "wrong" with those PCs. You have to open a ticket with support to get the debugger.
Posted by: kdasanmartino 14 years ago
Second Degree Green Belt
1
I've had something like that were they would not check in. It seemed to be on windows 2000 computers mostly
Posted by: airwolf 14 years ago
Red Belt
1
I've had the issue on XP and Vista clients. It's probably a .NET issue or some sort of application conflict. The problem is very rare and sporadic in our environment, so I'm attributing it to issues with the individual PCs.
Posted by: dtuttle 14 years ago
Purple Belt
1
Have you reinstalled the agent? Could just be a crap install....
Posted by: airwolf 14 years ago
Red Belt
1
In my case, I've reinstalled the agents several times using different methods.
Posted by: cblake 14 years ago
Red Belt
1
Make sure the agent is installing using the proper protocol for your environment (SSL on or off). Make sure there are no differences between config.xml and SMMP.conf at C:\Program Files\KACE\KBOX
We found that some files were pointing to different servers, ports, or protocols.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

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