I have to echo some of the sentiments here.
It's a great tool and it's potential is massive, but can be slow and inflexible.
Part of the issue for us - is that we're just as interested in it's use as a sandbox environment, as it's original backup verification use.
This role is mentioned in the documentation - but not in the GUI where it's still just a 'SureBackup'. This part really hasn't been developed to its potential.
I too have waited around for 20+ minutes for a successful ping test, sitting confused while running a constant ping from my local desktop in a separate command window.
Disabling the script/heartbeat etc checks still seems to require some verification which can take a long time when someone asks for a new environment - and if there's any issues (VM tools not loading correctly on one VM) it's right back to the beginning.
An override on all of this would be great - 'just bring them online, as quickly as possible'.
After much experimentation I've found the setup that works best for us:
Create a linux utility VM, with Apache Guacamole installed and configured
Create a Virtual Lab with a static IP mapping to the VM
Per sandbox request:
Clone all the requested sandbox VMs - with a DC, the aforementioned linux VM and any other required infrastructure.
Backup all the cloned VMs from the previous step
Create an Application Group with the VMs from the backup, and a SureBackup with the Application Lab + VirtualLab
Now you can RDP, puTTy, or VNC to the whole environment, for as long as you like without the backups interrupting and shutting it down, and without complex network configuration each time (as long as it starts successfully).