![]() |
|
|
|||||||
| Petri.co.il is happy to award auglan the title of Most Valuable Member !!! |
| Register | Calendar |
Search |
Today's Posts |
Mark Forums Read |
| Notices |
|
|
Windows 2003 Terminal Licensing Server not issuing licensesthis thread has 1 replies and has been viewed 13338 times
|
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||||||
|
||||||||
|
Hi,
Previously I had 3 Windows 2000 Terminal Servers with each one running their own Terminal Services Licensing Server on the same machine. These were all member servers in an NT domain. After upgrading to Windows 2003 AD, I realised that the licensing servers need to be installed on the domain controllers because I could no longer see the licensing servers after the domain upgrade. I installed Terminal Services Licensing on the Windows 2003 Domain Controller and re-activated all the TS CALs again. The CALs were registered as USER CALs in the Licensing server. However, the amount of CALs shown in the Terminal Services Licensing Manager does not decrease even when users connect. I am now worried because I believe either of these is happening: 1. The 3 Windows 2000 Terminal Servers only uses Device CALs and does not recognize user CALs like Windows 2003 TS. Therefore the users are now only using temporary CALs which will expire. If this is so, do I need to change all my CALs to device CALs instead on the Windows 2003 Terminal Licensing Server? Can this be done? Cos the purchased product is user CALs when I tried to re-activate the CALs. 2. I'm not too sure about this but user CALs do not decrease the count like device CALs when users connect? 3. The users are still using the cached licenses as the lease may not have expired yet? Additional question is previously when using Windows 2000 Terminal Licensing Servers, Windows 2000 clients do not need a license to use TS, but since now the licensing server has been shifted to Windows 2003, is this going to be different?? Cos that will mean all my windows 2000 clients will not be able to connect without a CAL anymore. I really don't know which one is the most probable cause. Really really appreciate any help on this. Many thanks in advance! Last edited by enkei; 7th January 2006 at 19:22.. |
|
#2
|
||||||||||
|
||||||||||
|
The easy way to manage TS license is to:
1. Install Win2k License server that serve Win2k TS. You can point the TS settings to the point to this server. * Install only Win 2000 TS license on this license server. 2. Install Win2003 License server License server that serve Win 2003 TS. You can point the TS settings to the point to this server. * Install only Win 2003 TS license on this license server. http://www.brianmadden.com/content/content.asp?id=154 http://support.microsoft.com/default.aspx/kb/823313 Regards, Yuval |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Migrate the NT4 Domain Controller to Windows 2003. | salara | Active Directory | 7 | 1st October 2007 16:51 |
| Terminal Server FAQ | yuval14 | Terminal Services | 0 | 16th March 2006 01:46 |
| licensing in server 2003 | roguecoolman | Windows Server 2000 / 2003 | 2 | 22nd November 2005 21:43 |
| Migrating Windows NT File and Print Server to Windows 2003 | fasahat | Windows Server 2000 / 2003 | 1 | 28th April 2005 18:47 |
| Useful add-ons for MS Project 2003 server | Ossian | Misc | 0 | 21st January 2004 14:07 |