Rollout of K1000 did not work properly--Need to edit amp.conf
IT Ninja!
I am a first time poster here, thank you for welcoming me to IT Ninja.
Without getting into all the detail I will summarize how I got to where we are.
The installer agent that we pushed out to via a click and download installed an empty amp.config file causing the endpoint to not be added to the console. When we go into the machines manually and perform the below the endpoint checks in.
Now our question is, can and how do we build a batch file that users can click and run to essentially replace or update the amp.config file. We would manually do this, but unfortunatly we now have 600+ endpoints that have already installed the agent that is not working.
All machines are running Windows 7 Pro
1. CMD admin: c:\Program Data (x86)\Dell\KACE
2. CMD admin: amptools.exe stop
3. Explore window to replace amp conf file in c:\programdata\Dell\Kace
4. CMD admin in directory above: amptools.exe start
5. CMD admin in directory above: amptools.exe restart
Thank you very much in advance!
I am a first time poster here, thank you for welcoming me to IT Ninja.
Without getting into all the detail I will summarize how I got to where we are.
The installer agent that we pushed out to via a click and download installed an empty amp.config file causing the endpoint to not be added to the console. When we go into the machines manually and perform the below the endpoint checks in.
Now our question is, can and how do we build a batch file that users can click and run to essentially replace or update the amp.config file. We would manually do this, but unfortunatly we now have 600+ endpoints that have already installed the agent that is not working.
All machines are running Windows 7 Pro
1. CMD admin: c:\Program Data (x86)\Dell\KACE
2. CMD admin: amptools.exe stop
3. Explore window to replace amp conf file in c:\programdata\Dell\Kace
4. CMD admin in directory above: amptools.exe start
5. CMD admin in directory above: amptools.exe restart
Thank you very much in advance!
1 Comment
[ + ] Show comment
-
Just out of curiosity what version of Kbox are you using? in 6.3 amp uses auto_amp.conf. This may be the reason the amp.conf file is blank. - KACE_Mary 9 years ago
Answers (3)
Please log in to answer
Posted by:
KACE_Mary
9 years ago
For a number of customers that have experienced this issue has used a GPO to correct the amp.conf file.
Comments:
-
Kace_Mary-- We are not on a domain. - allglobaltk 9 years ago
Posted by:
SMal.tmcc
9 years ago
If they are not in a domain and they all have a common account you can use pstools - psexec to push to all machines using a txt file containing the machine names
Comments:
-
90% have a common account. I don't think that pstools makes it easy for 600 users. - allglobaltk 9 years ago
-
if you have the machine names you create a txt file and run psexec calling the file and it is hands off at that point. You just need to create the txt file. - SMal.tmcc 9 years ago
-
psexec @machines.txt -i -accepteula -u administrator -p password -d "c:\program files (x86)\dell\kace\amptools.exe host=yourk1000name" - SMal.tmcc 9 years ago
Posted by:
jknox
9 years ago
You may be able to just reset the hostname using "c:\program files (x86)\dell\kace\amptools.exe host=yourk1000name".
It stops the service, sets the host and then restarts the service. If you are using a batch file, I'd recommend forcing a check-in after it with "c:\program files (x86)\dell\kace\runkbot 4 0".
It stops the service, sets the host and then restarts the service. If you are using a batch file, I'd recommend forcing a check-in after it with "c:\program files (x86)\dell\kace\runkbot 4 0".
