AC is wrong again. What you are describing is basically normal when you are setting up apps on a TS. As to your shared RDP (which is not a good idea), are you on a domain? Because if so, you would have signle sign-on, and everyone would be using their own RDP anyway. Plus, the TS would need to recognize the authentication. Most of this stuff needs to be done on Windows Server 2012 or newer.
An instance consists of a database (in your instance Amazing Charts) where the databases and the SQL Server engine work together. This is an instance. You can only have one of any particular instance. You can have multiple, multiple instances. So, in any situation in an office, you could not have more than once instance. What they are likely talking about are multiple ACs on the TS. Again, this is wrong. You are connecting from a client without AC on it to an app on TS which is using the database on the server. Each app requires a license and can be accessed by a certain user. Think of it as having unique AC apps on each computer client. You can have hundreds, although some would be for the same user on different computers. So, AC, although they use SQL do not seem to have IT support that knows SQL Server. It is kind of like if you call Microsoft about Exchange or Active Directory, they will route your support to that department. AND, they will answer the phone.
Edit: You could consider each user's running of AC on the Remote Desktop an instance. So, I am not completely sure how AC is looking at it. And, applications have to be able to be licensed to an RDP. I would have to guess that AC is.
I think in your situation using Remote Apps, which is a feature of Remote Desktop server (aka in the past as Terminal Server). Each user could download the app from the server and just click on it which would open an RDP session with Amazing Charts only.
PLUS, this would solve the problem of using MACs with AC. Or iPad with AC.
Sandeep can correct everything I just said. LOL.
