Windows Server 2012 to Windows Server 2016 Upgrade

%3CLINGO-SUB%20id%3D%22lingo-sub-2121938%22%20slang%3D%22en-US%22%3EWindows%20Server%202012%20to%20Windows%20Server%202016%20Upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2121938%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20Windows%20Server%202016%20server%20acting%20as%20our%20domain%20controller%20and%20I%20would%20like%20to%20upgrade%20that%20to%20Windows%20Server%202016.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20using%20this%20as%20a%20guide%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fupgrade%2Fupgrade-2012-to-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fupgrade%2Fupgrade-2012-to-2016%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhilst%26nbsp%3B%20preparing%20it%20says%20to%20make%20sure%20BuildLabEx%20says%20I%20am%20running%20Windows%20Server%202012.%26nbsp%3B%20But%20mine%20shows%20this%3A%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%220.30DE.png%22%20style%3D%22width%3A%20392px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F254251iBF3925202BF43471%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%220.30DE.png%22%20alt%3D%220.30DE.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20are%20the%20implications%20of%20not%20showing%20the%20value%20expected%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2121938%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-2122358%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Server%202012%20to%20Windows%20Server%202016%20Upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2122358%22%20slang%3D%22en-US%22%3E%3CP%3EAn%20in-place%20upgrade%20is%20never%20recommended%20and%20is%20risky%20especially%20for%20a%20domain%20controller.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'd%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20verify%20health%3CSTRONG%3E%20correcting%20all%20errors%20found%3C%2FSTRONG%3E%20before%20starting%20%3CSTRONG%3Eany%3C%2FSTRONG%3E%20operations.%20Then%20stand%20up%20the%20new%202016%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.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2121953%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Server%202012%20to%20Windows%20Server%202016%20Upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2121953%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F963825%22%20target%3D%22_blank%22%3E%40shuntera%3C%2FA%3E%26nbsp%3BThat%20looks%20like%20the%20correct%20string%20for%20Server%202012%20-%20%22win8%22%20as%20that's%20the%20desktop%20version%20it%20aligns%20with%2C%20and%20the%20build%20number%20at%20the%20start%20(9200)%20is%20%22Windows%20Server%202012%22%20(looked%20up%20on%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.gaijin.at%2Fen%2Finfos%2Fwindows-version-numbers%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.gaijin.at%2Fen%2Finfos%2Fwindows-version-numbers)%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

I have a Windows Server 2016 server acting as our domain controller and I would like to upgrade that to Windows Server 2016.

 

I am using this as a guide https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-2012-to-2016 

 

Whilst  preparing it says to make sure BuildLabEx says I am running Windows Server 2012.  But mine shows this:
0.30DE.png

 

What are the implications of not showing the value expected?

3 Replies

@shuntera That looks like the correct string for Server 2012 - "win8" as that's the desktop version it aligns with, and the build number at the start (9200) is "Windows Server 2012" (looked up on https://www.gaijin.at/en/infos/windows-version-numbers)

 

An in-place upgrade is never recommended and is risky especially for a domain controller.

 

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2016, 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.


 

@shuntera Yes, whilst that's the correct string I should have mentioned what Dave's covered - in place upgrade of domain controllers is not recommended and should be avoided in favour of building a new DC and migrating roles if possible. Make sure you have a full working backup if you're going ahead with the in-place upgrade (including System State and SYSVOL folders).