Also,

9. On PrimaryNode, Windows event error 319 "No remote node currently available. All remote nodes appear offline or busy." Should probably be worded to also include the firewall, and or the Server Load balancing settings is not activated.
As this is something most developers would not do all the time, this can never be made too obvious...

10. When changing an application Load balancing setting to 'controlled by load balancing master node' warn the user when the Server Options dialog is not set to accept connections (flag = "This machine can act as a Web Application Server load balancing slave node").
Also after setting this it appears you need to restart the service. It would be good to tell the user this (just like SQL server has that helpful message when changing the TCP/IP).

If sent you an email message re. the codes. Once sorted I'll do some automated fail-over recovery testing.

Kind regards
Marco