{"id":12516,"date":"2015-04-15T10:00:00","date_gmt":"2015-04-15T08:00:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=12516"},"modified":"2023-07-16T11:25:17","modified_gmt":"2023-07-16T09:25:17","slug":"vmware-vcsa-6-0-configuration-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-configuration-pt-2\/","title":{"rendered":"VMware VCSA 6.0 configuration - pt. 2"},"content":{"rendered":"

\"vcsa60configuration01\"<\/p>\n

Login to VMware vCSA 6.0 using the Windows Session authentication requires vCenter Server joined to the Active Directory domain.<\/p>\n

With the correct vCenter permissions assigned, authenticated administrators can manage the virtual infrastructure from vCSA.<\/p>\n

<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

VMware vCSA 6.0 deployment \u2013 pt. 1<\/a>
\nVMware VCSA 6.0 configuration \u2013 pt. 2<\/p>\n

 <\/p>\n

Join vCSA to Active Directory<\/h2>\n

Login to the appliance using the SSO Administrator<\/strong> credentials then click Login<\/strong>.<\/p>\n

\"vcsa60configuration02\"<\/p>\n

From main vCenter Server screen, select Administration<\/strong> section.<\/p>\n

\"vcsa60configuration03\"<\/p>\n

Select System Configuration<\/strong>.<\/p>\n

\"vcsa60configuration04\"<\/p>\n

Click on Nodes<\/strong> item and select the appliance name (vcsa60-01.nolabnoparty.local<\/em> in the example) under Nodes. In the right pane select Manage > Settings<\/strong> then click on Active Directory<\/strong> option. Click on Join<\/strong> button to configure AD settings.<\/p>\n

\"vcsa60configuration05\"<\/p>\n

Type the Domain<\/strong>, User name<\/strong> and Password<\/strong> of the Domain Administrator then click OK<\/strong>.<\/p>\n

\"vcsa60configuration06\"<\/p>\n

To join the domain you need to reboot the node. Click on the Refresh<\/strong> icon to enable vCSA to use AD authentication method.<\/p>\n

\"vcsa60configuration07\"<\/p>\n

Enter a reason for rebooting the node then click OK<\/strong>.<\/p>\n

\"vcsa60configuration08\"<\/p>\n

System reboots the node\u00a0to apply new changes.<\/p>\n

\"vcsa60configuration09\"<\/p>\n

In the Domain<\/strong> field appears the domain name just joined.<\/p>\n

\"vcsa60configuration10\"<\/p>\n

From Home > Administration<\/strong> select Configuration<\/strong> under Single Sign-On<\/strong> item and click the green plus icon<\/strong> in the right pane to add an identity source.<\/p>\n

\"vcsa60configuration11\"<\/p>\n

The Identity source type<\/strong> should be Active Directory (Integrated Windows Authentication)<\/strong> whilst the Domain name<\/strong> should report the domain previously joined. Click OK<\/strong>.<\/p>\n

\"vcsa60configuration12\"<\/p>\n

The Active Directory domain has been configured and it's listed in the Identity Source<\/strong> section.<\/p>\n

\"vcsa60configuration13\"<\/p>\n

 <\/p>\n

Grant permissions to access vCenter<\/h2>\n

To give AD users access to vCSA, we have to grant access permissions in the vCenter Server. From Home > Administration<\/strong> select Global Permissions<\/strong> section under Access Control<\/strong>. Click on the green plus icon<\/strong> to add a new User\/Group.<\/p>\n

\"vcsa60configuration14\"<\/p>\n

From the drop down menu select Administrator<\/strong> as Assigned Role<\/strong>\u00a0then click Add<\/strong> at the bottom to assign the correct User\/Group.<\/p>\n

\"vcsa60configuration15\"<\/p>\n

In the Domain<\/strong> field select the joined domain to display members then select the User\/Group you want to grant vCenter access. Click Add<\/strong> then OK<\/strong> to save the configuration.<\/p>\n

\"vcsa60configuration16\"<\/p>\n

The selected User\/Group has now access to vCenter<\/strong> Server with the Administrator role.<\/p>\n

\"vcsa60configuration17\"<\/p>\n

Login to vCSA using a domain user with permissions to access vCenter. Type the User name<\/strong> (domain\\username) and Password<\/strong> of the account to use or\u00a0thick Use Windows session authentication<\/strong> option to perform authentication against Active Directory with current user logged in Windows. Click Login<\/strong> to proceed.<\/p>\n

\"vcsa60configuration18\"<\/p>\n

The used account accesses the vCenter Server with the role assigned in previous steps. The username appears on the top right side of the screen.<\/p>\n

\"vcsa60configuration19\"<\/p>\n

 <\/p>\n

Add ESXi hosts to vCSA<\/h2>\n

From Home<\/strong>, click Hosts and Clusters<\/strong> item on the right pane of the screen to begin the configuration of the virtual environment.<\/p>\n

\"vcsa60configuration20\"<\/p>\n

First step is the Datacenter creation. Right click the vCSA name and select New Datacenter<\/strong> option.<\/p>\n

\"vcsa60configuration21\"<\/p>\n

Type the Datacenter name<\/strong> then click OK<\/strong>.<\/p>\n

\"vcsa60configuration22\"<\/p>\n

To add an Host to the datacenter, right click the vCSA and select Add Host<\/strong> option.<\/p>\n

\"vcsa60configuration23\"<\/p>\n

 <\/p>\n

Install vSphere Client<\/h2>\n

To access vCSA 6.0 using vSphere Client you need to upgrade\/install the client to the new version as well. Try login with an older client version.<\/p>\n

\"vcsa60configuration24\"<\/p>\n

The system detects you are using an older version of the client and offer to run or save the installer to perform the upgrade. Click Run the installer<\/strong> to begin installation.<\/p>\n

\"vcsa60configuration25\"<\/p>\n

The installation files are retrieved from the vCSA.<\/p>\n

\"vcsa60configuration26\"<\/p>\n

Click OK<\/strong> to continue.<\/p>\n

\"vcsa60configuration27\"<\/p>\n

Select the language for the installation then click OK<\/strong>.<\/p>\n

\"vcsa60configuration28\"<\/p>\n

The installation Wizard startup screen is shown.<\/p>\n

\"vcsa60configuration29\"<\/p>\n

Click Next<\/strong> to continue.<\/p>\n

\"vcsa60configuration30\"<\/p>\n

Accept the EULA then click Next<\/strong>.<\/p>\n

\"vcsa60configuration31\"<\/p>\n

Leave default destination folder and click Next<\/strong>.<\/p>\n

\"vcsa60configuration32\"<\/p>\n

Click Install<\/strong> to begin installation.<\/p>\n

\"vcsa60configuration33\"<\/p>\n

The vSphere Client is being installed.<\/p>\n

\"vcsa60configuration34\"<\/p>\n

When installation has completed, click Finish<\/strong> to exit the Wizard.<\/p>\n

\"vcsa60configuration35\"<\/p>\n

Open the vSphere Client, enter the vCSA parameters then click Login<\/strong>.<\/p>\n

\"vcsa60configuration36\"<\/p>\n

The Security Warning<\/strong> window is displayed. Thick Install this certificate and do not display any security warning for<\/strong>\u2026<\/strong> check box and click on Ignore<\/strong> button.<\/p>\n

\"vcsa60configuration37\"<\/p>\n

vCSA 6.0 main screen displayed from vSphere Client.<\/p>\n

\"vcsa60configuration38\"<\/p>\n

Administrators are now able to start configuring the working environment<\/strong> adding all required components hosts, clusters, network, and so on.<\/p>\n

\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"

Login to VMware vCSA 6.0 using the Windows Session authentication requires vCenter Server joined to the Active Directory domain. With the correct vCenter permissions assigned, authenticated administrators can manage the virtual infrastructure from vCSA.<\/p>\n","protected":false},"author":3,"featured_media":12478,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[241,583,1554],"class_list":["post-12516","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-appliance","tag-vcenter-en","tag-vcsa-6-0","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/12516","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=12516"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/12516\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/12478"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=12516"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=12516"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=12516"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}