Setting up TS - Licensing and Profile questions
- From: Mike Bailey <mbailey@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 10:37:44 -0400
I’m embarking on setting up TS for a few users to access an application from remote locations. We’re running Server 2003 SP1 and it’s the PDC as well. I have a few questions to start with:
As I understand, I’m currently allowed 2 connections which in the past have been used for remote administration only. We now wish to use Remote Desktop for a couple of users to run and accounting application. I will need to purchase 2 more licenses. I plan on purchasing Per User. I have made no configuration changes to the TS so far except to limit the idle session times and to log off disconnected and idle sessions after a period of time. Will I need to make any configuration changes for the Per User licenses? I’ve read in some of the posts here the mention of people needing to edit the Group Policy or the TS policy. Is this “required” to get TS running with more than the default 2 connections?
I see listed in my Administration Tools – Terminal Server Licensing. I’m assuming that this is where I will need to add the new CAL’s I purchase. When I select this though, I get the message “No Terminal Services Licensing server is available in the Domain.” Is this something that I just “set up” on my server or is this something else I must purchase?
Last, I read that it is advised to not store the TS profiles on your system drive as they can get quite large and can take away from system drive space. I’ve created a folder on the D: drive, shared it and have added the path to the remote users Terminal Services Profile in the Profile Path. In testing, I see that the profile is indeed created on the D: drive in their respective folder, but there is still a copy being created as well on the C: drive in the Documents and Settings folder. Why, and how can I stop this?
Thanks for any help! Mike .
- Prev by Date: Enable TLS for RDWC
- Next by Date: MDAC 2.8 on Windows 2003 Server
- Previous by thread: Enable TLS for RDWC
- Next by thread: MDAC 2.8 on Windows 2003 Server
- Index(es):
Relevant Pages
|