New Features in SCCM 2012

•  

Below are the new features introduced and improvements made in the SCCM 2012 when compared with the SCCM 2007:-

^NewAutomatic client health remediation: The Configuration Manager 2012 client sends its health status to the site server on specified interval (by default at mid night). For example: if certain key services are running or not. If not, those services will automatically be started on the client.

^NewApplication Catalog website: Application Catalog website is the self-service portal that allows users to browse and install available software or applications from the Software Library by entering below URL in the browser:http:///CMApplicationCatalog.

·         The Application Catalog website point and the Application Catalog web services point. These site system roles require IIS and support the new client application, Software Center.

Client User Experience

·         SCCM 2007: Run Advertised Programs

·         SCCM 2012: Software center

Software install from Website

·         SCCM 2007: None

·         SCCM 2012: Application Catalog

^Improved State-based application deployment: Configuration Manager 2012 provides more control to the administrators during application deployment by defining if the application is optional or required and whether the application must be installed or uninstalled. SCCM 2012 regularly monitors the state of the application deployment. For example, if an application deployment type is Required and the user uninstalls it, Configuration Manager automatically reinstalls the application.

^NewUser-device affinity: Configuration Manager 2012 associates a user with one or more specified devices, called primary and secondary device. Instead of deploying the application to all devices, we can tag the application to the user. So, when a user will log in to his primary device, entire application will be installed on that device. But if user log in to some other device, not primary device, the same application can be deployed as a virtual application.

ü  User-centric approach instead of device-centric

^NewDistribution point groups provide a logical grouping of distribution points for content distribution. When we distribute content to a distribution point group, same content will be distributed to all distribution groups that are members of the distribution point group. New distribution points can be added at any point of time to the distribution point group. Distribution point that can be added in the distribution point group can belong from a single site or from any site in the hierarchy.

^NewBoundary groups: A boundary is a network location on the intranet that contains users and devices. Boundaries can be Active Directory site name, IP subnet, IPv6 prefix, or and address range. To use a boundary, it must be added to one or more boundary groups. Boundary groups help client in locating assigned site and locate content when they have to install application, software, operating system images etc.

^NewApplication revision history: Configuration Manager 2012 creates a revision of an application or adeployment type contained in an application whenever we make any changes to the application. It helps in restoring a previous revision of an application, or deleting an old version.

^NewContent management: Configuration Manager 2012 provides the content management tool for managing content files for packages, applications, software updates, and operating system deployment. Content management feature relies on the distribution point site role.

^NewActive Directory Forest Discovery is a new discovery method that can discover subnets and Active Directory sites, and can add them as boundaries for your hierarchy.

^NewThe enrollment proxy point, which manages enrollment requests from mobile devices, and the enrollmentpoint, which completes mobile device enrollment and provisions AMT-based computers. These site system roles require IIS.

^Improved In Configuration Manager 2007, client agent settings are configured on a per-site basis and you cannot configure these settings for the whole hierarchy. In System Center 2012 Configuration Manager, client agent settings and other client settings are grouped into centrally configurable client settings objects that are applied at the hierarchy.

^Improved Fallback site

In Configuration Manager 2007, automatic site assignment would fail if the client was not in a specified boundary. New in System Center 2012 Configuration Manager, if you specify a fallback site (an optional setting for the hierarchy) and the client is not in a boundary group, automatic site assignment succeeds and the client is assigned to the specified fallback site.

^Improved Sites are no longer configured for mixed mode or native mode. Instead, you secure client communication endpoints by configuring individual site system roles to support client connections over HTTPS (PKI certificate) or HTTP with self-signed certificates.

^Improved Site-to-site communication now uses database replication in addition to file-based replication for many site-to-site data transfers, including configurations and settings.

^NewSCCM 2012 now supports:

o   iPads/ iPhones

o   Symbian

o   Android

o   Windows Phone 7

Central administration site: It has the following differences from a central site in Configuration Manager 2007:

·         Does not process data submitted by clients, except for the Heartbeat Discovery data record.

·         Does not accept client assignments.

·         Does not support all site system roles.

·         Participates in database replication

Primary sites in System Center 2012 Configuration Manager have the following differences from primary sites in Configuration Manager 2007:

·         Additional primary sites allow the hierarchy to support more clients.

·         Cannot be tiered below other primary sites.

·         No longer used as a boundary for client agent settings or security.

·         Participates in database replication.

Secondary sites in System Center 2012 Configuration Manager have the following differences from secondary sites in Configuration Manager 2007:

·         SQL Server is required and SQL Server Express will be installed during site installation if required.

·         A management point and distribution point are automatically deployed during the site installation.

·         Secondary sites can send content distribution to other secondary sites.

·         Participates in database replication.

The following site systems roles are removed:

·         The reporting point. All reports are generated by the reporting services point.

·         The PXE service point. This functionality is moved to the distribution point.

·         The server locator point. This functionality is moved to the management point.

·         The branch distribution point. Distribution points can be installed on servers or workstations that are in an Active Directory domain. Instead use BranchCache by Windows 7 

·         Network load balanced (NLB) management points are no longer supported. Instead, this functionality is automatically provided when you install more than one management point in the site.

·         There is no longer a default management point at primary sites. Instead you can install multiple management points and the client will automatically select one, based on network location and capability (HTTPS or HTTP).

·         At a secondary site, the management point is no longer referred to as proxy management point, and must be co-located on the secondary site server.