Advertisement
Promo

Desktop platforms Toolkit in association with http://ad.doubleclick.net/clk;205413468;14699245;m?http://adfarm.mediaplex.com/ad/ck/2397-58840-22058-14

Microsoft's draft licence, step by step

Ingrid Marson and Matt Loney ZDNet.co.uk

Published: 18 Mar 2005 18:10 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

In last year's European Commission antitrust ruling against Microsoft, the software giant agreed to create a server interoperability licence that would allow rival makers of server software to write applications that can "achieve full interoperability" with Windows client and server operating systems on "reasonable and non-discriminatory terms".

On Friday the EC rejected Microsoft's proposed server interoperability licence, saying it had concerns that the license excluded open source vendors and charged unjustifiably high royalty fees.

ZDNet UK examined a copy of Microsoft's proposed licensing agreement to see the source of the EC's concerns.

So first of all, why is this licence necessary?
Microsoft has been found guilty of breaking EU competition law by "leveraging its near monopoly in the market for PC operating systems onto the markets for work group server operating systems and for media players".

OK, so Microsoft broke the law and was found guilty. What's the punishment?
Well, a €497m (£345m) fine for a start. But the more important part of the punishment is the software giant has to open its protocols to competitors, to help them produce software that interoperates with Windows, both on the client and the server side.

No bird then?
No, nobody's going to prison. Let's call this community service.

Great, so I get a licence to use Microsoft's interoperability APIs in my software and go right ahead, right?
Not quite. Microsoft's draft copy of the licence requires you to pay royalties.

So they're asking to be paid for their community service?
Effectively, yes.

OK, so just what does the licence cover?
Implementation of the Microsoft Work Group Sever Protocol Program, or WSPP. This program comprises two types of software: operating systems that implement Microsoft Windows file and print protocols; and operating systems that implement Windows protocols for administration of users and groups, for things like directory services.

So any operating system that will let me access files on Microsoft servers, or provide file or printing services for Windows PCs or servers, or any operating system that will let me do any authentication, authorisation or directory services in an environment where I have Windows servers?
Right.

But surely this will only affect companies writing operating system software?
Directly, yes, but the royalties will be passed on.

Next

Previous

1 2 3 4


  • Email
  • Trackback
  • Clip Link
  • Print friendlyPrint with EPSON

Did you find this article useful?
261 out of 466 people found this useful


Company/Topic Alerts

Create a new alert from the list below:





Video icon

Video

Microsoft Windows 7 Special Report Special Report

How Microsoft can make Windows 7 a success

How Microsoft can make Windows 7 a success

Comment Many businesses have given Vista a wide berth; Microsoft must focus on five areas to make sure Windows 7 doesn't suffer the same fate, argues TechRepublic's Jason Hiner

More Special Reports

Desktop Management Benchmarking

Test Your Desktop Management Systems

How good are your company's desktop management solutions? How do they compare with those of your peers?

Take two minutes to complete our new Desktop Management and Energy Consumption benchmark, and find out what issues your business needs to focus on.


Skip Sub Navigation Links to CNET Brand Links

Help

Become part of the ZDNet community.

Newsletters