Software Deployment Question

Re-adding XP machine to Kace?

10/18/2016 1082 views
I have an old XP box that management wants added back into Kace K1000. The XP box is online, so I remotely logged into the system, and determined Kace AMP Agent was already installed. So thinking I could just launch the provisioning agent and re-connect it that way, I tried. 
The agent failed with a variety of errors, usually a variation of "bad username and/or password" (nt status logon failure, or nt status bad network name) so clearly I'm doing something wrong, the question is...what?

I tried for a username/password combo of "Domain\Domain Admin name (and associated password)" and "local system name\local admin name (and associated password)" and no change.

Help please?
0 Comments   [ + ] Show comments


Community Chosen Answer

what version of client and k1000 are you at.  have you tried to uninstall and install the client cleanly from the kace server share?
Answered 10/18/2016 by: SMal.tmcc
Red Belt

All Answers

I have tried to uninstall and re-install. And it's 6.4.120756 for the server and the agent is 6.4.522
Answered 10/19/2016 by: Radium_Angel
White Belt

  • check to see if it meets requirements for 6.4
    Windows XP SP3
    Professional, Tablet PC Edition, Media Center
    If it does go to the registry and delete the kace agent id keys MachineID & InstallID and then reboot. If you have multiple orgs you may want to go to system-orgs-devices and search for it there to see if it not being filtered properly to the correct org. Check the amp.conf file to make sure the host and other settings are correct

    now that you have the newer client you can use amptools to help debug

    amptools debug=true - use this option to enable logging to troubleshoot issues with the AMP Agent

    amptools resetconf host=x.x.x.x - use this option to reconfigure the AMP Agent to default, with a new AMP Server IP Address setting
    • Thank you, I'll look into this. We have a unified Domain so that's one less issue. The 6.4.x is installed on our other XP boxes, so that shouldn't be an issue
      • another thought see if this machine has a firewall running on it
      • This content is currently hidden from public view.
        Reason: Removed by member request For more information, visit our FAQ's.
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