Yesterday a new announcement has been done. There is a new servicing branch called: Long-Term Servicing Branch (LTSB) of Configuration Manager. Where ConfigMgr Current Branch offers new functionality and support for Windows 10 and Windows Server 2016, LTSB of Configuration Manager is not. When Software Assurance (SA) or equivalent subscription rights became expired, customers, per product terms, would have to move back to ConfigMgr 2012 (R2). Besides of support for an fixed 10-year lifecycle (and equivalent subscription rights as mentioned), I guess there is no need to use the LTSB version of Configuration Manager.
While the LTSB is derived from the current branch of Configuration Manager (version 1606), it is scaled back and reduced in functionality to permit the extended support model. LTSB of Configuration Manager will not receive new functionality or support for new Windows 10 and Windows Server 2016. It will continue to receive security updates only. By design, LTSB of Configuration Manager is intended to be fixed in functionality and very infrequently updated, so any features or components that require continuous updating or are tied to a cloud service have been removed. What's left is ConfigMgr 2012 (R2) with less features and no Hybrid MDM.
These removed features include:
-Support for Windows 10 Current Branch (CB) and Current Branch for Business (CBB)
-Support for the future releases of Windows 10 LTSB and Windows Server
-Windows 10 Servicing Dashboard and Servicing Plans
-The ability to add a Microsoft Intune Subscription, which prevents the use of Hybrid MDM and on-premises MDM
-Cloud-based Distribution Point
-Support for Exchange Online as an Exchange Connector
-Any pre-release features available in the current branch of Configuration Manager
Not my cup of tea :-)
Source: Enterprise Mobility and Security Blog