Tag: vRA

vRealize Automation enabling the VMware Identity Manager GUI

4

In this blog post, I am going to show you how to enable the VMware Identity Manager GUI when it is located inside vRealize Automation. I am going to explain why you sometimes should and how the procedure is performed.

For some who don’t know, VMware vRealize Automation (vRA) is using under the covers VMware Identity Manager (vIDM). By default is the VMware Identity Manager GUI disabled after the vRealize Automation installation process. If you want to configure parts of vIDM you are configuring it through the vRealize Automation GUI.

Let’s get everybody on the same page: So you are talking about two GUIs the vRealize Automation GUI and the VMware Identity Manager GUI? Who is who, explain it to me!

vRealize Automation GUI - Displaying Active Directory Users
Here is the vRealize Automation (vRA) GUI – Displaying multiple Active Directory users

VMware Identity Manager GUI - Displaying Active Directory User
Here is the VMware Identity Manager (vIDM) GUI – Displaying an Active Directory user (by the way: the name Dick is a common name in The Netherlands)

Keep in mind: I’m not completely sure what will happen if you would configure items with the vIDM GUI. Because you are bypassing the default vRealize Automation GUI. I have done some tests and no problems were caused in my Lab environment but it might cause issues later on… So why do you enable it then? Because of the large amount of information provided throughout the vIDM GUI. The vRealize Automation GUI is only showing a small peace and not the big picture.

Product support: I have tested this procedure on vRealize Automation version 7.3 and vRealize Automation 7.3.1. I would expect it to work on newer and older vRealize Automation 7.X releases.

Enable the vIDM Interface

This procedure is for enabling the interface:

  • Step 01: Connect with an SSH session to the vRealize Automation Appliance. Use for example Putty.
  • Step 02: Login with the root credentials.
  • Step 03: Run the following command to start the VMware Identity Manager Interface: (vcac–vami horizon ui enable).
  • Step 04: Open a web browser and navigate to the following URL:(https://%FQDN%/SAAS/admin/).
VMware Identity Manager (vIDM) interface enable
VMware Identity Manager (vIDM) interface enable

Disable the vIDM Interface

This procedure is for disabling the interface:

  • Step 01: Connect with an SSH session to the vRealize Automation Appliance. Use for example Putty.
  • Step 02: Login with the root credentials.
  • Step 03: Run the following command to stop the VMware Identity Manager Interface: (vcac–vami horizon ui disable).
  • Step 04: When you navigate to the following URL no page should appear: (https://%FQDN%/SAAS/admin/).
VMware Identity Manager (vIDM) Interface/GUI disable
VMware Identity Manager (vIDM) interface disable

Status of the vIDM Interface

This procedure is for viewing the vIDM Interface status:

  • Step 01: Connect with an SSH session to the vRealize Automation Appliance. Use for example Putty.
  • Step 02: Login with the root credentials.
  • Step 03: Run the following command to view the current status of the VMware Identity Manager Interface: (vcac–vami horizon ui status).
  • Step 04: When you navigate to the following URL no page should appear: (https://%FQDN%/SAAS/admin/).
VMware Identity Manager (vIDM) interface status
VMware Identity Manager (vIDM) interface status

VMware Identity Manager URLs

The following URLs are available when the GUI is enabled (there are probably more URLs available than listed below):

  • Main page: https://%vRA-Appliance-FQDN%:8443
  • Tenant-specific page (Tenant vSphere.local): https://%vRA-Appliance-FQDN%/SAAS/t/vsphere.local
  • Tenant-specific page (Tenant Production): https://%vRA-Appliance-FQDN%/SAAS/t/production
  • Tenant-specific page (Tenant Development): https://%vRA-Appliance-FQDN%/SAAS/t/development

vRealize Automation Internal Proxy Explained

To explain what happens under the covers is the following: When you run the command to start or stop vIDM interface the reverse proxy configuration located in vRealize Automation Appliance (vRA) is changed. The command adds or removes some configuration files. Then the proxy daemon is reloaded to pick up the changes. At that point, the vIDM webpage becomes available or unavailable depending on the given command. Under the covers, vRealize Automation uses HAProxy for IT guys working in container or web hosting environments that might be a very familiar product. Here is a quote from the HAProxy website to explain what HAProxy is capable of:

HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic websites and powers quite a number of the world’s most visited ones. Over the years it has become the de-facto standard opensource load balancer, is now shipped with most mainstream Linux distributions, and is often deployed by default in cloud platforms. Since it does not advertise itself, we only know it’s used when the admins report it.

https://www.haproxy.org/#desc

VMware Identity Manager GUI Advantages

The main advantages of enabling the GUI:

  • You can view the currently logged in users in vRealize Automation.
  • When logging into the default tenant in the vIDM GUI you can view the total amount of users and groups that are identified by vIDM (counters are from all tenants combined).
  • You can view the health status of VMware Identity Manager (vIDM).
  • You can view the user login history based on the last days and you have reporting functionality.

Final word

In this blog post, I explained how to enable and disable the VMware Identity Manager interface on a vRealize Automation Appliance. As noted before be careful! I personally only use this method for troubleshooting Identity Manager related problems with authentication and viewing user activity.

Content Update

The following items have been verified:

  • 2020-09-24: This is still working on vRealize Automation 7.6.

Removing a Virtual Machine from vRealize Automation with the vRealize CloudClient

0

Overview

Today I was dealing with an issue in vRealize Automation (vRA). The customer had deleted some virtual machines in the vCenter inventory that were managed by vRealize Automation (vRA). So this resulted in registered virtual machines in vRealize Automation that were reported as missing.

For this blog post I recreated the problem in my Lab environment to have the ability to share the screenshots.

vRealize Automation Missing Virtual Machines

vRealize Automation 7.3 – Infrastructure – Managed Machines

Environment

Like explained in the beginning of this blog post. I recreated the problem in my home lab environment. To give you some background information about this environment. The Lab environment is running the following products and versions:
– VMware vCenter 6.5
– VMware ESXi 6.5
– VMware vRealize Automation 7.3.1
– VMware vRealize Orchestrator 7.3.1
– VMware NSX-V 6.4.0

The clusters are split into a “Mgmt & Edge” Cluster and a “Payload” Cluster. The virtual machines that were managed by vRealize Automation were located on the “Payload” cluster. So to recreate the problem I removed the virtual machines in the “Payload” cluster.

Incase you are interested in more information about my Home Lab, you can go to the following page.

Procedure:

  1. Download the latest version of the vRealize ClientCloud from the VMware website (the link can be found below).
  2. When the download is done, unzip the zip file (VMware_vRealize_CloudClient-4.5.0-8227624.zip).
  3. Navigate to the following directory (VMware_vRealize_CloudClient-4.5.0-8227624bin).
  4. Start the CloudClient (Windows: cloudclient.bat / Linux: cloudclient.sh).
  5. Log in to the vRA Appliance:
    Syntax:
    vra login userpass --user admin ID --tenant Tenant Name --server vRA FQDN --password Password

    Example:
    vra login userpass --user "M. Buijs" --password VMware1! --tenant Production --server https://cmp.lab.local

  6. Log in to the IaaS Machine:
    Syntax:
    vra login iaas --user service account --domain the domain --server web server --password Password

    Example:
    vra login iaas --user svc-vra-iaas --password VMware1! --domain lab.local --server iaasweb.lab.local

  7. Remove the virtual machine:
    Syntax:
    vra machines forceunregister --name %VMname%

    Example:
    vra machines forceunregister --name Prod-IT-00021

Keep in mind: It may take 5 to 10 minutes to remove the virtual machine from the interface.

vRealize CloudClient

vRealize CloudClient 4.5.0 – Started Application

vRealize CloudClient 4.5.0 – Authentication and removal

Links:

Here are some useful links related to the problem:
– VMware KB2144269 – Removing a virtual machine from vRealize Automation 7.x using CloudClient
– VMware vRealize CloudClient 4.5.0 – Download Page

vRA: Installation Prerequisite Checker Hangs

0

Recently I was deploying a new vRealize Automation (vRA) 7.3.0 environment at a customer and I ran into some problems. In the “vRealize Automation Installation Wizard” the “Prerequisite Checker” stopped working after applying fixes. This caused a major problem because no buttons in the GUI were working. In this article, I’m explaining what might be the cause and how to get around the problem.

Read more