3. Review infrastructure changes in Configuration Manager
R2
Discuss new and updated features in Configuration
Manager R2
Highlight changes to support Windows Server 2012 R2
and Windows 8.1
Session Objectives and
Takeaways
4. Today’s Challenges
Deploying and managing
applications across
platforms is difficult.
Apps Data
Users need to be productive
while maintaining
compliance and reducing
risk.
Users expect to be able to
work in any location and
have access to all their
work resources.
Users
The explosion of devices is
eroding the standards-based
approach to corporate IT.
Devices
5. People-centric IT
AppsUsers
Empower users
Allow users to work on the
devices of their choice and
provide consistent access to
corporate resources.
Unify your environment
Deliver a unified application and
device management on-
premises and in the cloud.
Protect your data
Help protect corporate
information and manage risk.Management. Access. Protection.
DataDevices
7. Increased SQL Server flexibility in Setup
Easy client mobility
Reduced Need For Multiple Sites
Improved visibility into a better optimized content system
Upgrade/interoperability considerations
64-bit native PowerShell module
What’s New In Infrastructure?
9. Specify file locations for database and transaction log
Restore to a different SQL Server instance
Requires same SQL Server version
SQL Server flexibility In Setup
10. Scenario: I installed a new primary site in my hierarchy and
would like to move some or all of the clients from an existing site
to the new site (e.g. load-balancing, server replacement).
Solution: Client reassignment
Supports single or multi-select client reassignment
Enforces proper client/site versioning
User standard client policy channel (no client notification)
Note: This will not work for disaster recovery scenarios.
Easy client mobility
11. Why might you need multiple primary sites?
More than 100K clients
Organizational politics
Reporting from the CAS
Clients reside in multiple untrusted forests
Solution: multiple network access accounts per site
Supports backward compatibility for SP1 clients
Troubleshooting assistance provided through dts.log
Reduced Need For Multiple
Sites
13. In-console monitoring improvements
Pull DP on par with standard DP
Clearer and more detailed messages
Cancel/retry distribution
Pull DP improvements
Source DP ordering and randomization
Improved scalability (no more polling)
Migration of branch DP’s to pull DP’s
General content improvements
Content download optimizations (client side) for superseded
applications
Content distribution optimizations (priority, send requests in SQL,
versioning auto-cancel
Improved visibility into a better
optimized content system
15. Only supported upgrade path is from ConfigMgr 2012 SP1
Must upgrade Windows ADK first
Improved site to site interoperability
Upgrade/Interoperability
Considerations
16. Windows Server 2012 R2 and Windows 8.1 support
Virtual Hard Drive (VHD) management
Native integration of some MDT actions
What’s New In OSD?
17. Requires new version of Windows ADK
Added multi-version boot images support
Deploys just like Windows 8 or Windows Server 2012
Support for OSD-specific site system roles
State Migration Point on Windows Server 2012 R2
Distribution Point with PXE on Windows Server 2012 R2
Distribution Point without PXE on Windows 8.1
OSD for Windows Server 2012 R2
& Windows 8.1
18. Expanding virtualization scenarios
Example: workstation image validation, datacenter integration
Create VHD
Requires Hyper-V on ConfigMgr console computer
User standard task sequence (new template available)
Modify VHD
Uses offline servicing
Upload to Virtual Machine Manager
Virtual Hard Drive (VHD)
Management
22. Maintenance windows specific to updates
Automatic Deployment Rule (ADR) filter query preview
Package flexibility for ADR’s
What’s New In Software
Updates?
24. Windows Server 2012 R2 and Windows 8.1
Full client and site system role support (also OMADM)
On-Premise Self-Service Portal*
Windows Embedded
Support for Windows Embedded 8 Industry
Support for Unified Write Filters (UWF)
Mac OS
Enrollment UI
What’s New In Platform
Support?
25. SP1 Enrollement
Command lin experience with username, password, server
and other parameters to specify
Enrollement process biggest pain point for customers and
largest barrier to adaption
R2 Enrollment
Enrollment wizard
User only has to enter username/email, password, server
Command-line enrollment remains for scripting scenarios
Mac OS Enrollement: Current vs
New Experience
26. With SCCM 2012 R2, all reports updated to use RBA
configuration
Control access to specific reports
Enabled by default in R2 via registry/WMI setting
HKEY_LOCAL_MACHINESOFTWAREMicrosoftSMSSRSR
P
“EnableRbacReporting”
Role Based Administration