We’re excited to deliver the latest version of our User Environment Management and Application Layering solutions in ProfileUnity and FlexApp v6.8.3 r2.
ProfileUnity and FlexApp v6.8.3 r2 Management Console
The new r2 version builds on v6.8.3 that was first available earlier this year. Version r2 has updates to our existing features and a few new features as well such as VHDX support for ProfileDisk and FlexApp and hourly billing for the AWS Marketplace. This solution also remains available in the Microsoft Azure Marketplace as BYOL.
Now that Azure WVD is GA, you are starting to hear more about MSIX and the strategy of attaching applications to a WVD OS. MSIX is the Windows app package format that provides a modern packaging experience to all Windows apps. The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new, modern packaging and deployment features to Win32, WPF, and WinForm apps. Continue reading →
Amazon Workspaces Overview “Amazon WorkSpaces is a fully managed, secure desktop computing service which runs on the AWS cloud. Amazon WorkSpaces allows you to easily provision cloud-based virtual desktops and provide your users access to the documents, applications, and resources … Continue reading →
I have spent most of my career discussing applications and
how to manipulate them. It is safe to say that 2019 has seen some techtonic
shifting in the application space.
Microsoft, has surfaced (no pun intended) to mix it up in
the application space again. MSIX is a new
application installation format with a goal to become the new defacto standard
for application packaging baselines.
At the end of 2018, the Amazon AppStream 2.0 team released a new dynamic application framework feature that allows third party tools to help manage application entitlements and deliveries in real time. Liquidware is excited to announce that both ProfileUnity … Continue reading →
In my last blog, (please read this first as it goes into the actual architecture of FlexApp and how it’s different) I said I’d talk about a specific example of why you cannot simply say ‘all layering is the same’. In that write up, I pointed out a number of differences architecturally, but I really want to bring this home and show how these differences matter. My example is with Citrix Provisioning and how Citrix App Layering and FlexApp interact with it. Continue reading →
I was chatting with a customer the other day about FlexApp and they told me that “it’s a different kind of layering and I like it” – it’s not the first time I’ve heard that. This got me thinking ‘why are FlexApp customers having an all-around better experience when compared to other layering technologies. When I look at public forums like Twitter, user groups, forums, etc the overwhelming opinion appears to be that all layering products are essentially the same and if an application won’t work in one, it won’t work in any others. I feel your pain and I just want you to know “Not all layering products are the same.” While Citrix App Layering (CAL), VMware App Volumes and FlexApp share the “layering” moniker, FlexApp couldn’t be more different from the competition (see 9 things that FlexApp does that no one else can or does). It’s these differences that allow us to package applications that others cannot, deliver those FlexApps to the appropriate end point or user and do this in an extremely efficient manner very, very quickly. Continue reading →
FlexApp has a lot going for it. Architecturally it’s very different than other layering technologies. This difference gives FlexApp a much better application compatibility percentage when compared to being able to dynamically deliver layers to Windows.
One of the things I love about FlexApp is that it has taken the layering paradigm and essentially turned it on its head. We’ve all “grown up” thinking of layering as done in a particular way but FlexApp shows there are other ways of accomplishing the task of delivering applications dynamically. One of the critical designs of layering is figuring out what happens when files, folders or registry entries conflict. FlexApp uses a technology called Micro-Isolation to handle these types of conflicts. The technology was developed because of how FlexApp builds the view of the operating system file system and registry. It is a very different way of looking at how layers are laid down on the image and how conflicts are handled.
This blog is really about what I thought I knew about layering products and how much I simply didn’t know. I’ve been working with layering for about as long as anyone and I made the mistake of thinking that all layering products were essentially the same. Sure they each did things a little differently but in the end the concepts were the same and their abilities were, for all intents and purposes, the same. Boy was I wrong.