Home

In-Place Upgrade WIndows Server 2012 R2 Standard to 2019 Error

%3CLINGO-SUB%20id%3D%22lingo-sub-857715%22%20slang%3D%22en-US%22%3EIn-Place%20Upgrade%20WIndows%20Server%202012%20R2%20Standard%20to%202019%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857715%22%20slang%3D%22en-US%22%3E%3CP%3ECurrent%20server%20configuration%20is%3A%20PDC%20w%2F%20AD.%26nbsp%3B%20WIndows%20Server%202012%20R2%2064-bit.%26nbsp%3B%20I%20have%20tried%20mounting%20the%20image%20as%20a%20CD%2C%20running%20the%20install%20from%20that%20as%20well%20as%20copying%20the%20entire%20contents%20and%20putting%20it%20into%20a%20folder%20on%20the%20boot%20(C%3A)%20drive.%26nbsp%3B%20Each%20time%20I%20try%20I%20get%20the%20same%20error%20message%3A%20Windows%20cannot%20find%20the%20Microsoft%20Software%20License%20Terms.%26nbsp%3B%20Make%20sure%20the%20installation%20sources%20are%20valid%20and%20restart%20the%20installation.%26nbsp%3B%20This%20is%20NOT%20a%20VM.%26nbsp%3B%20The%20hardware%20is%20an%20HPE%20Proliant%20DL380%20Gen%2010.%26nbsp%3B%20%26nbsp%3B%20The%20Server%202019%20image%20works%20because%20I%20tested%20it%20by%20installing%20it%20onto%20a%20new%20system.%26nbsp%3B%20Any%20suggestions%20would%20be%20greatly%20appreciated.%26nbsp%3B%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20801px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131985iD6E7EA5F128B9105%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22UG1.PNG%22%20title%3D%22UG1.PNG%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20789px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131984iC73E0F4C229E0561%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22UG2.PNG%22%20title%3D%22UG2.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-857715%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-857731%22%20slang%3D%22en-US%22%3ERe%3A%20In-Place%20Upgrade%20WIndows%20Server%202012%20R2%20Standard%20to%202019%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857731%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409799%22%20target%3D%22_blank%22%3E%40ettlig%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20like%20you're%20using%20an%20evaluation%20media%20for%20the%20upgrade%2C%26nbsp%3Bit%20is%20not%20possible%20to%20perform%20an%20in-place%20update%20from%20a%20licensed%20product%20to%20an%20evaluation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20have%20a%20license%20for%20Windows%20Server%202019%2C%20check%20with%20your%20reseller%20to%20get%20the%20retail%20installation%20media%20for%20Windows%20Server%202019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3CBR%20%2F%3ELeon%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-857919%22%20slang%3D%22en-US%22%3ERe%3A%20In-Place%20Upgrade%20WIndows%20Server%202012%20R2%20Standard%20to%202019%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857919%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20order%20to%20perform%20an%20in-place%20upgrade%20you'll%20need%20to%20run%20%3CSTRONG%3Esetup.exe%3C%2FSTRONG%3E%20from%20the%20root%20of%20the%20install%20media%20within%20windows.%20The%20media%20needs%20to%20be%20licensed%20retail%20or%20volume%2C%20not%20evaluation.%20That%20being%20said%20an%20in-place%20upgrade%20is%20never%20recommended%20and%20a%20very%20risky%20move.%20The%20better%20option%20is%20to%20build%20a%20new%20one%20from%20scratch.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EThe%20two%20prerequisites%20to%20introducing%20the%20first%202019%20domain%20controller%20are%20that%20domain%20functional%20level%20needs%20to%20be%202008%20or%20higher%20and%20older%20sysvol%20FRS%20replication%20needs%20to%20have%20been%20migrated%20to%20DFSR%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FStorage-at-Microsoft%2FStreamlined-Migration-of-FRS-to-DFSR-SYSVOL%2Fba-p%2F425405%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FStorage-at-Microsoft%2FStreamlined-Migration-of-FRS-to-DFSR-SYSVOL%2Fba-p%2F425405%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EI'd%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20verify%20health%20%3CU%3Ecorrecting%20all%20errors%20found%3C%2FU%3E%20before%20starting.%20Then%20stand%20up%20the%20new%202019%2C%20patch%20it%20fully%2C%20license%20it%2C%20join%20existing%20domain%2C%20add%20active%20directory%20domain%20services%2C%20promote%20it%20also%20making%20it%20a%20GC%20(recommended)%2C%20transfer%20FSMO%20roles%20over%20(optional)%2C%20transfer%20pdc%20emulator%20role%20(optional)%2C%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20again%20verify%20health%2C%20when%20all%20is%20good%20you%20can%20decommission%20%2F%20demote%20old%20one.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
ettlig
Occasional Visitor

Current server configuration is: PDC w/ AD.  WIndows Server 2012 R2 64-bit.  I have tried mounting the image as a CD, running the install from that as well as copying the entire contents and putting it into a folder on the boot (C:) drive.  Each time I try I get the same error message: Windows cannot find the Microsoft Software License Terms.  Make sure the installation sources are valid and restart the installation.  This is NOT a VM.  The hardware is an HPE Proliant DL380 Gen 10.    The Server 2019 image works because I tested it by installing it onto a new system.  Any suggestions would be greatly appreciated.  UG1.PNGUG2.PNG

2 Replies

Hello @ettlig,

 

It looks like you're using an evaluation media for the upgrade, it is not possible to perform an in-place update from a licensed product to an evaluation.

 

The recommended and much safer method is to install fresh servers on the side, patch fully and migrate the roles or applications over to them.

 

If in-place upgrading is the only possibility then you'll need to purchase any interim license (if needed) as well as the end goal license, ask the license provider for the installation media for Windows Server 2019.

 

 

Best regards,
Leon

 

In order to perform an in-place upgrade you'll need to run setup.exe from the root of the install media within windows. The media needs to be licensed retail or volume, not evaluation. That being said an in-place upgrade is never recommended and a very risky move. The better option is to build a new one from scratch.

 

The two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYS...

 

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

 

  

 

 

 

 

 

Related Conversations
Extentions Synchronization
Deleted in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies