Microsoft Working For Samba Interoperability

JP writes "Andrew Bartlett of Samba fame has written a document describing their recent collaboration with Microsoft's Active Directory team. In brief, it would seem that the sky is falling, as Microsoft's engineers seem to be really committed to making Samba fully interoperable with AD. They have organized interoperability fests and have knowledgeable engineers answering technical questions without legal or marketing drones getting in the way. However according to Andrew the Samba AD team is currently very short on manpower, so if you have network experience, now is the time to get coding."

Comments

Novell, RedHat, want to help out.

[LWATCDR]

Seems like a good time for some of the larger distros to help Samba out.

Re:WTF?!

[ThePhilips]

You seem to not read carefully the most important part: "Microsoft's engineers seem to be really committed to making Samba fully interoperable with AD"

M$ engineers are normal folks like you and me. Well, probably not me. The all cr*p breaks loose when M$ management gets involved and start pushing its political agendas.

If cooperation between AD and Samba folks would be successful, rest assured some M$ managers would try to stick themselves into the project to get a free share of credit for the success.

Doesn't surprise me, from where I sit

[MikeRT]

I work for a company that does a lot of integration for enterprise customers. Sometimes there are spaces for Microsoft products in an otherwise Unix environment. Our customers happen to be pretty set on using Unix in general, so for Microsoft, it makes sense to make sure that their products can fit into an environment like that without any hassle. After all, a small sale is better than no sale.

Re:about time..

[gbjbaanb]

I suppose its all about realisation that Linux is making it into corporate environments, and Microsoft now has to do something to keep themselves there.

MS are saying that if you really, really must have a Linux server in your IT shop, they'd better make it so it can connect to the one true corporate user account register, before the people who put the Linux server in decide to try a different LDAP server, maybe even one supplied by Novell.

It makes sense for MS to start doing this, in this way they can keep their dominance in the corporate IT structure, by letting the lowly Linux boxes play in the same playground. The important thing to understand here is that even MS has realised linux is making it big in businesses, that kinda give Linux the seal of approval from MS, not even the most pro-MS, anti-OSS PHB can say its not a valid OS anymore.

Next: an Outlook client... MS won't mind that as it allows them to keep their Exchange systems ... until someone builds an Exchange replacement to go with it, and then watch MS share price tumble.

Big Guys: time to chip in

[alexborges]

I cannot believe the samba team is down to ONE full time developer.

Its a HUGE project to undertake.

When I buy my Red Hat, Suse or Ubuntu thingies for money, Im thinking some of that money goes to helping FOSS developers.

Hey, it better be that way guys: put some dough into Samba.... NOW!

Re:hah this is too little too late

[Shados]

Its already interoperable, but the MS AD team isn't going to stop adding features just because its going to break the desktops of people who don't pay them. But if they break things too much, they get sued to death over their monopoly. Their only solution is to make sure the Samba project keeps up, so its what they do.

Re:about time..

[rickb928]

"There is a reason why Windows servers are so popular and it is no one makes directory services, file sharing, group policy, and email/calendaring as easy as Microsoft. Microsoft has been so successful at creating these services and making them simple to administer that most open source projects try to emulate/replicate/duplicate what already has been done"

I disagree.

Before even Novell had NDS working well there was StreeTalk. But NDS worked just fine, than, you very much.

It was the client, being crippled by Microsoft, that hampered NetWare. Not NDS.

The whole Microsoft v. Novell thing is a good case study in using interoperability to first build a market, then crush your competition, leaving you dominant and solitary. Perhaps you need to go back and read some of the court papers to more fully appreciate the effort Microsoft put into making Novell fail on Windows.

And then there's the whole Lotus 1-2-3 and WordPerfect things, but we digress. When Microsoft starts 'working' on interoperability, it is not irrational to suspect foul play. It's experience.

ps- I rather liked GroupWise, which worked pretty well when Exchange was not. And I use Notes at work which, despite the complaints, works too well to ditch here. Not entirely fair, 'cause here we use so many Notes databases and apps that Exchange can't replace all of it. The IBMers are frantically converting everything into .NET and Web 2.0 so we can use Exchange, and coincidentally experience substantially enhanced downtime in our data apps. And they are succeeding well. We've even lost data. Woot! Believe me, I know, these guys don't need any help from Microsoft.

grrr....