Forum Discussion
SCVMM 2025 can't deploy Service Templates to Win2025 guest VMs.
I recently upgraded my SCVMM 2022 instance to 2025. I have a few Service Templates for lab/test purposes that expedite deployments such as installing the first DC in a new AD forest. I wanted to upgrade these Service Templates to work with Win2025 guest VMs so I built a new syspreped Windows Server 2025 image, and copied my "New Forest DC" Service Template so it could utilize a Win2025 guest. After a lot of troubleshooting, I found that SCVMM 2025 seems to fail to be able to configure a Win2025 guest. I originally thought there may be an issue with my Application Confg scripts that install the ADDS role and install the first DC. However, after removing those scripts and just trying to install Rolls and Features under the OS Configuration options, they appear to fail as well. Has anyone had any success deploying a Service Template with Win2025 guests VMs? Simple test to try to reproduce:
- Create a syspreped image .VHDK file with Windows Server 2025 (I've tested with both Gen2 and Gen1)
- Create a Service Template to deploy one guest VM Machine Tier.
- Add a few Windows Roles and Features (I'm adding ADDS, DNS, GPMC and the management tools) Example screenshot below.
- Deploy the service.
For me, the VM deploys properly but the Service Template eventually fails and no roles are installed as it hangs on the deploy applications task. (2nd screenshot below). This works just fine with a Windows Server 2022 image.
Can anyone else reproduce this? Did I miss something that is needed in the guest image?
Thanks in advance.
Yes, with your input, this was the fix:
- In the syspreped W2025 Server image, install WMIC: "DISM /Online /Add-Capability /CapabilityName:WMIC~~~~"
- Set [HKEY_LOCAL_MACHINE\SYSTEM\Setup] "Upgrade"=dword:00000001
Although I'm not sure #2 is needed as it may not have persisted through the Sysprep. In any event the service now deployed.
Thanks
4 Replies
WMIC is disabled after installation by a scheduled task \Microsoft\Windows\Servicing\OOBEFodSetup There are numerous articles how to prevent this or how to workaround this.
Hi Mark,
You need to enable the WMIC Optional Feature in your 2025 guest OS. It's disabled by default now. The VMAgent.iso installation used WMIC to install System Center Virtual Machine Guest Agent that gets deployed when using a SCVMM service template.
Regards,
Peter
Hi Mark,
Did you solve this by any chance? Looking at the debug logs it looks like the Msvm_KvpExchangeComponent is not set on the host so the heartbeat fails thus the deployment stops/hangs. This is correctly done when using a 2022 template for deployment.
xxx.local):root/virtualization/v2 WQL query select * from Msvm_KvpExchangeComponent where SystemName='80EE1416-1818-4FBE-8F33-8DC6E1E76612'"
"Message":"CarmineException [ex#3db] caught by IsGuestAgentHeartbeating Exception recieved when checking for heartbeat from vm guest
Regards,
Peter
Yes, with your input, this was the fix:
- In the syspreped W2025 Server image, install WMIC: "DISM /Online /Add-Capability /CapabilityName:WMIC~~~~"
- Set [HKEY_LOCAL_MACHINE\SYSTEM\Setup] "Upgrade"=dword:00000001
Although I'm not sure #2 is needed as it may not have persisted through the Sysprep. In any event the service now deployed.
Thanks