After reading the title of this article I’m sure you’re saying, ‘You can’t change VCSA hostname. You have to redeploy.’ That is what I was told and all the documentation I have read says you have to redeploy. Well it is not true. With that said here is your warning about mucking with the VCSA configuration. Don’t do it! Unless you are working in your test environment and you came across a ‘workaround’ that you wanted to try. I still wouldn’t recommend using this ‘workaround’ in your production environment without extensive testing and upon recommendation from VMware Support.
Why did I need to change the hostname in my test lab? I applied 6.5 U1 to the VCSA in my test lab. I then checked the VCSA and saw that the hostname was changed to ‘localhost’ and AD authentication was broken. It also broke ssl certificates. I was getting ready to redeploy the VCSA when I came across this ‘workaround’ and I gave it a try. It worked great.
Change VCSA 6.5 U1 Hostname with vami_config_net
The ‘workaround’ is really a built in utility called vami_config_net. The full name of this utility is configure-network command-line utility. Here is what the utility looks like in use with relevant configuration names blacked out.
Option # 3 will prompt with ‘New hostname’ and show the current hostname. I made this change in my test lab and it did not require a reboot to start working. However, I made this change after the VCSA had lost domain trust. I had to take the VCSA completely out of the domain, delete the computer object, and join it to the domain again. The VCSA is working wonderfully once more.
If I had tried to change the ip address it would have failed without changing the dns to reflect this before making the change. In this very limited use case vami_config_net worked because I changed the hostname back to the original name. I would not have faith in using this utility to just to change from one hostname to a completely different hostname until I have tested further.
More info on vami_config_net
Let me know if this article helps you. Please share your experiences with vami_config_net. I look forward to hearing from you!