Windows 10 Imaging and Deployment Discuss the process to prepare for and deploy Windows 10

Overview General Information Requirements Image Build Local Account Core App List Updates on the Image UAC Settings Start Menu NEW Start Menu Final Clean Up Deleting Other Apps Prep the Image Capture the Image MDT for Imaging

Windows 10 General Information Recommend using Windows 10 “Education Version” (EES) Same as enterprise edition, but with a K12 twist Current build / release - 1607 If on 1511, please start to use 1607 Microsoft pushing – assume due to technical issues Other vendors pushing the same Will discuss “feature updates vs quality updates” on second presentation

First Things First Build the Core Image Build image using a VM (HyperV or ESX) Quick image build Allows you to take CheckPoint or SnapShot to recover, if sysprep fails

Local Account Create the initial default local user and ONLY logon as that user (ITAdmin) Join the domain, but always logon locally with the ITAdmin account

Core Apps List Typical Install your core apps using the initial account Either manually install the apps or Try a program call PDQ Deploy Java 8.x Java 8.x (64-bit) Microsoft Office 2016 Microsoft Silverlight Mozilla FireFox NotePad ++ PhotoStory 3 QuickTime UltraVNC VLC Player Windows Essentials – Movie Maker Adobe Reader Adobe Air Adobe Flash - FireFox Adobe Shockwave Audacity with LAME ClassicShell GIMP Google Chrome Google Earth ITunes

Updates on Image Make sure to run all windows updates – takes forever… Change settings – Advanced – Give updates for other MS products Defer feature updates – please…

UAC Settings Change the UAC on the image Will discuss in more detail in next session Up 1 from bottom for App Store support ** Also turn off the firewall

Start Menu – Looks Like 7 ClassicShell – www.classicshell.net Customize using REGEDIT HKLM\Software\IvoSoft\ClassicStartMenu add a string - MenuStyle_Default - set to one of these - Classic1, Classic2 or Win7 "EnableExit"=dword:00000000 "EnableExplorer"=dword:00000000 "EnableSettings"=dword:00000000 Windows 10 Changes for Image HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization add - DWORD NoLockScreen and set its value to 1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System add - EnableFirstLogonAnimation DWORD - 0 to disable it.

New Start Menu (Tiles) Customize the Start Menu Tiles Remove most of the default tiles Add tiles you want to use as a default “template” Once completed – need to export Open Powershell console as Admin export-startlayout -path c:\download\startw10.xml  import-startlayout –layoutpath c:\download\startw10.xml -mountpath c:\

Final Clean-Up Remove App Store Apps before sysprep Will cause sysprep to fail if not removed Only need to remove for local (ITAdmin) account Launch PowerShell as current user Get-AppxPackage | Remove-AppxPackge I normally run this 3 times

Deleting All Apps If you wish to remove some or all App Store apps, then use this link as a reference I use 4sysops.com and other specific sites for good Windows information https://4sysops.com/archives/remove-provisioned-built-in-apps-in-windows-10/

Prep the Image Take a SnapShot (ESX) or CheckPoint (HyperV) Remove the App Store apps from the current user (only) Launch PowerShell as the current user (Not Run as Admin) Get-AppxPackage | Remove-AppxPackage Sysprep C:\Windows\System32\Sysprep folder Run Sysprep Will shutdown once finished

Capture the Image PXE boot using the regular boot wim At the first stop, press F8 (command prompt) Go to the D: drive (actually the C: drive) Delete the MININT folder Del d:\minint /s /f /q Rd d:\minint /s /q Go to the Z: drive Change to Z:\tools\x86 Run Imagex… Imagex /capture d:\ z:\captures\W1064Core031616.wim “W1064Coremmddyy”

Now Ready to Image Why Do I Use MDT 2013 Free – No cost solution for automating your imaging process ( 3 day setup including image build) Works very well to deploy Win 7, Win 8.1 and Win 10 Management Console only needed on one server (Work Bench) Does not require any other software to setup district wide – Just a DeploymentShare$ on remote servers – Free script to sync shares (MDTCopy) Easier to manage and implement than many other solutions Customizable to district’s desire – centrally manage, but distributed imaging Non-technical users can image and re-image computers (Delegate)

MDT 2013 Some Key Features Operating System Deployment Windows 7, 8.x and 10 Driver Injection – Granular based on “model” Model specific (Driver Group) and Unlimited drivers supported Application Installations – Post Image Directly associated to imaging process and / or Pick List UEFI Support (Win 2012 server for PXE support) Tablet support – No NIC / Dongle issues due to duplicate MACs Pre-Image automation – computer naming and even password protect imaging process(Scripted options) – UserExit script Active Directory OU Placement – choose OU prior to imaging from drop-down list

MDT 2013 Requirements Windows Server 2012 R2 (Support UEFI PXE) Windows Assessment and Deployment Kit (ADK) for Windows 10 (1607) Update Installed (management server) MDT 2013 Update 2 software (management server) Power Shell Disk space for drivers and images – assume 150G free disk space Windows Deployment Services – WDS – PXE booting Disk space on remote servers for distributed imaging (Deploymentshare$) Use Education version of Win10 ISOs

Deploy the Image

MDT 2013 Update 2 - Workbench Overview – Gaston County Schools Applications Operating System Out-of-Box-Drivers Task Sequences

Import Drivers Create a folder structure for OS Type Win7, Win81, Win10 Create Sub-Folders for 32 and 64 Bit Create Folders for each model Model “must” be the actual model Based on WMI query MDT provides a %Model% variable Set DriverGroup – based on model

Task Sequence Setup Create Task Sequence Disable – State capture State restore BitLocker Set DriveGroup Create variable Win10\64\%model% Inject Drive set to “Nothing” Additional Task Sequence Items Apps SCCM Wireless Etc

MDT 2013 CustomSettings.INI Controls Deployment Processes Rules – Default Task Rules – Per School

MDT 2013 BootStrap.INI 1 - Workbench Properties 2 - BootStrap.ini 3 - Build Boot.wim files in Boot folder 2 - BootStrap.ini 4 - WDS – PXE Boot

UserExist Script Runs prior to the Task Sequences

MDT Copy Easily replicate the DeploymentShare folder to remote servers Run on demand or scheduled event Given to schools

Live Demo “If Time” Show Workbench Review Folder Structure Import OS Import Drivers Show Task Sequence Boot a client Emphasis steps of TS District UserExit script and computer naming Show OU location list Show Pick List for Applications

Practical Solutions IT www. practicalsolutionsit Practical Solutions IT www.practicalsolutionsit.com Email:djones@practicalsolutionsit.com