From: Sean M. <se...@co...> - 2003-07-10 19:59:05
|
I know that MS licenses TSCALs by device/machine and the machine's name is how the TS License server tracks them. rdesktop apparently stores licenses that it receives from the server in ~/.rdesktop/license.test While the homedirectory seems like a logical place to store these things from a Unix standpoint it seems to be in direct conflict with the way Windows is doing things. So, here is my question: Scenario 1) Presume this is a brand new network and the TSCALs are activated but no one has used any yet (just for simplicity). The server is using W2K SP3 license-style If user A logs in from workstation1 then the terminal server issues a license to "workstation1" which rdesktop stores in ~A/.rdesktop/license.test So now user B logs in from workstation2 and it works similarly to A. Now, lets say that the next day user A is at workstation2 and user B is at workstation1. What happens? Does W2K let them in because they have a valid license even though it isn't the one for the station they are on? Or does W2K label them invalid for presenting a license not matching their machine name? Scenario 2) You have a station where many users come throughout the day to log on, use it, and log off (lets call it "sharedpc"). Starting off, assume none of them have used rdesktop before so none of them have a ~/.rdesktop. The first user to log receives a license issued to "sharedpc" from W2K. What happens for the following users who log in? I'm fairly new to rdesktop but it strikes me that unless you have a 1:1 user:workstation environment where users don't move around you are going to encounter some troubles. Does anybody with more knowledge about how the licensing works behind the scenes have any ideas? Has anybody been in this situation before and have first hand knowledge? I'm hesitant to do testing to arrive at an answer if someone already knows the answer because I am worried that limited testing might not show issues over time (such as when licenses expire, etc) Thanks, Sean |