S.K. (11/19/2009)
For starters: the syspolicy_purge_history job -- needs to be updated for the virtual server name of the sql instance;if you install node A on the D:\program files\... path, when you add the B node to to the failover cluster, it will put the binaries automatically on the C:\program files\... path. So, when a failover occurs, that job will look for the SQLPS.exe file in the D:\ path, but it won't be there.
these are just a couple. There's also the licence key issue and the famous "Current SKU invalid" problem. When addding a cluster node and getting to the point where the licence key appears if you dont delete the key first and click next then go back and re type the key you get a message informing the current sku is invalid and setup shuts down.
I have also found problems when supplying the password details for the service accounts.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉