Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 130
  • Last Modified:

The basics of Terminal Server User Accounts

Hi there, I'm new Terminal Services and would like to setup a remote site, that contains around 6 users, with terminal services accounts. I don't think that the remote site in question warrants hosting its own server, however, they do also have 2 networked printers out there that they need to be connected to. The site is connected the main building via a 512k/512k ADSL connection. The server platform is Windows 2000 (Exchange 2000) with Windows XP on the remote site's desktop computers. I think that everything has been installed and configured correctly on the actual terminal server (os and app wise) but getting the remote clients to work and keeping the printing remote (i.e. at their site and not traversing the WAN link) is perplexing me. I would like to get it to the stage where, when we next upgrade the PC's located at the remote site, it's not such a major drama. I'm in the middle of setting up this site now, so any help in the right direction would be greatly appreciated.
0
lkleeman
Asked:
lkleeman
1 Solution
 
NzarthCommented:
Is the Terminal Server a DC?  How many Servers do you have?  Terminal Services should not be on a DC, however if you have to then make sure you lock down what they can do by having them in their own OU and attach a Group Policy to that OU.

When you say network printers do you mean that they are attached to the remote workstations? or they have their own NICs in them?

If they are attached to workstations then make sure the drivers have been installed on the Terminal Server.

Print jobs have to traverse the WAN link (no way around that :( ).  Also I do not think 512 ADSL is the way to go especially if there is alot of internet surfing, printing and general day to day work, not even including contention.

Hope that helps some.

0
 
lkleemanAuthor Commented:
Thanks for that dude, the printing issue is gonna give me dramas for sure... (maybe T/S isn't the way to go?)

The T/S is a Windows 2000 Member Server only and I only have 1 server - no users are currently configured for use with T/S.
The network printers have NIC's installed in them (with an IP Address allocated to them) and are plugged directly into the Switch (all located at the remote site)

What if I want to set someone up so that when their PC boots and they log on - they log straight into their Terminal Services profile? Is this when I need to install that T/S client software? (baring in mind that the user at the remote site is running Windows XP on their machine..)

I've been told to keep the T/S profile seperate to a users roaming profile.. but doesn't that double-up on the amount of administration? I wanted to keep it simple for the users and have them log into JUST the Terminal Server (like automatically, from first logon - I don't want the remote user to need to log on locally and then have to start up a "Remote Desktop Connection" to the T/S...)
Have I confused you yet???
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now