今天跟大家分享下Windows 10升级部署的一些知识点，大家有什么疑问找个时间一起聊聊。
大家都知道，客户端操作系统Windows 7将于2020年1月份正式停止支持，也就是到2020年Windows 7就会像WindowsXP一样变成没人管的系统，Microsofr再也不会进行补丁发布，不在进行任何更新操作。而微软内部Windows研发事业部的同事表示Windows 10可能是微软发布的最后一批号系统，微软将不在发布Windows 11、Windows 12，以后的Windows系统将每隔3-6个月进行大补丁更新，并用内部版本号表示，例如Windows 10 1507、Windows 10 1703、Windows 10 1709等等。
Windows 10是微软号称目前最安全的Windows 10系统，自身配备了杀毒软件、病毒查杀隔离等软件，在发布的这2年多的时间内，微软与许多企业一起讨论过Windows 10，并且很多客户与终端用户给出了很多好的建议，微软也采取了很多好的建议，进行了很多好的功能的更新操作，并且微软号称将在2018年上半年大力推进Windows 10的市场占有率，也就是说在18年中旬或下半年很有可能会有大批量客户要进行Windows 10升级部署。所以今天简单跟各位介绍下Windows 10批量部署的知识点。
Windows 10的升级部署主要有3种解决方案，1、就地升级 2、全新部署 3、使用AutoPilot部署。
Windows部署大致需要经历如下几个阶段：
Windows 10系统部署要求：
处理器：1 GHz 或更快（支持PAE、NX 和 SSE2）
RAM：1 GB（32 位）或 2 GB（64 位）
硬盘空间：16 GB（32 位）或 20 GB（64 位）
图形卡：带有 WDDM 驱动程序的Microsoft DirectX 9 图形设备或以上版本，Windows 10桌面版支持最小的分辨率为 (1024 x 768)
Windows 10批量部署检查也有对于的工具，可以在http://technet.microsoft.com/en-us/library/bb977556.aspx网站上下载到。分享截图如下：
https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409
https://www.microsoft.com/en-us/WindowsForBusiness/upgrade-analytics
就地升级：
微软强烈推荐的方式，可以在最快的时间完成Windows 10升级操作，并且不需要从新安装所需的软件，原来Windows 7上的软件、驱动、C盘非系统文件将被保留。不建议在Windows XP上进行就地升级操作，版本扩大过大，可能会出现不知道的问题。就地升级通过点击未编译过的原版镜像内Setup.exe文件便可以进行就地升级升级操作，也可以使用SCCM与MDT、WDS等工具进行批量就地升级操作（需要注意Windows 10的版本，SCCM低版本不支持Windows 10），详见如下介绍:
针对就地升级微软发布了一张比较搞笑的图片，（就地升级过程中仅提供蛋黄，不动蛋清）：
就地升级的4个过程组：
SCCM部署Windows 10介绍：
Supported operating systems for clients anddevices for System Center Configuration Manager
Windows 10:Pro, Enterprise
See Supportfor versions of Windows 10 for details about the different releaseversions of Windows 10 that are supported by the different versions ofConfiguration Manager.
Support for Windows 10 as a client ofSystem Center Configuration Manager
https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10
System Center Configuration Manager:Support for Windows 10 and Microsoft Intune
In Summary: Planning and Guidance
| Product Version |
Release Timing |
Windows Servicing Support |
| System Center Configuration Manager |
By end of 2015 for initial release |
· Windows 10 Current Branch, Current Branch for Business, and Long Term Servicing Branch |
| System Center 2012 Configuration Manager SP2 CU1 |
May 2015, with cumulative updates as needed |
· Windows 10 LTSB 2015, · Windows 10 CB/CBB through February 2016* |
*ConfigMgr 2012 supportsWindows 10 version 1507 (build 10.0.10240) and 1511 (build 10.0.10586) for thelifecycle of these builds. Any new Windows 10 CB/CBB builds released in thefuture will not be supported With ConfigMgr 2012 and will require System CenterConfiguration Manager current branch for supported management.
If you want to deploy Windows 10 in your environment today, youshould have already upgraded ConfigMgr 2012 to the latest service pack andcumulative update as many of our customers already have.
If you are deploying Windows 10 Current Branch, then you alsoneed a plan to upgrade to System Center Configuration Manager. Once yourenvironment is upgraded to System Center Configuration Manager, then you willbe ready to start managing future builds of Windows 10 Current Branch as they arereleased.
If you don’t think you’ll be able to upgrade your environment toSystem Center Configuration Manager in the next several months, then you’llneed to deploy Windows 10 Enterprise LTSB 2015 with ConfigMgr 2012 to remain ina supported configuration going forward. Subsequent releases of the Windows 10Current Branch in 2016 and beyond will not be supported with ConfigMgr 2012.
Upgrade to System Center ConfigurationManager
https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager
In-place upgrade paths
Upgrade to version 1606
On December 15th, 2016, the baseline media for version 1606 was rereleased toadd support for additional upgrade scenarios. This new release supports theupgrade of the following to a fully licensed version of System CenterConfiguration Manager version 1606:4
· An evaluation install ofSystem Center Configuration Manager version 1606
· A release candidate install ofSystem Center Configuration Manager
· System Center 2012Configuration Manager with Service Pack 1
· System Center 2012Configuration Manager with Service Pack 2
· System Center 2012 R2Configuration Manager
· System Center 2012 R2Configuration Manager with Service Pack 1
If you use version 1606 baseline media downloaded prior toDecember 15th, 2016, you can upgrade only the following to a fully licensed versionof System Center Configuration Manager version 1606:
· An evaluation install ofSystem Center Configuration Manager version 1606
· System Center 2012Configuration Manager with Service Pack 2
· System Center 2012 R2Configuration Manager with Service Pack 1
4
Upgrade to version 1511
When you have version 1511 baseline media, you can upgrade the following to afully licensed version of System Center Configuration Manager version 1511:
· An evaluation install ofSystem Center Configuration Manager version 1511
· A release candidate install ofSystem Center Configuration Manager
· System Center 2012Configuration Manager with Service Pack 1
· System Center 2012Configuration Manager with Service Pack 2
· System Center 2012 R2Configuration Manager
· System Center 2012 R2Configuration Manager with Service Pack 1
全新部署（擦出重装）：
全新部署的场景一般用于Windows XP、全新购置的PC、不支持就地升级的一些场景，跟就地升级相比，全新部署更浪费时间与成本，所有软件、驱动等都需要重新安装，并且需要一步步进行相关配置。全新部署的就不过多的介绍了，相信大家都知道该如何玩。
使用AutoPilot部署：
AutoPilot是微软新推出的一款基于云的简化Windows 10部署配置的一款工具，还需要借助类似SCCM、WDS等工具进行系统部署，然后使用该工具进行统一化配置（需要将Windows 10设备加入AAD中）详细介绍如下：
https://docs.microsoft.com/zh-cn/windows/deployment/windows-10-auto-pilot
https://msdn.microsoft.com/zh-cn/partner-center/autopilot
