Reinstall Node on Windows Server Failover Cluster

Windows Server 2025 Core
Hyper-V

Situation

From Core Edition to Desktop GUI Edition.

PS C:\> Get-ClusterResource

Name                                State  OwnerGroup         ResourceType
----                                -----  ----------         ------------
Cluster Disk 1                      Online Cluster Group      Physical Disk
Cluster IP Address                  Online Cluster Group      IP Address
Cluster Name                        Online Cluster Group      Network Name
Storage Qos Resource                Online Cluster Group      Storage QoS Policy Manager
User Manager                        Online User Manager Group User Manager
Virtual Machine Cluster WMI         Online Cluster Group      Virtual Machine Cluster WMI
Virtual Machine Configuration Rocky Online Rocky              Virtual Machine Configuration
Virtual Machine Rocky               Online Rocky              Virtual Machine


PS C:\> Get-ClusterNode

Name      State Type
----      ----- ----
HYPER-V-1 Up    Node
HYPER-V-2 Up    Node

Reinstall Node

1. Stop cluster serivce and evict.

PS C:\> Stop-ClusterNode -Name HYPER-V-1

Name      State Type
----      ----- ----
HYPER-V-1 Down  Node

PS C:\> Remove-ClusterNode -Name HYPER-V-1

Remove-ClusterNode
Are you sure you want to evict node HYPER-V-1?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y

PS C:\> Get-ClusterNode

Name      State Type
----      ----- ----
HYPER-V-2 Up    Node

2. Unjoin the domain.

PS C:\> Remove-Computer -UnjoinDomaincredential (Get-Credential) -PassThru -Restart -Verbose

cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
VERBOSE: Performing the operation "Remove-Computer" on target "HYPER-V-1".

Confirm
After you leave the domain, you will need to know the password of the local Administrator account to log onto this
computer. Do you wish to continue?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y

3. Reinstall OS desktop experience and deploy hyper-v.

・ Deploying a Hyper-V Failover Cluster on Windows Server 2025 Core
・ Upgrade a Windows Server failover cluster with a cluster OS rolling upgrade

DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
DISM /online /Set-Edition:ServerDatacenter /ProductKey:D764K-2NDRG-47T6Q-P8T8W-YP6DF /AcceptEula

4. Check network and shared volume.

Get-NetAdapter
Get-VMSwitch
Get-PhysicalDisk

5. Add the node back to the cluster.

PS C:\> Add-ClusterNode -Cluster 'MyCluster' -Name 'HYPER-V-1'
PS C:\> Get-ClusterNode

Name      State Type
----      ----- ----
HYPER-V-1 Up    Node
HYPER-V-2 Up    Node

6. Disable UAC.

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System' -Name 'EnableLUA' -Value 0
Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System' | Select-Object EnableLUA

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System' -Name 'EnableLUA' -Value 1

Troubleshooting

Migrate VM fails with error 1152

PS C:\> Move-VM -Name Rocky -DestinationHost HYPER-V-1

Move-VM : Virtual machine migration operation failed at migration destination.
Virtual machine migration operation for 'Rocky' failed at migration destination 'HYPER-V-1'. (Virtual machine ID
6631EB12-9158-4C66-BA05-AEB49F90A378)
At line:1 char:1
+ Move-VM -Name Rocky -DestinationHost HYPER-V-1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Move-VM], VirtualizationException
    + FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.MoveVM

PS C:\> Compare-VM -Name Rocky -DestinationHost HYPER-V-1

VM                 : VirtualMachine (Name = 'Rocky') [Id = '6631eb12-9158-4c66-ba05-aeb49f90a378']
OperationType      : MoveVirtualMachine
Destination        : HYPER-V-1
Path               :
SnapshotPath       :
VhdDestinationPath :
VhdSourcePath      :
Incompatibilities  : {21026}
CheckpointPath     :

PS C:\> Get-WinEvent -FilterHashTable @{LogName='System'; StartTime=(get-date).AddHours(-1); EndTime=(get-date); Level=3; ProviderName='Microsoft-Windows-FailoverClustering'} | fl *

Message              : The pending move for the role 'Rocky' did not complete.
Id                   : 1155
Version              : 0
Qualifiers           :
Level                : 3
Task                 : 3
Opcode               : 0
Keywords             : -9223372036854775808
RecordId             : 51010
ProviderName         : Microsoft-Windows-FailoverClustering
ProviderId           : baf908ea-3421-4ca9-9b84-6689b8c6f85f
LogName              : System
ProcessId            : 4068
ThreadId             : 6528
MachineName          : HYPER-V-2.sj.com
UserId               : S-1-5-18
TimeCreated          : 7/12/2026 9:39:06 PM
ActivityId           :
RelatedActivityId    :
ContainerLog         : System
MatchedQueryIds      : {0}
Bookmark             : System.Diagnostics.Eventing.Reader.EventBookmark
LevelDisplayName     : Warning
OpcodeDisplayName    : Info
TaskDisplayName      : Resource Control Manager
KeywordsDisplayNames : {}
Properties           : {System.Diagnostics.Eventing.Reader.EventProperty,
                       System.Diagnostics.Eventing.Reader.EventProperty}

The virtual machine is not compatible with the another virtualization host (HPYER-V-1.sj.com).
The HYPER-V-1.sj.com is Windows server 2025 Desktop, the HYPER-V-2.sj.com is Windows server 2025 Core.

Desktop >>> Core ==> OK
Desktop <<< Core ==> NG

Solution:

Shutdown the virtual machine and then migrate.