Home
Microsoft

To simplify planning for IT, we have standardized the support lifecycle for the Microsoft Desktop Optimization Pack (MDOP) and are announcing a single end of support date for all the tools in the MDOP portfolio*. The Microsoft Desktop Optimization Pack is a suite of products that help to improve compatibility, simplify device management, reduce support costs, improve asset management, and improve policy control. Available as a subscription for Software Assurance customers, Windows Enterprise E3/E5 customers, and Microsoft 365 Enterprise E3/E5 customers. MDOP includes the following products:

Each product was created separately and later packaged as part of a single portfolio called the Microsoft Desktop Optimization Pack. However, each tool continued to have its own development lifecycle and, as such, its own support lifecycle.

The table below shows the original mainstream end of support date, the original extended end of support date, and the new, standardized extended end of support date for each MDOP product. Note that we are only extending extended support – and not mainstream support – for the latest version of each tool. For example, support for DaRT 8.0 is not being extended; support for DaRT 10.0 is.

Product

End of mainstream support

Original
end of extended support

New end of extended support

AGPM v4 SP3

April 10, 2018

Jan 12, 2021

April 14, 2026

App-V: 

  • Application Virtualization 5.0 for Remote Desktop Services Service Pack 3
  • Application Virtualization 5.0 for Windows Desktops Service Pack 3
  • Application Virtualization Hosting 5.0 for Windows Desktops Service Pack 3
  • Application Virtualization 5.1 for Remote Desktop Services
  • Application Virtualization 5.1 for Windows Desktops
  • Application Virtualization Hosting 5.1 for Windows Desktops

Jan 9, 2018

Jan 10, 2023

April 14, 2026

DaRT 10.0

April 13, 2021

April 14, 2026

April 14, 2026

MBAM 2.5 SP1

July 9, 2019

July 9, 2024

April 14, 2026

MED-V 2.0*

April 12, 2016

April 13, 2021

<not changing>

UE-V 2.1 SP1

April 14, 2020

April 8, 2025

April 14, 2026

What is the difference between mainstream and extended support?

While a product is in mainstream support, we continue to develop features for the product, provide updates and fixes, and offer support. When a product enters into extended support, we continue to provide updates and fixes and offer support, but will not add any new features.

How does this affect your previous announcement about MBAM being added to System Center Configuration Manager and Microsoft Intune?

We are still on track to add feature parity from MBAM to Microsoft Intune and Configuration Manager as noted in the May 2019 blog post, “Microsoft expands BitLocker management capabilities for the enterprise.” If you are using MBAM, but have not yet moved to the cloud, and are not using Configuration Manager, you can continue to use MBAM until April 14, 2026.

What does this mean for me?

If you are using any of the tools in the MDOP suite, we will continue to offer extended support for those products until April 14, 2026.*

Why did Microsoft choose April 14, 2026?

To make it easier for IT pros who use MDOP as a suite of tools, it made sense to standardize a single end of support date across all MDOP products. To ensure that we maintained the end of support promise we’d made to customers, we chose to align to the farthest date, April 14, 2026, which was originally just the end of support date for DaRT 10.0.

Learn more

For more information on MDOP, see the MDOP technical documentation. For more information on product lifecycles, see the Microsoft Lifecycle Policy page.


* Microsoft Enterprise Desktop Virtualization (MED-V) is not being extended. MED-V runs a Windows XP Service Pack 3 (SP3) virtual machine using Microsoft Virtual PC technology. Microsoft Virtual PC ended extended support on July 11, 2017, and Windows XP SP3 ended extended support on April 8, 2014.

15 Comments
Occasional Contributor

I assume this means that the MBAM integration to SCCM will also be postponed? 

Microsoft

Yannara - no. We aren't implying that at all. MBAM integration into Intune and SCCM are both on track at the scheduled timeline.

New Contributor

Hi - does this mean that MBAM will continue to be serviced for new Feature Releases of Windows 10? I.e. will support be present in MBAM 2.5 SP1 for Windows 10 1909 etc. when it is released (perhaps in the form of one of the servicing updates we see released periodically)?

Microsoft

We are no longer developing for MBAM. The MBAM features are still being rolled into Intune and SCCM (see blog post mentioned above), but MBAM (without Intune or SCCM) will continue to be supported until April 14, 2026.

New Contributor

Hi Joe, thanks for the quick response. I read the article and have tried the SCCM integration in the Tech Preview but it doesn't answer my question unfortunately. Scenario:

 

Secure network customers who want to deploy and manage encrypted Windows 10, who don't use Azure and seemingly can't use MDOP MBAM with modern versions of Windows 10 due to lack of support for say 1809 etc. What do you recommend for them while SCCM integration is being worked on???

 

I can't reccommend that they use MBAM as they won't be properly supported on recent versions of Windows 10, I can't recommend Azure/Intune as they can't use it in their environment and SCCM integration isn't available yet. So that leaves AD for key storage which isn't really fir for purpose when comparing with the features enabled with MBAM.

Microsoft

The MBAM client is supported on all Windows 10 versions. Our public documentation does not state any specific versions. Though we are no longer developing for MBAM, we do ensure its supported on all SAC releases of Windows 10. Here's our public support configuration:
https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/mbam-v25/mbam-25-supported-conf...

New Contributor

That's perfect. Thanks for the clarification. I was confused by service releases explicitly stating the addition of new Windows 10 versions and didn't know if this would be included in extended support going forward e.g. the May Servicing Release added support for Windows 10 1903:

https://support.microsoft.com/en-us/help/4505175/may-2019-servicing-release-for-microsoft-desktop-op...

Appreciate you clearing up the confusion :)

Occasional Visitor

Can we safely assume the App-V client in MDOP is for non-Windows 10 clients, and that the Windows 10 built-in App-V is not subject to this announcement?  Also what about the App-V Server?  (for publishing).  Thank you.

Microsoft

The App-v client built into Windows 10 from version 1607 will stay with the Windows 10 lifecycle. The extension is for the Server pieces.

Occasional Contributor

Joe, any insight when MBAM will be fully integraded in SCCM? 1910? :) 

The problem is, that we have been pending multiple projects for 6 months now (I work at large IT Service Provider) around MBAM because of this situation. We have multiple customers wanting reports and Bitlocker automation but not going in cloud. 

Microsoft

Those customers can still use MBAM; there's no reason to put any projects on hold. MBAM will be integrated into Configuration Manager when its ready :-). Our current schedule still has this happening in CY19, but we can't give an exact date at this time. 

Occasional Visitor

We are quite dependent upon AGPM. Is there a feature that is to supersede AGPM?

Occasional Contributor

Joe, naturally no customer would now order any MBAM implementation with old technique. Sense the anouncement of end of life happened in 2018 summer, everyone is just waiting…. business suffers because of this.

Occasional Visitor

Definitely interested to hear about what will happen with AGPM and DART (especially the latter).

Are there any plan to make these part of existing products (as MBAM which is being integrated with SCCM, or so I heard)?

Or maybe (wishful thinking here), making these available for free/open source?

Occasional Contributor

Is there an update as to the next version of AGPM? The last version I saw was v4 sp3. We heavily use GPO in our server environment and are looking to move away from Quest GPOAdmin.