Do not use VRDP when it is not configured
Brought to you by:
markbaa
Without chencking if there is a vrdp-port defined in machines.conf, the configuration command '$vboxcommand modifyvm $uuid -vrdpport $vrdpport_config' is still executed.
As it turns out, VirtualBox translates the empty value into the default 3389; this can also be defined as unwanted behaviour.
Solved in rev 71