{"id":2609,"date":"2017-03-03T09:48:25","date_gmt":"2017-03-03T14:48:25","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=2609"},"modified":"2017-03-10T08:16:30","modified_gmt":"2017-03-10T13:16:30","slug":"2609","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=2609","title":{"rendered":"App-V 5.1 Lifecycle"},"content":{"rendered":"

Sebasitan, the German Microsoft Escalation Engineer we often get new news from about App-V, recently blogged about the dates for the lifecycles for App-V 5.1.\u00a0 Before people get upset, let’s make sure you understand what this means.<\/p>\n

On the date when a product version, or service pack, is released, it sets the clock ticking for end of free mainstream support (general updates and fixes) and for extended support (security fixes), and more.\u00a0 This is true for both operating systems and additional products.\u00a0 Sometimes Microsoft will extended the original date from that clock, but normally not.<\/p>\n

App-V 5.1 refers to the MDOP based version of App-V released in 2015.\u00a0 As the product is shipping against existing operating systems, this means that those OSs that it supports will be older and normally have expiration dates prior to that of the released product. And that is the case here.<\/p>\n

So will there be a 5.2 version of App-V?\u00a0 Yes, there already is.\u00a0 Well sort of.<\/p>\n

Last summer, Microsoft added App-V directly into the operating system for Windows 10 1607 and Windows Server 2016.\u00a0 Internally, it is marked as version 5.2, but we are now in a new way to release App-V so the correct way to refer to a version is to reference the OS build you got it with.\u00a0 So starting with 5.2, the dates are tied together. From what I hear, maintenance will occur as follows:<\/p>\n