ConfigMgr 1511 (better known as ConfigMgr as a service) is released yesterday. Have a look on my earlier blogpost for that. Let's have a look at some new features known so far:
-ConfigMgr is a 'as-a-service' solution from now on!
-ConfigMgr is called 1511 because of versioning, which is YYMM
-Microsoft has the ability to update ConfigMgr when needed
-With a Maintenance Window you can choose when the update is done!
-No complex individual upgrades are needed anymore
Windows 10 support
-It has full support for Windows 10 (provisioning, servicing, imaging)
-An in-place upgrade task sequence is available by default
-Windows 10 on-premises MDM possible, but Intune subscription is still needed
-Windows 10 servicing possible and dashboard integrated
-Both Endpoint Protection and Windows Defender management
Updates and servicing:
-No servicepacks, CU's and hotfixes needs to be installed anymore
-Client deployment monitoring in the console (cool feature)
-No reboots are needed when update ConfigMgr with new functionality
-Preferred management points in ConfigMgr possible (new feature)
Other new features:
-Multiple deployments for Automatic Deployment Rules :)
-Cluster aware patch management (instead of using WSUS)
-Combined Software center and Application catalog (finally)
-and much, much more...
Because Microsoft is moving away from Silverlight (using HTML5 instead) no Application Catalog (as second Software Center) is needed anymore, but both Application Catalog roles still needs to be installed. Microsoft is using a unifying Software Center now, which can handle both packages and applications. That's great for end user experience if you ask me! It can be enabled in Client settings.
Migration is possible from 2007 (side-by-side) and 2012 (in-place) with the recommendation to run the latest Cumulative Update.
Have a look at What’s new on the Configuration Manager horizon (session by @Tim_DK) for more information!