Working with McAfee Platinum support this morning we managed to get to the bottom of this problem - once and for all!
I've also been able to confirm that this was sorted on a second from-scratch installation that was also exhibiting the same problem - to clarify, VMWare Workstation and Client Hyper-V, each with a Win2K8R2 Standard Guest.
If you are using a Named Instance of SQL - which in most "all on one" (Trial) installations will be the case as you will no doubt install SQL Express (which by default will install a Named Instance called "SQLExpress") you will *not* have the SQL Browser Agent started as this service is disabled by default.
Go into services.msc and set the SQL Browser service to start "Automatic" and then start it, then restart all the Foundstone services afterwards.
That will sort it out!
Just make sure you also have a hosts files entry for the hostname of the local machine so that it can resolve itself by hostname and then do a netstat -a and you'll see that port 3803 for the IP address of your machine will now be bound - which means the Scan Controller is started properly, and the Scan Engine will be able to connect!
One final point - SQL Express 2008 R2 *does* work, even though it's not (officially!) supported in the McAfee Installation guide.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.