An excellent TechNet-article explained how rules are evaluated in Windows Firewall, specifically in what order and which rules take precedence over others.
If for some reason the deployment of the VMWare vConverter agent fails, you can also copy the installer to the machine you wish to P2V and manually install it.
On the machine VMWare vConverter is installed, navigate to the location where it's installed (by default: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone), and look for the file VMware-Converter-Agent.exe. Copy over this file over to the target machine and run it to install the agent. Accept the defaults, including the TCP-port (unless your setup requires you to change it). Once finished, a service will have been installed and you will be able to connect to it using vConverter.
Found this article online about how vSphere virtualizes NUMA and how this is relevant to the configuration of vCPUs in your VMs:
In the event of migrating your old vCenter Server to a new version (or from Windows to the appliance), it may become necessary to first clear out old historical data. Not only will this speed up the migration process considerably, it will also prevent certain issues which may block the migration from completing successfully.
VMWare provided a KB with database scripts which allow you to selectively purge historical data and decreasing the database size: KB 2110031.
The Barracuda VPN Client does not work properly on macOS Mojave: after connecting the VPN, the UI crashes and restarting it immediately makes it crash again. The VPN tunnel itself does work, but other than manually killing the process (kill -9), it is not possible to terminate the tunnel (other than rebooting of course).
An updated version of the client, Barracuda VPN Client 220.127.116.11 for macOS is available which resolves these issues.