Wednesday, April 30, 2008 7:36 PM jhinkle

MMS 2008: Advanced OS Deployment with ConfigMgr - Part 2

Presented by Michael Kelley. Some guy decided to answer his phone in the middle of this session. If you were him, stop it. It's rude. Continued from part 1.

  • Multicast
    • Multicast of OS images to PE - no multicast for other packages, no multicast from PXE Service Point
    • Multicast is an option on the DP - requires Windows Server 2008 with WDS, builds on WDS
    • ScheduleCast - reaches minimum group size or maximum wait time
    • AutoCast - late joiners will catch up with parts they missed at end - less time delay, but less efficient
    • Only one Multicast session per image at a time - Multiple images at same time ok
    • DP lookups prefer multicast-enabled DPs
    • There are no remote multicasts

  • Driver Catalog
    • Auto Apply Driver - scans hardware and transmits to site server, site server sends list of drivers down, client determines best driver and downloads correct ones from DP - puts drivers in Drivers folder, in subfolders for each, Windows PnP logic installs drivers as normal
    • Apply Driver Package - forces one driver to installed - for disconnected USB or Boot-critical drivers
    • Drivers can be in more than one package - Separate packages can be used to direct drivers to DPs, non-PnP drivers that can't be used in Auto Apply, Pre-Vista boot critical drivers
    • Use categories for driver lifecycle management

  • Driver Versions
    • Catalog can hold different versions - different version is difference in any binary
    • Categories can be set in OSDAutoApplyDriverCategory

  • Exe Drivers
    • Run exe an unpack and add resulting files to catalog
    • Run exe on reference computer an manually pull out INF
    • Check web-site for .inf
    • treat the install as a software distribution package

  • Multi-level devices - Auto-apply drivers may not see child devices - Include both devices in same folder with parent device
  • Boot-Critical devices - put drivers in separate drivers, select driver from combo box, or use build mass storage
  • Get driver category GUID from View, Add/Remove Columns, add Category Unique ID in Drivers view in console
  • Bare Metal and PXE
    • WDS is PXE server - For 2008 compatibility, use ConfigMgr SP1
    • Mixed and native modes will work, legacy will work
    • Install WDS, but don't configure
    • Add a PXE service point site role for that computer, creates a server share DP to hold boot images
    • Replicate boot images to PXE DP as well as to a regular DP
    • Must replicate x86 and x64 boot images
    • Check log file to troubleshoot - %program files%\SMS_XXX\logs\smspxe.log - look for PXE boot, found matching computer, found advertisement, used abortpxe.com because the adverisement already ran, ignore log entries for all "F" self-check run
    • Stop and restart WDS service

  • Zero-Touch - Boot media, no way to get rid of wizard - PXE, Mandatory advertisement does not require F12, optional does
  • Resetting PXE - ignored if same mandatory advertisement is pending, choose "Clear Last PXE Advertisement" action to force reapplication, optional always asks
  • User Input - Task Sequence can't show UI - Collection and computer variables with no value will be prompted in R2 - In R1, use a pre-execution hook to use own UI, use Microsoft.SMS.TSEnvironment to script in VBS
  • Pre-exec hook - create a tsconfig.ini, put in root of WinPE, use as boot image
  • Unknown computers - MDT has an add-in for WDS that will fix in R1, R2 adds new resource type of unknown (x86 computer or x64 computer) - Task sequence advertised to collection for them - they will show up in Unprovisioned Computers node until deployment is complete - Must be enabled for PXE or Boot media
  • Client Identity - Mixed mode: ConfigMgr Client in Full OS will retain identity, Bare Metal will apply conflict resolution rules (by default, new identity and old is obsolete; there can be a manual process in the "Conflicting Records node", Merge, New, or Block); Native Mode: based on PKI subject name
  • State Migration
    • State Migration Point - Client can only use site migration point that are associated with the site they are assigned to - Can be protected - Admin controls disk space - Request State Store: finds an SMP with available space and sets OSDStateStorePath
    • USMT - 32-bit and 64-bit versions - wrapped by a task sequence - actions manage encryption key - specify more command line options in OSDMigrateAdditionalCaptureOptions
    • Computer Association entries for same computer or side-by-side


Filed under: ,

Comments

No Comments