Windows 10: Weird logon issue while using a VM in Hyper-V

Hello forum, I have home lab running in Hyper-V which consists of a couple of Domain Controllers and several clients, now when attempting to log on as any regular end-user on one the clients, I get a notification which says; to sign in remotely you need the rights to sign through Remote Desktop Service but if I go ahead and sign in as the Admin and log out immediately and then sign in as the user it works flawlessly. Also, I added the OU groups and even the users individually to the Remote Desktop Users and Remote management groups to make sure the accounts have the proper permission but still

:)

 

Account failed logon 4625 on VM guest when clicking the entry of VM guest on failover cluster Manager on VM Host

Issue:

We found a multiple failed logon events on VM guest (evert ID 4625) with account (the account you logon on VM host) when we clicking the entry of VM guest on failover cluster manager console on VM host with Integration servers (Data Exchange) is enabled.



How to reproduce:

1. Check the “Data Exchange” is enabled on a VM guest (Enabled by default, right?)
2. Open Failover Cluster Manager Console on VM host.
3. Click the VM guest entry
4. Then you may found multiple failed logon events on that VM guest.

Reference:

Hyper-V Integration Services | Microsoft Docs



Question:

1. Does the multiple failed logons are normal or necessary?
2. If the failed logons are normal and necessary to be happened and the “Data exchange” function is good to be enabled to gather data from VM guest, any recommendation for us to correct or avoid these failed logon?

Please advise.



Constrain:

We have no chance to use same account and password on VM hosts and VM guests (because all account are managed by password management) and the Audit Policy of Audit Credential Validation must be enabled.

 

Unassign Hyper V VM with deleted User account

Hyper V is not assigned based on user accounts.

Hyper V is a server feature that allows you to create VMs but they are not assigned to users.

Can you post a screenshot of what you are referring to?

And then share on a cloud drive and post link here for me to look at?

Also what are the steps you are doing to "assign" the VM to another User?

 

Move Hyper-V VM Without Reactivating?

According to this (How do I avoid needing to activate Windows when I move a VM? [Hyper-V]) link it is possible to move a Hyper V VM to a new host without having to reactivate the guest OS by exporting
it and importing it. Are there any additional steps I should know about or is it as simple as find the export and then import (on the new host) options/buttons?