Using Scripts to aid the deployment of App-V packages makes the virtual applications more flexible and deployable in production. Prior to the App-V 5.1 release, this was done by manually editing the external Deployment and/or User Configuration.xml files. Not only was the editing originally a clunky process (leading to the development of a free editor toolACE to edit those files), but we found that dealing with these external files was cumbersome. If you used the App-V Management Server or Stand-alone models to deploy your packages, you could easily forget to use the external files. And if you used Config Manager instead to deploy the files were automatically applied, but, it was possible to forget that only editing the Deployment config meant that the UserConfig file might override the change.
I suddenly seem to be getting asked by a number of software vendors to help them support customers that are using App-V. This is fantastic! Vendors that want to support App-V? We have dreamed of this for 15 years now. I am thinking that four is perhaps more than just a blip, maybe it is a trend. I certainly hope so.
Last year I wrote an article on App-V and .Net Native Images and how they didn’t work with App-V.
This might appear to be a relatively unnecessary rule, but the idea is to demonstrate the kinds of configurations that you can achieve with FsLogix.
This article highlights some of the topics covered in the upcoming new version of the “3D Graphics for Virtual Desktop Smackdown” whitepaper authored by Team Remote Graphics Experts (@TeamRGE). Stay tuned for the announcement of the release date.
If you have read the previous articles on creating a minimal infrastructure App-V environment (Here) then you will have seen that you can use FsLogix Apps to manage the availability of globally published App-V applications. The only slightly sticky point is creating the FsLogix .fxr rules for each App-V package. Whilst the steps aren't overly time consuming (see here for an overview) they do require a manual set of steps to create a rule for each application. If you have 50 App-V applications this might take the better part of a day importing the app into the cache, creating a new rule, browsing for the App-V Package Root Path etc. If the app needs to be run through the sequencer again then the PackageID and VersionID are going to change meaning recreating the .fxr. The goal of this tools is to reduce the time, effort and increase the accuracy when creating rules for FsLogix. (At least until the FsLogix guys implement a CLI/API to play with ;-) ;-) ).
After spending 6 years at VMware as one of the initial Desktop Sales Engineers, it became clear that traditional application virtualization (AppV and ThinApp) were still not meeting the expectations of the users, admins, and the industry. Many people were seeking the utopia of single image management, with layered or virtualized applications, however this was very difficult to achieve, due to the complications of app-virt and the inherent complications of app isolation from the OS, and isolating apps that were designed to work together. VDI and application virtualization had promised to simplify the enterprise workspace, but the products coming to market seemed to be just as complicated as distributed physical desktops, but now with the added problem of some tools working in one environment, some working in another, and none working together.