Installing SCVMM 2025 on Windows Server 2025

SCVMM 2025
Windows Server 2025

  1. Create a hypervscvmm domain user on AD.
User DC Host Hyper-V Host VMM Host
sj\hypervscvmm Domain Users / Administrators
  1. Convert an evaluation version to a retail version.
DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
DISM /online /Set-Edition:ServerDatacenter /ProductKey:D764K-2NDRG-47T6Q-P8T8W-YP6DF /AcceptEula
  1. Set date and timezone.
w32tm /config /manualpeerlist:"ntp.ntsc.ac.cn" /syncfromflags:manual /update
w32tm /query /status

Set-TimeZone -Id "China Standard Time" -PassThru
  1. Join a Domain sj.com by using sj\hypervscvmm.
Rename-Computer -NewName "VMMServer" -Restart
Add-Computer -DomainName sj.com -DomainCredential 'sj\hypervscvmm'

Add-LocalGroupMember -Group "Administrators" -Member 'sj\hypervscvmm'
Get-LocalGroupMember -Group "Administrators"

Restart-Computer
  1. Install Windows Assessment and Deployment Kit (ADK), Only need the Deployment Tools and Windows Preinstallation Environment options.


  1. Install SQL Server.

  1. Install SCVMM.

  1. Install Failover-Clustering and Hyper-V management tools.
Install-WindowsFeature -Name "RSAT-Hyper-V-Tools","RSAT-Clustering"

Troubleshooting

Issue: Hyper-V cannot be installed: The processor does not have required virtualization capabilities.

Solution

Set-VMProcessor -VMName 'VMMServer' -ExposeVirtualizationExtensions $true
Get-VMProcessor -VMName 'VMMServer' | fl

Issue: Hyper-V cannot be installed because virtualization support is not enabled in the BIOS.

Solution

bcdedit /set hypervisorlaunchtype auto
Restart-Computer

Issue: SCVMM 2025 Setup won't start after click Install option.

Solution

In conflict with the failover cluster role.

Remove-WindowsFeature -Name Failover-Clustering -IncludeManagementTools

Issue: Virtual-to-virtual conversion Error (10406).

Error (10406)
Virtual Machine Manager cannot contact 192.168.3.200 because the credentials for 192.168.3.200 are missing.

Solution

Modify vCenter properties on Infrastructure -> vCenter Servers, uncheck Communicate with VMware ESX hosts in secure mode.

Issue: VM boot failed, SCSI Disk (0.0) the signed image's hash is not allowed (DB).

Solution

  1. Disable secure boot.
  2. Maybe EFI boot incorrect, boot into HotPE to fix EFI partition.
    a) Use Diskgenius to format the EFI partition.
    b) Use NT6bootfix to fix the EFI partition.
Set-VMFirmware -VMName "Rocky" -EnableSecureBoot Off

Issue: The VMM Serivce SCVMMService fail to start after rename computer.

Solution

  1. Uninstall VMM server with "retain database".

  2. Rename the computer name and restart the computer.

  3. Rename the instance of SQL server by using the following commands.

    For a renamed computer that hosts a default instance of SQL Server, run the following procedures:

    sp_dropserver <old_name>;
    GO
    sp_addserver <new_name>, local;
    GO

    For a renamed computer that hosts a named instance of SQL Server, run the following procedures:

    sp_dropserver <old_name\instancename>;
    GO
    sp_addserver <new_name\instancename>, local;
    GO

  4. Restart the SQL service.

  5. Re-install the VMM server.