This guide in PDF provides prescriptive guidance to enable Microsoft Windows Server 2003 to be used for authentication and as an identity and authorization data store within heterogeneous Microsoft Windows and UNIX environments.The guidance covers evaluating, planning, building, and deploying a security and directory infrastructure based on Windows Server 2003. The guidance will be valuable for business and technical decision makers, IT architects, and systems administrators participating in infrastructure consolidation or integration projects.
Solution Guide for Windows Security and Directory Services for UNIX
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
But if you’ve got some nice Unix/BSD/Linux/… systems, why use windows for authentication? I would only ever use windows machines as clients, never servers.
It is way easier to make a security model that better represants your organization/work group/team with Windows than it is with *nix/linux. I don’t know about you, but managing 10000+ users in a multi-companies company with thousands of groups and sub-groups, I really wonder how you can do that with *nix/linux?
@Harky
You are aware that the Microsoft solution relies on Kerberos
and LDAP, neither of which is a M$ technology and both have been available on Unix for many years?
Unix and Novell solutions has accomplished what you’ve wondering about before Microsoft had a Network Operating System worthy of the name.
And, when NT first saw the light of day, I don’t believe it could have done what you’re talking about without some massive
hardware investments and funky config workarounds
I have only scanned the article but to authenticate a Unix machine with Active Directory you have to use Vintela (a SCO product) to achieve this! I’m not part of the “tin foil hat club”, but I would be a little more than concerned about a solution that requires software from a company that is on shaky grounds at best.
>It is way easier to make a security model that better
>represants your organization/work group/team with Windows
>than it is with *nix/linux. I don’t know about you, but
>managing
Easy? what are you kidding you talk about security and Microsft and then easy?? You really do not get do you?
Its not about easy this easy that click click, click..
Its about the security of your company and the mangment of it you do not need easyness you need knowledge.
>10000+ users in a multi-companies company with thousands of
>groups and sub-groups, I really wonder how you can do that
>with *nix/linux?
That is your problem, lack of knowledge about Unix. Unix/Linux is just made for such things most ISP for example have over 300.000 users in groups with rights etc.. most of them run Linux or BSD why? because they are very stable, very free, very fast, very maintable, very virus free, very spywar/trojan/bug free and do not need X to run all server services. If you still useb Windows on a server you would be scratching your bald heads by now and start thinking about making a swift.
Come join us its fun! We will guide you trough
Your comments should be directed to “Harky”, not “JimBough”
Other sources are also mentioned like MIT Kerbos and PADL’s LDAP. Not just Vintela. I also have not had a whole lot of time to look over this yet but it is hard to breeze through a 400 page document and pick out all of the important stuff.