- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- About VMware Horizon Automation
- Configuration Steps
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
About VMware Horizon Automation
VMware allows you to access and work with virtualized desktops and applications. Native selectors are generated for corresponding elements by Studio after you install the UiPath Remote Runtime component on the server and the UiPath Extension for VMware on the client machine. This enables you to create automation projects with the full range of UIAutomation activities, such as Click, Type Into, Get Text, Extract Data, and more.
Following the configuration steps is necessary for enabling native automation for VMware technologies.
Once you complete the configuration steps, selectors can be generated for individual UI elements of applications virtualized through VMware Horizon.
This is what the generated selector for Calculator opened as a VMware Horizon app looks like:
<wnd app='win32calc.exe' cls='CalcFrame' isremoteapp='1' title='Calculator' />
<wnd ctrlid='137' /><wnd app='win32calc.exe' cls='CalcFrame' isremoteapp='1' title='Calculator' />
<wnd ctrlid='137' />This is what the generated selector for Calculator opened as a local application looks like:
<wnd app='win32calc.exe' cls='CalcFrame' title='Calculator' />
<wnd ctrlid='137' /><wnd app='win32calc.exe' cls='CalcFrame' title='Calculator' />
<wnd ctrlid='137' />isRemoteApp='1' attribute. This gets added automatically when you select an UI element from a VMware Horizon app.
Apart from this attribute, there are no distinctions between an automation process for a local application and an automation process for a VMware Horizon app. All the activities and wizards work exactly the same.
With the UiPath Extension for VMware Horizon and the UiPath Remote Runtime component installed, the following actions are enabled:
- Generating selectors for UI elements in VMware applications and desktops.
- Using the activities from the
UiPath.UIAutomation.Activitiespackage (such as Click, Type Into, and more). - Using Data and Screen Scraping Wizards.
- Automating browsers opened as VMware Horizon apps.
The UiPath Remote Runtime is installed on the VMware Horizon application server, while the UiPath extension for VMware Horizon on the client machine. The communication between these components is done through an Horizon Virtual Channel. This is the same mechanism used for transmitting data such as audio and video, so no additional configuration is needed.
The diagram below showcases the data flow between the client and the server:
