Yes - I've read the 100's of posts that point to the same KB saying you can't change the vcsa name...ever.
And other posts that say you can't even change the IP of the vcsa - and some posts that suggest you *can* change the IP, but at your own peril.
Here's my situation:
- we initially installed vcenter on a windows server using "vcenter.mydomain.local" ("mydomain.local" is not the actual name)
- we deployed vcsa 5.5 with a fresh install and, to avoid naming conflicts with the windows server, called the new vcsa "vcenter5.mydomain.local"
- we have since upgraded to vcenter 6.0 using vcsa.
- we are looking to upgrade the vcsa from 6.0 to 6.5
There are 2 concerns with the upcoming upgrade:
1. the IP address of the new vcsa *must* change - we're moving it to a new network segment.
2. We don't want to continue to be locked into "vcenter5.mydomain.local" for the web client until eternity
We have some advanced features configured - including dvSwitches, so a fresh install is not something I want to undertake for fear of breaking critical services.
Are there *any* options to address changing the name *and* IP of the vcsa?
I'd settle for changing the IP - that is non-negotiable.
I've found that it works if I create a DNS name for a different hostname (e.g., "vcsa.mydomain.local"), but the web client redirects to the "vcenter5" name, and the vCenter server still shows as "vcenter5" in the navigation pane.
I can compromise with the hostname - albeit with much grumbling and dissatisfaction. I mean, c'mon, what if someone typo'd the hostname and it is a duplicate for another critical system? Locking a hostname in for all eternity seems like a bad plan.
