Integrating Mac OS X With Active Directory
Eric Zelenka writes "Apple has released a new document called 'Integrating Mac OS X with Active Directory.' This document describes how you can use the information stored in Microsoft's Active Directory to authenticate Macintosh users and provide file services and home directories for them on Mac OS X Server. It is available for download from the Mac OS X Server web site." I want my Mac OS X box to self-destruct if it comes into contact with a Microsoft server; does Apple have a document for that?
You have to contort your AD server to allow LDAP for this to work.
I hold it, that a little rebellion, now and then, is a good thing. -- Thomas Jefferson
For those that dont feel like actually looking through apples site for the article, here's a direct link to the PDF version of Integrating Mac OS X with Active Directory [apple.com]
Cire
I was under the impression that if you installed Services for Unix on the box hosting the AD, these fields would be automatically added, but would you still have to create unique LDAP IDs for each user? Is there a way you can do this in bulk?
AD. Whatever.
When are they going to release a lookupd agent for Novell's eDirectory?
Ouch! The truth hurts!
While this is all good and everything, we need a native, built-in solution for the opposite problem: accessing Active Directory servers (Samba, etc.) on OS X. X can do Samba, but not while Active Directories are in place (as far as I can determine.) C'mon, Apple, you're half way there!
Don't worry about self destruct: :) )
If the OSX box is in close proximity to a microsoft server, the explosion from the microsoft server after it spontaneously combusts (tends to happen on microsoft servers) should engulf the OSX box too
(unless apple uses some sort of fire-retardant on their imacs
pun: somehow, this sounds like flamebate
-- If you try to fail and succeed, which have you done? - Uli's moose
I couldn't find it though I knew it existed.
A norwegian company named MetaMerge who has started on this big task (synchronizing databases is not that easy).
I've seen that even Cisco is planning to support Active Directory. Wouldn't it be nice to right click on a user and just select what kind of access the user should have? E.g. "Allow only port 80, or only connections using https, or limit bandwidth of this user .. the solutions are endless".
Of course, Microsoft did not like the full LDAP specification, so they created another layer (ADSI), but what the heck, it still works.
Something that's been bugging me is, I'm pretty sure this topic icon is Apple's copywritten artwork. Shouldn't it be altered for use on /. or a new unique icon be made?
Has anyone gotten this to work without significant modifications to the Win2k server? The document prepares two scenarios -- authenticating via LDAP for access to a file server, and authenticating via LDAP for access to a client which will also mount a user's home directory.
I want to allow authentication, but I don't want to mount a home directory -- just plop them into a 777 temporary home that will be destroyed when they log out. (It's a lab config.)
The document doesn't go into this -- anyone have any insight?
PS: [the following comment applies to only a subset of you] <rant> Stop mindlessly bashing Windows 2000 because you've quit thinking. Win2k is here, it's gonna be here tomorrow, and you're using up my fucking bandwidth and time making me read your useless bantering. Grow up! </rant>
Or alternatively, simply attempt to run OS9 with AppleShareIP as a server. The thing will irritate everyone with constant crashing so much that it might have an 'accident'.
I must say it's the only so-called-network OS that I have seen that when the server crashes, there is at least a 50% chance of all macs connected to said server crashing too. Same thing happens if you repatch the network cables.