Delivering People Centric IT with Configuration Manager 2012 R2


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Grow path hit 100.000 limitLoad balancing Server replacement scenario
  • Down-level clients receives still single NAAR2 or higher clients receives multiple NAA
  • Reassignclients to siteMultiple Network Access Accounts
  • Performance improvements
  • Description Content package IDShow Pull distribution point (order)Interaction cancel/redistributeContent distribution optimizations behind the scene
  • R2 specific CI’s are not replicated to down-level SP1 sites until upgraded to R2
  • Down-level boot images read-only limited to WinPE 3.1
  • Delivering People Centric IT with Configuration Manager 2012 R2

    1. 1. Delivering People-centric IT with Configuration Manager 2012 R2 Ronny de Jong Inovativ | Consultant @ronnydejong
    2. 2. Agenda      Welkom Session Objectives & Takeaways People-centric IT Demo’s Q&A
    3. 3. Session Objectives and Takeaways  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
    4. 4. Today’s Challenges Users Devices Apps Data Users expect to be able to work in any location and have access to all their work resources. The explosion of devices is eroding the standards-based approach to corporate IT. Deploying and managing applications across platforms is difficult. Users need to be productive while maintaining compliance and reducing risk.
    5. 5. People-centric IT Empower users Allow users to work on the devices of their choice and provide consistent access to corporate resources. Unify your environment Users Devices Apps Data Deliver a unified application and device management onpremises and in the cloud. Protect your data Management. Access. Protection. Help protect corporate information and manage risk.
    6. 6. What’s New In Infrastructure?       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
    7. 7. SQL Server flexibility In Setup  Specify file locations for database and transaction log
    8. 8. SQL Server flexibility In Setup  Specify file locations for database and transaction log  Restore to a different SQL Server instance  Requires same SQL Server version
    9. 9. Easy client mobility  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.
    10. 10. Reduced Need For Multiple Sites  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
    11. 11. Demo Easy client mobility
    12. 12. Improved visibility into a better optimized content system  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
    13. 13. Demo Content System Enhancements
    14. 14. Upgrade/Interoperability Considerations  Only supported upgrade path is from ConfigMgr 2012 SP1  Must upgrade Windows ADK first  Improved site to site interoperability
    15. 15. What’s New In OSD?  Windows Server 2012 R2 and Windows 8.1 support  Virtual Hard Drive (VHD) management  Native integration of some MDT actions
    16. 16. OSD for Windows Server 2012 R2 & Windows 8.1  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
    17. 17. Virtual Hard Drive (VHD) Management  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
    18. 18. Demo Create Virtual Hard Drive (VHD)
    19. 19. Native MDT Actions  Check Readiness  MDT Validate action  Prevent late failure or bad targeting  Set Dynamic Variables  MDT Gather action  Dynamic task sequence through conditional rules  Run PowerShell Scripts  Set PowerShell Execution Policy  ConfigMgr Cmdlets x64
    20. 20. Demo Native MDT Actions
    21. 21. What’s New In Software Updates?  Maintenance windows specific to updates  Automatic Deployment Rule (ADR) filter query preview  Package flexibility for ADR’s
    22. 22. Demo Software Updates
    23. 23. What’s New In Platform Support?  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
    24. 24. Mac OS Enrollement: Current vs New Experience  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
    25. 25. Role Based Administration  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_MACHINESOFTWAREMicrosoftSMSSRSRP “EnableRbacReporting”
    26. 26. Bedankt! Vragen? Volgende spreker: Hyper-BBQ 