Friday, 23 January 2015

SCCM 2007 to 2012 R2 Migration why

A common answers from SCCM administrator for migration to SCCM 2007 to SCCM 2012.

As an IT administrator or technology lead you should look for migrating from SCCM 2007 to SCCM 2012

or higher versions if any of the below mentioned technologies are in your IT blue print. In addition, the

System Center Configuration Manager team of your organization would find the some of the features of

SCCM 2012 or higher versions are extremely handy in daily operations:
Deploying Windows 8 / 8.1 or Windows Server 2012 / R2 are available with System Center

Configuration Manager 2012 R2
Additional support for Unix, Linux, Apple, Android, and Nokia mobile devices will assist to enable a

BYOD environment

System Center Configuration Manager 2012 allows one to flatten the infrastructure, instead of having multi-tier hierarchy of Primary and Secondary Servers, significantly decreasing the management

Overhead

The new state-based application model replaces the conventional configuration manager package and programs, incorporating dependencies and requirements for more granular software distribution.

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
System Center Configuration Manager 2012 bring an in-built enterprise portal that allows for self

Service provisioning of applications
the new role-based administration feature flattens the complex hierarchies once required to isolate access to Configuration Manager Features
Assignment of client agent settings, inventory collection, and remote control settings by collection offers increased flexibility in configuration
Ability to “inject” new windows updates into existing WIM files used for operating system deployment by leveraging Component-Based Servicing.

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

No comments:

Post a Comment