As a Consultant at ITQ, I have gained extensive knowledge and experience in End User Computing (EUC) and Cyber Security over the past decade. In 2018, I was awarded the VMware vExpert status, and I have been part of the vExpert EUC subprogram since 2020. As a security enthusiast, I am always looking for ways to improve my skills and stay up-to-date on the latest technologies. In this blog post, I will guide you through the steps for creating a custom connector in VMware Workspace ONE Intelligence that can send messages to your Microsoft Teams channel(s).

To follow along with this blog post, you will need a Workspace ONE Intelligence tenant, a Microsoft Office 365 subscription with Teams, and Postman to create and modify the API. I am using my VMware TestDrive environment and a Microsoft 365 Developer account for this tutorial.

Step 1: Create an Alerts Channel in Workspace ONE Intelligence

In my Microsoft 365 Developer environment, I have created a new Team and some additional channels to simulate a SOC team. In the alerts channel, I want Workspace ONE Intelligence to post any new Carbon Black alerts with a severity of 6 or higher. To set this up, I’ve created the following Automation in Workspace ONE Intelligence:

1. Go to Integrations > Outbound Connectors > Add Custom Connector.

2. Copy the webhook URL into the Base URL field, and select No Authentication in the Auth Type field. Click Save to add the connector.

3. Click on the … (dots) of the Microsoft Teams connector and select View Actions.

4. Drag the created JSON file to the upload field to import the Microsoft Teams API.

Step 2: Import the Microsoft Teams JSON File

To import the Microsoft Teams JSON file, follow these steps:

1. Click here to download the Microsoft Teams JSON file from the EUC samples page on Github.

2. Import the JSON file into Postman.

3. Insert the webhook URL in each of the POST requests.

4. Click on the … (dots) at the Microsoft Teams level and select Export.

5. Leave it on the default Collection v2.1, click on the Export button, and save the JSON file on your computer.

Step 3: Create an Automation in Workspace ONE Intelligence

To set up an automation that sends a message to Microsoft Teams when a new Carbon Black alert with a severity of 6 or higher is detected, follow these steps:

1. Go to Automations > Add > Custom Workflow.

2. Select Category > Carbon Black > Carbon Black Threats.

3. In the Filter (IF) field, select Carbon Black Severity Score > Greater Than or Equal To > 6.

4. In the Action (Then) field, enter a message you want to send to the teams channel. I used the following message: “An alert with Severity Score ${carbonblack.threat.threatinfo_score} has been raised for ${carbonblack.threat.deviceinfo_devicename} in the Carbon Black Console.”

5. Click Test to start the test.

6. Select one of the alerts found and click Next (if you don’t see any alerts, change the filter to a lower severity).

7. The text in the text field should automatically be adjusted, click Test to launch send the message to Microsoft Teams.

8. Open your teams channel and see the result!

I hope this blog post has been informative and helpful. If you have any questions or comments, please let me know. When I’m offline, I enjoy spending time with my family, playing sports, and grilling on my BBQs.

Building an RDSH Farm in Horizon: A Step-by-Step Guide

In this blog post, we will guide you through the process of creating an RDSH (Remote Desktop Session Host) farm in Horizon 8 (2212), with a focus on the new feature “Published Apps On Demand”. This feature allows users to access published applications on demand, without the need for a dedicated application server.

Prerequisites:

Before we begin, there are a few prerequisites you need to be aware of:

1. You need an RDSH server with Horizon installed.

2. It is recommended to have the DEM (Desktop and Application Management) and App Volumes Agent installed as well.

3. Create a snapshot of your VM before proceeding, as this is required for cloning.

Creating an RDSH Farm:

To create an RDSH farm, follow these steps:

1. Open the Horizon management console and navigate to Farms.

2. Click “Add” to start creating a new farm.

3. Leave the “Automated Farm” setting on default, and click “Next”.

4. Select your vCenter Server and click “Next”.

5. Leave the “Storage Optimization” settings as default, as we don’t use vSAN in our lab. Click “Next”.

6. Enter a Farm ID and specify any additional settings if desired. For this blog, we will leave these settings default. Click “Next”.

7. Choose a Naming Pattern and select the maximum number of machines you want to create in your farm. Click “Next”.

8. Specify the VM and snapshot of the VM you have created. Select the location where you want the cloned VMs to land. Click “Next”.

9. Select your Instant Clone Domain Account and the OU where the computer objects need to be created. Click “Next”.

10. Review your selected settings, then click “Submit” to start the cloning process.

Monitoring the Cloning Process:

After submitting your settings, you can monitor the progress by selecting your farm. When the cloning process is successfully finished, the state should be “Published”.

Navigating to the RDS Hosts Tab:

To see the hosts you’ve created, navigate to the “RDS Hosts” tab in the Horizon management console.

Conclusion:

In this blog post, we have demonstrated how to create an RDSH farm in Horizon 8 (2212) with the new feature “Published Apps On Demand”. We have also covered the prerequisites and the step-by-step process for creating a farm. We hope this guide has been informative and helpful for you. If you have any questions, feel free to contact us.

About the Author:

Hi, my name is Age Roskam, and I work as a Consultant at ITQ. Over the last decade, I’ve gained a lot of knowledge and experience in the field of End User Computing, and in recent years, also in the world of Cyber Security. Since 2018, I’ve been awarded the VMware vExpert status every year. In 2020, I received the honor to be part of the first vExpert EUC subprogram, and in addition to that, I’m part of the vExpert Security subprogram since 2021. When I’m offline, I enjoy family, sports, and grilling on my BBQs.

Creating an On-Demand Package in App Volumes: A Step-by-Step Guide

In this blog post, I will guide you through the steps of creating an on-demand package in App Volumes. This type of package allows users to access the application only when they need it, reducing the storage requirements and improving performance. I will be using 7-Zip as the example application, but the process applies to any application.

Step 1: Log in to App Volumes Manager

To create an on-demand package, you need to have App Volumes Manager installed and created a package VM. Open App Volumes Manager and log in to your account.

Step 2: Create the Application

Click on the “Create” button to create a new application. Give the application a name, and select the “On-demand” radio button. Click “Create” again to continue.

Step 3: Attach the Package VM

Now it’s time to attach the empty .vmdk to the package machine. Click on “Package” and search for your package VM. Select it and click “Create” again. Click “Start Packaging” to start the attachment process.

Step 4: Install the Application

When you are logged into your package VM, you’ll see a small window in the bottom right corner. Do not click OK yet! First, install the application. In this case, I’m using 7-Zip, so I’ll run the installer and follow the steps to install and configure the application.

Step 5: Finalize the Package

When you have finished installing and configuring the application, click OK. You’ll be prompted to review the name and version of the package, and you can add some notes if needed. Click “Finalize” to finalize the package.

Step 6: Set the CURRENT Marker

Now we need to set the CURRENT marker on the package we’ve just created. In the App Volumes Management console, click on the “Set CURRENT” button and select the package you just created. Click “Set Current” to set the marker.

Step 7: Assign the Package

The final step is to assign the package to the user(s). On the home screen of the management console, click on the + icon of the application and click on “Assign.” In my case, I’m going to assign it to an AD security group. Enter the name, select the right group, and click “Assign.” Leave the Assignment Type on Marker!

That’s it! You have now successfully created an on-demand package in App Volumes. This type of package allows users to access the application only when they need it, reducing storage requirements and improving performance. If you have any questions or need further assistance, feel free to contact me.

Published Apps on Demand in Horizon version 2212: A Game Changer!

In the latest version of Horizon, version 2212, Published Apps on Demand have been released as GA. This feature allows you to publish applications on demand, making it possible to provide users with a more flexible and efficient way of accessing applications. In this blog, I will guide you through the steps required to configure this new feature in the Horizon Management console and test a brand new On-demand Published App.

Prerequisites:

* A Horizon environment up and running together with an App Volumes manager.

* At least one “on-demand” package created in App Volumes.

Configuring Published Apps on Demand:

1. Open the Horizon management console.

2. Navigate to Servers, App Volumes Managers, and click Add.

3. Enter the App Volumes manager FQDN, port number, and credentials. Click OK.

4. Important: Your App Volumes manager needs to have a valid SSL certificate signed by a trusted CA. The default, a self-signed certificate will not work unless it’s added to the trust store. However, I don’t recommend doing that in a production environment.

5. Repeat the steps if necessary.

6. Associate the App Volumes manager with a Farm in Horizon. If you don’t have a farm ready, follow the steps here.

7. Navigate to the Applications tab, select Add, and Add from App Volumes Manager.

8. Select the applications you want to add as published apps, and click Next.

9. Review the ID and Display Name of the apps, and click Submit.

10. Select the added applications, click Entitlements, and select Add Entitlements. Click on Add, enter and select the group or user(s) you want to entitle, and click OK.

Testing Published Apps on Demand:

1. Log in on the RDSH server to show that none of the applications I’ve just added is installed or attached to the host. It’s called Published Apps on Demand for a reason ;-).

2. In the App Volumes Manager, you can see that there is not a single package attached to a machine.

3. Open the Horizon HTML5 client, and you will see the three applications I’ve added to the Horizon management console as published apps. When I start Notepad++, I don’t see a virtual desktop, just the application running in the browser.

4. When I go back to my RDP session, I’m refreshing the programs and features windows I had open, and there you go! It looks like Notepad++ is installed on this machine.

5. When I refresh my App Volumes management console, I now see one attachment of Notepad++ to my RDS host.

Conclusion:

Published Apps on Demand in Horizon version 2212 is a real game changer! It provides users with a more flexible and efficient way of accessing applications, and it’s easy to configure in the Horizon Management console. I have a great use case for it, which I’ll explain in another blog. Thank you for reading, and if you have any questions, feel free to contact me.

Agustín Malanco is a VMware CTO Ambassador and recently attended the OCTO Global Field & Industry program, where he had the opportunity to learn about new technologies and architectures that are being developed or have already been introduced within the VMware ecosystem. One of the most striking new technologies he encountered was Bitfusion, which was acquired by VMware a few months ago.

Bitfusion is a solution that enables the creation of a distributed pool of GPU resources, allowing applications to access these resources as if they were local, thereby improving the utilization of available resources and enabling more flexible and scalable computing environments. This technology has the potential to revolutionize the way we approach computing and data processing, particularly in fields such as machine learning (ML), artificial intelligence (AI), and big data.

So, what do these technologies have in common? They all rely on the use of GPUs to process large amounts of data quickly and efficiently. However, traditional methods of accessing GPU resources have been limited by the need for local access and management of these resources, which can lead to silos within data centers and suboptimal resource utilization.

Bitfusion changes this by providing a distributed pool of GPU resources that can be accessed by applications as needed, without the need for physical local access or rearchitecture of applications. This allows for more flexible and scalable computing environments, and enables applications to take advantage of the vast processing power of GPUs without the limitations of traditional GPU access methods.

The architecture of Bitfusion is designed to be simple and straightforward, with three main components:

1. The Bitfusion Client: This component provides a simple interface for applications to request access to the distributed pool of GPU resources.

2. The Bitfusion Server: This component manages the pool of GPU resources and directs requests from the client to the appropriate resource.

3. The GPU Resources: These are the actual GPU resources that are being pooled and made available for access by applications.

There are several key considerations when designing with Bitfusion, including:

1. Resource Management: Bitfusion must be able to manage the pool of GPU resources effectively to ensure that they are utilized efficiently and that there is no wasted capacity.

2. Application Compatibility: Bitfusion must be able to work seamlessly with a wide range of applications, without requiring any modifications or rearchitecture of these applications.

3. Security: Bitfusion must provide robust security features to ensure the integrity and confidentiality of data being processed by the GPU resources.

Overall, Bitfusion represents an exciting development in the field of computing and data processing, and has the potential to enable new use cases and applications that were previously not possible. As more and more organizations look for ways to harness the power of GPUs, solutions like Bitfusion will play an increasingly important role in enabling flexible, scalable, and efficient computing environments.

Running Published Apps on Demand from a VDI Desktop Pool

In recent times, VMware has introduced the feature of Published Apps on Demand, which can revolutionize your application delivery strategy and take it to the next level. This feature allows users to access applications directly from the App Volumes manager into the Horizon console without requiring an RDSH farm. However, most blog posts and presentations focus on running published apps from an RDSH farm, leaving out the possibility of running them from a VDI desktop pool. In this article, I will explain how to run published apps on demand directly from a VDI desktop pool, and how to build an On-demand package if you don’t have one already.

Requirements:

1. At least one application package in App Volumes with delivery type set to “On-demand”.

2. An Horizon environment with a published VDI desktop & applications pool.

3. The ability to build an On-demand package if you don’t have one already.

Step 1: Creating an On-Demand Package

If you don’t have an On-demand package, you can create one by following these steps:

a. Open the App Volumes manager and select the application you want to create an On-demand package for.

b. Click the “Packages” tab and click “Add Package”.

c. Select “On-Demand” as the delivery type and click “Next”.

d. Follow the wizard to complete the package creation process.

Step 2: Publishing a VDI Desktop Pool

To publish a VDI desktop pool, follow these steps:

a. Open the Horizon management console and select “Desktops & Applications” from the left menu.

b. Click “Publish” and select the VDI desktop pool you want to publish.

c. In the “Session Type” settings, select “Desktop & Applications” or “Applications” depending on your requirements.

Step 3: Adding a Published Application Manually

Once you have published a VDI desktop pool, you can add a published application manually by following these steps:

a. Open the Horizon management console and select “Applications” from the left menu.

b. Click “Add” and select “Add Manually”.

c. Select your VDI pool from the desktop pool radio button.

d. Enter the application ID, display name, and parameters for the application shortcut. The path should be:

e. The parameters will be different for each application, because of its own GUID. But it should look like this:

f. Click “Submit” and confirm with “OK”.

g. Add an entitlement to the published application and click “OK”.

Step 4: Testing Published Apps on Demand

Once you have created an On-demand package, published a VDI desktop pool, and added a published application manually, you can test the Published Apps on Demand feature by doing the following:

a. Login to a desktop with the Horizon Client installed and log in to the Horizon environment.

b. Open the start menu and find the shortcut for the published application.

c. Click the shortcut to open the application, and you should see a message at the bottom right of your screen saying “App delivery in progress”.

d. When the package is mounted to your VDI, the application will be started and streamed to your local desktop as a Published App on Demand!

Conclusion:

Running published apps on demand from a VDI desktop pool can be a game changer for organizations looking to revolutionize their application delivery strategy. With this feature, users can access applications directly from the App Volumes manager into the Horizon console without requiring an RDSH farm. By following the steps outlined in this article, you can start using this feature today and take your application delivery to the next level.

Configuring TrueSSO for VMware Horizon with Okta

In this blog post, we will cover the basic guide on how to configure Okta and VMware Horizon to provide an end-to-end single sign-on experience to the end-user. We will focus on configuring TrueSSO on our Horizon environment, which enables users not to enter Active Directory credentials when using a remote desktop or applications.

Step 1: Configure Okta App Integration

In the Okta Admin Console, navigate to Applications > Applications > Create a new App Integration. Select SAML 2.0 and press Next. Enter your App name, upload an app logo (optional), and click Next. We will configure the SAML settings later, so skip this step for now.

Step 2: Download Okta Metadata

In the Sign On page, scroll down to the SAML 2.0 section, copy the Metadata URL, and open a new browser window. Save the file as my_metadata.xml.

Step 3: Assign App to Group

Go to the Assignments tab and select Assign > Assign to Groups. Assign your Active Directory group to the Application.

Step 4: Configure Identity Bridging Settings

Login to the VMware Unified Access Gateway by entering the correct credentials. Navigate to the Identity Bridging Settings. Press the gear button next to Upload Identity Provider Metadata. Upload the Okta metadata that you downloaded in step 2. Save your settings on the Unified Access Gateway.

Step 5: Configure SAML as Authentication Method

In the Horizon Administration Console, navigate to Settings > Servers > select the Connection Server. Click Edit. Set SAML 2.0 Authenticator to Allowed, and click Manage SAML Authenticators. Click Add button to create a new SAML Authenticator. Give your SAML 2.0 Authenticator a name, in the SAML Metadata field, paste the contents from step 2 (my_metadata.xml), and enable the Enabled for Connection Server option.

Step 6: Enable TrueSSO on Horizon Environment

Since our environment leverages Horizon TrueSSO, we need to enable TrueSSO on our Horizon environment. To do so, we need to login to the VMware Connection Servers and open a Command Prompt as administrator. We need to use the following command line to list all the authenticators and their True SSO mode status:

“list authenticators -type SAML 2.0 -enabled”

Replace: with the Horizon administrator user, with the fully qualified domain name for the Horizon admin user, and with the password for the Horizon administrator.

If True SSO mode is DISABLED for the authenticator you are trying to configure, execute the following command line to enable:

“enable authenticators -type SAML 2.0 -name “

After you enable True SSO, the True SSO mode for the authenticator you are enabling displays as ENABLE_IF_NO_PASSWORD.

Step 7: Test the End-to-End Single Sign-On Experience

In my demo, I am using an IGEL Thin Client to access my Horizon environment. But you can also install the Horizon Client on a Windows or macOS client machine. When you launch a remote desktop or application, you will be redirected to the Okta login page. Enter your credentials and click Log in. You will be redirected back to the remote desktop or application without entering any additional credentials.

That’s it! By following these steps, you have successfully configured TrueSSO for VMware Horizon with Okta, providing an end-to-end single sign-on experience to your end-users.

Managing Devices with Workspace ONE and Okta

In today’s digital age, managing devices for end-user computing has become an essential part of any organization’s IT strategy. With the proliferation of mobile devices, laptops, and desktops, it is crucial to ensure that these devices are secure, compliant, and productive. To achieve this, organizations can leverage endpoint management tools such as VMware Workspace ONE and Okta to manage devices, deploy applications, and enforce security policies.

In this blog post, we will explore how to use Okta and Workspace ONE to manage devices, deploy client certificates, and ensure compliance with device management policies. We will also discuss how to leverage the Device Management flag in Okta to simplify the endpoint management process.

Managing Devices with Workspace ONE

To begin with, let’s take a look at how to manage devices using Workspace ONE. Workspace ONE provides a unified endpoint management (UEM) solution that enables organizations to manage and secure devices across different operating systems, including Windows, macOS, and Android.

To manage devices using Workspace ONE, follow these steps:

1. Log in to your Workspace ONE console and navigate to the DEVICES tab.

2. Click on the device you want to manage and select the Management tab.

3. Under the Management section, click on the Certificates tab and select Add Device Management Platform.

4. Enter the Okta SCEP URL and Secret Key, which are required for the VMware Workspace ONE setup.

5. Click Test Connection and save your settings.

Now that we have set up the device management platform, let’s move on to deploying client certificates using Okta.

Deploying Client Certificates with Okta

To deploy client certificates using Okta, follow these steps:

1. Log in to your Okta admin console and navigate to the Security tab.

2. Click on Device Integrations and select Add Platform.

3. Select Desktop (Windows and macOS only) and click Next.

4. On the Add Device Management Platform page, enter the Okta SCEP URL and Secret Key.

5. Click Test Connection and save your settings.

6. To create a certificate authority, click on the Certificate Authority tab and select Download x509 Certificate.

7. Upload the certificate to VMware Workspace ONE in a later step.

8. To create a request template, click on the Request Templates tab and select Add.

9. Enter the required information and save your settings.

10. To create a device profile, click on Profiles & Baselines and select Add Profile.

11. Select Windows and select Device Profile.

12. On the General page, enter the required information.

13. Select Credentials in the left pane and click Configure.

14. On the Credentials page, enter the required information and save your settings.

15. To create a user profile, navigate to the Windows Desktop section and select User Profile.

16. Enter the required information and save your settings.

Now that we have set up device management and deployed client certificates using Okta, let’s discuss how to leverage the Device Management flag in Okta to simplify the endpoint management process.

Leveraging the Device Management Flag in Okta

The Device Management flag in Okta enables organizations to manage devices as part of their endpoint management strategy. By leveraging this flag, organizations can automate device management tasks such as certificate deployment, policy enforcement, and compliance monitoring.

To leverage the Device Management flag in Okta, follow these steps:

1. Navigate to the Okta Admin Console and select Security.

2. Click on Device Integrations and select Add Platform.

3. Select Desktop (Windows and macOS only) and click Next.

4. On the Add Device Management Platform page, enter the Okta SCEP URL and Secret Key.

5. Click Test Connection and save your settings.

6. To create a certificate authority, click on the Certificate Authority tab and select Download x509 Certificate.

7. Upload the certificate to VMware Workspace ONE in a later step.

8. To create a request template, click on the Request Templates tab and select Add.

9. Enter the required information and save your settings.

10. To create a device profile, click on Profiles & Baselines and select Add Profile.

11. Select Windows and select Device Profile.

12. On the General page, enter the required information.

13. Select Credentials in the left pane and click Configure.

14. On the Credentials page, enter the required information and save your settings.

15. To create a user profile, navigate to the Windows Desktop section and select User Profile.

16. Enter the required information and save your settings.

Conclusion

In conclusion, managing devices for end-user computing is a critical aspect of any organization’s IT strategy. By leveraging endpoint management tools such as VMware Workspace ONE and Okta, organizations can simplify the endpoint management process, deploy client certificates, and ensure compliance with device management policies. The Device Management flag in Okta provides an additional layer of automation and streamlines the endpoint management process.

EUC TECH: Managing iOS Devices with Workspace ONE and Okta

In today’s digital age, managing mobile devices has become an essential aspect of endpoint computing. With the increasing use of iOS devices in the workplace, it is crucial to ensure that these devices are properly managed and secured. In this blog post, we will explore how to manage iOS devices using Workspace ONE and Okta.

Before we dive into the configuration process, let’s first understand why managing iOS devices is essential. iOS devices are popular among end-users due to their ease of use and versatility. However, these devices can also pose a significant security risk if not properly managed. Unmanaged devices can lead to data breaches, unauthorized access, and other security threats. Therefore, it is crucial to ensure that all iOS devices used in the workplace are properly managed and secured.

Workspace ONE and Okta provide an ideal solution for managing iOS devices. Workspace ONE is a unified endpoint management (UEM) platform that allows IT administrators to manage and secure various endpoints, including iOS devices. Okta, on the other hand, is an identity and access management (IAM) platform that provides secure authentication and authorization. By combining these two platforms, IT administrators can create a seamless and secure experience for end-users.

To begin managing iOS devices with Workspace ONE and Okta, follow these steps:

1. Log in to your Okta Admin Console and go to Security > Device Integrations. Click the Endpoint Management tab and then click Add Platform. Select iOS as the platform and click Next.

2. Configure the management attestation by selecting Use existing key if you already have a secret key, or generate a new secret key using the default setting. Copy the provided secret key to your clipboard for later use.

3. In the Enrollment link field, enter the URL provided by Workspace ONE UEM for redirecting end-users with unenrolled devices.

4. Log in to your Workspace ONE UEM Console and navigate to the Apps section. Press the ADD APPLICATION button to add the Okta Verify application. Select Platform (Apple iOS) and enter the Application Name (Okta Verify). Press Next to continue.

5. You should see the Okta Verify app in the search results. Press SELECT on the right to add the app to your Inventory. Adjust settings as needed, such as application label, and press SAVE & ASSIGN to continue.

6. Within the Distribution menu, enter a Name, select a group (Workspace ONE Assignment Group(s)), and set the App Delivery Method to Auto.

7. In the Application Configuration menu, enable Send Configuration and click ADD to add the following configuration keys:

Configuration Key: managementHintValue Type: String Configuration Value: Enter the secret key you copied from the Okta Console (management attestation configuration)

Configuration Key: OktaVerify.OrgUrlValue Type: String Configuration Value: Your Okta URL (example.okta.com)

Press CREATE and SAVE your settings.

Now, you should see the Okta Verify app in your Workspace ONE UEM Application Inventory. To enable SSO extension profiles for Okta FastPass authentication on managed iOS devices, follow these steps:

1. Navigate to RESOURCES –> Profiles & Baselines –> Profiles. Click ADD and select Add Profile.

2. Select Apple iOS as the platform and click Device Profile. Label the profile and navigate to the SSO Extension Payload.

3. Configure the following settings:

* Management Hint Value: Enter the secret key you copied from the Okta Console

* Okta Verify URL: Enter your Okta URL (example.okta.com)

* Save & Publish your profile.

4. Navigate to DIRECTORY –> PEOPLE and select the desired user.

5. Navigate to the DEVICES section and select your device. You should now see that your device has a Management status of “Managed.”

6. To add an authentication policy rule and leverage the Device management flag, follow these steps:

* Navigate to POLICY –> AUTHENTICATION –> POLICIES. Click ADD POLICY.

* Select the desired user and click SAVE & ASSIGN.

By following these steps, you can successfully manage iOS devices using Workspace ONE and Okta. This solution provides a seamless and secure experience for end-users while ensuring that your organization’s data and assets are protected.

Hello! Welcome to my blog post about VMware Aria Operations 8.12, the latest version of the vRealize Operations platform. In this article, I will share my thoughts and experiences with this new release, and provide you with some helpful tips and tricks for getting started with it.

First things first, let me tell you that VMware Aria Operations 8.12 is a game-changer when it comes to managing and monitoring your vSphere environment. With its intuitive interface and powerful features, this tool can help you streamline your workflows, improve your productivity, and make more informed decisions about your IT infrastructure.

One of the things I love about VMware Aria Operations 8.12 is its simplicity. Unlike some other monitoring tools on the market, this one doesn’t require a degree in rocket science to figure out how to use it. In fact, you can deploy it in just a few clicks, and start exploring its features right away.

Of course, as with any new software, there may be some questions and doubts about how to use certain functions or features. But don’t worry, I’ve got you covered! I’ll be sharing some tips and tricks for getting started with VMware Aria Operations 8.12 throughout this article, so keep reading to learn more.

First things first, let me tell you that there are two main types of deployments for VMware Aria Operations 8.12: a single-node deployment and a multi-node deployment. Now, I know what you’re thinking – “What’s the difference?” Well, let me tell you.

A single-node deployment is perfect for small environments or for testing purposes, as it only requires one node to be deployed. This means that you can get started with VMware Aria Operations 8.12 right away, without having to worry about complex configurations or multiple nodes.

On the other hand, a multi-node deployment is ideal for larger environments, as it allows you to distribute the workload across multiple nodes. This not only improves performance but also provides more flexibility and scalability for your IT infrastructure.

Now, let’s talk about some of the key features of VMware Aria Operations 8.12. One of the most exciting ones is the ability to monitor your vSphere environment in real-time, using the new Performance Analyzer feature. This allows you to identify performance bottlenecks and potential issues before they become critical, so you can take proactive action to prevent them.

Another cool feature is the new Capacity Planner, which helps you optimize your resource utilization and plan for future growth. With this tool, you can easily visualize your IT infrastructure, identify areas of inefficiency, and make data-driven decisions about capacity planning.

Finally, let me share some tips and tricks for getting started with VMware Aria Operations 8.12. Firstly, I recommend starting with a single-node deployment to get familiar with the platform, and then gradually scaling up to a multi-node deployment as needed.

Secondly, be sure to take advantage of the new Performance Analyzer feature to monitor your vSphere environment in real-time. This can help you identify potential issues before they become critical, so you can take proactive action to prevent them.

Lastly, don’t forget to explore the other features of VMware Aria Operations 8.12, such as Capacity Planner and the new and improved dashboards, to get the most out of this powerful tool.

In conclusion, VMware Aria Operations 8.12 is a powerful and intuitive monitoring and management platform for vSphere environments. With its real-time performance monitoring, capacity planning, and other features, this tool can help you streamline your workflows, improve your productivity, and make more informed decisions about your IT infrastructure.

So, what are you waiting for? Get started with VMware Aria Operations 8.12 today, and experience the benefits of this amazing tool for yourself!