Kace Agent Reporting Migrating from Physical Appliance to Virtual Appliance
Good day Ninjas,
We are in the process of migrating from our physical K1000 server to a VM. We imported our backups into the new appliance yesterday and spun it up. That part went fine, minus a couple bumps like having to re-enable to Help Desk POP settings.
Here's where I'm getting stuck, and I'm not sure what the best method for this is: Kace Agent Reporting
We have changed the DNS and the webserver names from the original appliance. I can push out a script to update the amp.config file and have the agent point to the updated address but in testing, though the update passed to a client, the client didn't start reporting into our new K1 VM, even after calling runkbot.
So I have a couple questions.
Is it better to push out the amp.config update on the original physical server before migration and allow time for the clients to update, and then do the migration?
Can I re-provision from the virtual appliance and have it update the amp.config on systems that already have the agent installed?
If I push out a new config successfully from the VM, do I need to stop and then restart the AmpAgent services to switch over and if so, what is the go-to method to do that?
Thanks,
-- Ray
We are in the process of migrating from our physical K1000 server to a VM. We imported our backups into the new appliance yesterday and spun it up. That part went fine, minus a couple bumps like having to re-enable to Help Desk POP settings.
Here's where I'm getting stuck, and I'm not sure what the best method for this is: Kace Agent Reporting
We have changed the DNS and the webserver names from the original appliance. I can push out a script to update the amp.config file and have the agent point to the updated address but in testing, though the update passed to a client, the client didn't start reporting into our new K1 VM, even after calling runkbot.
So I have a couple questions.
Is it better to push out the amp.config update on the original physical server before migration and allow time for the clients to update, and then do the migration?
Can I re-provision from the virtual appliance and have it update the amp.config on systems that already have the agent installed?
If I push out a new config successfully from the VM, do I need to stop and then restart the AmpAgent services to switch over and if so, what is the go-to method to do that?
Thanks,
-- Ray
2 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
SMal.tmcc
7 years ago
are you using the amptools command to reset?
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
resetconf host=x.x.x.xThis resets the AMPTOOLS configuration in case SSL settings are stuck in place and AMPTOOLS does not seem to get new settings in. The hostname here is set with ip address, but can be hostname or FQDN also.
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
resetconf host=x.x.x.xThis resets the AMPTOOLS configuration in case SSL settings are stuck in place and AMPTOOLS does not seem to get new settings in. The hostname here is set with ip address, but can be hostname or FQDN also.
Additionally, I'm having odd provisioning issues with my new one. For example, this tells me it was successful, but on the target PC, the agent is NOT installed:
[10/13/16 02:36:44 PM] Begin provisioning...
[10/13/16 02:36:44 PM] Executing Windows platform provisioning.
STEP 1: CONNECT TCP/SSH - SUCCESSFUL
[10/13/16 02:36:44 PM] Executing remote communications:
Initializing RPC
Connecting to ADMIN$
ERROR: Failed to open connection - NT_STATUS_LOGON_TYPE_NOT_GRANTED
STEP 3: PUSH SCRIPT\PROVISIONING - SUCCESSFUL
[10/13/16 02:36:44 PM] End of remote communications.
[10/13/16 02:36:44 PM] End provisioning run. - phillybits 7 years ago
Would you happen to know how to do the same thing in OSX?
I've found a couple of articles indicating that it is better to take the agent.dmg and repackage it with the proper server settings. I've also found what appears to be script instructions on how to do this in Kace, but I am really a novice when it comes to terminal and OSX cmds.
My goal is to be able to update existing WIN and OSX agents that are already checking in and deal with stragglers later. - phillybits 7 years ago
/Library/Application\ Support/Dell/KACE/bin/AMPTools set host=newhost
https://support.software.dell.com/k1000-systems-management-appliance/kb/146458 - SMal.tmcc 7 years ago