A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
For us this effort is still valuable. We use not only virtual desktops but published applications as well. The client itself has had instances of vulnerabilities and the notion that the BITS can be updated without launch to auto-update is very valuable as it reduces the update cycle substantially.
Ran into a fun issue while testing this app. Installs work great, updates through WSUS/ConfigMgr Updates however, fail due to the fact that the installer checks to see if Windows Updates are running and fails out if they are running during the installation. Since it is in fact Windows Update running the installation, I do not see a way of supporting this product via WSUS/ConfigMgr Updates. Is there still enough value to add this product as a ConfigMgr App, Intune App and Intune Update?
Actually, it looks like the ESB is a different type of release: Horizon 8 2111 is an Extended Service Branch (ESB). Approximately once a year, VMware designates one VMware Horizon release as an Extended Service Branch (ESB). An ESB is a parallel release branch to the existing Current Releases (CR) of the product. By choosing to deploy an ESB, customers receive periodic service packs (SP) updates, which include cumulative critical bug fixes and security fixes. Most importantly, there are no new features in the SP updates, so customers can rely on a stable Horizon platform for their critical deployments.
I was able to download 2111 without logging in. After downloading, I logged in and the only difference is that it takes me directly to the downloads. No special paywall or licensing from what I can see.
Last question (I think). I see there is a 2106 release and a 2111 release. The 2111 release says it is an "Extended Service Branch", does that mean that it is typically behind a paywall, or has special licensing or other considerations?
We are running the following line in powershell- & cmd /c $path /s /v`"/qn ADDLOCAL=Core,NGVC,RTAV,ClientDriveRedirection,PrintRedir,VmwVaudio,HelpDesk`" | Out-Null
It seems there are a number of command line options that can be accepted with this application.
The basic silent installation of this app seems to be /S /v"/qn", however, if we provided that as the default installation string, adding additional parameters would be more difficult.
How common is it to customize the install string for this application? From what I can tell, it is at least very common, and at most required. If it is the case that a custom commandline is basically required for this application, we will ship it with the default command-line argument being "/s". That way customers can provide custom command-line options, but would have to include the /v"/qn" manually.
please :)
+1
+999
any chance?
Any updates on this application request?
:)))
bump :D
Having a ConfigMgr app would still be super helpful.
It is still worth it. If WSUS doesn't work, we can always deploy as a repeating task sequence.
yes please
For us this effort is still valuable. We use not only virtual desktops but published applications as well. The client itself has had instances of vulnerabilities and the notion that the BITS can be updated without launch to auto-update is very valuable as it reduces the update cycle substantially.
Ran into a fun issue while testing this app. Installs work great, updates through WSUS/ConfigMgr Updates however, fail due to the fact that the installer checks to see if Windows Updates are running and fails out if they are running during the installation. Since it is in fact Windows Update running the installation, I do not see a way of supporting this product via WSUS/ConfigMgr Updates. Is there still enough value to add this product as a ConfigMgr App, Intune App and Intune Update?
Actually, it looks like the ESB is a different type of release:
Horizon 8 2111 is an Extended Service Branch (ESB). Approximately once a year, VMware designates one VMware Horizon release as an Extended Service Branch (ESB). An ESB is a parallel release branch to the existing Current Releases (CR) of the product. By choosing to deploy an ESB, customers receive periodic service packs (SP) updates, which include cumulative critical bug fixes and security fixes. Most importantly, there are no new features in the SP updates, so customers can rely on a stable Horizon platform for their critical deployments.
I was able to download 2111 without logging in. After downloading, I logged in and the only difference is that it takes me directly to the downloads. No special paywall or licensing from what I can see.
Last question (I think). I see there is a 2106 release and a 2111 release. The 2111 release says it is an "Extended Service Branch", does that mean that it is typically behind a paywall, or has special licensing or other considerations?
We are using the EXE.
When installing this app, are most people installing with the exe as provided by VMWare, or extracting the MSI from the EXE and deploying that out?
+1
We are running the following line in powershell-
& cmd /c $path /s /v`"/qn ADDLOCAL=Core,NGVC,RTAV,ClientDriveRedirection,PrintRedir,VmwVaudio,HelpDesk`" | Out-Null
We are looking more into this application now.
It seems there are a number of command line options that can be accepted with this application.
The basic silent installation of this app seems to be /S /v"/qn", however, if we provided that as the default installation string, adding additional parameters would be more difficult.
How common is it to customize the install string for this application? From what I can tell, it is at least very common, and at most required. If it is the case that a custom commandline is basically required for this application, we will ship it with the default command-line argument being "/s". That way customers can provide custom command-line options, but would have to include the /v"/qn" manually.