Reassociate HV as a perimeter network to VMM Server

Marek 101 Reputation points
2021-06-02T12:12:45.523+00:00

I have some Hyper-Vs (for example HV1, HV2, HV3) added as a perimeter network to VMM Server (ver. 10.19.2445.0) - all was ok.

For test from HV1 I deleted VMM agent, so from VMM Server HV1 isn't reacheable. After HV1 reboot I installed agent again - process was ok and I got new "SecurityFile.txt".

My next step was to reassociate HV1 with VMM Server, so I ran creator to add HV1 again: hostname is ok, serucity file nad password key too. In the next step I checked (I think that option should be checked" "Reassociate this host with this VMM environment".

So, reusult was not good, I got error like:

Error (2912)
An internal error has occurred trying to contact the '***' server: : .

WinRM: URL: [http://***:5985], Verb: [INVOKE], Method: [GetVersion], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]

No mapping between account names and security IDs (0x80070534)

Recommended Action
Check that WS-Management service is installed and running on server ''. For more information use the command "winrm helpmsg hresult". If '' is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.

So, how can I fix that problem? I will be greatfull for any tips.

Best regards,
Marek.

System Center Virtual Machine Manager
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Marek 101 Reputation points
    2021-06-15T07:19:21.527+00:00

    So, finally I found a solution. After reinstall the same version or install new version of VMM agent in HV, agent created new local account with admin privileges, so in VMM server in "run as account" have to change to the same account.

    Best regards,
    Marek.

    1 person found this answer helpful.
  2. Crystal-MSFT 43,721 Reputation points Microsoft Vendor
    2021-06-03T05:21:47.077+00:00

    @Marek , For the error, based on my research, this can occur if the account specified in the registry for the server setup value below does not exist as a valid account. This is likely due to the fact that it was removed in the past.
    HKLM\Software\Microsoft\Microsoft System Center Virtual Machine manager Server\Setup\VMMerviceAccount

    here is a link for the reference:
    https://social.technet.microsoft.com/Forums/en-US/7e66f834-bff2-43f1-99e4-d8b746d20f00/error-2912-when-adding-hyperv-host-within-vmm?forum=virtualmachingmgrhyperv

    We can check the account. to see if it can be fixed If there's any update, feel free to let us know.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. Marek 101 Reputation points
    2021-06-04T08:37:40.677+00:00

    Hello again.

    Thank you for reply. On the VMM Server in registry entry HKLM\Software\Microsoft\Microsoft System Center Virtual Machine manager Server\Setup\VMMerviceAccount I got user vmm_service and it is a AD user. That user is valid, password not expired. What do you mean about "valid accound"? What should I check on that accout yet?

    For first time, when I have added that HV to the VVM Server all was ok. That error shows after removed agent, installed again and in VMM server reassociated that HV again.

    Best regards,
    Marek.