[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

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
0
mikehale1
Asked:
mikehale1
  • 2
  • 2
  • 2
1 Solution
 
Rob WilliamsCommented:
The terminal server itself requires one license but the SBS user CALs will cover the users. One of the many advantages of SBS.
0
 
llefebureCommented:
If you connect to a Windows 2000 Terminal server from either 2000 or XP Pro, you do not need to purchase any CALs for the Terminal server portion. Those just come with the OS. If you wish to connect Win95/98/ME/NT or XP Home machines to the 2000 Terminal server, then those devices will need TS CALs.

As for the SBS side, the rules are the same as if it was a desktop. If you are running device based licensing, then the TS is another device on your network. If you have user CALs for the users that are using the TS, then they already have the CALs needed to connect to the SBS server. If the TS is for users that don't normally connect to the SBS server locally, then they will need CALs just as if they were locally.

Even if you have a 2000 TS and don't really need any CALs, you'll still want to configure your SBS server to be the Terminal Services Licensing Server. Go into add/remove programs, windows components, and add this one piece. Just go through the activation wizard, but you won't be adding any CALs to it. When you open it up, it will tell you the number of CALs that it has issued, probably all of which will be the 2000/XP Pro ones. When you're in there, you'll see how they get broken down into each specific section for temp licenses, built-in licenses, and purchased licenses.
0
 
mikehale1Author Commented:
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"?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
llefebureCommented:
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.
0
 
Rob WilliamsCommented:
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
0
 
mikehale1Author Commented:
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
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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