Thats the output i´m getting inside the collector:

Remote Powershell from the mgmt-server to the Hyper-V-Host is working fine.

ntnxcollector.log:

2021-02-19 14:56:21,528  INFO:  No old dump exists
2021-02-19 14:56:42,531  ERROR:  HYPERV_PRECHECK_ERROR
 

There can be multiple reasons for this occurring.  @Arun Vijapur can you reach out

This is a known issue and will be fixed in the upcoming release. 

As a workaround: Create a "Domain Admins" (English) group in the OU wherever your localized Domain Administrator group is. Then add the user you plan to use into the newly created "Domain Admins" group. Update your group memberships on the Hyper-V Hosts and then collector should work fine.

By the way, it is recommended to use Hyper-V (Local) mode of connection unless your cluster host operating system is Windows Core addition. 

Thanks for your answer. What do you mean by “Update group memberships on the Hyper-V Hosts?” Do I need to add the created “Domain Admins” group to the Hyper-V admins?

Hello Erik,

The group memberships or changes to Active Directory are not immediately refreshed on the Windows host. For the host to pick up the newly added “Domain Admins” group, you got to manually refresh the group memberships if you want to use Collector immediately. 

Simple user (the username which is used to connect via Collector) logoff & login should refresh the group memberships. Here is a thread that talks about ways to refresh without user logoff or restart of the system:

http://woshub.com/how-to-refresh-ad-groups-membership-without-user-logoff/

Hope this helps, let me know if you have questions.

FYI, this issue is resolved in Collector 3.3 which was launched earlier this month.