Terminal Servers acting as database server recommendations
Posted on 2012-08-14
I need a little feedback from some experts in the field of Terminal servers in general such as Citrix, and Remote Desktop services etc. We have a server up and running smoothly with applications such as office, Microsoft CRM, call manager applications in a "session based" desktop environment. My superiors are requesting I place software locally installed on the server in which currently work off of a client/server, or client to database connectivity to eliminate the need for the application server. The client is currently installed on TS and a separate application server. This request is in an effort to reduce the number of servers in use as well as eliminate issues the application is having. Also, the second request is to start installing applications on a "per-user" basis and not installed system wide for all users. Against better judgement, I continue to advise against it so the terminal server can continue to serve the function it was designed and deployed to do. I would love to hear from anyone out there that can give me maybe some "best practices" documents or point me to some hardened examples of why NOT to do this (install database software, run a database server on terminal server) so I can have a little to arm myself with.
There is a lot more in which is not detailed here such as the original design to use RemoteApp and session based connections based on user need, the use of App-V and Webapp but that's all too much to discuss. Thank you!