![vcenter 6.5 join to domain vcenter 6.5 join to domain](https://cdn.statically.io/img/www.starwindsoftware.com/blog/wp-content/uploads/2017/08/Joining-VCSA-to-Microsoft-AD-join.png)
- #Vcenter 6.5 join to domain install#
- #Vcenter 6.5 join to domain update#
- #Vcenter 6.5 join to domain manual#
- #Vcenter 6.5 join to domain windows#
Stay tuned, there will be a more detailed blog post with examples coming soon. The final step is to decommission the external PSC using the decommission JSON template.
#Vcenter 6.5 join to domain manual#
This is actually taken care of as part of the JSON template and requires no manual intervention. But we’re not done, we still need to replicate the vSphere SSO data between the external PSC and the embedded PSC. After the PSC service gets registered on the external VCSA, its now converted to embedded.
#Vcenter 6.5 join to domain install#
We start by using the converge JSON which will install the necessary PSC RPMs on the external VCSA. There are two JSON template options, converge and decommission. Meaning migrate to the vCenter Server Appliance (VCSA) you should!
#Vcenter 6.5 join to domain windows#
Second, the convergence tool does not support Windows PSCs or vCenters Servers. This includes all the external PSCs and vCenter Servers in the vSphere SSO domains.
#Vcenter 6.5 join to domain update#
First, a vSphere environment must be running vSphere 6.7 Update 1. Before using the convergence tool there are two important prerequisites.
![vcenter 6.5 join to domain vcenter 6.5 join to domain](https://www.starwindsoftware.com/blog/wp-content/uploads/2017/08/Joining-VCSA-to-Microsoft-AD-click-System.png)
The convergence tool is available in a directory called “VCSA-Converge-CLI” on the VCSA 6.7 Update 1 ISO. vSphere 6.7 Update 1 introduces a new CLI tool to converge a PSC deployment from external to embedded. Until now customers who deployed an external PSC for ELM had no way to change their topology to an embedded PSC. Starting with vSphere 6.7 and 6.5 Update 2 the embedded deployment model supports ELM, but only for greenfield deployments. Otherwise, use the embedded deployment model for simplicity. The only reason to use an external PSC at the time was for Enhanced Linked Mode (ELM). The PSC has two deployment models, embedded and external. The role of the PSC is to manage the following vSphere SSO domain components: vSphere 6.0 introduced us to a new vCenter Server service called the PSC. VCenter Server is going back to its roots of a simplified architecture. Glad the vSphere team was able to get this nice surprise in this release. Keep in mind other features and plugins may not render well until the necessary changes are in place.
![vcenter 6.5 join to domain vcenter 6.5 join to domain](https://www.altaro.com/vmware/wp-content/uploads/2016/12/120216_1427_Howtoinstal1.png)
![vcenter 6.5 join to domain vcenter 6.5 join to domain](http://www.virtually-limitless.com/wp-content/uploads/2015/04/5.png)
In this release dark theme supports vSphere features and plugins. When switching to dark theme a blue information banner appears at the top of the screen. Now customers can switch between the traditional light theme to the new dark theme in a single click. The vSphere team has been listening and now the dark theme option is available. The second feature I want to highlight is considered one of the top feature requests. For common searches, there is also an option to save the search for future usage. These attributes include Tags, Custom Attributes, and VM power state to name a few. Customers can now search objects with a string and filter based attributes. The first is the improved searching capabilities. There are two features I want to highlight from the vSphere Client in vSphere 6.7 Update 1. This release includes smart porting over and completing the remaining features which included: Ensuring the best customer experience possible. The vSphere team also wanted to optimize the vSphere Client’s performance and workflows. Delivering a fully featured client to customers was only part of the process. The wait is finally over! We now have a fully featured vSphere client in vSphere 6.7 Update 1. Without further ado, here is what’s new in vCenter Server 6.7 Update 1. Of course, there are more new features and enhancements in this release. It now supports native vCenter Server templates (.vmtx) and Open Virtual Appliance (OVA). Another feature with enhancements in vSphere 6.7 Update 1 is Content Library. Now a single embedded deployment can move to another vSphere SSO domain. The vSphere SSO domain also is receiving more flexibility with support for embedded repointing. Customers can now convert to a simplified embedded deployment supporting the same functionality. An external Platform Services Controller (PSC) for enhanced linked mode is a thing of the past. Also, included in this release are the necessary tools for convergence and repointing. I’m referring to the HTML5 based vSphere Client, now fully featured. This release includes a single vSphere Client to manage them all. Today I’m happy to announce vSphere 6.7 Update 1 is now generally available.