In Microsoft’s documentation they mentioned this occurred with earlier versions of 2016 and it seems to have carried over to 20 as well from what I have found online. The only option given when converting it is to convert to Datacenter.
I did a new install myself in a VM and confirm you can’t convert 2019 Standard Core to full licensed copy. You can do this through the command line again with the FeatureName "Server-Gui-Shell".I have a case where customer installed 2019 Server Standard Core EVAL version and has it all setup and configured for production and we can’t convert it to non-EVAL version. amd64_microsoft-.18066.).ģ) On the server core system: Dism /Online /Enable-Feature /All /FeatureName:Server-Gui-Mgmt /Source:C:\TempTest /LimitAccessĤ) After it installed, it required a rebootĥ) When it came back up, got the cmd prompt and after about a minute Server Manager popped up (some GUI management features are available after “Server-Gui-Mgmt” feature is installed)Ħ) I then used Server Manager to add the “Server Graphical Shell” feature which is under the “User Interfaces and Infrastructure” section and rebooted.
NOTE: I actually had to copy over the WinSxS folder from two different servers because the first time I tried to enable the feature I saw the same payload problems in the CBS.log except it would point to a different version (e.g. Example: "Failed to find payload files, component:amd64_31bf3856ad364e35_.18039_en-us_a9315b328356154d, file: "Ģ) From another Server 2012 R2 system that had the GUI and was fully patched, I copied over the C:\Windows\WinSxS folder to a temp folder on my Server 2012 R2 Core server (My folder was C:\TempTest). Hopefully it helps someone!ġ) Checked C:\Windows\Logs\CBS\CBS.log after trying to install the feature and saw payload files were missing. Here's how I got my Server 2012 R2 Core system moved over to the GUI.
0 kommentar(er)
