Browse Author

admin

Error Code: LCMVSSC10013

While trying to upgrade my SaltStack Config environment to 8.16.2 I encountered Error Code: LCMVSSC10013 in VMware Aria Suite Lifecycle.

The error details:

Error Code: LCMVSSC10013
Failed to import VMware Aria Automation Config.
Exception occurred while importing VMware Aria Automation Config host. Exception message: Import of VMware Aria Automation Config failed for tenant Standalone vRASSC

com.vmware.vrealize.lcm.vsse.common.exception.VsscImportFailureException: Import of VMware Aria Automation Config failed for tenant Standalone vRASSC
	at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.execute(VsscImportTask.java:185)
	at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158)
	at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: Cannot execute ssh commands. Exception encountered : Session.connect: java.security.spec.InvalidKeySpecException: key spec not recognized
	at com.vmware.vrealize.lcm.util.SshUtils.execute(SshUtils.java:721)
	at com.vmware.vrealize.lcm.util.SshUtils.runCommand(SshUtils.java:532)
	at com.vmware.vrealize.lcm.util.SshUtils.runCommand(SshUtils.java:516)
	at com.vmware.vrealize.lcm.util.SshUtils.runCommand(SshUtils.java:628)
	at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.fetchFipsStatus(VsscImportTask.java:342)
	at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.getProductDetails(VsscImportTask.java:260)
	at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.execute(VsscImportTask.java:158)
	... 5 more
Caused by: java.lang.RuntimeException: Cannot create session for ssh://[email protected]
	at com.vmware.vrealize.lcm.util.SessionHolder.newSession(SessionHolder.java:57)
	at com.vmware.vrealize.lcm.util.SessionHolder.<init>(SessionHolder.java:37)
	at com.vmware.vrealize.lcm.util.SshUtils.execute(SshUtils.java:663)
	... 11 more
Caused by: com.jcraft.jsch.JSchException: Session.connect: java.security.spec.InvalidKeySpecException: key spec not recognized
	at com.jcraft.jsch.Session.connect(Session.java:550)
	at com.vmware.vrealize.lcm.util.SessionHolder.newSession(SessionHolder.java:53)
	... 13 more
Caused by: java.security.spec.InvalidKeySpecException: key spec not recognized
	at org.bouncycastle.jcajce.provider.asymmetric.util.BaseKeyFactorySpi.engineGeneratePublic(Unknown Source)
	at org.bouncycastle.jcajce.provider.asymmetric.edec.KeyFactorySpi.engineGeneratePublic(KeyFactorySpi.java:212)
	at java.base/java.security.KeyFactory.generatePublic(Unknown Source)
	at com.jcraft.jsch.jce.XDH.getSecret(XDH.java:71)
	at com.jcraft.jsch.DHXEC.next(DHXEC.java:134)
	at com.jcraft.jsch.Session.connect(Session.java:328)
	... 14 more

To get around it I had to enable FIPS mode in Aria Suite Lifecycle under Lifecycle Operations -> Settings -> Tips Mode Compliance -> check the enabled box -> Click Update

Wait for the services to restart ~3 minutes

Upon retrying the request we can see that the request is now continuing.

Upgrading VMware Aria Automation Config to 8.16.2

In this post i will go over upgrading my 8.x SSC appliance to 8.16.2. As a pre requirement we do need to have VMware Aria Suite Lifecycle upgraded to 8.16. Instructions can be found here. The upgrade does not include the latest PSPACK that contains the 8.16.2 Aria Automation Config release. Instructions to get the PSPACK can be found on my other blog post here.

To get started we can go to VMware Aria Suite Lifecycle -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to VMware Aria Suite Lifecycle -> Lifecycle Operations -> Settings -> My VMware)

Click on Add Binaries under Product Binaries

Select My VMware and click on Discover

We can see a list of binaries that have been discovered. We can select what we need and click on Add

This will create a request and start downloading the package. To view the progress we can click on the Click Here hyperlink

Click on the in Progress button to view the details

We now have to wait for the download to complete

After the download is complete we can go to Environments -> View Details on the environment that includes the VMware Aria Automation Config

Under VMware Automation Config tab Click on Upgrade

An Inventory sync is recommended if the environment has changed since Aria Suite Lifecycle performed the last sync. We trigger the sync from the UI or click on Proceed to continue

Select product Version 8.16.2 and click Next. We can also review the compatibility matrix to make sure the environment is compatible.

We can automatically create and delete a snapshot part of the upgrade process

Run the Precheck to make sure there are no errors

Once the check is complete, click on Next. Review the upgrade details and click on Next. We are taken to the progress screen where we can follow the progress.

The system will get rebooted and once its back up we will be on 8.16.2

Here are a few additional blogs that might be useful post upgrade:

Error Code: LCMVSSC10018

SSC 8.8 sseapi_rpc_queue: could not connect to SSE server

SSC 8.8 urllib3 (1.25.11) or chardet (4.0.0) doesn’t match a supported version

Authentication failed: no Authorization header

Upgrading VMware Aria Automation to 8.16.2

In this post i will go over upgrading my 8.x vRA appliance to 8.16.2. As a pre requirement we do need to have VMware Aria Suite Lifecycle upgraded to 8.16. Instructions can be found here. The upgrade does not include the latest PSPACK that contains the 8.16.2 VMware Aria Automation release. Instructions to get the PSPACK can be found on my other blog post here.

To get started we can go to VMware Aria Suite Lifecycle -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to VMware Aria Suite Lifecycle -> Lifecycle Operations -> Settings -> My VMware)

Click on Add Binaries under Product Binaries

Select My VMware and click on Discover

We can see a list of binaries that have been discovered. We can select what we need and click on Add

This will create a request and start downloading the package. To view the progress we can click on the Click Here hyperlink

Click on the in Progress button to view the details ex:

We now have to wait for the download to complete

After the download is complete we can go to Environments -> View Details on the environment that includes vRA

Click on Upgrade

An Inventory sync is recommended if the environment has changed since LCM performed the last sync. We trigger the sync from the UI or click on Proceed to continue

Select product Version 8.16.2 and click Next. We can also review the compatibility matrix to make sure the environment is compatible.

A new feature that was added was the capability to automatically create a snapshot prior to the upgrade and remove it after the upgrade. On this screen we also have the ability to chose if we want to keep the snapshots post upgrade for validation testing for example. Click next

Run the Precheck to make sure there are no errors

The next screen remind us of hardware requirements for vRA which can be checked here and vIDM which can be checked here. As far as i can tell they haven’t changed since the 8.3 release. Check the I took care of the manual steps above and am ready to proceed check mark and click on Run Precheck

Once the check is complete we can review the checks that were performed and we can continue by clicking Next.

Review the upgrade details and click on Submit. We are taken to the progress screen where we can follow the progress.

The system will get rebooted and once its back up we will be on 8.16.2

Since we are doing a major upgrade i strongly recommend to clean the cache before using the new vRA version.

VMware Aria Suite Lifecycle Product Support Pack (PSPAK) Upgrade

In this guide i will go over the steps of getting an existing 8.x VMware Aria Suite Lifecycle (formerly vRSLCM vRealize Lifecycle Manager) appliance to support the latest product releases available. Here is a great blog that goes in to the details about what the Product Support Pack is https://blogs.vmware.com/management/2019/01/vrslcm-pspak.html. Typically the newer Product Support Pack is included part of the upgrade for LCM, however sometimes there are product releases in between releases where product support packs come in handy.

The first step is to log in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section

Go to settings -> Product Support Pack

We can see that i recently upgraded to 8.16.0.0 however a new update is available 8.16.0.1. Based on what we can see in the details the new support pack adds support for the Aria 8.16.2 products. If an update is not available click on the Check Support Packs Online button and refresh the screen within a few minutes

Click on Apply Version

Verify that a snapshot or a backup exists and click Submit

We can view the progress by clicking on the Click Here link after submitting the request

Once the process is complete the system will most likely reboot. To check the status we can go back to settings -> Product Support Pack. As we can see we are now at the updated patch level

If you get an error when logging in, clear the browser cache and try again

Enhancing vCenter Server Firewall Management with Ansible

In today’s dynamic IT environments, maintaining a secure and efficient infrastructure is paramount. For VMware vSphere administrators, managing the firewall settings on vCenter servers is a critical task that ensures the security of the entire virtualized infrastructure. Ansible, an open-source automation tool, offers a streamlined approach to managing firewall settings across multiple vCenter servers. This blog post will guide you through automating vCenter server firewall configurations using Ansible, showcasing how to apply these changes across multiple servers seamlessly.

Prerequisites:

  • Ansible installed on a control node (e.g., your workstation or a dedicated Ansible server).
  • Administrative access to your vCenter Server(s).
  • SSH access enabled on all target vCenter servers for Ansible.
  • A user account with sufficient privileges to modify firewall settings on the vCenter servers.

Part 1: Preparing Your Ansible Environment Before automating the firewall settings, ensure Ansible can communicate with your vCenter servers. This involves setting up an inventory file that lists all the target servers.

  1. Create an Inventory File: In your Ansible working directory, create a file named hosts.ini and add your vCenter servers under a group [vcenters]:
[vcenters]
vcenter1.example.com
vcenter2.example.com
vcenter3.example.com
...

Part 2: Writing Your Ansible Playbook An Ansible playbook defines the tasks to be executed on the target machines. For firewall management, you’ll create a playbook that ensures the desired firewall rules are present and active.

  1. Create the Playbook: In your Ansible working directory, create a file named manage_firewall.yml. Below is an example playbook that enables SSH access on the vCenter servers by modifying the firewall settings.
---
- name: Manage Firewall Settings on vCenter Servers
  hosts: vcenters
  become: yes  # Use elevated privileges
  tasks:
    - name: Ensure SSH access is allowed in the firewall
      ansible.builtin.firewalld:
        service: ssh
        state: enabled
        permanent: true
        immediate: yes

This playbook uses the ansible.builtin.firewalld module to manage firewall settings, specifically to enable SSH access. Adjust the module parameters as needed for your specific firewall rules.

Part 3: Executing the Playbook With the playbook and inventory file ready, you can now apply the firewall configurations to your vCenter servers.

  1. Run the Playbook: Execute the following command from your Ansible control node:
ansible-playbook -i hosts.ini manage_firewall.yml

This command instructs Ansible to run the playbook manage_firewall.yml against the hosts listed in hosts.ini, applying the firewall settings as defined.

Part 4: Scaling and Automating with Ansible Ansible’s power lies in its ability to scale and automate complex IT workflows. Consider integrating this playbook into your regular IT automation routines, such as part of a CI/CD pipeline or scheduled via Ansible Tower or AWX for regular compliance checks and updates.

Conclusion: Automating the management of firewall settings on vCenter servers with Ansible not only improves your security posture but also enhances operational efficiency by reducing manual tasks and potential for human error. By leveraging Ansible’s straightforward playbook syntax and powerful modules, you can ensure consistent firewall configurations across your VMware environment, freeing up time to focus on other critical IT initiatives.

Note: Always test your Ansible playbooks in a non-production environment before deploying them to production to ensure they work as expected and do not disrupt your services.

Streamlining vCenter Server Firewall Management with SaltStack Config

In the realm of VMware vSphere management, securing your vCenter Server is critical to maintaining a robust and secure infrastructure. SaltStack Config, integrated into VMware’s vRealize Automation suite, offers a powerful way to automate and manage configurations across your VMware environment, including firewall settings. This blog explores how to leverage SaltStack Config to automate firewall adjustments on your vCenter servers, ensuring consistent security policies and simplifying the process across multiple instances.

Prerequisites:

  • A working VMware vSphere environment with vCenter Server(s).
  • SaltStack Config setup and integrated with your vSphere environment.
  • Basic understanding of SaltStack fundamentals and the Salt state files.

Part 1: Setting Up Your SaltStack Environment Before diving into firewall management, ensure that your SaltStack Config is correctly set up and that your Minions (managed nodes) are communicating with the Salt Master. The Minions in this context would be the servers or systems where the vCenter Server runs.

  1. Verify Minion Connectivity: Use the salt-key command to check if your Minions are correctly connected and authenticated with the Salt Master.
salt-key -L

This command lists all Minions connected to your Salt Master.

Part 2: Creating a Salt State for Firewall Management You’ll create a Salt state file to manage the firewall settings on your vCenter servers. This example assumes you’re managing firewall rules related to SSH access, but you can adjust the configuration according to your specific needs.

  1. Create a Salt State File: Navigate to your Salt Master’s state file directory (typically /srv/salt) and create a new state file named vcenter_firewall.sls.

enable_ssh_access:
firewalld.present:
– name: ssh
– enabled: True

This state ensures the SSH service firewall rule is enabled, allowing SSH access to the vCenter server.

Part 3: Applying the State Across Multiple vCenter Servers With the state file ready, you can now apply this configuration across your vCenter servers. If your vCenter servers are already configured as Minions and grouped appropriately, you can target them directly.

  1. Apply the State: Use the salt command to apply your state file to the targeted vCenter servers.

salt ‘vcenter_minion_group’ state.apply vcenter_firewall

Replace 'vcenter_minion_group' with your specific target or group name. This command applies the firewall configuration state to all targeted Minions.

Part 4: Automating and Scheduling State Application To ensure ongoing management and enforcement of your firewall settings, consider scheduling the state application using SaltStack’s scheduler or integrating it into your CI/CD pipeline for regular enforcement.

  1. Scheduling with SaltStack: You can use SaltStack’s built-in scheduler to regularly apply your state to ensure compliance and react to any changes.

schedule_firewall_management:
schedule.present:
– function: state.apply
– job_args:
– vcenter_firewall
– minutes: 1440 # Adjust the timing based on your requirements.

Conclusion: Automating firewall management on vCenter servers with SaltStack Config not only strengthens your VMware environment’s security posture but also streamlines operations, reducing manual effort and potential for error. By leveraging SaltStack’s powerful automation capabilities, you can ensure consistent firewall policies across your infrastructure, enhancing overall security and compliance.

Note: Always validate your automation scripts and state files in a test environment before deploying them in production to avoid unintended disruptions.

Automating vCenter Server Firewall Configuration with PowerShell: A Guide for Scaling to Multiple Environments

The vCenter Server acts as the central nervous system for VMware vSphere environments, providing crucial management capabilities. As with any critical component of your infrastructure, ensuring the vCenter Server is secured is paramount. The firewall settings play a vital role in protecting your vCenter Server against unauthorized access. This blog post dives into how you can programmatically change the firewall settings on the vCenter Server using PowerShell, and how to scale this automation across multiple vCenter servers efficiently.

Prerequisites:

  • PowerShell 5.1 or higher.
  • VMware PowerCLI 12.0 or higher installed.
  • Administrative access to your vCenter Server(s).
  • A list of vCenter Server IPs or hostnames you intend to manage.

Part 1: Setting Up Your Environment First, ensure that VMware PowerCLI is installed on your machine. PowerCLI is a command-line tool offering over 600 cmdlets for managing and automating vSphere and vCenter environments.

Install-Module -Name VMware.PowerCLI -Scope CurrentUser

Part 2: Automating Firewall Changes on a Single vCenter Server To modify the firewall settings on a vCenter Server, we’ll first connect to the vCenter instance using PowerCLI. Then, we’ll execute commands to adjust the firewall settings as needed.

  1. Connect to the vCenter Server:
$vcServer = 'vCenterServerNameOrIP'
Connect-VIServer -Server $vcServer -User 'yourUsername' -Password 'yourPassword'
  1. Change Firewall Settings: Assuming you want to enable SSH access through the firewall, you can use the following script:
Get-VMHost | Get-VMHostFirewallException | Where-Object {$_.Name -eq "SSH Server"} | Set-VMHostFirewallException -Enabled $true

This command gets all ESXi hosts managed by the vCenter, retrieves the firewall rule for the SSH Server, and enables it.

Part 3: Scaling to Multiple vCenter Servers To scale this process across 10 vCenter Servers, you can wrap the commands into a function and iterate over an array of vCenter Server addresses.

function Set-FirewallSettings {
    param (
        [String]$vcServer,
        [String]$username,
        [String]$password
    )
    Connect-VIServer -Server $vcServer -User $username -Password $password
    Get-VMHost | Get-VMHostFirewallException | Where-Object {$_.Name -eq "SSH Server"} | Set-VMHostFirewallException -Enabled $true
    Disconnect-VIServer -Server $vcServer -Confirm:$false
}

$vCenters = @('vCenter1', 'vCenter2', 'vCenter3', 'vCenter4', 'vCenter5', 'vCenter6', 'vCenter7', 'vCenter8', 'vCenter9', 'vCenter10')

foreach ($vc in $vCenters) {
    Set-FirewallSettings -vcServer $vc -username 'yourUsername' -password 'yourPassword'
}

Part 4: Automating as a Batch Job To automate this process as a batch job, you can schedule the script using Task Scheduler on Windows or cron jobs on Linux. Ensure the machine where the script is scheduled has VMware PowerCLI installed and is configured to run scripts.

Conclusion: Automating firewall configuration on your vCenter Servers enhances your infrastructure’s security posture and saves time. By leveraging PowerShell and VMware PowerCLI, you can efficiently manage firewall settings across multiple vCenter Servers, ensuring consistent security policies across your VMware environment.

Remember: Always test scripts in a development environment before deploying them to production to ensure they perform as expected without unintended consequences.

Mastering the /v1/credentials API in SDDC Manager for Enhanced Security Management

In the rapidly evolving landscape of VMware’s Cloud Foundation, security management is a cornerstone for maintaining the integrity and confidentiality of the software-defined data center (SDDC). The SDDC Manager, a critical component of VMware’s Cloud Foundation, offers a comprehensive suite of APIs for managing various aspects of the SDDC, including credentials management. This blog post delves into the specifics of leveraging the /v1/credentials API in SDDC Manager, offering a detailed guide for VMware professionals to enhance their security posture through efficient credentials management.

Understanding the /v1/credentials API

The /v1/credentials API endpoint in SDDC Manager facilitates the management of credentials used across the SDDC components. It enables administrators to perform crucial operations such as creating, listing, updating, and deleting credentials securely. These credentials encompass a wide range of use cases, including but not limited to, ESXi hosts, vCenter servers, and backup solutions.

Key Operations and Their Significance

  • Creating Credentials: The ability to programmatically create credentials ensures that administrators can automate the deployment and configuration processes, adhering to security best practices such as the use of strong, unique passwords for each component.
  • Listing Credentials: By listing the available credentials, administrators can audit and review the credentials being used across the SDDC, ensuring compliance with the organization’s security policies.
  • Updating Credentials: The dynamic nature of security necessitates regular updates to credentials. The /v1/credentials API provides a straightforward mechanism for rotating credentials, thereby enhancing the security against potential breaches.
  • Deleting Credentials: In scenarios where certain credentials are no longer required or components are decommissioned, the ability to delete credentials helps in maintaining a clean and secure environment.

Practical Use Cases

  1. Automated Deployment Scripts: Incorporate the /v1/credentials API in deployment scripts to dynamically create and assign credentials during the setup of new components, streamlining the deployment process while maintaining a high security standard.
  2. Routine Security Audits: Utilize the API to list and review credentials as part of routine security audits, ensuring that all credentials meet the organization’s security requirements and identifying any credentials that need rotation.
  3. Operational Efficiency: Leverage the API to update and delete credentials as part of operational tasks, such as decommissioning old components or responding to security incidents, ensuring a swift and secure response to changes in the environment.

Best Practices for Using the /v1/credentials API

  • Secure API Access: Always secure access to the SDDC Manager APIs, using HTTPS and strong authentication mechanisms to protect against unauthorized access.
  • Regular Credential Rotation: Implement a routine process for rotating credentials using the API, minimizing the risk exposure from potential compromises.
  • Audit and Compliance: Regularly audit the credentials through the API, ensuring they comply with your organization’s security policies and industry standards.

Conclusion

The /v1/credentials API in SDDC Manager is a powerful tool for VMware professionals, enabling efficient and secure management of credentials within the SDDC. By understanding and leveraging this API, administrators can significantly enhance their security posture, streamline operations, and ensure compliance with security standards.


This guide serves as a foundation for mastering credentials management in SDDC Manager. However, the landscape of cybersecurity is constantly evolving, and it’s crucial to stay informed about the latest threats, vulnerabilities, and best practices to safeguard your SDDC environment effectively. Always refer to VMware’s official documentation and consider engaging with the community through forums and social media for the latest updates and insights.

Stopping a Running Task in SDDC Manager: A Step-by-Step Guide

In the world of VMware’s Cloud Foundation, the SDDC Manager plays a pivotal role in streamlining and automating the deployment, management, and orchestration of the software-defined data center components. However, administrators occasionally face the need to halt an ongoing task for various reasons, such as incorrect parameters or prioritizing other operations. This blog post provides a detailed walkthrough on how to gracefully stop a running task in SDDC Manager, ensuring minimal impact on the environment and maintaining system integrity.

Understanding the SDDC Manager’s Task Framework

Before diving into the procedure, it’s important to grasp how SDDC Manager handles tasks. Tasks in SDDC Manager represent operations such as deploying a new workload domain, adding a cluster, or updating software components. Each task is associated with a unique ID and comprises one or more subtasks, reflecting the task’s complexity and multi-step nature.

Identifying the Task to be Stopped

First, you need to identify the task you wish to stop. This can be done via the SDDC Manager UI or API. In the UI, navigate to the ‘Tasks’ tab where you can view ongoing, completed, and scheduled tasks along with their IDs. If you’re using the API, you can list the current tasks by querying the /tasks endpoint.

Gracefully Stopping the Task

After identifying the task, the next step is to stop it gracefully. This involves two critical considerations:

  1. Determine if the Task Can Be Stopped: Not all tasks can be safely interrupted. Check the documentation or use the API to query the task’s state and understand if it’s in a state that can be safely stopped.
  2. Use the SDDC Manager API to Stop the Task: SDDC Manager doesn’t provide a direct ‘Stop Task’ button in the UI for all tasks. Instead, use the API to send a stop command. This usually involves sending a PUT request to the /tasks/{taskId}/cancel endpoint, where {taskId} is the ID of the task you wish to stop.
  3. Option 2 Use the CLI:
curl -X DELETE http://localhost/tasks/registrations/{taskId}

Monitoring and Verification

After issuing the stop command, monitor the task’s status through the UI or API to ensure it transitions to a ‘Stopped’ or ‘Cancelled’ state. It’s crucial to verify the partial execution of the task hasn’t left the system in an inconsistent state. Depending on the task, you may need to revert certain operations or manually complete the task’s intended actions.

Conclusion

Halting a running task in SDDC Manager is a powerful capability, but it comes with the responsibility of ensuring system integrity and consistency. Always assess the impact and necessity of stopping a task before proceeding.

Remember, in the realm of VMware and SDDC Manager, thorough understanding and careful operation are key to maintaining a robust, efficient, and agile data center infrastructure.


This guide aims to arm VMware professionals with the knowledge to manage their SDDC environments more effectively. However, as every environment is unique, it’s important to adapt these guidelines to fit your specific situation and consult VMware documentation for the latest features and best practices.

VMware Aria Suite Lifecycle upgrade to 8.16

In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.16 release. The release notes can be found here. We can upgrade from vRealize Lifecycle Manager to VMware Aria Suite Lifecycle.

The first step is to log in to VMware Aria Suite Lifecycle under the Lifecycle Operations section

Go to Settings -> System Upgrade

Click on Check for Upgrade

We can see that the check found a new version available for 8.16. Click on Upgrade

Verify that a snapshot or backup exists in case the process fails. Check the check mark for I took a snapshot of the vRealize Suite Lifecycle Manager before I performed this operation. Click Next

Click on Run Precheck, verify that all check have passed, and click on Upgrade

This will fire up the upgrade process and start upgrading packages. The system will automatically reboot on 8.16 once completed. We can check the version by going to Settings -> System Details

Don’t forget to clear the browser cache in order to avoid any caching issues.