• User device affinity is introduced, a method of associating a user with one or more devices. Software distribution in Configuration Manager 2012 is primarily user-based; applications are targeted to the user rather than the device
  • Assignment of Client Agent settings, Inventory collection, and Remote Control settings by collection offers increased flexibility in configuration
  • The Configuration Manager client agent now includes a Client Health check to identify and remediate agent issues
  • The Desired Configuration Management client feature has been enhanced as Compliance Settings, allowing for both identification of non-compliant systems and automatic remediation if desired
  • The new Role-based Administration feature flattens the complex hierarchies once required to isolate access to Configuration Manager features
  • The new state-based Application Model replaces the conventional Configuration Manager Package and Programs, incorporating dependencies and requirements for more granular software distribution
  • Software update groups and automatic deployment rules greatly streamline the management of deploying software updates to clients
  • Ability to “inject” new Windows Updates into existing WIM files used for Operating System Deployment by leveraging Component-Based Servicing
  • Remote Control, removed from Configuration Manager 2007, is re-introduced in Configuration Manager 2012 with complete multi-monitor and Aero interface support
  • The need for Secondary Sites and Proxy Management Points has largely been removed, as Distribution Points can now have rate limits
  • New Alerts feature allows enhanced monitoring of operations and conditions within Configuration Manager
  • New Content Library feature features Single Instance Store technology, removing redundant files found in multiple applications, packages, software updates, etc
  • Native mode has been eliminated, greatly simplifying the requirements for Internet-based client management
  • The Application Catalog server role has been introduced, granting end users the ability to request software.
  • Endpoint Protection integrated into the CM Console
  • Deploying Windows 8 / Server 2012 come SP1.

Read more http://myitforum.com/myitforumwp/2012/07/19/reasons-to-move-from-sccm-2007-to-2012/