Depends how tightly you want to integrate it.
You can make Linux and other Unix boxes a complete AD client using various tools.
You see AD isn't something new. What it is a LDAP server with configuration stored on a customized database. Like with everything else MS wasn't happy to stick with the standards but did it's extend dance to make it slightly unusable for most OSes.
So what you do to make it work is thru using PAM modules, LDAP server, and SAMBA. Plus you need to install a Unix compatability thingy for your w2k server. This alows the naming and permission conventions to be translated to something Unix/Linux can use. You can install Unix services for windows, but there is a free program that MS made that can work well enough, unfortuanatly I don't remember what it was.
SAMBA 3.0 is a great thing, but you could do what I think you wanted before it was released, but it makes it more complete transition.
PAM modules are things that allow you to setup how you want to authenticate you users in Linux. Before that you would have to recompile each authication program like "login" for each type of authentication sceme. However with PAM you can "plugin" different support.
So basicly your goal is to make a LDAP client to AD's LDAP server, and then set up PAM to authenticate your users thru that instead of using the local stuff. Then set up SAMBA to allow your users to access windows shares. The only mod to the w2k server is to extend the scema to support Unix naming/password/permission conventions.
here is one link
Here is a link showing howto use Windows Linux services
here is another link, check out the text file linked from this page
Just do a search on google for this stuff, you can find lots of resources...
With SAMBA 3.0 I think you can actually use Linux as a DC for AD. You can set up trust relationships with W2k and Linux just like you can set up with W2k and NT, but I think that the authentification one flows from windows down, linux can't send configurations back up into the w2k server, since it isn't designed to allow that.
You could also use SAMBA 3.0 as a standalone domain controller for windows clients. I beleive.
Unfortuanatly I haven't gotton around to setting this stuff up myself, but It seems like you can with some effort make Linux a nice file sharer and client/server that you can integrate pretty seemlessly into windows domains. And visa versa. You could probably even use Linux as a glue to get a bunch of disparent OSes to work together, like get MACs to work with Sun servers and Windows servers and so on a so forth.
Good luck!
edit: actually when I say LDAP for Linux versus LDAP for AD I mean to say that you use OpenLDAP for linux.
Facebook
Twitter