1. Niall Brady Senior Consultant, Enfo Zipper MVP System Center Configuration Manager Email:niall.brady@enfo.seniall.brady@enfo.se Twitter: @ncbrady Blog: www.windows-noob.com

2.  Customer feedback on software updates in Configuration Manager 2007  Key investments for software update management in Configuration Manager 2012  General troubleshooting review Agenda

4. ConfigureConfigure  Superseded update support  SUM admin role (with RBA)  Client agent settings  Migration from CM07 DeployDeploy  Simplified update groups  Automated deployments  End user experience MaintainMaintain  In-console views and monitoring  In-console alerts  Reporting  Content library and cleanup

5. Publisher can expire or supersede software updates ConfigMgr 2007 automatically expires superseded updates In CM12, you control supersedence behavior

6. Role: Limit the SUM administrator to software- update related actions Scope: Control access to specific console objects Example: SUM Admin for Europe can manage software updates only on desktops in the Europe collections

8. New UI for client agents settings Apply to collections Customize settings for different systems on the same site, like servers and desktops

10. Migrate packages, deployments, lists and templates Persist update content availability from CM07 through Distribution Point sharing Important: SUP products & category settings must be the same on CM07 and CM12 Important:

12. ConfigureConfigure  Superseded update support  SUM admin role (with RBA)  Client agent settings  Migration from CM07 MaintainMaintain  In-console views and monitoring  In-console alerts  Reporting  Content library and cleanup

13. Lists and deployments combined into Update Groups Improved search to find updates Updates added to groups automatically deployed Groups can be deployed and/or used for aggregate compliance

15. Automated deployment of desired updates Schedule or run rules manually Daily (Forefront) and monthly (Patch Tuesday) scenarios Daily (Forefront) and monthly (Patch Tuesday) scenarios Rules create update groups that can be further edited or used manually

17. Update details and progress in all user sessions

19. ConfigureConfigure  Superseded update support  SUM admin role (with RBA)  Client agent settings  Migration from CM07 DeployDeploy  Simplified update groups  Automated deployments  End user experience

20. Critical information now in-console: Compliance and deployment views per update and update group Detailed state of all assets targeted with update deployment Interpreted error codes Hierarchy-wide SUP synchronization status Alerts for synchronization failures and compliance not met

22. Extensive state and compliance information in out-of-box reports

24. Updates optimized with new content model to reduce replication and storage Expired updates and content automatically cleaned up

25. LogTypes of issues SUPsetup.logInstallation of SUP Site Role WCM.log, WSUSCtrl.logConfiguration of WSUS Server/SUP WSyncMgr.logSMS/WSUS Updates Synchronization Issues Objreplmgr.logPolicy Issues for Update Assignments/CI Version Info policies RuleEngine.logAuto Deployment Rules

26. LogTypes of issues UpdatesDeployment.logDeployments, SDK, UX UpdatesHandler.logUpdates, Download ScanAgent.logOnline/Offline scans, WSUS location requests WUAHandler.logUpdate status(missing/installed – verbose logging), WU interaction UpdatesStore.logUpdate status(missing/installed) %windir%\WindowsUpdate.logScanning/Installation of updates