FMSCUG 1802 Meeting Notes

Big thanks to Gary Blok for presenting at this month’s FMSCUG meetup! Make sure to follow him on twitter @gwblok and visit his website for more OSD goodness. As always thanks to High Point Networks for hosting!

Meeting notes below (thanks to @bittletime)

  • Twitter is awesome to stay connected.
  • OSD and In-Place Uprades
    • Troubleshooting
      • New models need new drivers.
      • Additional components in WinPE add weight to the boot image, but often can be worth it. (e.g. Powershell)
      • Use MDT Monitoring – you don’t have to use all the features, just this one.
      • DaRT Remote Control to troubleshoot issues on PCs in WinPE.
      • Backup log files.
    • MDT Monitoring
      • Monitoring is easy to add.
    • Front Ends
      • Avoid using many different task sequences. Be modular.
      • Front End to collect variables to customize what steps will run in the task sequence.
    • Drivers
      • Driver packs. Vendor tools.
      • “Holy Grail” driver management.
      • Keep them up to date!
    • Windows 10 Tweaks
      • Limit the tweaks to reduce testing between versions.
      • Keep what you might need. Remove what you don’t.
      • Apply tweaks as as part of the task sequence.
    • Other Good Ideas
      • See PowerPoint.
      • Custom WMI / Registry Entries
    • Additional Notes
      • Extend hardware inventory to collect BIOS data.
      • Talk to your vendor for help.
  • Use Nested Task Sequences! (CM 1710)
    • Anything that is repeated in multiple task sequences can be separated into its own.
    • Modifying one nested task sequence updates any parent task sequences where it is used.
  • Check out Gary’s website for blogs/scripts/task sequence examples.

More Customization Stuff

  • Consider using different steps for each tweak in order to better control things, at least for testing.
  • Group policy is a great way to set customizations as well.
  • Decide for yourself what customizations are right for you – the less, the better.
  • UEV can help “bridge the gap” for transferring user settings during upgrades and OSD. Not recommended for large organizations.
  • Customizing OEM information – include your logo, business information, etc., using registry keys, etc., in the computer’s system information.
  • Clean up the “Quick Menu”.
  • Set “This PC” to display your disk drives or show recently used folders.
  • Name “This PC” as the name of the computer to help users.
  • Allow apps to run as different user.
  • Customize user icon, lock screen, wallpaper, start menu, etc.
    • Start menu can only be changed before the user’s first login.
  • Set defaults but allow users to change their settings.
  • Nested task sequences log everything in the same log as the parent. The client still sees everything as “one big task sequence”, even if it’s split up in the console. Be mindful of how long the task sequence might become for the client.
  • One task sequence can satisfy the needs of multiple lines of business with help of variables.
  • Set custom variables / registry keys to help track information. E.g. What was the last task sequence that ran? How long did it take? What the image name? Etc. Collect information, create metrics, etc.
    • Pull this information into CM with hardware inventory.
    • Use collection variables to reduce/eliminate the need for front-ends.
  • Give users the rights to change things they like – it keeps them happy.
  • Deny users the ability to log in during OSD with GPO – and include exceptions for admin accounts.
  • BIOS updates during OSD.

Leave a Reply

Your email address will not be published. Required fields are marked *