Speaker: Olav Tvedt @olavtwitt  olavtvedt.blogspot.com
 
This better be a good session. It's so full I decided to stand. Then I was told due to fire code I have to sit down. Odd- seems like if I was already standing and there was a fire I'd be safer…
 
The mission here is simple: we want happiness. To be happy we need to make things efficient to stop the phone calls. So let's not forget to make the users experience solid. The challenges to this are of course the complexity of a rollout of this size. It looks different, the client targets may be vast and varying. Mobile clients may be the biggest change for most admins these days- last time we rolled out a Windows release, mobility wasn't as widely adopted. 
 
http://www.windows.com/itpro is a good resource (yet again). More specifically: http://technet.microsoft.com/en-us/windows/hh771457
Check out this 1-pager with tons of useful planning and resources: http://www.microsoft.com/en-us/download/details.aspx?id=34798
 
First thing to think of here is your deployment plan. Start thinking about how to maximize your user experience early in the deployment phase. Consider the master image, Recovery, and user self-refresh and recovery. The image should be installed, updated, configured, and then captured (with a K2000). Recommended that the image be updated and refreshed every 3 months, but with K10000 & K2000 KACE can make that easier with automation.  
 
The refresh image tools (recimg /createimage C:\refresh) can capture a local refresh image copy. See MS KB 2748351 
REAgentC.exe is another useful command.
 
WinRE (Windows® Recovery Environment (Windows RE) is an extensible recovery platform based on Windows Preinstallation Environment (Windows PE). When the computer fails to start, Windows automatically fails over into this environment, and the Startup Repair tool in Windows RE automates the diagnosis and repair of an unbootable Windows installation. Furthermore, Windows RE is a starting point for various tools for manual system recovery.) is in the DaRT image tool.
 
Usually this image refresh toolset would be pre-configured for the user at the time of delivery. It might also be useful to run this on a scheduled basis to help the user have a "snapshot". This toolset will reset everything except of the App Store data and [something else].
 
Not hearing a lot of performance, or tuning. Just how to roll back to a previous date. This guy obviously knows his stuff, but is not a native english speaker, and is also a pretty bad presenter in general. Really hard to follow and I'm not entirely sure he has a plan.

Handy tip: reagentc /boottore will boot the machine to the recovery image on next boot.

Group policies in Win8 allow WMI filtering to ensure GPO's only happen on WMI filtered objects, such as only dell computers, or only Win8 machines, only machines with samsung monitors. So on.

With win8 the boot time is improved in part due to new triggers to launch services, Automatic, Auto(Delayed), Auto(Trigger), and Manual. 

The page file disk defrag, and performance settings are key. For pagefile it doesn't need to be big and it should be a fixed size. Performance settings include visual effect degradation for sure. All of this can also be controlled with GPO, including the preferences. Preference GPOs can largely replace logon scripts. Some of Olav's favorites include a registry wizard in GPO fir Server 2012. Browser is built right into the GPO tools. The targeting editor allows hardware and software queries with WMI and such. He likes the GPO for creating a local user such as a local admin. All of this is in Preferences>Control Panel, explore a bit. Combining things like the local user creation, and the WMI filtering (maybe via the targeting editor) we can make some pretty dynamic use cases.

So there was some pretty good stuff in here, but soooo disorganized. Sorry for being all over the place- the instructor was as well.