Terminal server and database application
I was hoping someone could enlighten me on how TS works. I understand that if you have a TS running, say, Windows Server 2008 it gives one the advantage of certain network settings. Also, given terminal services, it can allow multiple connections from remote users.
This is where I get confused. In our LAN we have around eight computers (XP Pro) which are running an application connected to a SQL Server database on the server (the actual server with the domain controller, etc.). So multiple users can enter and read data and it is entered into the database.
I am thinking that the idea of the TS is that the remote users can use RDP or whatever to log into the TS and access this application. So, is this application on TS or on the actual network server? I understand how there can be multiple connections to TS, but how can more than one person access the application at one time?
This is where I get confused. In our LAN we have around eight computers (XP Pro) which are running an application connected to a SQL Server database on the server (the actual server with the domain controller, etc.). So multiple users can enter and read data and it is entered into the database.
I am thinking that the idea of the TS is that the remote users can use RDP or whatever to log into the TS and access this application. So, is this application on TS or on the actual network server? I understand how there can be multiple connections to TS, but how can more than one person access the application at one time?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Matt and mkuehnqoe,
I read your posts and they were very helpful especially the Microsoft article. It's a bit technical for me, but I think I understand it.
But, to simplify it for me, I want to make sure this is the right setup:
We have an Electronic Medical Record program on all client computers. Each staff member logs onto their computers, opens the EMR app and reads and writes to the central server database, in this case SQL Server 2005 Express.
My guess is if the staff were not using the computers, users from a remote site could RDP into the individual computers and use the program. Obviously, this would not be a good solution since it would be likely that the host users would be on the computers, and the remote connections would log them off.
So, all of the remote users that are licensed to use the TS would log into the Terminal Server. The EMR application would be on the TS connected to the database just like all of the other EMR applications. So each remote user could access this program. I guess where I am confused is how could each user use the program simultaneously? If one user were in one patient's chart how could another user be in another patient's chart? Something tells me it is because every user has his own session on TS as stated above, but I still am not sure if I am clear on this.
Thank you.
Bert
I read your posts and they were very helpful especially the Microsoft article. It's a bit technical for me, but I think I understand it.
But, to simplify it for me, I want to make sure this is the right setup:
We have an Electronic Medical Record program on all client computers. Each staff member logs onto their computers, opens the EMR app and reads and writes to the central server database, in this case SQL Server 2005 Express.
My guess is if the staff were not using the computers, users from a remote site could RDP into the individual computers and use the program. Obviously, this would not be a good solution since it would be likely that the host users would be on the computers, and the remote connections would log them off.
So, all of the remote users that are licensed to use the TS would log into the Terminal Server. The EMR application would be on the TS connected to the database just like all of the other EMR applications. So each remote user could access this program. I guess where I am confused is how could each user use the program simultaneously? If one user were in one patient's chart how could another user be in another patient's chart? Something tells me it is because every user has his own session on TS as stated above, but I still am not sure if I am clear on this.
Thank you.
Bert
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks. That's perfect. And, on a slightly different subject with the new Remote Desktop Services and 2008, it is nice to be able to run RDP without 3389 being open.
ASKER
Thanks guys. After forever, I finally understand TS. Well mostly. It is always easier if you actually have a terminal server and play with it. I hope I got the points right.
1. You need to install program via the add/remove programs or you can put the current user session in "install mode" first. See this article to learn more about install mode: http://support.microsoft.com/kb/252330. It mentions Windows 2000 but it's still valid for all current TS/RDS servers. The article has a typo on switching back to execute mode. It's supposed to be "change user /execute". Also note logging out the session automatically returns you back to execute mode. Only use install mode to install software. Don't stay in install mode normally.
2. In Active Directory User & Computers you can assign each user account home directory and terminal services profile. If you don't assign a terminal services profile it will attempt to load the user's roaming profile (if a location has been set). Otherwise all profiles will be local profiles. If you have more then one terminal server you'll definitely want roaming or terminal services profiles otherwise users will have different settings on each terminal server.
3. Printing is the same except for remote printing. This article goes in-depth in to how printing works in a terminal services environment: http://www.brianmadden.com/blogs/brianmadden/archive/2004/02/02/the-ultimate-guide-to-terminal-server-printing-design-and-configuration.aspx. The biggest pain is loading the necessary drivers for remote printers. If you like there are several 3rd party vendors that can make this much easier. A few are triCerat, ThinPrint, and UniPrint.
-Matt-
-Matt-