When beginning any migration project it is important to understand the reason behind managements decision. The biggest reasons will be End of Life support for Windows 7 has already ended. The Windows 10 OS has been designed to be the most secure version of the Windows operating system to date, organizations can now take advantage of several new security features and improvements. These enhancements focus on three key areas — threat resistance, information protection, and identity protection and access control- using advanced and now widely available hardware and firmware features. Security enhancements within Windows 10. This is how I would start my migration to windows 10
First we must first identify if our SCCM infrastructure will support deploying, maintaining, and patching Windows 10 systems. Then we will have to second identify systems that are windows 10 ready based on physical features. Finally we will touch on a few of the features such as Device Guard, Credential Guard, Secure boot, ELAM in a future post. (Some features were available in earlier versions of windows, but not as widely implemented as it is expected to be in win 10) We will Focus on what is needed to deploy windows 10 V1607 first.
SCCM Server Req – (1511, and 1607 win 10 versions have different SCCM Min Versions)
Site Server Server 2012 or 2012 R2
SUP Role WSUS 4.0 to patch win 10 systems
ADK 1511 or 1607
SCCM must be on Current Branch (due to SCCM 2012 versions do not support deploying win 10 v1607)
Workstation Req - Processor: 1 gigahertz (GHz) or faster processor RAM: 1 gigabyte (GB) for 32-bit or 2 GB for 64-bit (personally recommend 4gb+) Hard disk space: 16 GB for 32-bit OS 20 GB for 64-bit OS (personally recommend 120gb+) Graphics card: DirectX 9 or later with WDDM 1.0 driver Display: 800x600
SCCM Req: https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-configurations
Workstation Req: https://www.microsoft.com/en-us/windows/windows-10-specifications
End of life Support for OS: https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet
NOTE: If you are in an environment where you do not current meet the server specs for Current Branch you will have to upgrade or perform a side by side migration. I have worked in multiple environments where I have implemented both solutions. In a future blog post I will write how to perform an upgrade and a side by side migration.
ALSO SEE : SCCM 2012 R2 SP1 failed upgrade