- #Vcenter 6.5 join to domain how to#
- #Vcenter 6.5 join to domain install#
- #Vcenter 6.5 join to domain update#
- #Vcenter 6.5 join to domain full#
The SSO Domain name defaults to vsphere.local, but can be edited during installation of the vCenter Server to a preferred name. An SSO Domain is the domain that vSphere uses to connect vCenter Servers in a federation. An SSO Domain contains Tags, Licenses, Categories, Global Permissions, Roles, and Privileges. Let’s also recap what a vSphere Single-Sign-On (SSO) Domain is and what it contains. In the event of an issue, the vCenter Server can then be quickly restored to its last state.īy running cmsso-util domain-repoint -help from the vCenter Server appliance shell we can quickly find the usage of the command. Another important prerequisite task is taking a backup. To ensure no loss of data, take a File-Based backup of each vCenter Server before proceeding with domain repointing.
#Vcenter 6.5 join to domain update#
In vCenter Server 6.7 Update 1 and later, Embedded and External PSC deployments are supported for domain repointing. The domain-repoint sub-command of cmsso-util is available starting with vCenter Server 6.7 and supports domain repointing for External PSC deployments. In vSphere 6.7 an additional sub-command (domain-repoint) was added expanding the power of this utility. You may already be familiar with this command utility as it’s used to perform other actions in an SSO Domain such as decommissioning a PSC, or pointing a vCenter Server to another Site, etc. Repointing is handled by the CMSSO-UTIL command.
#Vcenter 6.5 join to domain how to#
Prerequisitesīefore we dive into how to leverage this feature we should discuss some of the requirements and prerequisites that must be considered prior to using it. If there is a need to repoint a vCenter Server from its current domain to a brand new SSO Domain, that is also possible. This powerful feature can not only help customers with mergers & acquisitions who may have a need to change the name of an SSO Domain but also joining two different SSO Domains into one common domain. SSO Domain Repointing was introduced to allow the repointing of a vCenter Server from one SSO Domain to another, something that was not possible in vSphere 6.0/6.5. The vCenter Server being repointed, moves from its current SSO domain and joins the other existing domain as another vCenter Server connected via Enhanced Linked Mode (ELM). Whether building new, changing, or redesigning an SSO Domain, vSphere 6.7 has a great new feature to help lessen this complexity. Remember that this is not a VMware recommend change in a production environment.Planning, designing, and architecting a vSphere SSO Domain for vCenter Server can occasionally feel complex to many VMware Administrators. Overall this process work well outside of these possible issues.
#Vcenter 6.5 join to domain install#
If the PCS was separated from the vCenter install I would not feel this would be a viable solution. If I would have done this after the machine was joined to the domain, I would have had to clean up the old DNS records. Make sure to take the VCSA completely out of the domain, delete the computer object, and join it to the domain again if it had been joined to the domain previously. I made this change and it did not require a reboot for the vCetner to be joined to the domain. This will open the menu: Select 3 to update the hostname SSH into the vCenter host as root and run the following command: Here is what the utility looks like in use with relevant configuration names blacked out.
#Vcenter 6.5 join to domain full#
The full name of this utility is configure-network command-line utility. This “workaround” is really a built-in utility called vami_config_net. Change VCSA 6.5 U1 Hostname with vami_config_net Just as I was getting ready to redeploy the VCSA, I came across this “workaround” so I decided to give it a try. I then checked the VCSA hostname and saw that the hostname was changed to ‘localhost’ when I was trying to join the vCenter to the domain. I had just installed 6.5 U1 in the production environment with the correct hostname. Now with that being said, I have made this change in a production environment with an embedded Platform Service Controller (PSC). Don’t do it! I would not recommend using this workaround in your production environment without being directed to make this change by VMware support. You have to re-install.” That is also what I have been told and all the VMware documentation has pointed to this. After reading the title of this blog I’m sure you’re thinking to yourself, “It is not possible to change the VCSA hostname.
0 kommentar(er)
