This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 95%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
ITNOA
Hi,
I have a licensed media, and I can in-place upgrade from Windows Server 2019 Data Center [Desktop Experience] to Windows Server 2022 Data Center [Desktop Experience].
But When I want to in-place upgrade from Windows Server 2019 Data Center Core to Windows Server 2022 Data Center Core, Keep files, settings, and apps option is disable. How to resolve this issue?
My current Windows Server 2019 core details is in below
Get-ComputerInfo -Property WindowsProductName,WindowsBuildLabEx,WindowsEditionID
WindowsProductName WindowsBuildLabEx WindowsEditionId
\------------------
----------------- ----------------
Windows Server Datacenter 19041.1.amd64fre.vb_release.191206-1406 ServerDatacenterACor
All of my roles installed on server core is
Get-WindowsFeature | Where-Object {$_. installstate -eq "installed"} | Format-List Name | more
Name : AD-Domain-Services
Name : DNS
Name : FileAndStorage-Services
Name : File-Services
Name : FS-FileServer
Name : Storage-Services
Name : NET-Framework-Features
Name : NET-Framework-Core
Name : NET-Framework-45-Features
Name : NET-Framework-45-Core
Name : NET-WCF-Services45
Name : NET-WCF-TCP-PortSharing45
Name : Containers
Name : GPMC
Name : RSAT
Name : RSAT-Feature-Tools
Name : RSAT-System-Insights
Name : RSAT-Role-Tools
Name : RSAT-AD-Tools
Name : RSAT-AD-PowerShell
Name : RSAT-DNS-Server
Name : System-DataArchiver
Name : System-Insights
Name : Windows-Defender
Name : PowerShellRoot
Name : PowerShell
Name : PowerShell-V2
Name : WoW64-Support
And the edition of my Windows Core server is
DISM /Online Get-CurrentEdition
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19042.1889
Current edition is:
Current Edition : ServerDatacenterACor
The operation completed successfully.
Thanks
I add this question to serverfault https://serverfault.com/q/1117679/145811
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
What's the result of?
Dism /Online /Get-CurrentEdition
What roles have been installed?
All of my roles installed on server core is
Get-WindowsFeature | Where-Object {$_. installstate -eq "installed"} | Format-List Name | more
Name : AD-Domain-Services
Name : DNS
Name : FileAndStorage-Services
Name : File-Services
Name : FS-FileServer
Name : Storage-Services
Name : NET-Framework-Features
Name : NET-Framework-Core
Name : NET-Framework-45-Features
Name : NET-Framework-45-Core
Name : NET-WCF-Services45
Name : NET-WCF-TCP-PortSharing45
Name : Containers
Name : GPMC
Name : RSAT
Name : RSAT-Feature-Tools
Name : RSAT-System-Insights
Name : RSAT-Role-Tools
Name : RSAT-AD-Tools
Name : RSAT-AD-PowerShell
Name : RSAT-DNS-Server
Name : System-DataArchiver
Name : System-Insights
Name : Windows-Defender
Name : PowerShellRoot
Name : PowerShell
Name : PowerShell-V2
Name : WoW64-Support
And the edition of my Windows Core server is
DISM /Online Get-CurrentEdition
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19042.1889
Current edition is:
Current Edition : ServerDatacenterACor
The operation completed successfully.
Any update?
The simplest and safest solution may be to stand up the new one, patch fully and migrate roles over to it.
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2022, 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.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
I need to in-place upgrade, but you do not provide solution for resolving my issue
thanks
I run your command and I have one error, and do not know how to resolve this?
Starting test: SystemLog
An error event occurred. EventID: 0x00000022
Time Generated: 12/13/2022 11:08:42
Event String:
The time service has detected that the system time needs to be changed by 0 seconds. The time service will not change the system time by more than 172800 seconds. Verify that your time and time zone are correct, and that the time source VM IC Time Synchronization Provider is working properly.
Not sure what command you're asking about? Looks like the in-place is blocked for some reason unknown to us. The simplest solution is the migration I mentioned above. You can also start a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness
--please don't forget to upvote and Accept as answer if the reply is helpful--
As you says, I run dcdiag command and I have only one error like below
The time service has detected that the system time needs to be changed by 0 seconds. The time service will not change the system time by more than 172800 seconds. Verify that your time and time zone are correct, and that the time source VM IC Time Synchronization Provider is working properly.
thanks
If the PDC emulator then turn off time sync in integration services, then do
w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:<ntp ip address> /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration
--please don't forget to upvote and Accept as answer if the reply is helpful--
I run my windows server on Hyper-V
Yes, I can tell. Nothing changes.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
w32tm /query /source
return correct source after
w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update
but after I start, start service with
net stop w32time
net start w32time
the source change to previously value local cmos
How to resolve this?
thanks
Just a reminder, please don't forget to close up the thread by 
Please close this one by and open a new thread for this new question.