5. Configuration Manager 2007 Configuration Manager 2012
Optimized for Systems Management scenarios • Still committed and focused on System Management
scenarios
• Challenging to manage users: • Embrace User Centric scenarios:
• Forced to translate a user to a device • Moving to a state based design, for apps, deployments,
• Explicit: run a specific program on a specific device content on DPs.
• Full application lifecycle model. Install, Revision Mgt,
Supersedence and Uninstall
• Software Distribution is a glorified script execution • Understand and intelligently target the relationships
between user systems
• Management solution tailored for applications
6.
7.
8.
9.
10.
11. Jamie is ‘ConfigMgr Admin’ and has rights to
entire console
Jamie assigns the ‘Application Deployment’
role to Meg
Meg is responsible for deploying software
Meg has a limited view
12.
13. 2012 will allow CreatePrimaries are needed to optimize LAN/WAN for:
ConfigMgr tiered primary sites for scale out only
-content distribution
admins to minimize
2007
or consolidate
-client inventory
-agent status
scenarios2007
ConfigMgr
CreateOptions for contentsites (or hierarchies!) for:
separate primary distribution:
where a
infrastructure -Secondaries
-different serverthrottling/scheduling agent settings
-DPs with and desktop client
unique -BranchCache,
primary
CreateClient agent settings configurable by roles only see the data they need to see for
a primary site boundary so admin collection
could be their job
used
Data Segmentation via Role Based Administration
