a180a41bba1d50822df23fff0099e90b86638b89vboxsyncTo be able to connect to Microsoft Windows 2000 Terminal Services (and
a180a41bba1d50822df23fff0099e90b86638b89vboxsyncprobably later versions), you'll need to deal with licensing. This is
a180a41bba1d50822df23fff0099e90b86638b89vboxsynccomplicated. This file is supposed to contain some information about
a180a41bba1d50822df23fff0099e90b86638b89vboxsynchow rdesktop works with Microsofts license systems.
a180a41bba1d50822df23fff0099e90b86638b89vboxsyncThere's a lot of information on the MS web site, for example,
a180a41bba1d50822df23fff0099e90b86638b89vboxsynchttp://support.microsoft.com/default.aspx?scid=kb;EN-US;287687.
a180a41bba1d50822df23fff0099e90b86638b89vboxsyncFrom the rdesktop mailing list:
a180a41bba1d50822df23fff0099e90b86638b89vboxsyncPeter Åstrand <astrand@cendio.se>, 2003-02-06
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> We are running rdesktop 1.2 on machine A and connects to a Windows 2000
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> Server (machine B). The W2K machine has 5 real licenses installed ("Windows
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> 2000 Terminal Services Client Access License", "Open" type). This can be
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> verifier by using "Terminal Services Licensing". The problem is that all
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> issued licenses have an expire-date. The expire date for the license issued
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> to A was reached today, and no more connections could be made until we
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> changed the client name (by using -n).
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> We also have another similiar systems, with Linux machine C and W2K server
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> D. This server has 200 licenses installed of the type "Select". On this
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> server, the issued licenses seems to be permanent: The expire date is set
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> to "-", and we have no problem with this system.
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> The question of course is why the first system issues license with
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> expiration date, while the second system issues permanent licenses.
a180a41bba1d50822df23fff0099e90b86638b89vboxsyncDarryn Capes-Davis, 2003-02-07
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> I have been through the problems and can tell you what is going
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> on. The main difference of Machine B (Server 1) and Machine D (Server
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> 2) is that from what I see Machine B has Service Pack 3 installed and
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> Machine D does not. You see in Service Pack 3 there was a change made
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> to TS Licencing in that Microsoft introduced a licence recovery
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> mechanism. To cut to the point (I don't know the details) rdesktop 1.2
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> with SAVE_LICENCE defined works fine. In the new lic method the
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> terminal server expects a valid licence to be presented to renew
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> it. Otherwise it just expires it - and a day later you will see it
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> actually gone (it does housekeeping once a day)! So if SAVE_LICENCE
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> code is not enabled then it just expires and you can't use the licence
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> until it cleans it away - and this is where a little gotcha is - if
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> you move from using an rdesktop without SAVE_LICENCE to one with
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> SAVE_LICENCE then it still won't recover an 'expired' licence. You
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> have to wait for the daily housekeeping to clean it up - this really
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> had me going for half a day or so! This is exactly what happened to
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> The Server pre Spk 3 has the old model where licences never expire. To
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> recover a licence that you never wanted to use again you have to call
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> the Microsoft Clearing House. That's why they introduced the new
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> method. And if you upgrade a Pre Spk3 server to Spk3 then the licences
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> granted still stay with the old method - only new licences granted
a180a41bba1d50822df23fff0099e90b86638b89vboxsync> will use the new expiry method.