So the App-V client has some hidden registry keys to disable the different subsystems globally and this can be very useful.
Months have passed since our first blog on the topic (Recipe: Virtualize Edge with App-V). During this time the Edge has proven to be a very stable App-V application. If I read from time to time that a new critical vulnerability is emerging, the virtual Edge can react quickly. At this point I would like to point out that we regularly create the Edge and other browsers for our customers. This is done with known AppV bugfixes and with customer specific settings. If you are interested please contact me. For example on Twitter @Nickinformation
The old recipe for SSMS 17.x was a nice success for me with about 1000 hits. Especially the comments were enlightening. The licensing problem could be solved with a simple registration key. With 18.5 there is nothing more to do here.
Microsoft released a new Edge Browser based on the Google Engine Chromium a few weeks ago. This will be installed over an existing installation, but can also be installed on server systems that did not have an Edge Browser before. It is interesting that this Edge can be installed without problems on older systems like Server 2012 R2 or Windows 8.1. Nice is that the new Edge-Browser can be virtualized easily with App-V. We have been using an App-V variant of the application since the release and have had no problems with it so far.
The package works on current and on all older Microsoft operating systems when created with a classic (not ADK) sequencer (App-V 5.1). The Edge App-V package can work parallel to an existing Edge. An App-V Edge browser has its own settings, if you like. For example, your own homepage or another search engine. All this is only valid for Windows systems. Because the new Edge-Browser is also available for MacOS!
Again and again we had to find out that sometimes App-V shortcuts in the user profile or even globally on the back. This can happen for various reasons. In particular, after a missing unpublishing for a user even if the package no longer exists. For nonpersistent VDI or Terminal Server this is no problem in the global context under C:\ProgramData\Microsoft\Windows\Start Menu\Programs, because the systems are always in their original state after a reboot.For user profiles, however, this is a problem.
Since I have a little more time right now, I finally get to publish the script I created a long time ago for this problem.