none
Win 10 Pro Upgrade RRS feed

  • Question

  • In our lab environment we are running Windows 7 Pro clients with valid OEM licenses. We are using MDT Standard client upgrade task sequence to upgrade these devices to Windows 10 Pro. We followed the steps from the following page https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit. The upgrade goes well however the computers are unable to activate and we get an error stating “No key management service (KMS) could be contacted.”  The Windows 10 ISO we imported to MDT was downloaded from Microsoft Licensing Service Center. 

    We created a second upgrade task sequence and placed our WIN 10 MAC key and we ended up with the same error as the first test

    Please advise!

    Monday, May 23, 2016 3:02 PM

All replies

  • Un cannot in-place upgrade an OEM copy to a volume license copy. If you want to upgrade OEM you will need to download the "retail" version of Windows 10 using Windows 10 Media Creation Tool and import that into MDT.

    https://www.microsoft.com/en-us/software-download/windows10


    Dave Barker

    Monday, May 23, 2016 7:35 PM
  • Yea, there are a couple of Microsoft Licensing "Gotchas" with this scenario.

    1. Microsoft *really* doesn't like it when you re-image using OEM Media.

    2. Windows 10 "pro" does not allow you to perform "In-Place" upgrade. Only Windows 10 "Enterprise VL" can perform an InPlace upgrade using MDT.

    3. Why is Windows 10 trying to go to a KMS server? did you use the Windows 10 VL media?

    Question: It is not clear what you are actually "licensed" to do here. Do you have a KMS server? or do you have WIndows 10 Enterprise VL MAK Keys?

    If you are just trying to install Windows 10 Pro Retail, just install them on the machine, Windows 10 Version 1511 will install and use the Windows 7 OEM product key in the BIOS to activate just fine! No Upgrade though.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, May 23, 2016 11:30 PM
    Moderator