When deploying machines using Instant Provisioning on Hyper-V host, only half of the machines are created successfully. The other half are created with "Access Denied" errors and never powered up. vWorkspace farm has 2 Connection Brokers. Everything works if specific broker is stopped or deleted from CB list.
Hyper-V host registry does not reflect both brokers, so Hyper-V Catalyst service is not accepting requests from unlister broker machines.
The issue may happen after new brokers were added after Hyper-V host into the vWorkspace Management console. Defect ID 210463 has been created for the issue.
Workaround: after adding a new broker into the farm, manually perform Hyper-V host Initialization.
Please make sure to remove "stuck" machines from Hyper-V Manager and from disk manually because they taking up space and unusable.