Windows Server 2008R2 in-place upgrade to Windows Server 2012/2012R2

Post migrated to:


11 responses to “Windows Server 2008R2 in-place upgrade to Windows Server 2012/2012R2”

  1. Cyril says :

    Ok, this works only in best case scenario. I popped my 2012R2 in the DVD drive and start the process however after I select the OS type that I want, I get an obnoxious error:

    Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart installation.

    From there, I click ok and can’t proceed with the update.

    This is a physical box, no VMs involved.

    Any Ideas?

    • iSiek says :

      What kind of installation media do you use? Retail or OEM version?

      • Cyril says :

        We use RTM (Retail).

      • iSiek says :

        OK, strange. Does it happen on any 2008R2 server you would like to upgarde?
        Do you have other Windows Server 2012 media copy or ISO image to test?

      • Cyril says :

        I haven’t tried yet on another server as we didn’t have the needs to upgrade them. I”m sure there is a tweak that can be done to bypass the license, I need to find it.

      • iSiek says :

        Did you look into error log on C-drive? What is written there?

  2. Cyril says :

    In the event logs, nothing beside “The Software Protection service entered the running state”

  3. Cyril says :

    Tried another ISO download from Microsoft, same results. Bummer!

  4. Cyril says :

    I tried my ISO on another server and I can go through the process. The server I want to upgrade is a domain controller, what gives?

    • iSiek says :

      OK, looks like one of those 2 things are stopping you from in-place upgrade.

      1) Please check if your Forest Functional Level is at least on Windows Server 2003

      Windows Server 2008/2008R2 requires Windows 2000 FFL and Windows 2000 native Domain Functional Level to allow using it as Domain Controller. Since Windows Server 2012, Windows Server 2003 FFL is required

      but most possible is that one

      2) Check your current schema version if it has been extended to 69 and domain is prepared for new Domain Controller’s operating system.

      To check that, please follow one of those 2 articles on my blog

      Determine Schema Version using PowerShell


      Manual schema check

      if this version is not 69 you need to extend it first manually as transparent adpreping in this case would not work.

      To do that, open elevated command-prompt and type

      netdom query fsmo

      identify Schema and Infrastructure Masters then log on to them and mount Windows Server 2012R2 media. Now on Schema Master type

      cd :\support\adprep
      adprep.exe /forestprep

      Next, log on to Infrastructure Master and type

      cd :\support\adprep
      adprep.exe /domainprep

      After that try gain in-place upgrade

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: