On the Art of Predicting Compatibility Regression when Assessing Risk

  In my last blog post: (https://blogs.technet.microsoft.com/gladiatormsft/2018/02/20/determining-an-applications-impact-when-assessing-risk/) I discussed my first recommended vector for assessing an application’s risk: impact to business or organization. In this post, I will discuss the second recommended vector: probability of regression. Internally at Microsoft, we refer to these as technical blockers. Throughout the first 5 iterations of Windows 10, we’ve…


Determining an Application’s Impact when Assessing Risk

In my most recent blog (https://blogs.technet.microsoft.com/gladiatormsft/2018/02/14/leverage-a-risk-based-approach-to-application-compatibility-testing/) I discussed how successful shifts to managing application compatibility involve moving to a model that prioritizes testing according to risk factors. The model I usually recommend to customers is to apply a common two-dimensional graph based on two primary risk factors: Impact to business and the application’s likelihood of…


Leverage a Risk-Based Approach to Application Compatibility Testing

Once upon a time, application compatibility projects usually followed these basic tenets: 1.)     Find all the applications being used. 2.)     Rationalize as much as possible. 3.)     Thoroughly test as many as possible. 4.)     Repackage all the applications. Depending on the size of the portfolio and the number end-users, these projects lasted from 9 to 12…


How Detailed is Your Enterprise Application Catalog?

Over the past several years, I have been involved in many application projects. Whether the project was centered around packaging, virtualization, or compatibility testing for operating system migrations (as my specialty is now) a variable for success was and remains – the enterprise application catalog. You’ll read synonyms for this as well (including package store,…


Recent App-V Case Studies

Internally, I was recently asked if I had any examples of recent App-V Case Studies that other potential App-V customers could view. Many case studies have previously been mentioned on the legacy App-V team blog but those were for older versions of the product. Many of our customers are looking to find examples of App-V…


A New MED-V Blog Post . . . Yes, for Real

For most individuals in my profession, any plans that were originally made for today were upended by the recent worldwide cybersecurity event. To assist our customers still on legacy systems, patches for the MS07-010 exploit were made available for Windows Server 2003 and Windows XP. While Windows XP has been out of support since 2014,…


Resolving the App-V 4 – SQL Server 2008 R2 Supportability Conundrum

Over the past 6 months, I’ve had quite few customers coming to me with concerns regarding what they see as a potential supportability gap for legacy App-V 4 infrastructures. Their main concern lies with the fact that App-V 4.6 SP3 remains in support through July 2020 while SQL Server 2008 R2 (the latest version it…


On Debugging Virtual Applications Part 4: The Case of the Missing Dump

I’ve been blogging lately (well . . . not exactly lately) about debugging virtual applications that misbehave – whether by hanging, crashing, or spewing some strange error message. In discussing the use of tools, one question I often get is the relationship of attaching the debuggers to the virtual application inside or outside the virtual…


Application Virtualization and Compatibility at Microsoft Ignite 2016!

Greetings all! If you are headed to Atlanta for #MSIgnite this year, I wanted to give you a heads up of some key sessions that will interest those of you looking specifically for application compatibility, App-V, and UE-V-related content. If you do not have a chance to see any of these in person, you can…


On Debugging Virtual Applications: Part 3 – Situations where a Debugger is most needed for Virtual Applications

In parts 1 and 2 of this series, I’ve covered some of the basic fundamentals of the concept of debugging compiled software code which, for the most part, has been a black box for many working with virtual applications. In part 3, I would like to now move the discussion towards those situations that warrant…