Microsoft XP License Prohibits VNC
jhml writes: "Looks like the monopoly muscles are flexing. According to this article in Infoworld, the XP license prohibits products other than from Microsoft's from being used to remotely control an XP workstation. So ... guess they were having a little trouble with VNC being widely used?"
Free cell phone tracking
In any case, what matters is not whether VNC lets you do this but that Microsoft tries to impose such restrictions. It's just another indication of how much they are trying to milk and control their customers. Any rational buyer should run from that kind of company, and this should be added to the long list of anticompetitive practices to be investigated.
"Except as otherwise permitted by the NetMeeting, Remote Assistance, and Remote Desktop features described below, you may not use the Product to permit any Device to use, access, display, or run other executable software residing on the Workstation Computer, nor may you permit any Device to use, access, display, or run the Product or Product's user interface, unless the Device has a separate license for the Product."
This is taken out of context, but I'm assuming 'Product' is referring to XP. It doesn't say you can't run VNC, it says that there needs to be a seperate license of XP for the client. That is bogus for VNC users, but if you look a little closer at the wording, I'm not sure they exactly intended to wipe out VNC. It sounds like they're saying 'you have to be using XP to control XP', but that's only true if this agreement is for the home edition of XP. Again, this was taken out of context, but I can't help but wonder if this was taken from the Corporate version of XP's agreement.
If that's the case, suddenly it makes more sense. What MS is trying to do is get companies to buy the XP Enterprise Edition (at least I assume there's a version like that...) that has 25 client licenses. In which case, using PC Anywhere to connect to that product would require an extra license. This sounds shitty unless you think about it some more. Computers are getting more powerful, right? So it gets to a point where you could have one computer powerful enough to perform a number of people's needs, all you'd need is a terminal to connect to it.
Let me tell you about an interesting feature that XP has that the rest of the Windows line doesn't: It can have multiple users running programs at the same time. Unix has done this for ages, but XP finally supports this. You can log in as yourself, run a program, then log in as somebody else and run a program there too. In effect, both your programs are still running. A company looking to save a few bucks could make a central computer running XP and hack a version of VNC to divvy up incoming connections into different users. Then they build a bunch of Linux machines using VNC that connect to this server and make it look like a Windows desktop. They could buy exactly one copy of Office and support a whole office with that license. This would be harder to do with Win2K, but it seems like it'd be fairly easy with XP. I think MS's license is saying that you can't do this.
As a side effect, VNC and PC Anywhere are technically unable to be used legitimately, unless MS specificially says it's ok. They probably have done that with PCAnywhere (there's hints to that effect on Symantec's site), but VNC probably won't be since it's open source.
Alot of people are interpreting this line of text as an attempt to maintain a monopoly, or to wipe out VNC or something like that, but that really doesn't make a whole lot of sense. If MS really didn't like remote computing, then by default all they'd have to do is disable the common ports used for it. I think it's more likely they're trying to prevent people from doing something that hasn't been attempted yet.
"Derp de derp."
I also agree with an earlier poster -- for the Windows platform, the Terminal Services client is *FAR* superior to VNC -- of course it is -- VNC works by sending bitmaps across the pipe -- the terminal services client can send API calls -- same principle as behind Xwindows.
Nonsense!! With Palm VNC I can take over my desktop with my Kyocera Smartphone. Can you give me a Windows Terminal services client that runs on a palm pilot? There are VNC clients and servers for a large variety of platforms. What do you think are the chances that MS will permit interoperability with Linux (which they've called THE major threat to Windows) or with PalmOS (the major competitor to WinCE)?
Window Terminal Services are only far superior if you've already been assimilated. Even if I am sitting in front of a Windows machine, a Terminal Services client won't help me take over one of my Linux boxes. Terminal Services is mostly just good for locking me into Windows. No thanks.
Adrian
An AC wrote:
> Sure, punish success. That'll inspire people to create!
Microsoft has broken the law and been found guilty. That is a matter of public record (verified by an Appeals court). Breaking the law carries a penalty.
Allowing Microsoft to break the same laws over and over (like they are doing now) and to let them successfully get away with it only inspires them and others to continue breaking the law. Microsoft needs to be punished so they and others will take the law seriously.
Take this case for example. The EULA of XP is forbidding the use of an entire category of software if it comes from a third party. If XP does catch on to become the version of Windows used the most, then everybody else making that category of software is immediately out of business, regardless of how successful or good their product is. How exactly does that situation inspire people to create? It doesn't, it punishes them for trying to create. Microsoft is wrecking their businesses just because Microsoft is greedy and wants people to buy more licenses.
Maybe you don't care about Microsoft's victims. When Microsoft starts charging you for every time you turn your computer on, will you care then?
Then it will be too late.
What happens when you embrace and extend Godzilla? Nuclear heartburn!
See "Godzilla 2000" (released in Japan as "Godzilla 2000 Millenium") for details.
...you may not use the Product to permit any Device to use, access, display, or run other executable software residing on the Workstation Computer, nor may you permit any Device to use, access, display, or run the Product or Product's user interface, unless the Device has a separate license for the Product.
Notice that last part, where they prohibit running the windows user interface remotely on a machine that is NOT licensed for windows. What they want to prevent is using workstation licenses to set up a "windows server", which could let you run windows programs from a non-windows machine.
This is to keep people from buying a small number of windows licenses and putting a few machines running VNC or the like in the server room, to run those few windows applications that the company hasn't been weaned from yet.
Again they're monopolizing - this time by trying to block migration paths from windows to non-windows shops.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
Now it's "no big deal, VNC runs just fine".
In 2 years when the next version comes out and VNC won't run anymore it's "no big deal, VNC wasn't legal anyway, it should not run"
It's the same with WPA:
Now: "No big deal, it works fine"
In 2 years: "Subscription is great because you don't get any WPA-codes for unsupported versions anymore anyway."