Changing properties of VMs takes 4-20 minutes

Hi,

I got a VMM server with 4 hosts in 1 cluster connected and currently only 19 VMs.

The VM running VMM is speced with 4GB of RAM and 2vCPUs.

When we update VMs (e.g. adding a ISO) the update takes 4-20+ minutes to complete. If we do the same change via FCM or Hyper-V Manager it's instant. I can't find any errors on the cluster, or on the VMM server and I can't see any resource congestion during the task execution.

Continuing with the example (using powershell):



Set-SCVirtualDVDDrive -VirtualDVDDrive $dvd -ISO $iso -link 
Used 2:08 to complete  
Set-SCVirtualDVDDrive -VirtualDVDDrive $dvd -NoMedia
Used 1:52 to complete

Not good times at all.

Doing the same via GUI:

Mount ISO: 4:23
unmount ISO: 4:10

Even worse!

So pulling out what the GUI acctualy does, is that it updates the VM aswell as the virtualdvddrive. 

# These first 2 lines, are the ones that's acctualy needed.
$VirtualDVDDrive = Get-SCVirtualDVDDrive -VMMServer localhost | where {$_.Name -eq "TestVM2"}
Set-SCVirtualDVDDrive -VirtualDVDDrive $VirtualDVDDrive -Bus 1 -LUN 0 -NoMedia -JobGroup 9151c946-4246-461d-923f-bd88ccfd80c4 

# Thes lines, are just basicly setting all the stuff that's already configured, again.. redundency and useless from what i can see (please do enlighten me if I'm wrong!). 
$VM = Get-SCVirtualMachine -VMMServer localhost -Name "TestVM2" -ID "e605ce8a-476e-4917-952b-b385da6754e0" | where {$_.VMHost.Name -eq "VMHOST03.domain.com"}
$OperatingSystem = Get-SCOperatingSystem -VMMServer localhost -ID "00000000-0000-0000-0000-000000000000" | where {$_.Name -eq "Unknown"} 
$UserRole = Get-SCUserRole -VMMServer localhost  -Name "Administrator" -ID "75700cd5-893e-4f68-ada7-50ef4668acc6"

$CPUType = Get-SCCPUType -VMMServer localhost | where {$_.Name -eq "3.60 GHz Xeon (2 MB L2 cache)"}

Set-SCVirtualMachine -VM $VM -Name "TestVM2" -Description "" -OperatingSystem $OperatingSystem -Owner "domain\adminmd" -UserRole $UserRole `
    -CPUCount 2 -MemoryMB 1024 -DynamicMemoryEnabled $true -DynamicMemoryMinimumMB 512 -DynamicMemoryMaximumMB 4096 `
    -DynamicMemoryBufferPercentage 20 -MemoryWeight 5000 -VirtualVideoAdapterEnabled $false -CPUExpectedUtilizationPercent 20 -DiskIops 0 `
    -CPUMaximumPercent 100 -CPUReserve 0 -NumaIsolationRequired $false -NetworkUtilizationMbps 0 -CPURelativeWeight 100 `
    -HighlyAvailable $true -HAVMPriority 2000 -DRProtectionRequired $false -NumLock $false -BootOrder "CD", "IdeHardDrive", "PxeBoot", "Floppy" `
    -CPULimitFunctionality $false -CPULimitForMigration $false -CPUType $CPUType -Tag "(none)" -QuotaPoint 1 `
    -JobGroup 9151c946-4246-461d-923f-bd88ccfd80c4 -RunAsynchronously -DelayStartSeconds 0 -BlockDynamicOptimization $false `
    -EnableOperatingSystemShutdown $true -EnableTimeSynchronization $true -EnableDataExchange $true -EnableHeartbeat $true -EnableBackup $true 

but, since it's running 1 extra Set-* command, and it's using ~twice the time, I'm thinking it might be related to some sort of timeout or such, that halt's the command (either as a pause or as a timeout) for ~90-120 seconds. From other environments I've been working with, this have not been an issue, changes like these have taken  ~10 seconds to complete (and I can live with that, even though I think that's kinda to slow to :-) ) 

Does anyone have any idea what's causing this? I've gone though the powershell logs, VMM logs and I can't find any errors or warnings at all.

Thanks!