4. Five issues, commonly addressed on the forums and mailing lists Boundaries Client identity Business hours and maintenance windows Deployment type evaluation Upgrade to SP1

6. Boundaries: common questions

7. Are used forAre not used for Primary site MP or SUP selection by clients Internet clients Any server side processes Client site re-assignment

8. ProCon IP Subnet Fast processing time Requires knowledge of all client subnet masks No aggregation Requires no aggregation of IP subnets in AD for site assignment to function correctly AD Site Fast processing time Easy to setup Requires AD sites to be properly defined Requires AD sites to be granular Software Updates during OSD has issues IP Range Easy to implement No dependencies on AD Granular Slow processing time

9. Boundaries must be contained within a boundary group to be used Site assignment One per primary site One per secondary site Published to AD Content location One per DP/SMP or One per location Not published to AD

10. AD Sites AD subnets are well defined or Auto-site assignment is not needed A lot of boundaries are needed Cannot be used by workgroup clients IP RangeIP Subnets AD subnets are well defined or Auto-site assignment is not needed Client subnet masks are known A lot of boundaries are needed

12. Secondary sites and site assignment

16. Security Identifier (SID) Used by Windows Known to AD and local system but never used by anything except local client* Uniquely generated for each Windows system Not used by ConfigMgr to generate GUID Globally Unique Identifier (GUID) Used by ConfigMgr Uniquely generated by the ConfigMgr client agent Known to ConfigMgr site and client “Secret” generation process Hardware Identifier (HWID) Generated by ConfigMgr client agent to uniquely identify hardware Known to ConfigMgr site and client Helps identity systems that have been “reimaged” Resource ID Sequential ID known only to the site Used for nearly all client centric activity Client certificate Used to generate new client GUID

19. Common questions

20. Key facts

21. Comparison Maintenance windows Evaluated by the client Administrator centric Control when deployments with deadlines can (and can’t) be enforced Business hours Evaluated by the client User centric Can initiate deployments before deadlines

22. A scenario Computer is idle at deadline 9:30 PM Client business hours: 5 AM – 8 PM Maintenance window:9 PM – 4 AM Installation deadline:9:30 PM Deployment start time:6 PM User working at 9:30 PM 9:30 PM Computer off at deadline until the next morning 9:00 PM next evening User enables installation during non-business hours 8:00 PM

24. Business hours references

31. Common questions

32. Pre-download all requirements Run the pre- requisite checker on all site servers Check your SQL Server version and upgrade to the latest SP Backup your DBs, reports, and source files Install KB2734608 for WSUS, upgrade Windows Update Agents Uninstall WAIK, install ADK

33. Update the ConfigMgr client package Upgrade your clients to SP1 Recreate and redeploy boot images Learn about and explore new features and functions

34. Anti-virus Turn it off for the upgrade Exclusions in place Offline servicing/boot image updates WinPE 4.0 vSphere 4 not compatible Requires NX bit Microsoft Policy Provider signing Re-download media or Use hotfix from KB2801987

35. References

38. 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.

39. Resources