Creating a AOAG listener using CluAdmin... any pitfalls?

When using CluAdmin & not SSMS, there are some difference in the properties of the CAP resource object like

• Register All IP is 0
• Listener resource is offline

And it requires some manual steps to

1. Online
2. Add dependency to the AG resource
3. Specify port under SSMS
4. Dependency on is_conformant

Other than the manual process, I believe there is no shortfall, when using CLUadmin for the purpose.

It’s beneficial for the following reasons;

1. After creation the resource is offline, we can change the parameters before bringing it online & thus the required changes propagate much quickly through multiple AD’s. This is for multi-subnet clusters, where at time we are changing the TTL & RegAllIP.
2. In case of a multi-subnet scenario, the listener can still be brought up with limited resources (1 IP less). SSMS GUI wizard will not allow such.
3. Validations are done better.
4. Error messages returned by CLUadmin are much understandable as compared to those from SSMS.
5. Listener Resource name created has no pre-fix, which at times makes it easy to do changes via CLI.
6. Multiple listeners can be added.

Other than those stated above, are there any differences or pitfalls of creating an AOAG listener from CluAdmin & not by SSMS?

This link here says don’t do it. http://msdn.microsoft.com/en-us/library/ff929171.aspx#FCMrestrictions

While these two state that there is no other option but CLUadmin / PSH only.

http://msdn.microsoft.com/en-us/library/hh213080.aspx#CreateAddiitListener

http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/03/how-to-create-multiple-listeners-for-same-availability-group-goden-yao.aspx