locked
Terminal service license problem RRS feed

  • 問題

  • Dear Technical support,

    I have 2 Servers which are:

    Server A: Windows 2003 enterprise R2 + Domain controller + Terminal service licensing

    Server B : Windows 2003 standard + terminal server

    Last year i purchased 5 TS CAL and i activated and everything is OK.

    Last week i purchased an additional 10 TS licenses and added to Server A and it's OK.

    When i tested it,  it only enables 5 connections from client PC  which was the original amount of licenses.

    Not sure what happened. It does not detect the extra licenses.

    I run lsview,exe and i am making sure that the server B is pointing to the right server which Server A for license.

    We are running Microsoft Dynamic NAV in server B and client PC connects to server B to access NAV via TS.

    Does software application (NAVISION) matter?

    Please help

    I hope i do not need to re-install NAV.

    Thank you

    Regards, c00kie
    2009年1月25日 上午 11:41

解答

  • Dear Customer,

     

    Thanks for posting here!

     

    According to the OS version of your terminal server, there are several possible causes for this behavior:

     

    Scenario 1: If your terminal server is installed on Windows Server 2003

    ------------------------------------

    In the past, the TS CAL requirement was waived if the device accessing the terminal server was running the same or later version of the equivalent desktop operating system. For example, a device running Windows 2000 Professional could access a Windows 2000 terminal server without needing an associated TS CAL. With the release of Windows Server 2003, this is no longer the case.

     

    If your terminal server is installed on Windows Server 2003, you will need to separate Windows Server 2003 TS CALs for Windows 2000 and XP Professional computers.

     

    To assist customers with this change, Microsoft has a transition plan in place.

     

    For more information about the transition plan, please refer to the following resource:

     

    Microsoft Terminal Server Licensing Changes and Transition Plan

    http://download.microsoft.com/download/2/f/f/2ff38f3e-033d-47e6-948b-8a7634590be6/ts_transition.doc

     

    Windows Server 2003 Terminal Server Licensing

    http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx

     

    Every Windows XP Professional license purchased or owned before April 24, 2003, is eligible for a complimentary Windows Server 2003 TS CAL. Note that the Windows XP Professional license does not have to be installed as of April 24, 2003, to qualify. The product must simply be owned by that date. Also, you may need to setup a Terminal Services Licensing Server to control the TS CALs.

     

    You may refer to the following resource to find out the answers to commonly asked questions about the Terminal Server CAL transition for Windows Server 2003. Select a question from the list to show the answer or view answers to all the questions by selecting the checkbox.

     

    Terminal Server CAL Transition Plan: Frequently Asked Questions

    http://www.microsoft.com/windowsserver2003/howtobuy/licensing/tscaltransfaq.mspx

     

    Scenario 2: If your TS license mode is set to Per User

    ------------------------------

    The license mode of the Terminal Server, and the type of Terminal Server CALs installed on the License Server must match for client machines to use permanent licenses. If your terminal server is on Windows Server 2003 and the Licensing Mode in Terminal Services is set to Per Device, Windows XP client will get temporary TS CAL as the Terminal Server Licensing server only has Per User CALS.

     

    To correct this problem, change the Licensing Mode in Terminal Services Configuration to Per User. To do this, follow these steps:

     

    1. Click Start, point to Administrative Tools, and then click Terminal Services Configuration.

    2. Click Server Settings, and then double-click Licensing Mode.

    3. Change the Licensing Mode to Per User, and then click OK. Please check whether the license mode is configured properly.

     

    822134 The Function of Terminal Server CALs in Windows Server 2003

    http://support.microsoft.com/?id=822134

     

    Scenario 3:

    --------------

    When the terminal server licensing is configured in Per Device mode, the first time a device connects to a terminal server, it is issued a temporary license, which is valid for 90 days. This behaviour is by design so that devices do not accidentally use up a CAL when mistakenly connecting to a terminal server. The next time the client logs on to a terminal server, it is allocated a permanent Terminal Server CAL token, which the device stores for later connections. Please take a new Windows XP client and logs on to the terminal server twice by Remote Desktop to see whether this problem continues.

     

    If this problem continues, let us perform the following tests to analyse this problem:

     

    1. Follow the steps in the following Microsoft Knowledge Base article to correct registry keys:

     

    323597 Windows XP Clients Cannot Connect to a Windows 2000 Terminal Services

    http://support.microsoft.com/?id=323597

     

    2. Logon to the Terminal Server by remote desktop. You should get a temporary TS CAL now.

    3. Log off.

    4. Logon to the Terminal Server by remote desktop again. Now you should get a permanent TS CAL .

     

    Hope the information above is helpful!

     

    Sincerely,

     

    Tom Zhang

    2009年1月26日 上午 10:33
    版主

所有回覆

  • Dear Customer,

     

    Thanks for posting here!

     

    According to the OS version of your terminal server, there are several possible causes for this behavior:

     

    Scenario 1: If your terminal server is installed on Windows Server 2003

    ------------------------------------

    In the past, the TS CAL requirement was waived if the device accessing the terminal server was running the same or later version of the equivalent desktop operating system. For example, a device running Windows 2000 Professional could access a Windows 2000 terminal server without needing an associated TS CAL. With the release of Windows Server 2003, this is no longer the case.

     

    If your terminal server is installed on Windows Server 2003, you will need to separate Windows Server 2003 TS CALs for Windows 2000 and XP Professional computers.

     

    To assist customers with this change, Microsoft has a transition plan in place.

     

    For more information about the transition plan, please refer to the following resource:

     

    Microsoft Terminal Server Licensing Changes and Transition Plan

    http://download.microsoft.com/download/2/f/f/2ff38f3e-033d-47e6-948b-8a7634590be6/ts_transition.doc

     

    Windows Server 2003 Terminal Server Licensing

    http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx

     

    Every Windows XP Professional license purchased or owned before April 24, 2003, is eligible for a complimentary Windows Server 2003 TS CAL. Note that the Windows XP Professional license does not have to be installed as of April 24, 2003, to qualify. The product must simply be owned by that date. Also, you may need to setup a Terminal Services Licensing Server to control the TS CALs.

     

    You may refer to the following resource to find out the answers to commonly asked questions about the Terminal Server CAL transition for Windows Server 2003. Select a question from the list to show the answer or view answers to all the questions by selecting the checkbox.

     

    Terminal Server CAL Transition Plan: Frequently Asked Questions

    http://www.microsoft.com/windowsserver2003/howtobuy/licensing/tscaltransfaq.mspx

     

    Scenario 2: If your TS license mode is set to Per User

    ------------------------------

    The license mode of the Terminal Server, and the type of Terminal Server CALs installed on the License Server must match for client machines to use permanent licenses. If your terminal server is on Windows Server 2003 and the Licensing Mode in Terminal Services is set to Per Device, Windows XP client will get temporary TS CAL as the Terminal Server Licensing server only has Per User CALS.

     

    To correct this problem, change the Licensing Mode in Terminal Services Configuration to Per User. To do this, follow these steps:

     

    1. Click Start, point to Administrative Tools, and then click Terminal Services Configuration.

    2. Click Server Settings, and then double-click Licensing Mode.

    3. Change the Licensing Mode to Per User, and then click OK. Please check whether the license mode is configured properly.

     

    822134 The Function of Terminal Server CALs in Windows Server 2003

    http://support.microsoft.com/?id=822134

     

    Scenario 3:

    --------------

    When the terminal server licensing is configured in Per Device mode, the first time a device connects to a terminal server, it is issued a temporary license, which is valid for 90 days. This behaviour is by design so that devices do not accidentally use up a CAL when mistakenly connecting to a terminal server. The next time the client logs on to a terminal server, it is allocated a permanent Terminal Server CAL token, which the device stores for later connections. Please take a new Windows XP client and logs on to the terminal server twice by Remote Desktop to see whether this problem continues.

     

    If this problem continues, let us perform the following tests to analyse this problem:

     

    1. Follow the steps in the following Microsoft Knowledge Base article to correct registry keys:

     

    323597 Windows XP Clients Cannot Connect to a Windows 2000 Terminal Services

    http://support.microsoft.com/?id=323597

     

    2. Logon to the Terminal Server by remote desktop. You should get a temporary TS CAL now.

    3. Log off.

    4. Logon to the Terminal Server by remote desktop again. Now you should get a permanent TS CAL .

     

    Hope the information above is helpful!

     

    Sincerely,

     

    Tom Zhang

    2009年1月26日 上午 10:33
    版主
  • Dear Customer,

    Based on my research, this issue is related to Nortel Callpilot. I recommend you contact Nortel Callpilot for more dedicated assistance. I believe that you will get detailed and informative suggestions there.

    Thank you for your understanding.

    Sincerely,
    Tom Zhang

    2009年1月27日 上午 10:13
    版主