One of the many feature benefits in ProfileUnity is its ability to persist Office 365 Outlook Search Indexing from non-persistent desktop, DaaS, RDS, and Citrix XenApp sessions. This is very helpful to end users because in a non-persistent environment you would not want to keep indexing or OST files in the users roamed or streamed profile because the files would be quite large and cause a slow logon. If you turned on local indexing for each non-persistent Outlook session, the indexing process would need to start over again, causing many resources to be used each desktop session.
Of all the interesting notions a new year brings with it – fresh starts, the chance to predict the future, etc. – one of the things I have come to appreciate is the ability to look back and learn.
I’m very excited to announce the general availability of Stratusphere UX 6.0. With this release, the solution has received an architectural upgrade, a dashboard builder, support for new client devices, and application features to facilitate application strategy and reporting.
Under the Covers
Primary to this release is a new and highly-scalable architecture, which will support an increase of 400 percent in scale and increases of 40 percent in interface responsiveness and over 100 percent in reporting time. Additionally, Stratusphere UX 6.0 introduces a distributed Collector Appliance, for the aggregation and collection of Stratusphere Connector ID Key (an extremely lightweight in-guest agent) data and network data—related, Connector ID Keys now offer a feature to failover to another Stratusphere Collector in the event of an appliance or infrastructure failure.
Just over a year ago, we added GPU visibility within Stratusphere UX. Through our partnership and the NVIDIA GRID software development kit made available to us, we incorporated machine-level GPU metrics into the Stratusphere UX Advanced Inspectors. Very soon Liquidware will … Continue reading
Amazon RE:Invent 2017 is right around the corner and I am excited to announce that I have been selected to co present during a session this year. Justin Bradley, one of the top solution architects from the Amazon EUC space and we will be presenting session GPSTEC316 titled “GPS: Image management Best Practices for Amazon WorkSpaces and AppStream2.0“.
Yes, Windows 10 to Windows 10 migrations are now officially a “thing.” Confused? Don’t be, read on…
By several indications, Windows 10 adoption rates are not even at 50% for enterprise sized businesses, and plenty are still running Windows XP, Windows 7, and Windows 8.1 in pockets. However, even as Windows 7 still dominates the market, Windows 10 is still coming on strong.
Profile Containers/Disks for Windows desktops enable Administrators to offload the entire user profile to a profile disk (VHD or VMDK). This approach allows for an otherwise large profile to be read at a block-level (very efficient) over the network. Liquidware ProfileUnity features the option to use a ProfileDisk™ and containers in ProfileUnity. They can be great – except when they are not. Here are the Pros and Cons that you should know before you rely solely on a profile container/disk to provide an excellent user experience.
- Great for offloading Office 365/Outlook caches
- Ideal to solve Outlook indexing conundrums for virtual desktops like XenDesktop, XenApp, and VMware Horizon.
- Really great at keeping cloud storage (Microsoft OneDrive, Dropbox, Amazon Drive, Google Drive, etc) on a virtual network drive.
- Run in the user context only and therefore can’t pick-up or virtualize other areas of the user profile outside of shell folders.
- Profiles are exactly like a local profile except it is on the network so they are susceptible to profile corruption.
- They are locked to a Windows OS version so you must have a disjointed profile disk/container for every OS the user logs onto, the user cannot migrate their profile or co-exist it with another Windows version.
- Network only – there is no method to go offline. Laptops that even occasionally leave the office are not a candidate for a profile disk/container.
We’ve recently signed a new distributor, Prianto, in the UK. They were established to address the market needs for specialized distribution, as the smaller, more niche organizations were being swallowed up by the large, fulfillment players. In the few months since we started working with the team at Prianto, we’ve seen the momentum with ongoing and new partner engagements swell. In particular, we are seeing avid interest in moving desktop workloads to the cloud, with an emphasis on Amazon Workspaces.
“Nuvens is an AWS WorkSpaces VDI specialist partner. We help clients move from both traditional desktop client infrastructure and Citrix environments into the AWS WorkSpaces managed infrastructure.
Every feature that has been incorporated in Liquidware FlexApp is in the product because either a customer has requested it or our experienced development and product management teams knows first-hand how important it is to a provide a seamless, enterprise, and scaleable application layering solution.
FlexApp layering has emerged as a leader as a scalable enterprise-ready layering solution. If you are evaluating layering solutions or working on a RFP (Request for Proposal), consider a solution that leads the market with multiple ways to save time, make users more efficient, and save money.
Here are 10 exclusive ways that FlexApp sets the bar for application layering in the industry.
In comparison to traditional ways to install applications and other application delivery methods that have been around for quite some time – such as application virtualization – application layering technology is still in its early stages. Because app layering is relatively new, tools for editing existing layers are unfortunately sparse.
You might ask, “Why would I need to edit an application layer?” Well, you could find yourself needing to edit registry keys for an application layer because you want the application to behave differently. So, how would you edit registry keys for a layer that is already created? The default answer for all layering vendors (assuming they can even edit layers, you should ask!) is to put the layer back into capture or packaging mode and make your registry changes there. Sure, this will work, but this is a “sledgehammer” approach when a “scalpel” may be better. When you put a layering tool into capture mode, it records all changes that happen to the operating system. This is a bit heavy-handed when you’re only trying to make a single registry key change.