SQL AlwaysOn lessons learned
So I've seen this in a number of different scenarios now with additional colleagues and customers so figured I would pass it along. The issue causes various odd behavior to happen in a Citrix XenDesktop environment if you are using a SQL AlwaysOn cluster. If you setup the XenDesktop site using the installation GUI it creates the database and broker logins in SQL on the active node of the AlwaysOn availability group. The database gets synced to the non-active node, however
