As we approach VMworld 2016, there has been a tremendous amount of excitement building around the solutions from Liquidware Labs. We just released version 6.5.5 of ProfileUnity with FlexApp back in June, here are a few of the highlights:
Liquidware Labs is announcing the release of a new WP “VMware UEM and App Volumes Overview Comparison with Liquidware Labs ProfileUnity and FlexApp” White Paper. At its core the focus of this new whitepaper attempts to compare and contrast the two platforms. Additionally, the whitepaper provides real world customer based implementation guidance around when to use a Liquidware solution as opposed to the VMware solution stack. Continue reading
Liquidware Labs has released a new whitepaper detailing how FlexApp can integrate with the FlexCast delivery models from Citrix. Click here to down load the new FlexApp Integration with FlexCast models from Citrix Whitepaper.
What is “FlexCast” from Citrix? Continue reading
FlexApp Layering from Liquidware Labs is evolving at a rapid pace. With that in mind we have updated the content with the primary white paper. Here is link to the “FlexApp: Application Layering Technology White Paper”. Continue reading
I remember those days back in school when my teacher would ramble at the chalkboard explaining some new concept or theory and then my marveling at the equations she used to document the solution. Simple. Beautiful. I was (and am) a math nerd.
As many of you know the running joke in our industry for the past, heck, 8 years almost – has been that this year, no doubt, without question, slam dunk – is going to be the YEAR OF VDI. I … Continue reading
2015 was an impressive year for product announcements and innovations. Liquidware Labs re-released the FlexApp Layering platform after a significant architecture shift. Customer adoption and validation for FlexApp has been extremely positive. Looking back, something seemed to be missing in the EUC space with respect to application lifecycle management. Application virtualization started off strong but has tapered off lately, primarily because of compatibility challenges. The timing for a platform like Application Layering was perfect as companies push further towards desktop integration with the “Cloud”. FlexApp Layering is poised to take its place as one of the pillars of the application layering space.
The FlexApp Layering Technical FAQ has been released by Liquidware Labs. As customers look to adopt and implement the FlexApp technology, they are bound to have questions. Questions within the FAQ are divided into various sections for faster reference:
- FlexApp Layering Requirements
- FlexApp Layering Installation and Configuration
- FlexApp Storage
- Creating FlexApp Layers
- FlexApp Management
- Updating FlexApp Layers
- FlexApp Layering with remote Desktop Session Hosts / Citrix XenApp
- Troubleshooting FlexApp Layers
- Getting help with ProfileUnity
One of the potential challenges that application layering technology creates is around interlayer application conflicts with respect to the corresponding host operating system. In an effort to address these potential challenges, Liquidware Labs developers have created a feature called Micro-Isolation.
The recent release of ProfileUnity 6.5 was a significant platform improvement for both ProfileUnity and FlexApp. The commitment to robust integration points between ProfileUnity and the FlexApp layering platform is reflected based on the positive feedback from current and new customers alike.
One question that comes up in conversation a lot recently is where App Virtualization stops and App Layering starts. There are typically no wrong answers when attempting to design application solutions around both App Virtualization and App Layering, but what is clear so far is that App Layering has a wider compatibility with enterprise applications. There seems to be another option, why not combine them for a best of breed solution for enterprises. This blog entry will examine the combination of FlexApp Layering from Liquidware Labs and ThinApp from VMware.
A number of years ago when I first started working with ThinApp, I was told they would run faster if they were launched from the local disk versus a network share. For physical or persistent OS, this can be accomplished by copying the ThinApp package locally and then running thinreg.exe against the file(s) or by packaging the application with ThinApp as an .msi package and installing it on the OS. For non-persistent desktops, copying the files locally or running the msi version isn’t really an option because this would need to be done each time a user logs on to a desktop.