Forum Discussion
JonEllisDeltaD
May 10, 2023Copper Contributor
Upgrade Windows Server 2019 Evaluation Issue
Every time I try to upgrade our evaluation datacenter I get this error. DISM.log 2023-05-10 13:32:23, Info DISM PID=1812 TID=2520 Scratch directory set to 'C:\Users\sajellis\AppData\Local\Tem...
- May 11, 2023Dave,
So this command:
Dism /online /Set-Edition:ServerDataCenter /ProductKey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /AcceptEula
is the same thing as downloading the Windows Server 2019 iso and running it on the computer.
I downloaded that iso, ran it, installed the Windows Server 2019 Datacenter (Desktop Experience) and kept files and apps.
The server went through the upgrade process.
I then used the slmgr /ipk and slmgr /ato command and everything was fine.
Thank you again for assisting me in finding the resolution.
JonEllisDeltaD
May 10, 2023Copper Contributor
the only available target edition is Datacenter.
I forget which command I ran but it only had the Datacenter one.
are you saying it is possible to use the ServerStandard and then convert it to Datacenter?
Dave Patrick
May 10, 2023MVP
No, installing a DataCenter edition then down converting to Standard is not possible to do, you'll need to clean install it if that's the question.
- JonEllisDeltaDMay 10, 2023Copper ContributorOh! No I’m not trying to do that. I’m going from a ServerDatacenter Evaluation to ServerDatacenter. As for your previous reply, that was the way I was trying to do it. But I get that 14081 error every time.
It keeps failing on upgrading. I cannot figure out why.- Dave PatrickMay 10, 2023MVP
What channel is the product key? OEM, retail, volume? Just to confirm you're using a KMS key that fails?
- JonEllisDeltaDMay 10, 2023Copper ContributorI’m using the KMS Client Product Key for Windows Server 2019 Datacenter from the link you sent in your first reply.
I run the command in the picture of my post, it will go through without errors normally, I reboot the server then put in the slmgr /ipk and slmgr /ato.
It has worked fine with other servers before and after this server. But for some reason this server will not go through the first command.
I hope that makes sense.