Issues with connecting and managing headless hyperv server from win 11 using HV manager

[merrittr]

Hi all I have a real mess , as I am trying to recover vms from old machines Hyper-V 2012 r2 using Hyper V manager (hacked onto win 11 home)

I get this error when connecting

I have the registry updates to what I thought would allow remoting to anywhare

Any idea how to resolve this

 

[ChatGPT]

Hi merrittr — the key clue is in the error: Hyper‑V Manager is trying to use WinRM/CredSSP, but your client policy currently allows only:
AllowFreshCredentials
The error specifically requires:
AllowFreshCredentialsWhenNTLMOnly
That is usually needed when managing a workgroup / non-domain Hyper‑V host such as a standalone Hyper‑V Server 2012 R2 box.
Also, since this is Hyper‑V Manager hacked onto Windows 11 Home, keep in mind that setup is unsupported. It may work, but if it keeps fighting you, use Windows 11 Pro/Enterprise, Windows Admin Center, or temporarily manage it from a supported Windows Pro/Server machine.

Fix on the Windows 11 client​

Open PowerShell as Administrator and run:

$server = "HVSERVER"

Set-Item WSMan:\localhost\Client\TrustedHosts -Value $server -Force

Enable-WSManCredSSP -Role Client -DelegateComputer $server -Force

If name resolution is flaky, add the server to your hosts file:
notepad C:\Windows\System32\drivers\etc\hosts
Add a line like:
192.168.1.111 HVSERVER
Use the actual IP of the Hyper‑V server.

Fix the registry policy you showed​

Your screenshot shows this key:
HKLM\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentials
For your error, you also need this key:
HKLM\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentialsWhenNTLMOnly
Create it manually if needed.
Inside it, create:

Name: 1
Type: REG_SZ
Data: WSMAN/HVSERVER

You can also use:
WSMAN/*
But WSMAN/HVSERVER is safer than a wildcard.
Then run:
gpupdate /force
Or reboot the Windows 11 machine.

Fix on the Hyper‑V Server 2012 R2 host​

On the Hyper‑V server console, from PowerShell/Admin command line, run:

Enable-PSRemoting -Force
Enable-WSManCredSSP -Role Server -Force

Then confirm WinRM is listening:
winrm quickconfig
Also make sure remote management is enabled in sconfig:

1. Log on to the Hyper‑V Server console.
2. Run:

sconfig

1. Choose Configure Remote Management.
2. Enable remote management.
3. Reboot the server if prompted.

Check the account you are using​

The user you connect with must be a local admin on the Hyper‑V server.
On the Hyper‑V server, check/add it like this:
net localgroup administrators
If needed:
net localgroup administrators HVSERVER\YourUserName /add
If the local username/password are different from your Windows 11 login, in Hyper‑V Manager use:

1. Right-click Hyper‑V Manager.
2. Click Connect to Server.
3. Enter HVSERVER.
4. Select Connect as another user.
5. Use:

HVSERVER\username
Not just username.

Quick test before opening Hyper‑V Manager​

From the Windows 11 client, run:
Test-WSMan HVSERVER
Expected result: you should get a WSMan response, not an authentication or connection failure.
Then test CredSSP:
Get-WSManCredSSP
You should see the client delegating to something like:
WSMAN/HVSERVER

If it still fails​

Try connecting by server name, not IP address. CredSSP delegation usually behaves better with the hostname:
HVSERVER
Not:
192.168.1.111

Undo / cleanup if needed​

If you want to back out the CredSSP changes later:

Disable-WSManCredSSP -Role Client
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "" -Force

On the server:
Disable-WSManCredSSP -Role Server

Most likely fix in your case​

Add this missing registry path:
HKLM\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentialsWhenNTLMOnly
With:
1 = WSMAN/HVSERVER
Then run:

Enable-WSManCredSSP -Role Client -DelegateComputer HVSERVER -Force
gpupdate /force

Then reconnect using Connect as another user with HVSERVER\username.

 

[merrittr]

hmmm I get this now sorry it is an image it thinks the virtual machine management service isnt running , the filrwall is off and I am rdped into the hvserver

I check and 4 Hyper-V services are running out of 17 see in this image I cant cut it out as text unfortunately

 

[ChatGPT]

Hi merrittr — good news: your second screenshot actually shows Hyper‑V Virtual Machine Management is running.
The sc query ... | find "yper" output only shows display names, not status. The second command lists running services only, and this one is present:
Hyper-V Virtual Machine Management
So I would not chase the “4 out of 17 services” yet. Many of the Hyper‑V entries are drivers or demand-start services and will not all be running all the time.
The new error:
The operation is not supported.
points more toward client/host compatibility, WMI/WinRM, or unsupported Windows 11 Home Hyper-V Manager behavior, not the VMMS service itself.

1. First verify Hyper-V works locally on HVSERVER​

Since you are RDP’d into HVSERVER, run this on the server:

powershell
Get-Service vmms
Get-VM
Get-VMHost

Expected:

Status   Name
------   ----
Running  vmms

If Get-VM lists the VMs, the Hyper‑V host itself is basically OK.
If Get-VM fails locally, then the issue is on the server, not the Windows 11 client.

2. Check the Hyper-V WMI namespace on the server​

Still on HVSERVER, run:
Get-CimInstance -Namespace root\virtualization\v2 -ClassName Msvm_VirtualSystemManagementService
If that fails, try:
winmgmt /verifyrepository
Expected:
WMI repository is consistent
If WMI is inconsistent, do not reset WMI immediately unless needed — that is more invasive. Report the exact result first.

3. Restart only the key services​

On HVSERVER, run:

Restart-Service vmms -Force
Restart-Service WinRM -Force

Then confirm:
Get-Service vmms,WinRM
Expected:

Running  vmms
Running  WinRM

4. Re-enable the firewall later​

For testing, firewall off is understandable, but long-term it is not ideal. Hyper‑V remote management normally needs the correct WinRM/WMI/Hyper-V firewall rules, not the whole firewall disabled.
For now leave it as-is while testing, but once fixed, turn it back on and use proper rules.

5. Re-check CredSSP on both machines​

On HVSERVER, run:

Enable-PSRemoting -Force
Enable-WSManCredSSP -Role Server -Force

Then check:
Get-WSManCredSSP
On the Windows 11 machine, run PowerShell as Administrator:

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "HVSERVER" -Force
Enable-WSManCredSSP -Role Client -DelegateComputer "HVSERVER" -Force
Get-WSManCredSSP

Expected on the client: it should say credentials can be delegated to something like:
wsman/HVSERVER

6. Make sure you connect using the exact same name​

If your CredSSP entry says:
WSMAN/HVSERVER
Then in Hyper‑V Manager connect to:
HVSERVER
Do not connect using the IP address unless you also configured the IP address in TrustedHosts and Credential Delegation.
If needed, add this to the Windows 11 client’s hosts file:
192.168.1.111 HVSERVER
Path:
C:\Windows\System32\drivers\etc\hosts

7. Try the PowerShell remote test from Windows 11​

From the Windows 11 client:
Test-WSMan HVSERVER
Then:
Get-CimInstance -ComputerName HVSERVER -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem
If this second command fails, Hyper‑V Manager will fail too. The exact error from this command will be more useful than the GUI message.

8. Important: Windows 11 Home may be the blocker​

Because you said Hyper‑V Manager is hacked onto Windows 11 Home, that may now be the real problem.
Microsoft only supports Hyper‑V tools on Windows editions that include Hyper‑V support, normally:

Windows 10/11 Pro
Windows 10/11 Enterprise
Windows Server

The symptom changing from a CredSSP error to:
The operation is not supported
could mean authentication is now mostly fixed, but the Windows 11 Home Hyper‑V Manager install is not fully functional.

Best practical workaround​

If the goal is just to recover old VMs, I would do this:

1. Use a temporary Windows 10/11 Pro machine or VM.
2. Install Hyper‑V Management Tools normally.
3. Configure CredSSP/TrustedHosts.
4. Connect to HVSERVER.
5. Export the VMs or copy the VHD/VHDX files directly.

Alternatively, from HVSERVER itself, you can export VMs with PowerShell:

Get-VM
Export-VM -Name "YourVMName" -Path "D:\VMExports"

My read of your screenshots​

The host service is probably not the issue. Your vmms service appears to be running. The next thing I would test is:

Get-VM
Get-CimInstance -Namespace root\virtualization\v2 -ClassName Msvm_VirtualSystemManagementService

Run those on HVSERVER first. If both work locally, the fastest fix is likely to manage it from a supported Windows Pro/Server machine instead of the modified Windows 11 Home install.

 

[merrittr]

All the server side commands worked

on the win 11 home client I get an error on the get-ciminstance

any ideas

 

[ChatGPT]

Hi merrittr — that narrows it down nicely.
Your server-side results prove:

vmms is running
Get-VM works
Get-VMHost works
root\virtualization\v2 works locally

So the Hyper‑V host is OK. The current problem is now specifically:

Access is denied
HRESULT 0x80070005

That means the Windows 11 client can reach HVSERVER, but the account being used does not have a usable elevated remote token for the Hyper‑V WMI namespace.

Most likely cause​

You are in a workgroup / non-domain setup, so Windows is probably applying remote UAC token filtering to the local administrator account.
In short: even if you are logging in as Administrator, the remote WMI/CIM call may not receive full admin rights unless you explicitly allow it.

Step 1: Test using explicit server credentials​

On the Windows 11 client, run PowerShell as Administrator:
$cred = Get-Credential
When prompted, enter the server account like this:
HVSERVER\Administrator
Then run:
Get-CimInstance -ComputerName HVSERVER -Credential $cred -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem
If that works, Hyper‑V Manager should also work if you use Connect as another user with:
HVSERVER\Administrator

Step 2: If it still says Access is denied, enable full local admin token remotely​

On HVSERVER, run this from an elevated command prompt or PowerShell:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
Then restart WinRM and VMMS:

Restart-Service WinRM -Force
Restart-Service vmms -Force

Or just reboot HVSERVER.
Warning: This weakens remote UAC filtering for local administrator accounts. On a trusted home/lab network it is commonly used for workgroup Hyper‑V management, but I would not use it casually on an exposed or untrusted network.

Step 3: Retest from the Windows 11 client​

Run:

$cred = Get-Credential HVSERVER\Administrator
Get-CimInstance -ComputerName HVSERVER -Credential $cred -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem

Expected result: it should list Hyper‑V VM/system objects instead of Access is denied.

Step 4: Try Hyper-V Manager again​

In Hyper‑V Manager:

1. Right-click Hyper‑V Manager.
2. Click Connect to Server.
3. Enter:

HVSERVER

1. Select Connect as another user.
2. Use:

HVSERVER\Administrator
Do not use just Administrator, and avoid using the IP address unless all your TrustedHosts/CredSSP entries also use the IP.

Step 5: Optional cleaner method — create a dedicated management user​

On HVSERVER:

net user hvadmin * /add
net localgroup Administrators hvadmin /add
net localgroup "Hyper-V Administrators" hvadmin /add
net localgroup "Remote Management Users" hvadmin /add

Then from the Windows 11 client, connect as:
HVSERVER\hvadmin
This is cleaner than using the built-in Administrator account.

Undo command if needed​

If you want to reverse the token-filtering registry change later:
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /f
Then reboot or restart WinRM.

My read​

You have now passed the “is Hyper‑V running?” test. This is now a permissions / remote admin token problem. I would apply LocalAccountTokenFilterPolicy=1, reboot HVSERVER, then test again with:
Get-Credential HVSERVER\Administrator
That should be the next big step forward.

 

[merrittr]

hmmm there doesnt seem to be an option for credentials Get-CimInstance

PS C:\WINDOWS\system32> $cred = Get-Credential
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:

PS C:\WINDOWS\system32> Get-CimInstance -ComputerName HVSERVER -Credential $cred -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem

Get-CimInstance : A parameter cannot be found that matches parameter name 'Credential'.
At line:1 char:40
+ Get-CimInstance -ComputerName HVSERVER -Credential $cred -Namespace r ...
+ ~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: ) [Get-CimInstance], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Management.Infrastructure.CimCmdlets.GetCimInstanceCommand

 

[ChatGPT]

You’re right, my mistake — Get-CimInstance does not accept -Credential directly in your PowerShell environment. For CIM you pass credentials through a CIM session instead.
Try this from the Windows 11 client, in Windows PowerShell as Administrator.

1. Confirm you are using Windows PowerShell​

Run:

$PSVersionTable.PSEdition
$PSVersionTable.PSVersion

Ideally this should say:

Desktop
5.1.x

If it says Core, you are in PowerShell 7. For this old Hyper‑V Server 2012 R2 management work, use Windows PowerShell 5.1, not PowerShell 7.

2. Create a CIM session with credentials​

Run:
$cred = Get-Credential HVSERVER\Administrator
Then:
$session = New-CimSession -ComputerName HVSERVER -Credential $cred
Now test Hyper‑V WMI through that session:
Get-CimInstance -CimSession $session -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem
If that works, try:
Get-CimInstance -CimSession $session -Namespace root\virtualization\v2 -ClassName Msvm_VirtualSystemManagementService

3. If New-CimSession fails in a workgroup setup​

Try this version:

$cred = Get-Credential HVSERVER\Administrator
$opt = New-CimSessionOption -Protocol Wsman
$session = New-CimSession -ComputerName HVSERVER -Credential $cred -SessionOption $opt -Authentication Negotiate

Then:
Get-CimInstance -CimSession $session -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem

4. If you still get Access Denied​

Then apply the remote local-admin token fix on HVSERVER:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
Then reboot HVSERVER, or run:

Restart-Service WinRM -Force
Restart-Service vmms -Force

Then retry from the Windows 11 client:

$cred = Get-Credential HVSERVER\Administrator
$session = New-CimSession -ComputerName HVSERVER -Credential $cred -Authentication Negotiate
Get-CimInstance -CimSession $session -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem

5. Also test with old WMI​

Since this is Hyper‑V Server 2012 R2, the old WMI cmdlet can be useful for testing:

$cred = Get-Credential HVSERVER\Administrator
Get-WmiObject -ComputerName HVSERVER -Credential $cred -Namespace root\virtualization\v2 -Class Msvm_ComputerSystem

If Get-WmiObject works but Get-CimInstance does not, the problem is specifically WinRM/CIM authentication, not Hyper‑V itself.

6. Clean up the CIM session afterwards​

Remove-CimSession $session

What this tells us​

If the CIM session works with HVSERVER\Administrator, then your Hyper‑V host permissions are fine and Hyper‑V Manager should be attempted using:

Connect as another user
HVSERVER\Administrator

If the CIM session still gives Access denied, the next thing to fix is definitely the remote local admin token filtering / local account permissions on HVSERVER.

 

[merrittr]

still geting this

 

[ChatGPT]

Hi merrittr — at this point the screenshot by itself does not tell us whether the remaining failure is permissions or the Windows 11 Home Hyper‑V Manager hack.
The server side is already proven good. The key next test is whether the Windows 11 client can query Hyper‑V through an authenticated CIM/WMI session.

1. Please run this exact test on the Windows 11 client​

Open Windows PowerShell as Administrator, not PowerShell 7, then run:

$cred = Get-Credential HVSERVER\Administrator
$session = New-CimSession -ComputerName HVSERVER -Credential $cred -Authentication Negotiate
Get-CimInstance -CimSession $session -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem

If that fails, also try:

$cred = Get-Credential HVSERVER\Administrator
Get-WmiObject -ComputerName HVSERVER -Credential $cred -Namespace root\virtualization\v2 -Class Msvm_ComputerSystem

Please post the text result of those two commands.

2. If those commands still say Access Denied​

On HVSERVER, run this once:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
Then reboot HVSERVER.
Important: this relaxes remote UAC filtering for local admin accounts. It is common for workgroup Hyper‑V management, but only do it on a trusted private LAN.
Undo command if needed:
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /f

3. If the CIM/WMI commands work but Hyper-V Manager still fails​

Then I would stop chasing server settings. That would strongly indicate the problem is the unsupported Windows 11 Home Hyper‑V Manager install.
Your host is working, WinRM is reachable, and VMMS/WMI are working locally. If the command-line remote query works but the GUI still says:
The operation is not supported.
then the Hyper‑V Manager snap-in is the bad part.

4. Workaround to recover the VMs without Hyper-V Manager​

Since your goal is recovery, use PowerShell from the server side.
On HVSERVER:
Get-VM
Then export one VM:
Export-VM -Name "VMNAME" -Path "D:\VMExports"
Or export all VMs:
Get-VM | Export-VM -Path "D:\VMExports"
Make sure D:\VMExports has enough free space first.

5. Best GUI workaround​

Use a supported management machine:

1. Use Windows 10/11 Pro, Enterprise, or a Windows Server machine.
2. Install Hyper‑V Management Tools normally.
3. Configure TrustedHosts/CredSSP as before.
4. Connect to HVSERVER.

Windows 11 Home with Hyper‑V Manager forced onto it may be the reason you are now stuck at “The operation is not supported.”

My current take​

You have already proved the Hyper‑V Server itself is healthy. The next split is:

CIM/WMI remote test fails = permissions / remote UAC issue
CIM/WMI remote test works = Hyper-V Manager on Windows 11 Home is the blocker

 

[merrittr]

this works


PS C:\WINDOWS\system32>
$cred = Get-Credential HVSERVER\Administrator
$session = New-CimSession -ComputerName HVSERVER -Credential $cred -Authentication Negotiate
Get-CimInstance -CimSession $session -Namespace root\virtualization\v2 -ClassName Msvm_ComputerSystem


Caption : Hosting Computer System
Description : Microsoft Hosting Computer System
ElementName : HVSERVER
InstanceID :
CommunicationStatus :
DetailedStatus :
HealthState : 5
InstallDate :
Name : HVSERVER
OperatingStatus :
OperationalStatus : {2}
PrimaryStatus :
Status : OK
StatusDescriptions : {OK}
AvailableRequestedStates :
EnabledDefault : 2
EnabledState : 2
OtherEnabledState :
RequestedState : 12
TimeOfLastStateChange :
TransitioningToState :
CreationClassName : Msvm_ComputerSystem
IdentifyingDescriptions :
NameFormat :
OtherIdentifyingInfo :
PrimaryOwnerContact :
PrimaryOwnerName :
Roles :
Dedicated :
OtherDedicatedDescriptions :
PowerManagementCapabilities :
ResetCapability : 1
EnhancedSessionModeState :
FailedOverReplicationType :
LastApplicationConsistentReplicationTime :
LastReplicationTime :
LastReplicationType :
LastSuccessfulBackupTime :
NumberOfNumaNodes : 1
OnTimeInMilliseconds :
ProcessID :
ReplicationHealth :
ReplicationMode :
ReplicationState :
TimeOfLastConfigurationChange :
PSComputerName : HVSERVER

 

[ChatGPT]

Great — that result is very important.
It proves:

WinRM works
Credentials work
Remote CIM/WMI works
root\virtualization\v2 works
HVSERVER is reachable
You are authorized when explicit HVSERVER\Administrator credentials are used

So the remaining failure is not the Hyper‑V service and probably not the server. It is almost certainly the Hyper‑V Manager GUI on the Windows 11 Home client, or the GUI is not using the same credentials that your CIM session is using.

Try launching Hyper-V Manager with network credentials​

On the Windows 11 client, open Command Prompt as Administrator and run:
runas /netonly /user:HVSERVER\Administrator "mmc virtmgmt.msc"
Enter the HVSERVER\Administrator password when prompted.
Then in Hyper‑V Manager:

1. Click Connect to Server.
2. Enter:

HVSERVER

1. Do not use the IP address.
2. Try connecting again.

/netonly is useful in workgroup setups because the program still runs locally as you, but network access uses the specified remote account.

Alternative: store the server credential​

On the Windows 11 client, run:
cmdkey /add:HVSERVER /user:HVSERVER\Administrator /pass
Then open Hyper‑V Manager normally and connect to:
HVSERVER
To remove it later:
cmdkey /delete:HVSERVER

Try Hyper-V PowerShell from the client​

Since CIM works, see whether the Hyper‑V PowerShell module works from the client:
Get-Module -ListAvailable Hyper-V
If it exists, run:

$cred = Get-Credential HVSERVER\Administrator
$session = New-CimSession -ComputerName HVSERVER -Credential $cred -Authentication Negotiate
Get-VM -CimSession $session

If that lists your VMs, you can manage/recover them without the GUI.

Export VMs from the client using the working session​

If Get-VM -CimSession $session works, export one VM like this:
Export-VM -CimSession $session -Name "VMNAME" -Path "D:\VMExports"
Or export all VMs:
Get-VM -CimSession $session | Export-VM -Path "D:\VMExports"
Important: the export path is on HVSERVER, not your Windows 11 laptop.

If PowerShell works but Hyper-V Manager still fails​

Then I would call it: the Windows 11 Home Hyper‑V Manager hack is the blocker.
At that point your best options are:

1. Use PowerShell with the working CIM session.
2. Use RDP into HVSERVER and run Get-VM, Export-VM, etc. locally.
3. Use a temporary Windows 10/11 Pro or Windows Server machine with official Hyper‑V management tools.
4. Copy the VM files manually if you only need the disks.

For recovery, simplest server-side export​

Since you can RDP into HVSERVER, this may be the cleanest route:
Get-VM
Then:
Export-VM -Name "VMNAME" -Path "D:\VMExports"
Or:
Get-VM | Export-VM -Path "D:\VMExports"

My recommendation​

First try:
runas /netonly /user:HVSERVER\Administrator "mmc virtmgmt.msc"
If that still gives “The operation is not supported”, stop fighting the GUI and use the working CIM/PowerShell route or a supported Pro/Server management machine. Your server-side Hyper‑V stack is working.

 

[merrittr]

Holy crap "runas /netonly /user:HVSERVER\Administrator "mmc virtmgmt.msc"" worked !

thanks you my robot overlord

 

[ChatGPT]

Excellent — great result, merrittr!
That confirms the server was fine and the problem was the Windows 11 client not presenting the right network credentials to Hyper‑V Manager.

Why that fixed it​

This command:
runas /netonly /user:HVSERVER\Administrator "mmc virtmgmt.msc"
runs Hyper‑V Manager locally as your normal Windows 11 user, but uses:
HVSERVER\Administrator
for network access to HVSERVER.
That is why the GUI now behaves like your working CIM test did.

Optional: make a shortcut​

You can create a desktop shortcut with this target:
runas /netonly /user:HVSERVER\Administrator "mmc virtmgmt.msc"
It will ask for the password each time.

Optional: store the credential instead​

If you do not want to type it every time, you can use:
cmdkey /add:HVSERVER /user:HVSERVER\Administrator /pass
Then open Hyper‑V Manager normally and connect to:
HVSERVER
To remove the saved credential later:
cmdkey /delete:HVSERVER

Before doing VM recovery​

Since you are recovering old VMs, I’d strongly suggest:

1. Export the VMs before modifying settings.
2. Avoid upgrading VM configuration versions until you are sure you no longer need to run them on Server 2012 R2.
3. Copy the exported folders to backup storage before importing them elsewhere.

Glad it’s working!