Hi
ejdgr8,
From your screenshots and description, this looks like a
leftover SCVMM agent / trust issue after the SCVMM rebuild. When VMM is rebuilt, Hyper‑V hosts often still contain
old agent configuration or registry entries, which causes:
- Host stuck in “Pending”
- Manual agent install “Setup Wizard ended prematurely”
- Cluster status Unknown in VMM
Even if the agent was uninstalled,
residual files/registry keys often remain.
Below is the cleanest way to fix it.
Step 1 — Completely remove the old SCVMM agent remnants
Run the following on
each Hyper‑V host.
1. Stop the VMM agent service (if present)
Open
PowerShell as Administrator:
Stop-Service SCVMMAgent -Force
2. Remove the agent
msiexec /x {8B63C3D2-...}
If that fails, remove it from:
Control Panel → Programs → Microsoft System Center Virtual Machine Manager Agent
Step 2 — Delete leftover folders
Delete these folders if they exist:
Code:
C:\Program Files\Microsoft System Center\Virtual Machine Manager Agent
C:\ProgramData\VMMLogs
Step 3 — Clean registry entries
Open
regedit and remove:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Agent
Also check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VMM
Delete if present.
Step 4 — Reset WinRM (very important)
SCVMM uses
WinRM to push the agent.
Run:
winrm quickconfig
Then reset it:
winrm invoke Restore winrm/Config
Restart the service:
Restart-Service WinRM
Step 5 — Verify firewall rules
Make sure these are open on the Hyper‑V host:
Code:
5985 WinRM HTTP
5986 WinRM HTTPS
8100 VMM Agent
Quick test from SCVMM server:
winrm id -r:hyperv01
Step 6 — Add the host again from SCVMM
In
VMM Console:
Code:
Fabric
→ Servers
→ Add Resources
→ Hyper‑V Hosts and Clusters
Use
Run As account with local admin rights on the Hyper‑V host.
VMM will
push the agent automatically.
Important check (very common after VMM rebuild)
Make sure the
SCVMM service account is:
- Local Administrator on Hyper‑V hosts
- Member of Hyper‑V Administrators
Example:
net localgroup administrators DOMAIN\VMMServiceAccount /add
If the issue still happens
Please check this log on the Hyper‑V host:
C:\ProgramData\VMMLogs\scvmmagent.log
or
C:\Windows\Temp\VMM*.log
The
exact error in that log will show why the agent install fails.
One more quick question:
- What SCVMM version did you rebuild? (2019 / 2022?)
- What Windows Server version are the Hyper‑V hosts?
- Is this a Hyper‑V cluster or standalone hosts?
Those details will help narrow it down quickly.
—
Regards,
ChatGPT
WindowsForum Support Assistant
