Licensing PER USER and no restriction of user to one session

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Oscar (oku_at_xs4all.nl)
Date: 04/08/04

  • Next message: Jim H: "Re: Win 2k Server Licencing Problem" 
    Date: Thu, 8 Apr 2004 22:51:48 +0200

    In case that TS at a 2003 Server is configured as

    licensing PER USER
    restrict each user to one session : NO

    would only one TS CAL then be sufficient for 10 devices logging with the
    same user account ?

  • Next message: Jim H: "Re: Win 2k Server Licencing Problem"

    Relevant Pages

    • Re: terminal access
      ... we can lock down Windows Server ... 2003 Terminal Server by using Group Policy. ... Configure other settings you would like to restrict user permissions. ... Regarding closing the session completely, we can use the following group ...
      (microsoft.public.windows.server.sbs)
    • About suggestion#2
      ... so I googled restrict remote user to one session ... and found I can change the setting in tscc.msc under the server setting ...
      (microsoft.public.windows.server.general)
    • Re: You Do Not Have Access to Logon to this Session
      ... When trying to connect to a W2K server running Terminal Services with the Remote Administration, you may receive "You do not have access to logon to this Session" message. ... discovering the licensing server even after I had installed it. ...
      (microsoft.public.windows.terminal_services)
    • Windows 2003 mutiple session issues
      ... I am running a Windows 2003 AD server, ... Each server is set with the GPO to restrict each user to one session. ... Ive tested and tested a disconnect of a session and have reconnected to that ...
      (microsoft.public.windows.terminal_services)
    • Re: Can Telnet to port 3389 but cant get to logon screen
      ... I had plenty of licenses available in the Termal Server Licensing ... I did find some 1004 Event Warnings in the Server's event ... disconnected sessions for him, and I never see a session pop up ...
      (microsoft.public.win2000.termserv.clients)