Windows Licensing and Win4Lin Terminal Servers? 63
miguelk asks: "I'm helping a company (in Brazil) legalize their desktop operating system licenses by migrating to Linux on the desktop. WINE was tried but unfortunately did not work out for this particular case, so the idea is to install a Linux server with Win4Lin Terminal Server for 5 users, since the company has 5 Windows98 licenses to use for this purpose. All of the other 50+ desktops would be running Linux and would access these 5 licenses as needed, whenever they use a legacy Windows application. I have a question about the legal aspect of using the Windows desktop remotely. From all I have researched so far, this is legal since the actual Windows code will be installed on only one computer and will not be loaded in RAM on any other computer. I see it as equivalent to having 5 PCs on a desk and users walking up and using whatever PC happens to be available. I suspect that a direct, unprepared question to Microsoft is not a good idea, so I want to prepare first. Can anybody comment on this solution or share their experiences?"
From the FAQ: (Score:3, Informative)
How many Windows licenses do I need to have?
One Win 9x/ME license per active user
Now, defining "active user" is the fun part, isn't it? It sounds like what you're trying to do is within the bounds here, but then again, IANAL. If the MS EULA is hazy for VNC [slashdot.org] then who the hell knows.
Looks like it's so far so good for netraverse tho.
Re:From the FAQ: (Score:5, Funny)
Tight usage of industry abbreviations, 10 yard penalty. 1st down.
Rather than address the original question, (Score:3, Funny)
You are actively searching for a way to get the machines at your company running in a productive manner on any OS in any means other than running any legitimately licensed Windows OS.
This choice is driven purely by financial decisions.
You are jumping through hoops in order to run the programs you want to run, that happen to run on Windows nicely, but don't want to (can't) purchase enough licenses of Windows OS's for all the machines.
You don't particularly dislike Windows, you just have already decided not to buy any more copies at $300 apiece.
The economy in the country in which you live and operate is so shattered that buying licenses at the current price is impossible. Much like the situation in China(?) we read about here the other day (no I am not going to look it up.)
Microsoft recognized the issue in China and is offering massive discounts over there if they will go legit. My suggestion - figure out what that price is, convert it to your local currency to determine a price per license, go out and actually buy a NEW legit single copy/license (pay $300 or $500 or whatever it costs for that particular version) and then do the math : however many licenses that would have given you in China, use that many.
If it helps your consience any, use an older (unsupported) OS like Win95 or NT4.0 on those machines, figure that the discounted pricing gets you older outmoded warez - but in a round-about way you did pay your fair share.
If the SPA hassles you, invite them for an on-site inspection and tell the local drug lords that they are DEA agents. That will pretty much keep you off the SPA mailing lists.
If anybody else give you any grief, tell 'em I said it was ok.
BillG
Re:Rather than address the original question, (Score:1)
Or (Score:4, Insightful)
Or just buy a bunch of seats of older licenses (if you can't afford the OS, odds are the hardware is a little old - no offense) from eBay - for the amount of hassle per seat just buy a legit license for each one and be done with it. I went to eBay and did a search on 'windows license' and found several under $10.
Lets face it, if you could just run a legit copy of NT4.0 or Win9x on each machine you would be a LOT happier.
Or at least that is what I got from your question.
Re:From the FAQ: (Score:2, Informative)
Are you kidding? (Score:2)
They don't even know how their own product is used legally? That's kinda scary. Honestly tho, I wish you the best of luck!
Raw WINE? (Score:3, Interesting)
So I wonder if raw WINE use is less robust than, say, something like Lindows?
[Don't quote me, but IIRC from a few years ago, "remote control by variable different people" of any MS software seems like it is addressed in their licenses in a prohibitive fashion...unless they all have a license:)]
As far as i know.,... (Score:1)
Re:As far as i know.,... (Score:2)
Also, recruiters don't give a shit about software licensing. They are there for the warm bodies.
don't be an idiot (Score:3, Insightful)
Most OEM versions of 98 were tied to the PC, meaning you couldn't legally move them to another PC. This is fixed recently, but the older licences, I'm sure, still hold.
Re:don't be an idiot (Score:2)
Please note that I said "in some countries" so seeking advice as suggested above might be a good thing. Seeking advice from Microsoft might not, because even though courts in those countries have ruled
sounds like bad advice (Score:3, Insightful)
The MS licensing rep isn't going to give any legally binding commitments, he is just going to try to talk people into as many licenses as they can afford by applying just the right amount of arm twisting.
Most OEM versions of 98 were tied to the PC, meaning you couldn't legally move them to another PC.
Companies write all sorts of restrictions into their licenses that wouldn't hold up in court.
Re:don't be an idiot (Score:2)
That would make sense... except these are the same people who said "Win95 doesn't have DOS". My own PERSONAL experience was having them tell Best Buy sales people when Win95 came out to sell the customer Win95, not matter what they needed. "If they need RAM, sell them Win95. If they need more CPU, sell them Win95." Of course, I was a tech, and MS only talked to the floor people..
No, I would
Read the EULA (Score:2, Informative)
Re:Read the EULA (Score:4, Funny)
I have my own EULA that all software companied implicitly agree to bt runnin on one of my compuers, it stated the following:
In excange for money, and by use on this computer, the software company agrees to, and warrants, the folowing:
This agreement superceses all previsous agreements.
This software is sold, and not leased or licensed.
This software is a product and is fit for the use it it advertised for.
This agreement does not superved any copy-rights tha software company may have on this product.
The software can be resold, transfered or duplicate under the same laws and regulations that govern the sale, transfer and duplication of published books.
So there, my EULA trumps their EULA because they agreed to it by running on my computer.
If a 'click though' EULA is good for them, it's better for me!
HA!
Re:Read the EULA (Score:3, Funny)
Re:Read the EULA (Score:3, Interesting)
I never, "received or agreed" to their EULA before purchase.
What's good for the one party, is good for all parties.
If they feel that their EULA is valid because I implicitly agreed to it by clicking a mouse*, then I my EULA is vaild because their software installed itself on my computer.
*there is no record, admissable in court, that I ever clicked or did not-click throught their EULA. In fact, I don't remember ever needing to do anything of the sort. (hint hint).
Re:Read the EULA (Score:2)
You may hold a different opinion, but opinons don't count in issues like this.
Re:Read the EULA (Score:4, Interesting)
I went down the hall to our contract attourney, and he read a bit of the thread and basicall agreed with me. The gist is that all EULA are pretty much have been held to be invalid because they attempt to alter the sale contract without consideraion.
You county may differ than the US, but here in case after case, egrigious cluases in EULA type documents, signs and such have been unenforcable - especually when there is no considersion.
You're attempting to alter the responsibilities of a seller after the transaction is complete.
I sorry, but you're wrong - the transaction takes place when money is exchanged for producet, and not at instation time.
Re:Read the EULA (Score:2)
Re:Read the EULA (Score:2)
In that case, I oplogise for putting words in your mouth.
Yes, I agree, that if one form of EULA is weak (I know they are), then my uber-EULLA is equally weak.
Just fighting fire with fire.
Good idea, but prolly violates Microsoft's EULA (Score:1, Insightful)
Those licenses are not available for Windows 9x, but you could probaly purchase Windows 2000/XP terminal access licenses and not be considered in violation.
It does not matter where the processing is being done -- a user is a user.
You would be better off advising your customer to either ditch the legacy app, or bite the bullet and buy 50 Windows XP Pro licenses at about $100/per.
When they compare what you are charging them to build & support this terminal server system, Microsoft is prolly cheaper.
Re:Good idea, but prolly violates Microsoft's EULA (Score:4, Interesting)
This is where some creative scripting or programming can keep you out of a lot of trouble. If you have 5 Windows licenses, then you must ensure that only 5 people can access those applications. As long as you have positive control and proper documentation, you should be able to sail through any audit. At one of my previous jobs, we used a net-installed version of Wordperfect that had about 20 liscenses for 100 employees. Occassionally, when you went to start the program, you'd get a message saying something like "Sorry, no liscense is available. Currently, there are 4 people waiting. The program will start as soon as a liscense is available."
Re:Good idea, but prolly violates Microsoft's EULA (Score:3, Informative)
Microsoft's own Systems Management Server lets you do this as well; install a piece of software on all your desktops, and the SMS client will keep track of who's running it, and deny once you've maxed out your license count until somebody quits.
Re:Good idea, but prolly violates Microsoft's EULA (Score:2)
Re:Good idea, but prolly violates Microsoft's EULA (Score:2)
If you have a call center or some other environment where time is important, that solution won't work.
Re:Good idea, but prolly violates Microsoft's EULA (Score:2, Informative)
I believe that is the whole point.
His question rather, I believe, is more about whether MS considers this using 10 licenses, one each on the host terminals and one for each user accessing a host. (AFAIK, this is not the case anyways...he should be just fine using the setup he has come up with).
DEFINITELY violates Microsoft's EULA (Score:2, Insightful)
WRONG.
MS Windows 2000 Terminal Server's license explicitly makes it clear that each device connecting to a Terminal Server needs its own Client Access License. Licenses are not "per active user"; they are "per active machine", where "active" means "is being used by this company" -- this month, this year, whatever. You are only allowed to reclaim and reassign licenses when a device goes out of service permanently.
Similar remarks apply at least in spirit to every single one of MS's current products. MS rejected the "per connection" license model years ago and has firmly refused to entertain returning to it.
You Lose.
Re:Good idea, but prolly violates Microsoft's EULA (Score:1)
Why bother? (Score:2)
Re:Why bother? (Score:1)
> No offense intended, but I doubt Microsoft is worried about a small shop in Brazil.
Ah, but then again, why would microsoft be worried about an underfunded elementry school? The school dosen't use computers to make money, infact they use them to teach children.
*shrug* all they can to squeeze a few more $$
Re:Why bother? (Score:2)
Famous last words.
Re:Why bother? (Score:2)
Re:Why bother? (Score:1)
Re:Why bother? (Score:2)
Re:Why bother? (Score:1)
Not Legal (Score:2, Informative)
Re:Not Legal (Score:1)
5 licences. at any one time only five people will be using windows. Therefore the licences is not being used concurrently on different computers.
Sounds Legal to me. INAL
Re:Not Legal (Score:1)
"however, you must acquire and dedicate a license for each separate COMPUTER on or from which the SOFTWARE PRODUCT is installed, used, accessed, displayed or run."
Pretty crafty, those MS lawyers. I hope the EULA gets its ass kicked in the CA lawsuit. [com.com]
Per user or per client, whichever costs you more. (Score:2)
Also, Microsoft's licensing is often so complex, even Microsoft reps cannot answer licensing questions. I once worked for a Certifed MS Solution Provider, being one of the MCSEs which enabled the shop to qualify for such status. MS has these bundles of software, designed to allow solutions providers to run reasonable numbers of copies of most software so that they could better serve customers. One day we called into the regional MS office to ask a question about the licensing, to see if we were in compliance. The guy we spoke to didn't know, so we got bounced around for weeks until we were too disgusted to pursue it further. We eventually decided that we had exhibited "due dilligence" and felt we were in compliance.
In any event, use the worst case scenario (cost-wise) for determining the number of client licenese to purchase.
The advice we were given by a MS sales guy: Got five actual PCs but a hundred potential users? Purchase a hundred licenses. Got a hundred machines, but only five employees? Purchase a hundred licenses.
You need to buy a CAL for every user (Score:3, Informative)
Things get a little more complicated than this with Terminal Server, as Microsoft's USED to sell concurrent licenses for their Office products, but they NO LONGER sell concurrent licenses. This means that you will also have to purchase one Office license for every user who will access Office through Terminal Server. This results from MS's EULA statement where they declare that you are not allowed to "share" a license. Having 10 people take turns using 5 Office licenses involves "sharing".
As has already been noted by another poster, the safest position for a company to take w.r.t. Windows and Office licences is to ensure that they have purchased sufficient licenses to cover every possible PC/user that could possibly use/access Windows or Office. You then have to perform enough due diligence that if MS ever audits you that you can defend the position you have taken regarding the number of licenses you acquired.
For example, in your 100 person company: if you have some Linux file/compute servers in your server room, then you can safely risk not purchasing MS licenses for those PCs; however, if the 100 Linux users are able to access the Terminal Server server through your LAN, then even if you have put passwords on the server you would still have to purchase 100 CALs and 100 Office licenses to keep yourselves out of court following an audit as MS could claim that users sometimes share passwords and that there was no possible way you could guarantee that only a subset of the 100 users accessed the server.
Your best bet is to not use Terminal Server, but rather to purchase 5 extra PCs that are located in common areas and the users share access to---and those 5 PCs are the only computers that have Windows and Office installed on them. Then, when someone needs to use PowerPoint, they walk over to one of the Windows PCs and do their PowerPoint. In that manner you eliminate the audit risk and cap your investment in MS products.
Re:You need to buy a CAL for every user (Score:1)
The real problem is actually going to be divying up those licenses as TS (even with patches) won't release a license from a connection for some number of hours. So if you have 5 licenses and 100 potential connecting users you're going to be constantly cleaning up the un-expired licenses...
Re:You need to buy a CAL for every user (Score:1)
You have to purchase a CAL for each of the 100 users. CALs cannot be shared.
You have to purchase an Office license for each of the 100 users. Office licenses cannot be shared.
The issue you raise of Terminal Server only allowing N concurrent sessions is something I didn't even touch on in my post.
Re:You need to buy a CAL for every user (Score:1)
Re:You need to buy a CAL for every user (Score:1)
Re:You need to buy a CAL for every user (Score:1)
As the ever-alert
Re:You need to buy a CAL for every user (Score:2, Informative)
AFAIK Client Access Licenses (CAL) are for Windows NT/2k/.NET Terminal/Advanced Server, which has the one machine and CALs for each connecting IP. (I wont even get into the technica problems with limiting via IP when you're using a remote X with rdesktop setup from one linux, and one windows server)
However W4LTS has a true windows license for each user, and exports the display remotely. It works almost identically to running 5PC's with V
Re:You need to buy a CAL for every user (Score:1)
For the Win4Lin situation, CALs are not required; however, if you are using any version of MS Office newer than Office 95 then I believe Microsoft will assert that you are sharing licenses and need to acquire one per possible user.
VEGA 'Buddy' (Score:2)
Re:VEGA 'Buddy' (Score:2)
Windows Terminal Server Licensing (Score:1)
I'm curious (Score:2)
I'm curious, what software are you having problems with under WINE? Maybe all you need is some configuration advice instead of additional licenses.
Enjoy,
Re:I'm curious (Score:1)
You gotta love it.. (Score:1)
Seriously tho, you gotta watch out, you don't wanna get your butt in trouble. Someone said in a thread, that talking to an M$ Rep, he said 'if you have 100 people but 5 computers, buy licenses for 100 people.. If you have 100 computers but 5 people, buy licenses for 100 computers.' this isn't the first I've heard of it. Infact, we thought that we didn't have to buy 300 licenses for
It Depends on version of WIndows (Score:2)
OLD WIndows = Legal, if you stick with 1 licence per concurrrent user.
NEW Windows = illegal, they have restrictions againts remote viewing/control
That said, if you dont talk to a REAL lawyer, and get it in writing so THEY are responsible.. you are an idiot..