r/sysadmin 8d ago

Can't get SCVMM 2025 to convert vmware VM

Tried anything and everything. I cannot get SCVMM to convert a VM from vmware v8 cluster to Hyper-V. Fully up to date SCVMM 2025 (10.25.1439.0) and esxi 8.03

It always fails at 33% with the error:

Error (2901)

The operation did not complete successfully because of a parameter or call sequence that is not valid.

The parameter is incorrect (0x80070057)

Recommended Action

Ensure that the parameters are valid, and then try the operation again.

8 Upvotes

15 comments sorted by

11

u/Negative-Cook-5958 8d ago

Use Veeam for the migration, I never had luck with SCVMMs conversion feature.

6

u/Maverick0 8d ago

Second this. Even the free / eval version of Veeam will do it just fine, but only with 10 VMs at a time max.

-2

u/TheThird78 8d ago

Was hoping for an alternate path. Our Veeam infrastructure is pretty bogged down overnight when our migration maintenance windows will need to be.
Tried WAC with some success, but it was hit or miss - not 100% success rate.

4

u/Maverick0 8d ago

Would spinning up a separate instance of Veeam on another host be an option just for this purpose? Once you're done migrating, you can just get rid of it as well.

3

u/Magic_Neil 8d ago

Same. WAC is fast but its success rate for me was probably 20%.. multiple VMs, missing disks. SCVMM seemed to work but it kept trying to convert UEFI to Gen1 BIOS VMs. Starwind is working wonderfully but only 500mbps.

2

u/Stonewalled9999 8d ago

Bruh, get a PC with a fast NMVE drive and 16 or more GB RAM put 2022 server Eval and rock it on that dedicated box.

u/Fighter_M 7h ago

Tried WAC with some success, but it was hit or miss - not 100% success rate.

WAC Converter does a pretty lousy job. Skip it and stick with one of the purpose-built V2V tools out there, as they’ve been doing this for years, and it shows.

2

u/crisscar 8d ago

It took a few tries and I had to install a bunch of vcredist.exe libraries, but try it with WAC. I moved a DC from vCenter 6 to Hyper-V in a few hours. It was a lot smoother than I anticipated it would be.

2

u/snafu_44 8d ago

I had to copy the script the convert wizard generated and add a few things to get it to go. Specifically "-VhdType DynamicallyExpanding -VhdFormat VHDX" for Gen2 vms. (then paste the script into an admin powershell prompt on the vmm server). Also you need to uninstall vmware tools and remove any snapshots from the source vm ( a huge pita)

1

u/archaic_android 5d ago

Vmtools has been a pain for us as well. We actually wrote a script to take care of it after the fact if it was missed during the migration.

2

u/BlackV I have opnions 8d ago

use your backup product to do this, any good one will do it natively and likely much quicker

1

u/WillVH52 Sr. Sysadmin 7d ago edited 7d ago

Agreed never used anything apart from Veeam B&R to migrate VMs to Azure/Hyper-V/new hardware.

2

u/Sunstealer73 5d ago

I've seen this when you have vCenter added to SCVMM. You have to go to each VMW host and configure the credentials there too. Make sure CBT is turned off, make sure SCVMM is showing the correct OS, then do a Refresh VM on it right before you try the migration again.

1

u/archaic_android 5d ago

Have you checked out the logs in c:\programdata\vmmlogs? It often times has more detail than the jobs output. We’ve migrated an entire VMware infrastructure using scvmm 2022 and for some trouble machines we did use veeam, or starwind, but it was very rare.