Terminal Services is built into the Windows operating system so that users can access company data that exists in a remote location. Essentially, Terminal Services makes it so that most, if not all, of your company's data exists in one location that can be accessed by users wherever they are, saving Windows administrators from the headaches that come with managing dozens, hundreds or even thousands of fat client network endpoints floating around.
Built in conjunction with the IT Knowledge Exchange, this Terminal Services tutorial is designed to make data and server management easier for you and your staff. Learn how to troubleshoot Terminal Services, manage end users and roaming network endpoints, Terminal Services licensing and more.
Terminal Services tutorial
To start learning about Terminal Services management, simply click a link below to jump to a section.
What is IT Knowledge Exchange?
IT Knowledge Exchange (ITKE) is a community of IT pros that share and pool their knowledge. You can ask your own IT question or share your expertise by answering a question. Do you have an IT problem that's driving you crazy? Come ask your peers and colleagues on IT Knowledge Exchange. You can even start your own blog and earn some cash for posting regularly.
Visit the ITKE Community Blog to learn how to get IT answers
Terminal Services client hangs on connection
Sometimes rebooting your machine(s) can help you solve problems when trying to connect to Terminal Services. But is such a solution good enough for your network?
Windows 2003 Terminal Services sessions will not logoff
If your users are having issues with Terminal Services hanging as they try to log off, forcing a disconnect is one thing to try. But this isn't the preferred way to log users out of a Terminal Services session. So what is?
How to stop Terminal Services users from running programs
Helping users log off from Terminal Services is one thing, but what about preventing them from logging in in the first place? What if you're doing network maintenance and users continually attempt to sign in?
Terminal Services connection that can access the software which will be running on a Windows server
So you've got your remote connection set up and the server side of your Terminal Services environment is all set up. But, what about what you want your users to connect to? Do you need to make any special accommodations with the configurations of your users' destinations?
Microsoft Terminal Services and RPG socket programming
Is there a way of identifying a workstation on the Terminal Services Server from within an RPG socket program or at least from an AS/400?
Windows Server 2003 - Terminal Services & DC on same server
Is it possible to have one server that not only acts as a domain controller but as the Terminal Services licensing server? How powerful can a single server be?
Windows Server 2003 Terminal Services Licenses
Is there a way to expire old licenses after certain systems have gone extinct?
Installing Terminal Services to existing domain
If you install a second server to act as a terminal server, is there a way to run applications from the first server?
Windows Server 2003 Terminal Services
Are you looking for a file server for your small office? Find out how Terminal Services can handle your off-site file hosting and licensing concerns.
Terminal Services and Group Policy Objects in Windows XP
Using Group Policy Objects (GPOs) and organizational units (OU) can make management of your Terminal Services environment pretty tricky. Can your Group Policy precautions really help you better manage your TS network?
Terminal Services user CALs
It's imperative for IT admins to try and cut costs wherever possible these days, and Terminal Services licensing is certainly an area that is rarely kind to your budget.
GOT IT QUESTIONS? YOUR PEERS HAVE ANSWERS
Your peers and colleagues have faced the same or similar problems.
So ask your own question on the IT Knowledge Exchange community.