System Center Configuration Manager 2012 Help You Enable Consumerization of IT

Content Source: Microsoft Server and Cloud Platform Blog 

The main use case for "consumer" devices in the enterprise still revolves around email, and there are all kinds of studies and research articles backing up that claim. Simply put, the overwhelming majority of those who use smartphones and slates for work are using them to do email or calendar (and sometimes for other stuff). Fortunately, Microsoft Exchange has long included basic mobile device management features built-in with Exchange ActiveSync (EAS). The problem is that the Exchange administrator is the wrong person to be worrying about security and policy management for mobile devices. The Exchange admin's day job is to keep the mail servers up and running. The folks whose day job is to worry about the security and configuration of mobile devices are most often the same people who are worrying about that for traditional desktops and laptops.

With ConfigMgr 2012, Microsoft wanted to address this tools mismatch so you can consolidate all of your security and configuration management under a "single pane of glass", no matter what types of devices are at the end of the line. Simply specify the connection properties so ConfigMgr can talk to your Exchange 2010 "organization" and begin managing any EAS-connected device directly from ConfigMgr. And it all works whether you have Exchange deployed internally or you're using Office 365. The features that come with ConfigMgr 2012 for managing non-traditional, "consumer" devices include:

• Asset inventory and reporting - ConfigMgr automatically discovers all those devices that have connected through EAS and collects basic inventory, so you can view them directly in the ConfigMgr console, build device collections and queries, and run asset reports. We also have a bunch of reports built-in to help you analyze the use of mobile devices at your company, such as a useful summary report that breaks out the devices by operating system. And we can even automatically associate the devices to the users, so you can pull lists of just the users who are affected by a policy change or whose chosen device may need to be updated to a newer version of its mobile operating system.
  
  
• Settings policy management - Define the default settings policy applied to devices connecting to EAS. Within seconds the policy will be pushed to Exchange and applied to mobile devices the next time they sync. There are close to 50 different policies that may be configured through EAS. Most common, and the most important ones in my humble opinion, are the use of strong PIN, required device encryption and remote wipe. These can ensure that your company's data is reasonably protected regardless of the mobile device choices made by your users.
  
  
• Remote wipe - Microsoft is calling this one out separately from the rest of the policy management as they believe it has the greatest end user impact, but it’s a critical feature to deal with lost or stolen devices or similar situations. And, if ConfigMgr has the user association information, the end user can self-service this action from the new ConfigMgr Software Catalog (stay tuned for future blogs and demos about the Software Catalog).

 

Client Management Licenses (MLs) are required for managed devices that run non-server OSEs. There are three System Center 2012 Client ML offerings:


Client MLs are available on a per-OSE or per-user basis. Components included in the Client MLs are not available separately.

Note pricing will vary based on licensing program and country.

Transition Process for Existing Customers with Valid Software Assurance

To facilitate a smooth transition to the new editions and licensing, Microsoft is offering a license migration grant to qualifying Software Assurance customers.

Existing licenses with Software Assurance in place when System Center 2012 becomes generally available will qualify for license grants for System Center 2012 as summarized below. Customers will continue to pay for existing licenses at their original price through the end of their agreement and will be able to renew Software Assurance coverage on the new licenses.

The Microsoft Volume Licensing Service Center (VLSC) will automatically reflect the license migration grant for qualifying licenses. You do not need to take any action to receive your license grant and will have access to System Center 2012 Software via VLSC in the month System Center 2012 becomes generally available.

License Grant for Clients

If you have Software Assurance on your System Center Client MLs as of the date System Center 2012 becomes generally available, you will receive the following System Center 2012 Client ML grants at a 1:1 ratio:

Note: There are no step-up paths for Client MLs.

How does the license migration grant work under my Enterprise Agreement (EA)?

License migration grants under the EA will be provided as explained above. Where EA differs is the amount of time through which additional standalone Server ML and/or Management Server Licenses may be purchased and continue to qualify for the license migration grant described above. As a benefit to customers purchasing the existing licenses through an Enterprise Agreement, Microsoft will honor the license migration grant for standalone Server ML and Management Server Licenses purchased through your first anniversary after January 17, 2012 of the System Center 2012 licensing model and license migration grant terms.