VMware Horizon View

Horizon Agent Client and Agent Silent msi /x guid uninstall

Horizon Agent Client and Agent Silent msi /x guid uninstall

Overview

In many cases, people use the .msi/.exe format and third-party deployment tools to manage software installation, updates, and in some cases, uninstallation. In this article, we will be discussing the Horizon Client and Horizon Agent. These concepts can also be applied to other .msi/.exe file types. The Horizon Client and Agent use these file types for installation and modification. This article can serve as a guide for your deployment, upgrades, modifications, or removal of the software.

The .exe file acts as a wrapper that contains the MSI files and runs them in the correct order during the installation process. For example, a software product may have multiple components, each with their own MSI file. The software vendor may choose to bundle these MSI files into a single .exe file to make the installation process easier for the end user.

It is always important to follow official documentation for procedures below and it may be best to utilize the switches with the .exe to better cleanup the install if you are trying to uninstall it completely. For instance in some cases you may find yourself looking for the codes for the MSI but find that you may have missed some of the other msi files that the exe installed. For example with the Horizon Client uninstall I would try this first then work with the MSI code.

VMware-Horizon-Client-y.y.yxxxxxx.exe /uninstall

Here is an example of the agent 2212.

msiexec.exe /qb /x {53D6EE37-6B10-4963-81B1-8E2972A1DA4D}

Documentation source:

Uninstall Horizon Client for Windows

Uninstalling VMware Horizon 8 Components Silently by Using MSI Command-Line Options

 

How to:

First you must look at what is installed on your machine. We can use Windows Powershell for that. Start by entering this into your Powershell window. Once you run this command you can see the output below shows us the ID we need.

Agent:

Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, ModifyPath |
Where-Object {$_.DisplayName -eq ‘VMware Horizon Agent’} | Format-Table –AutoSize

Client:

Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, ModifyPath |
Where-Object {$_.DisplayName -eq ‘VMware Horizon Client’} | Format-Table –AutoSize

Once you have your unique information on that msi you will then be able use the command line to uninstall it or use my script for additional cleanup. I will say that if you are going to use my script this is something that I wrote and is not something officially supported. Use at your own risk.

Simple command line to uninstall 2212 client example:

MsiExec.exe /X {A37284DF-37C2-40D8-B857-E1DB2BA6892B}

Script with logging and directly cleanup:

@echo off

rem Uninstall Horizon Client
msiexec /x {A37284DF-37C2-40D8-B857-E1DB2BA6892B} /q /l*v “C:\temp\HorizonClientUninstall.log”

rem Remove related files and directories
rmdir /s /q “C:\ProgramData\VMware\VMware Horizon View”
rmdir /s /q “C:\Program Files\VMware\VMware Horizon View Client”
rmdir /s /q “C:\Program Files (x86)\VMware\VMware Horizon View Client”

echo Horizon Client has been successfully uninstalled and related files and directories have been removed.
echo Log file with detailed information can be found at “C:\temp\HorizonClientUninstall.log”

What’s New In Horizon 2212 – Now Generally Available

What’s New In Horizon 2212 – Now Generally Available

Overview

Just released and made generally available on 01/12/2022, Horizon Version 2212 is the latest Extended Service Branch release, and it’s a big one! When you move to the Extended Service Branch, you can expect a more stable Horizon environment. You are free to move out of Extended Service Branches to current releases, so long as you upgrade to a version at the same or later date than your most recent ESB SP update. As a reminder, the ESBs are typically released 12 months apart. In the future I will be going over some of these new announcements in future posts.

 

Horizon Server and Instant Clones

  • Ability for admins to import and validate SSL certificates in Horizon Console
  • Support Cloud Pod Architecture with IPv6
  • Full clone AD binding
  • Instant Clone support for Microsoft MAK licensing
  • Instant Clone mode B support for vTPM desktops
  • Migrate from Azul to Bellsoft OpenJDK in Horizon Server
  • Increased max number of VMs per host support from 200 to 500 for non-vSAN storage
  • Support for Full Clone agent auto upgrade (Beta)
  • Additional REST APIs
  • Support for latest VMC on AWS and AVS platforms

Client and Agent Release

  • Auto install Zoom & WebEx plug-in
  • Support QT Tool to support Blast on Teradici zero clients
  • DEEM reporting Windows client
  • WebRTC SDK
  • Support comments in location based printing
  • Custom ports for UDP with AVI
  • Migrate to BellSoft OpenJDK
  • LinuxVDI add SuSE 15 SP4; RHEL 7.9; Debian support
  • PIV-D support iOS client
  • Blast tuner for easy pre-sets
  • Prevent multiple server icons with AVI, UAG & SAML IDP with HTML Access

App Volumes

  • Published Apps on Demand
  • Ability to Update Package Notes
  • Apps On Demand: Login Improvements for a Large Number of Apps

 

Dynamic Environment  Manager

  • The features in this release are the same as DEM 2209
  • No upgraded needed unless you are looking to align with Horizon 2212 ESB

 

 

Release Notes

Documentation

Horizon Universal License/Term Key Location – Where Are My License Keys

Horizon Universal License/Term Key Location – Where Are My License Keys

Overview

In this article, I would like to guide you on where to find your keys when you have transitioned from VMware Horizon perpetual licenses. Detailed information on why you should choose the term option vs universal will not be covered in this article.

First, you should know that there has been a shift towards subscription licenses within the end-user compute business unit for some time. In EUC, we were an early adopter of this model. Now, it seems that more of VMware is following this trend. To set the stage for your options, think of it like this: options can be broken down into Term subscription and Horizon Universal Subscription

 

Term Subscription

  • Keys can be obtained from the customer connect portal or through support.
  • No Redeployment.
  • Identical feature set as Horizon perpetual license.
  • Managing your keys is identical to how you are used to.
  • Should be and can be utilized in a offline/dark site.
  • Your keys will expire when the term is nearing it’s end. You will get notification in your Horizon Connection Server Administrator Console 30 days prior to expiration.
  • No Universal Console/Control Plane.
  • No Entitlement to cloud solutions and deployment* (U.S.Federal Only).

Horizon Universal Subscription

  • Keys can be obtained through Horizon Universal Console or support. The Universal Console/Control Plane is maintained by VMware and is stood up as part of your subscription.
  • Management services provided through the Horizon Control Plane/Universal Console.
  • No redeployment of on-premise pods is required,
  • A horizon edge/cloud connector installation is a hard requirement. The cloud connector is an appliance that resides on-premises and connects to the Control Plane. One Edge/Connector per POD
  • As of writing this article VMware still has assistance for setting up your first cloud connector/edge.
  • Entitlement to all supported cloud solutions and deployment options.

 

Accessing and Generating Your Keys In Version 1 Universal Console

After signing up for the Horizon Universal Subscription, you will receive an email with instructions and next steps. If this is your first time setting it up, you can follow the steps for onboarding, such as Horizon Service Deployments and Onboarding Pods All keys generated from the Universal Console will not be available in your Customer Connect portal. Currently the database is not shared with customer connect. If you do not have access to the version 1 console, you can contact VMware support for assistance in gaining access to your keys.

  1. Go to https://cloud.horizon.vmware.com and enter your Customer Connect Credentials that has the Horizon Cloud Customer Administrator Role.

 

2. If you are logged in to Customer Connect with the appropriate permissions, you will be able to see the ‘View Perpetual Keys’ link. By clicking on this link, you can generate new keys and view previously generated keys.

3. If you need to generate keys you can select the product version and generate the keys.

Accessing and Generating Your Keys In Version 2 (next-gen) Universal Console

Remember, even with the version 2 (next-gen) control plane, we need to deploy our Horizon Edge (analogous to the Cloud Connector in the version 1 control plane). You will also receive an email with instructions for onboarding after upgrading from perpetual. If this is your first time setting it up, you can follow these steps for onboarding: Onboarding Horizon Cloud Next-Gen.

Today if you have access to both version 1 and version 2 Universal Consoles you can generate your keys from version 1. If you only have access to version 2 then you need to open a ticket with VMware per this KB. VMware KB 2006985

Changing the View Connection Server Ciphers

Changing the View Connection Server Ciphers

Have you ever wanted to control your cipher suite or enforce a certain tls protocol in VMware View? Changing your cipher suite can be warranted for a few reasons. Maybe one cipher suite is to weak, or maybe development on a particular endpoint does not support this type of cipher. Or maybe your security policy requires you to do so. Whatever the reason may be you can control it with VMware at the server level forcing the clients to negotiate on only a few ciphers or protocols

To change the view connection server ciphers and negotiation protocol open a notepad and enter the following below. After you are done editing make sure you save as locked.properties

#should be ordered with the latest protocol first:

secureProtocols.1=TLS1.2

#this setting must be the latest protocol givin in the list above:

preferredSecureProtocol=TLSv1.2

# The order of the following list is unimportant:

enabledCipherSuite.1=TLS_ECDHE_RSA_WITH_AES128_CBCSHA

enabledCipherSuite.2=TLS_RSA_WITH_AES_128_CBC_SHA

copy this into: C:\program files\vmware\vmware view\server\sslgateway\conf