About six months ago I wrote about the challenges of using the Always-On Availability Group Listeners with SSMS. At the time, I had presented three problems and only solutions for two of them. At this time, I am happy to announce that Microsoft has responded to our connect ticket and provided a current version work around as well as a promise for feature implementation in vNext.
The problem was that, with Availability Group Listeners (AGLs), you often needed to connect with the MultiSubnetFailover parameter, the ApplicationIntent parameter, or both. If you use SSMS for these connections, it has been very inconvenient. You would be required to perform several clicks and retype the parameters every time that you connected to the AGL. The best solution that I was able to present was to up vote the Microsoft connect ticket.
IMPORTANT NOTE: This will not work for Central Management Server, local registered servers only.
1. Open SSMS.
2. Browse to the Registered Servers by going to view > registered servers.
3. Right-click on Local Server Groups.
4. Select New Server Registration.
5. Fill out the connection information for your Availability Group Listener. Don’t forget to set your default database to be within the Availability Group, if applicable.
7. Close SSMS.
8. Open %APPDATA%\Microsoft\Microsoft SQL Server\$(Ver)\Tools\Shell\RegSrvr.xml (where $(Ver) is the SQL version such as 110, 120, 130 of your SSMS install).
9. Find the <RegisteredServers:Name> node with the name of the server you just created.
10. Edit the <RegisteredServers:ConnectionStringWithEncryptedPassword> node and add any other parameters you want to the end (such as MultiSubnetFailover=true).
11. Save the file.
12. Open SSMS.
13. Attempt to connect to your registered server by double-clicking.
ANOTHER IMPORTANT NOTE: If you ever update this registered server, you will need to repeat the XML edit steps because it will be overwritten.