/build/static/layout/Breadcrumb_cap_w.png

5.3 problems on XP computers?

Hi all,

Has anyone else had issues with 5.3 agents on XP computers? I have 3 (so far) computers that cannot check in with the new agent, even after clean installs of the new agent. They will inventory once and then they will not inventory again even though they show as connected. I had this happen when I was using an earlier 5.3 agent and ended up installing the old 5.1 agent to get it to work. I'd really like to have everyone use the new agent as it seems to work better for distributions than 5.1.

Anyone else having this issue and found what is causing it?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: RichB 13 years ago
Second Degree Brown Belt
0
You're not trying to use kbscriptrunner with 5.3 clients, right? If runkbot is running in the computer's Task Manager Processes list then it may be already doing an inventory or managed install so won't respond until done.
Posted by: KevinG 13 years ago
Red Belt
0
Are you running the latest version of the 5.3 agent? (5.3.47173)
Posted by: cleitch 13 years ago
Senior Yellow Belt
0
I am not trying to use kbscriptrunner. I mean that once I've installed the agent it will check into the KBOX once after the initial install, and then nothing else will work on that agent. I can't push out scripts to it, or force inventories from the admin interface.

Yes, I am running 5.3.47173.
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