Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again.”

actually, after reboot member server, we are able to login but after sometimes we try to login showing error

Hello Mohammed,

Thank you for posting question on Microsoft Windows Forum.

Based on the provided error message which might indicate that while the VMM Console is installed correctly, the specific user account attempting to open the console has not been authorized within the SCVMM application itself, or there is a communication block between the client and the server preventing authentication.

The following are some suggestions you can try in an attempt to resolve this issue.

1.Verifying User Role Membership On (Server Side).

• Even if you are a Domain Admin or a Local Admin on the machine, you cannot access the VMM Console unless your account is explicitly added to a User Role inside VMM. Log in to your Primary SCVMM Server (the one that is working fine). Open the Virtual Machine Manager Console. Navigate to the Settings workspace. Expand Security and click on User Roles. Double-click the Administrator role (or the specific role you intend to use). Click the Members tab. Ensure the user account trying to log in from the remote console is listed here. If not, add it.

2.Checking the Target Server Name & Port.

• When you launch the remote console, you are prompted to enter the server name. Please make sure that you are using the Fully Qualified Domain Name (e.g., vmmserver.domain.com) rather than just the hostname or IP address and also ensure the port is set to 8100 (by default).

3.Checking Service Principal Names.

• If you are using a specific service account for the SCVMM Service (on the main server), authentication issues can arise if the SPN is missing. This often triggers "access denied" or role validation errors remotely. Open Command Prompt as Admin. Run this command setspn -L <VMM_Service_Account_Name> .Then verify that you see entries for SCVMM/<VMM_Server_FQDN> and SCVMM/<VMM_Server_NetBIOS>.

4.Verifying Version Consistency.

• Ensure the VMM Console version matches the VMM Server version exactly. Since you are on SCVMM 2025, verify that you did not accidentally install the SCVMM 2022 console on the remote servers. Check Control Panel > Programs and Features on both machines to verify the version numbers match.

Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same issue too.