Everything, Everything

2024: J F M A M J J A S O N
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
KMS Activation
Friday 24th March, 2017 17:51 Comments: 0
The introduction of Windows 10 really made KMS activation more complicated than it needed to be. First of all there were the updates and additional KMS keys for Server 2012 R2 that allows you to use it to activate Windows 10 clients. But then along came Windows 10 1607 (LTSB 2016), which then requires another update for Server 2012 R2 to allow you to activate the newer versions of Windows 10 (as well as Server 2016) (this detail is buried away under July 2016). I finally stumbled on this really good Microsoft blog post, which clarifies things. Apparently you need all the Windows updates plus the right KMS key (Windows Srv 2016 DataCtr/Std KMS), and then you should be able to activate all versions of Windows 10. Fingers crossed this works, as I want to roll out a Windows 10 build based on 1607 without having to join it to the domain for activation.
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3