14. Software Update Groups Update Deployments Assign updates to clients Define when, where, how, who Update Packages

18. Available (no deadline) User initiated (typically) Best for systems with tight control Required (deadline) System initiated (typically) Best with normal use systems Required with maintenance windows System initiated Best with servers or always on systems that have business defined service hours

20. One for every update schedule Endpoint protection Monthly (one per-month) Out-of-band Software Update Groups No specific technical separation needed More than one Recommended: at least one per calendar year Update Packages One for every “class” and “phase” defined by your SLA Typical classes: Workstation, Server Typical phases: Test, Pilot, Production Collections

28. User initiated Increases compliance Increases user satisfaction Reboots enforced at deadline Completely silent Two hour deadline randomization (controllable in SP1) No reboot postpone Maintenance window availability

31. Do Review what an ADR created or updated Plan, document, and communicate Learn which reports are available Don’t Use the WSUS admin console Treat Software Updates as WSUS Use the “Required” ADR search filter

33. Complete your session evaluations today and enter to win prizes daily. Provide your feedback at a CommNet kiosk or log on at www.2013mms.com. Upon submission you will receive instant notification if you have won a prize. Prize pickup is at the Information Desk located in Attendee Services in the Mandalay Bay Foyer. Entry details can be found on the MMS website.