Posts

Replacing NSX-T Certificate with Custom Certificate

Image
                                Replacing NSX-T Certificate with Custom Certificate.   As part of best practice, it is always recommended to replace VMware self-signed Platform certificates with your organization's CA signed certificate. To do the same we need to create a Certificate Signing Request for the NSX Manager. NSX-T Data Center deployment install VMware self-signed certificated by default. The same can be checked by navigating to System > Certificates to view the platform certificates created by the system. By default, these are self-signed X.509 RSA 2048/SHA256 certificates for internal communication within NSX-T Data Center and for external authentication when NSX Manager is accessed using APIs or the UI.   To replace the VMware self-signed certificate with the custom cert there are four main steps:   1). Generate CSR. 2). Request the certificate from Certificate Authority. 3). Import Certificate 4). Validate and Replace the certificate on eac

Enterprise Federation using VMware Workspace One Access Connector

Image
                             Enterprise Federation using VMware Workspace One Access Connector Workspace One Access Connector. VMware Workspace ONE Access was formerly called VMware Identity Manager. It is Responsible for directory synchronization and handles some of the authentication methods between on-premises resources such as Active Directory, VMware Horizon, Citrix, and the Workspace ONE Access service. The main components of a cloud-based Workspace ONE Access implementation are described in the following table.     Please note that to perform the federation, the organization Owner needs to kick the federated setup from CSP and then can assign an Enterprise Admin role to manage the directory service and identity providers.     Authentication flow using IDP and vIDM.   The four services of the Workspace ONE Access Connector   Key requirements for the Deployment:   1). Org Owner of CSP to kick-start the federation setup from CSP and assign Enterprise Admin to manage the directory s

SRM Limitations to Protect and Recover Virtual Machines

SRM Limitations to Protect and Recover Virtual Machines There are few limitations which I will like to highlight today while protecting and recovering VM with VMware Site Recovery Manager. 1). Protection and Recovery of Virtual Machines in Suspended State . When we suspend a virtual machine, vSphere creates and saves its memory state. When the virtual machine resumes, vSphere restores the saved memory state so that the virtual machine can continue to operate without any disruption to the applications and guest operating systems that it is running. 2). Protection and Recovery of Virtual Machines with Snapshots Array-based replication supports the protection and recovery of virtual machines with snapshots, but with limitations. We can specify a custom location for storing snapshot delta files by setting the workingDir parameter in VMX files. Site Recovery Manager does not support the use of the workingDir parameter. But if you still want to protect the virtual machines with sna

VMware App Volumes 4

VMware App Volumes   VMware App Volumes is a portfolio of application and user management solutions for VMware Horizon, Citrix Virtual Apps and Desktops, and RDSH virtual environments. These solutions take desktop and application environments to the next level by providing radically faster application delivery and simplifying and unifying application and user management, while reducing IT costs by up to 70 percent.   App Volumes is available in two editions:    1).  App Volumes Advanced  – An advanced application and user management solution for enterprise customers with virtual environments powered by Horizon, Citrix Virtual Apps and Desktops, and RDSH. 2).  App Volumes Standard  – An application and user management solution for virtual environments powered by Horizon, Citrix Virtual Apps and Desktops, and RDSH.   App Volumes app delivery architecture and user environment manager helps IT reduce costs and increase productivity. Here’s how:  • Reduce

VMware vRealize Automation 7.x Troubleshooting Infra issues

Image
Troubleshooting Infra Issues in vRA 7.x     To manually troubleshoot vRA issues, we must know what all things we need to check.   1). In the vRA portal one should check the status of all the services whether the status is registered, fail or blank.   https://vRAserver_name:5480   If the status is registered than all good but if it is showing failed then it seems something is wrong with that service. If the status of service is blank it means that the service is responding but not correctly. XML link to check why services are not running are as follows:   https://vRA/component-registry/services/status/current?page=1&limit=50   2) If in the vra page one is giving Error 503 then please check below things to isolate that: -->IIS Pools -->SQL DB Connectivity -->Certificate Issues -->Service Account Issues -->Service Dependency   3). Service which need to checked to monitor load balancing is "shell-ui-app" and it can be c