CloudArena

Hi There, This article is for how to resolve the vRA replica nodes domain joining issues. Let me tell you the background of this issue, I have upgraded my vRA environment 7.3 to 7.6 version successfully. After the upgrade, I introduced 2 replica nodes into vRA cluster to make it distributed deployment. Once, i have added the replica nodes into vRA cluster successfully. I logged into my vRA portal default tenant and try to add these 2 nodes( which are basically called as connectors into vRA portal) to my Active Directory domain so that i can leverage the benefit of Load balancer and user authentication can be made via any nodes into the vRA cluster. On vRA portal, go to Administration Tab, under Directories Management, click on Connectors tab When i click on Join domain tab on my second Replica node, i got below error. Connector communication failed with response: Certificate for <VRA002.cloudarena.com> doesn't match common name of the certificate subject: VRA

Hello there !! I am covering this post for the configuration of LDAPS authentication for vCenter server or Platform Service controller in case of external PSC deployment. Before doing this, let me give you an important update that Microsoft gave advisory that everyone needs to enable the LDAP binding and signing at Active Directory domain controllers for secure LDAP authentication. Below are some KB articles for how to enable LDAP binding and signing at AD level. ·          KB4520412:  2020 LDAP channel binding and LDAP signing requirement for Windows ·          KB4034879:  LDAP channel binding ·          KB935834:  LDAP signing This LDAP change will affect all applications which are using LDAP authentication with AD.  So. Lets begin to change the LDAP configuration on vCenter Server 6.7 in my case here. Step 1 First check which domain controller is preferable to this vCenter server as per site. May be someone has different DCs as per sites basis.

  Hello !! Today, I am writing this post for the upgrade of vRealize Automation platform from 7.3 to 7.6 version. Let me give you a look at my current vRA infrastructure components. We have vRA 7.3 platform in distributed deployment  mode which have following components/Nodes. 3 X vRA Appliances. 2 X IAAS Web server. 2 X IAAS Manager server  2 X DEM server for ABC vCenter server Endpoint 2X DEM server for DEF vCenter server Endpoint 2X DEM server for XYZ vCenter server Endpoint 2 X SQL 2016 server All the IAAS/Manager/DEM/SQL servers are running on Windows 2012 R2 STD edition. First of all, we need to prepare for some pre-requisites for the upgrade. I have upgraded my 2 vRA distributed platform and basis on that experience, i can say it is quite difficult and you can face many issues during the upgrade. The Reason of issues is that the mixture of appliances and Windows servers on this vRealize product. So, let's don't worry about th

                          vCenter 6.5 file based Backup and Restore process Hello Everyone, This article is for how to take VCSA 6.5 file based Backup and Restore process in case of vCenter server appliance got failed due to any O/S or application issues. VCSA 6.5 has in-built feature available with management interface of vCenter server appliance 6.5 (VAMI) page. With this native Backup and Restore VCSA 6.5 features removes the dependency on third-party native backup tools to backup and restore vCenter server appliance. Native Backup feature of VCSA 6.5 supports the backup and restore of vCenter server appliance and also can take backup and restore of platform services controller. This native backup and restore feature  of VCSA 6.5 helps you to protect vCenter data and helps us to reduce the downtime required for to restore the vCenter management stack. Backup of VCSA 6.5 process collects the important files into tar bundle and compress the bundle to reduce the load on