Brian Madden and team just completed their 17th BriForum. Wow do I feel old now.
It was an honor to be named as one of the Best of Citrix Synergy 2015 Award Winners, and the winner for the Application and Desktop Virtualization category.
With our announcement at Synergy this week we hope to have put the final nail in the coffin for traditional profile management approaches in VDI and RSDH.
I build a LOT of App-V Sequencer and Client VMs over the course of a year. Not only do I test each release, but hotfixes and a bunch of private builds that I get, and then I also need to handle changes to my own tools (which need testing before release). Plus I want to reuse the technique to build VMs for all of those training classes. So it should be no surprise that I automate that process as much as I can.
"Traditional profiles are dead, long live layered profiles!"
This article has been in my pipeline for quite a while, and after talking to a number of subject matter experts I thought that now is the time to finally publish it: When dealing with virtual Windows desktops or remote user sessions, profile management and personalization pops up as a discussion topic or a pain point on a regular basis. This has not changed since 10 years and it is independent of the underlying virtualization or remoting technology. As a rule of thumb, once or twice a year, Windows user profile management is on the agenda. But things have changed over time. A couple of years ago, it was all about maintaining the EXACT layout of a user’s desktop. Moving application icons by a couple of pixels or removing the custom wallpaper may have resulted in seriously angry users. Typically, this is not the case anymore since users are used to having access to other personalized “desktops”, like their tablets or smartphones. They have learned how to deal with different background images and user interface element locations. But still, user profile management is a hot topic when it comes to maintaining application-specific settings across various work-related Windows desktops.
Last June, I posted a way to sequence AutoCAD 2015 using App-V 5 on a Blog post here. This was done using the then latest-and-greatest version of App-V, 5.0 SP2 with Hotfix 4. We had been having trouble with many AutoCAD versions since the 2014 versions started appearing with some sort of incompatibility, and Hotfix 4 overcame whatever that was.
Coming Soon! In version 4.0 of AppV_Manage, we will have an optional (paid for) feature to generate package documentation in Microsoft Word format. This work is an outgrowth of the package analyzer function. In version 4 I have enhanced the analysis, going beyond reporting on extensions reported by App-V but also analyzing the package contents to see some of what the packager didn’t notice.
You have no doubt heard the term “Mobile First” used liberally these days. Clearly, enterprise adoption of smartphones and tablets has exploded lately (and, continues to grow). But, what does it mean and how does it affect your Endpoint Management strategy? The modern Mobile platforms have adopted a fundamentally different architecture compared to Windows OS of the past (XP,7 - we will call this "old Windows"). Along with iOS and Android, Microsoft also moved to a similar OS model, initially with Windows Phone, and going forward with a unified Win 10 platform.
One of the things I really enjoy about my current role in the virtualization industry is evaluating new products and concepts in my test lab. I’m in the lucky situation that Dell, Intel, NVIDIA, AMD, HP and some other vendors provided me with wonderful hardware, but sometimes off-the-shelf servers are simply not the right choice to start with. This is particularly true if you want to compare different remoting products in a fair and reproducible way. Shawn Bass and I began building our own “Darco Labs” reference servers when we seriously started comparing remoting protocols in our labs. You better know exactly what you’re doing and what kind of hardware you are using when you’re challenging vendors such as Microsoft, Citrix and VMware. For the sake of credibility, it is a prerequisite to select hardware that is equally compatible with the latest versions of all tested virtualization and remoting products. So this article is about the lessons I’ve learned when building the white label server for the 2014 remoting protocol comparisons.