Link to home
Start Free TrialLog in
Avatar of mikehale1
mikehale1

asked on

Terminal Server License

I have a client with a SBS 2003 server and a second Windows 2000 Server, that they want to use as a Terminal Server.  I haver Term server setup on the 2000 box in Application mode.  Can someone please point in the right direction or let me know what I need to do for licensing and the best way to get this configured?  Do they need seperate CALs or will the SBS CALs work?

Thanks,
Rob
Avatar of Rob Williams
Rob Williams
Flag of Canada image

The terminal server itself requires one license but the SBS user CALs will cover the users. One of the many advantages of SBS.
ASKER CERTIFIED SOLUTION
Avatar of llefebure
llefebure

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mikehale1
mikehale1

ASKER

Thank you, I got the licensing part added and now when I try to connect as a user (other then Administrator), I get the message "The local policy of this system does not permit you to logon interactively"?
Since your domain controller is Windows 2003, I believe that you will be effected by it's new setup for allowing users into TS. Inside Active Directory Users & Computers, you will find one group called Remote Desktop Users. I believe you will have to add the user accounts you wish to access the TS into this group.

Of course you can work around this by looking through the local security policy on your TS. You can find the policy that specifies which users and groups can do an interactive logon, but you may as well do it the windows is pre-designed to do it if possible.
Make sure you users have been added. One method is using the terminal server configuration manager:

Administrative tools | Terminal Server Configuration | click on connections | right hand window right click on RDP-tcp and choose properties | Permissions | add the users
Thanks again for the posts, I tried both of these solutions and it still did not work.  I did some more searches and found the following MS KB that solved it - http://support.microsoft.com/kb/247989/en-us.

Thanks again for everyone's help,
Rob