/build/static/layout/Breadcrumb_cap_w.png

K1000 Effects on changing Domain and Webserver Name

Hi all

Just theoretically, what would happen if you'd change the Domain and Webserver Name of your Dell Appliance.
Both Domains have full rights on each other. Let's say the current domain is company.com and the future domain is company.local.

All the clients on which the Dell Agent is installed, will still be in company.com. Would I need to reinstall all Agents? 

Would LDAP into another Domain than itself work?

What else would I need to change or what wouldn't work after the change?

I'm curious because there is a small possibility for me having to change this soon. I hope someone has already done it and can tell me their story. 

Thanks and Regards

az


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
In theory, as long as the IP address of the K1000 stays the same after the domain change, the agents should continue to check in as long as they can resolve the IP address. Once the agents check in, any updated information like the domain or webserver should be changed in amp.conf. To make sure the transition was as seamless as possible, I would add a DNS record that points the old hostname and/or fully qualified domain name to the new one as well.
Posted by: Nico_K 11 years ago
Red Belt
2

as the agents ask the "old" system, they may not able to reconnect.

You could uninstall the agents and push the installation afterwards or do a GPO changing the amp.conf-file on the affected machines.


Comments:
  • You might have better luck using amptools.exe unisntall all-kuid and then running a script to make sure that you remove the Kuid out of the registry.
    Best of Luck! - mikesharp1 11 years ago
  • Oh location c:\program files (x86)\dell\kace - mikesharp1 11 years ago
  • kuid location registry HKEY_LOCAL_MACHINE\system\\Wow6432Node\dell\kace delete dell key. - mikesharp1 11 years ago
Posted by: jknox 11 years ago
Red Belt
2

In theory, as long as the IP address of the K1000 stays the same after the domain change, the agents should continue to check in as long as they can resolve the IP address.

Once the agents check in, any updated information like the domain or webserver should be changed in amp.conf.

To make sure the transition was as seamless as possible, I would add a DNS record that points the old hostname and/or fully qualified domain name to the new one as well.

LDAP from company.com should work just fine if the K1000 is using a company.local address so long as the LDAP server can be accessed from the .local network.

My suggestion for testing your .local implementation would be to get a virtual K1000 and restore your current back up to it (changing IP address, hostname, webserver,etc on the virtual unit during testing). This would allow you to test out your configuration without impacting your production environment.  The VK1000 can be purchased from KACE directly, or you could sign up for the trial: https://www.kace.com/trial-download

You probably wouldn't be able to test the agent switching over, but as long as you have the DNS entry to guide the agents I don't believe you should have any problems.


Comments:
  • Absolutely, Jason is right, duplicate DNS record point to new machine and give the agents time to check in and they update themselves. - jdornan 11 years ago

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