Jan 07, 2017 On the 'License Server Activation' page, click the hyperlink to connect to the Terminal Server Activation and Licensing Web site. Under Select Option, click Activate a license server, and then click Next. How can I install a Windows Server 2003 Terminal Services licensing server? How do I install Windows Server 2003 Terminal Services licenses? How do I Activate. Posted: 16 Feb 04 (Edited 12 Nov 04) What you need: At least 1 Windows 2003 server, though at least 2 is suggested, one being License server, and one being the Terminal Server. Install License server on a WIndows 2003 Server (This can be the same server you are using for TS). Note: A Windows 2000 Server can be used for the licensing manager only if you have Per Device CALs, INSTEAD of Per User, NOT Mixed. Note: Although you can have a mixture of Device and User CALS, you cannot run both from the same server at the same time. Note: (added by mlichstein) he suggests the following: If you have 2003 Terminal servers, you MUST have a 2003 licensing server, regardless of the type of licenses. It is my understanding, after conversations with MS that this is not the case, and that if you have ONLY Per Device CALs, then you can use a Windows 2000 Server. It is only if you have User CALs that you MUST use Windows 2003. For this reason, MS suggest you don't use Windows 2000 if you have Windows 2003 Terminal Servers. Call Microsoft to activate your License Server, AND your CALs. Note: Apparently this can be done over the internet, but that's not how I did it! Also, (added by ChicagoTechNet) you can auto-activate licences. Change the configuration of the Terminal Server to use Per User, rather than the default Per Device. Note: To do this, click Start -> (All programs ->) Administrative Tools -> Terminal Service Configuration. Then click on Server Settings and change the Licencing value to "Per User". Note: IMPORTANT! If you install TS with Per User CALs, because the default is Per Device, you HAVE TO change to Per User, or 120 days later you will have problems. (added by ChicagoTechNet) 4. If users still can't get in, and get "You do not have permission to access this session", or something similar, then you need to do 2 things: a) Make sure the local security policy on the Terminal Server reflects that the required users have "Allow Log On Locally" rights, and "Allow log on through Terminal Services" rights. Note: When you open Local Security Policy under Administrative Tools, these two are found in Local Policies -> User Rights Assignment b) If still can't log in, then likely the server has trouble locating itself as licensing server, or the licensing server is hard to reach. In this case, follow the directions here: Note: The final Key (looks like a folder), which would be your server's name should contain NO data values, except (Default). If still no joy. Well, youneed to call MS because youmust have done something wrong!;) Some important points: 1. You only need current Windows Server 2003 license for Terminal Server, and not a separate license. You do need CALs for all active connections to the server. These are of two types: a) Per Device: This is the default configuration, and is the type of licnese that is temporary for 120 days when TS is first installed. These licenses allow a machine to connect to the server, and ANYONE using that machine can legally access the TS under its license, but a user using that machine cannot then go to their machine and access the TS under the same license! If they do this a new Per Device license will be issued if one is available. B) Per User: This (as described above) is not default, but means that once a user logs onto the TS, that same user account in AD can access the TS from ANY machine connected to the network, and this includes a terminal session via a link through some hotel on the other side of the world, if need be!;) 2. This is diferent than Windows 2000 which only has one type of CAL, which is equivalent to Per Device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2018
Categories |