SOLVED
Home

Upgrading windows server 1709 to 1803?

%3CLINGO-SUB%20id%3D%22lingo-sub-253012%22%20slang%3D%22en-US%22%3EUpgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253012%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20am%20wondering%20if%20this%20is%20even%20possible%20or%20supported%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20trying%20to%20complete%20the%20upgrade%20as%20described%20here%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmarklewis.blog%2F2018%2F05%2F24%2Fwindows-server-1803%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmarklewis.blog%2F2018%2F05%2F24%2Fwindows-server-1803%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20the%20command%20from%20the%20administrator%20cmd%20prompt%20through%20a%20remote%20desktop%20connection.%3C%2FP%3E%3CP%3EBut%20I%20keep%20getting%20the%20ugly%20%22Setup%20couldn't%20start%20properly.%20Please%20reboot%20your%20pc%20and%20running%20windows%2010%20setup%20again%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20when%20I%20look%20here%2C%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fget-started-with-1803%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fget-started-with-1803%26nbsp%3B%3C%2FA%3E%20%26nbsp%3B%20It%20states%20that%20%22%3CSPAN%3EThis%20release%20should%20be%20installed%20as%20a%20clean%20installation.%3C%2FSPAN%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESooo%20...%20is%20an%20upgrade%20from%201709%20to%201803%20even%20possible%3F%26nbsp%3B%20%26nbsp%3BIt%20is%20a%20little%20crappy%20if%20we%20have%20to%20reinstall%20the%20half%20year%20releases%20from%20scratch%20every%20time%20...%20I%20understand%20this%20would%20be%20less%20of%20an%20issue%20if%20we%20use%20the%20non-lts%20windows%20versions%20solely%20as%20container%20images%2C%20but%20I%20would%20like%20to%20run%20this%20on%20my%20server%20as%20well%20...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-253012%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-311529%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-311529%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%2C%20I%20just%20want%20to%20make%20sure%20that%20this%20is%20clear%20for%20everyone.%20There%20is%20no%20such%20thing%20as%20Windows%20Server%202016%201803.%20There%20is%20only%20one%20RTM%20release%20of%20Server%202016%2C%20and%20that%20was%201607.%20There%20is%20Windows%20Server%202016%20and%20then%20there%20is%20Windows%20Server%201803.%20You%20must%20view%20them%20as%20two%20different%20product%20offerings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Windows%20Server%20releases%20with%20YYMM%20build%20numbers%2C%20like%201607%2C%201709%2C%201803%2C%20etc...%20are%20part%20of%20the%20windows%20semi-annual%20channel%20(SAC)%20and%20will%20be%20released%20every%20six%20months.%26nbsp%3BThese%20releases%20will%20be%20bleeding%20edge%20releases%20and%20will%20not%20support%20the%20GUI%20interface%20at%20all%2C%20only%20a%20core%20install.%20They%20will%20only%20have%20a%20support%20life%20span%20of%2018%20month.%20Even%20though%20there%20is%20cases%20of%20engineers%20upgrading%20a%20SAC%20deployment%20to%20the%20next%20release%2C%20this%20is%20not%20supported%20and%20MS%20is%20expecting%20you%20to%20deploy%20brand%20new%20installs%20when%20the%20new%20version%20is%20released.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Windows%20server%26nbsp%3Brelease%20with%20the%20actual%20year%20referenced%20are%20the%20Long%20Term%20Servicing%26nbsp%3BChannel.%20They%20are%20what%20we%20are%20used%20to%20seeing%20released%20every%20so%20many%20years%2C%202012%2C%202016%2C%202019%2C%20etc...%20They%20will%26nbsp%3Binclude%20some%20of%20the%20technologies%20that%20have%20been%20released%20in%20the%20SAC%20channel%20that%20have%20been%20deemed%20production%20stable%20and%20supportable.%20These%20releases%20will%20have%20the%20normal%20mainstream%20support%20of%205%20years.%20These%20releases%20on%20the%20other%20hand%20can%20be%20upgraded%20from%20old%20to%20new%20releases.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreat%20Ref%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fsemi-annual-channel-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EWindows%20Server%20Semi-Annual%20Channel%20overview%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253586%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253586%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54016%22%20target%3D%22_blank%22%3E%40Jim%20Gaynor%3C%2FA%3E%26nbsp%3B%20%26nbsp%3B%20Solid%20info.%20That%20all%20makes%20good%20sense%2C%20and%20I'll%20go%20to%20the%20LTS%20Windows%20Server%202019%20then%20when%20it%20comes.%20It's%20just%20a%20windows%20container%20and%20hyper-v%20host%20lab%20anyway.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253503%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253503%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F194373%22%20target%3D%22_blank%22%3E%40Lars%20Andersen%3C%2FA%3E%2C%20in-place%20upgrades%20from%20Windows%20Server%201709%20to%20Windows%20Server%201803%20were%26nbsp%3Bpart%20of%20the%20initial%20Insider%20previews%2C%20and%20were%20promoted%20as%20a%20feature%20of%20that%20version%20early%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fredmondmag.com%2Farticles%2F2018%2F01%2F23%2Fwindows-server-in-place-upgrades.aspx%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fredmondmag.com%2Farticles%2F2018%2F01%2F23%2Fwindows-server-in-place-upgrades.aspx%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20it%20looks%20like%20they%20dropped%20that%20feature%20when%20they%20announced%2C%20in%20late%20March%2C%20that%20the%20SAC%20versions%20would%20be%20focused%20entirely%20on%20%22%3CSPAN%3Emodern%20applications%20and%20innovation%20scenarios%20such%20as%20containers%22%2C%20and%20would%20drop%20most%20of%20the%20infrastructure%20roles.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcloudblogs.microsoft.com%2Fwindowsserver%2F2018%2F03%2F29%2Fwindows-server-semi-annual-channel-update%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcloudblogs.microsoft.com%2Fwindowsserver%2F2018%2F03%2F29%2Fwindows-server-semi-annual-channel-update%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAccordingly%2C%201803%20has%20even%20fewer%20infrastructure%20services%20than%201709%20(which%20dropped%20Storage%20Space%20Direct%20just%20as%20it%20was%20released).%20So%20an%20in-place%20upgrade%20would%20have%20likely%20stripped%20out%20features%20from%20a%201709%20installation%2C%20causing%20issues%20for%20administrator%20who%20(rightfully)%20expect%20an%20in-place%20upgrade%20to%20maintain%20roughly%20the%20same%20feature%20set.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20seen%20any%20indication%20if%201809%20will%20offer%20an%20in-place%20upgrade%2C%20since%20all%20the%20attention%20has%20been%20focused%20on%20the%20LTSC%20Windows%20Server%202019%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253047%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253047%22%20slang%3D%22en-US%22%3E%3CP%3EYou're%20welcome.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253046%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253046%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20idea%20Dave.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253044%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253044%22%20slang%3D%22en-US%22%3E%3CP%3EBetter%20to%20provide%20your%20feedback%20over%20here%20on%20uservoice.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F304618-installation-and-patching%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F304618-installation-and-patching%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3Bor%20vote%20this%20one%20up%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295047-general-feedback%2Fsuggestions%2F34209076-upgrade-a-server-running-core-to-the-next-version%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295047-general-feedback%2Fsuggestions%2F34209076-upgrade-a-server-running-core-to-the-next-version%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253041%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253041%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20I%20am%20reading%20that%20as%20well.%20I%20even%20quoted%20it%20in%20my%20original%20question%20above%20...%26nbsp%3B%20%26nbsp%3BExcept%20for%20that%20one%20guy%20who%20wrote%20on%20his%20blog%20how%20he%20upgraded%20from%201709%20to%201803.%26nbsp%3B%20See%20my%20initial%20question.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20like%201709%20was%20just%20swept%20under%20the%20carpet%3F%26nbsp%3B%20Or%26nbsp%3Bshould%20we%20expect%20to%20reinstall%20version%201809%2C%201903%20and%201909%20as%20well%2C%20when%20they%20will%20be%20released%3F%26nbsp%3B%20That%20reduces%20the%20usability%20of%20the%20semi-annual%20core%20versions%20to%20be%20something%20that%20we%26nbsp%3Buse%20as%20the%20basis%20of%20our%20container%20images%2C%20where%20we%20can%20just%20bump%20the%20version%20number%20in%26nbsp%3Bdocker%20files%20...%20seems%20like%20a%20bit%20of%20a%20problem%20to%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253037%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253037%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%2C%20missed%201709%2C%20I%20cannot%20find%20the%20document%20right%20now%20but%20as%20far%20as%20I%20know%20you%20cannot%20in-place%20upgrade%20to%20Server%202016%201803%3B%20you%20should%20clean%20install%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253034%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253034%22%20slang%3D%22en-US%22%3E%3CP%3ESo%26nbsp%3Byou%20are%20saying%20that%20Windows%20Server%201709%20Core%20that%20has%20been%20running%20my%20server%20since%20it%20was%20released%20in%20september%202017%20is%20not%20an%20RTM%20version%20of%20Server%202016%2C%20but%201803%20is%3F%26nbsp%3B%20That%20does%20not%20make%20any%20sense.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%26nbsp%3Bfully%20understand%20the%20semi-annual%20release%20program%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fsemi-annual-channel-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fsemi-annual-channel-overview%3C%2FA%3E%20vs%20the%20LTS%20versions%20(2016%2F2019%20etc)%3C%2FP%3E%3CP%3EAnd%20I%20get%20that%201803%20is%26nbsp%3Ba%20semi%20annual%20release.%26nbsp%3BBut%20appluing%20logic%20I%20would%20asume%20that%201709%20was%20part%20of%20that%20channel%20as%20well%3F%26nbsp%3B%20%26nbsp%3BIt%20is%20only%20briefly%20mentioned%20in%20the%20semi-annual%20channel%20overview%20above.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20Microsoft%20just%20forget%20that%20they%20released%201709%3F%26nbsp%3B%20So%20when%20we%20get%20to%201809%2C%20what%20are%20the%20odds%20that%20we%20have%20to%20reinstall%20again%20a%20second%20time%20if%20we%20want%20to%20run%20the%20core%20version%20of%202016%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253028%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253028%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ECurrently%20there%20are%20two%20RTM%20versions%20of%20Server%202016.%201607%20and%201803.%201803%20is%20a%20core%20only%20version%20and%20must%20be%20clean%20installed%2C%20you%20cannot%20in-place%20upgrade%201607%20to%201803%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fget-started-with-1803%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fget-started-with-1803%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253014%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%20windows%20server%201709%20to%201803%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253014%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20...%20I%20tried%20all%20the%20windows%2010%20related%20fixes%20for%20the%20error%20I%20get.%20Nothing%20helped.%20Keep%20getting%20that%20error.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Lars Andersen
Occasional Contributor

Hi, I am wondering if this is even possible or supported?

 

I was trying to complete the upgrade as described here

https://marklewis.blog/2018/05/24/windows-server-1803/

 

Running the command from the administrator cmd prompt through a remote desktop connection.

But I keep getting the ugly "Setup couldn't start properly. Please reboot your pc and running windows 10 setup again".

 

But when I look here,  https://docs.microsoft.com/en-us/windows-server/get-started/get-started-with-1803    It states that "This release should be installed as a clean installation."

 

Sooo ... is an upgrade from 1709 to 1803 even possible?   It is a little crappy if we have to reinstall the half year releases from scratch every time ... I understand this would be less of an issue if we use the non-lts windows versions solely as container images, but I would like to run this on my server as well ... 

11 Replies

Also ... I tried all the windows 10 related fixes for the error I get. Nothing helped. Keep getting that error.

Currently there are two RTM versions of Server 2016. 1607 and 1803. 1803 is a core only version and must be clean installed, you cannot in-place upgrade 1607 to 1803

https://docs.microsoft.com/en-us/windows-server/get-started/get-started-with-1803

 

 

 

So you are saying that Windows Server 1709 Core that has been running my server since it was released in september 2017 is not an RTM version of Server 2016, but 1803 is?  That does not make any sense.

 

I fully understand the semi-annual release program https://docs.microsoft.com/en-us/windows-server/get-started/semi-annual-channel-overview vs the LTS versions (2016/2019 etc)

And I get that 1803 is a semi annual release. But appluing logic I would asume that 1709 was part of that channel as well?   It is only briefly mentioned in the semi-annual channel overview above.  

Did Microsoft just forget that they released 1709?  So when we get to 1809, what are the odds that we have to reinstall again a second time if we want to run the core version of 2016?

Sorry, missed 1709, I cannot find the document right now but as far as I know you cannot in-place upgrade to Server 2016 1803; you should clean install it.

 

 

Yeah, I am reading that as well. I even quoted it in my original question above ...   Except for that one guy who wrote on his blog how he upgraded from 1709 to 1803.  See my initial question.

 

It's like 1709 was just swept under the carpet?  Or should we expect to reinstall version 1809, 1903 and 1909 as well, when they will be released?  That reduces the usability of the semi-annual core versions to be something that we use as the basis of our container images, where we can just bump the version number in docker files ... seems like a bit of a problem to me.

Good idea Dave. Thanks.

You're welcome.

 

 

Solution

@Lars Andersen, in-place upgrades from Windows Server 1709 to Windows Server 1803 were part of the initial Insider previews, and were promoted as a feature of that version early on.

 

https://redmondmag.com/articles/2018/01/23/windows-server-in-place-upgrades.aspx

 

However, it looks like they dropped that feature when they announced, in late March, that the SAC versions would be focused entirely on "modern applications and innovation scenarios such as containers", and would drop most of the infrastructure roles.

 

https://cloudblogs.microsoft.com/windowsserver/2018/03/29/windows-server-semi-annual-channel-update/

 

Accordingly, 1803 has even fewer infrastructure services than 1709 (which dropped Storage Space Direct just as it was released). So an in-place upgrade would have likely stripped out features from a 1709 installation, causing issues for administrator who (rightfully) expect an in-place upgrade to maintain roughly the same feature set.

 

I haven't seen any indication if 1809 will offer an in-place upgrade, since all the attention has been focused on the LTSC Windows Server 2019 version.

Thanks @Jim Gaynor    Solid info. That all makes good sense, and I'll go to the LTS Windows Server 2019 then when it comes. It's just a windows container and hyper-v host lab anyway.

 

@Dave Patrick, I just want to make sure that this is clear for everyone. There is no such thing as Windows Server 2016 1803. There is only one RTM release of Server 2016, and that was 1607. There is Windows Server 2016 and then there is Windows Server 1803. You must view them as two different product offerings.

 

The Windows Server releases with YYMM build numbers, like 1607, 1709, 1803, etc... are part of the windows semi-annual channel (SAC) and will be released every six months. These releases will be bleeding edge releases and will not support the GUI interface at all, only a core install. They will only have a support life span of 18 month. Even though there is cases of engineers upgrading a SAC deployment to the next release, this is not supported and MS is expecting you to deploy brand new installs when the new version is released.

 

The Windows server release with the actual year referenced are the Long Term Servicing Channel. They are what we are used to seeing released every so many years, 2012, 2016, 2019, etc... They will include some of the technologies that have been released in the SAC channel that have been deemed production stable and supportable. These releases will have the normal mainstream support of 5 years. These releases on the other hand can be upgraded from old to new releases.

 

Great Ref: Windows Server Semi-Annual Channel overview

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