Home › Forums › OS X Server and Client Discussion › Active Directory › Using ADAM for AD integration?
- This topic has 2 replies, 3 voices, and was last updated 16 years, 9 months ago by
Micah.
-
AuthorPosts
-
March 29, 2007 at 6:28 pm #368667
jdyck
ParticipantHello all…
I’ve seen two posts from Joel (MacTroll) that mention using ADAM to add the Apple settings to Active Directory to support MCX via AD… I’m wondering if anyone has any links or documentation for this? I’ve been dabbling in ADAM since I saw those notes, but am a big confused…
So far, I’ve installed ADAM on a test Windows 2003 Server, ran the “schema sucker” (ie: adschemaanalyzer) and pointed it at an OD server, then chosen my AD server as the base Schema, selected all the Apple extras, and saved the LDIF file that resulted.
So now it’s time to somehow import that LDIF file into AD, which is where I’m running into a lot of questions…
Question #1:
Since I already have Active Directory running on port 389, if I start an ADAM instance it will run on a non-standard port (defaults to 50001)… Will the OS X machines be able to figure this out? Or (I’m leaning this way) do I skip running an ADAM instance completely and just import the LDIF into AD?Question #2:
Either way, part of the import procedure involves specifying the Distinguished name to import to. The command looks something like:ldifde -i -u -f Apple-OSXStuff.LDF -s server:port -b username domain password -j . -c “cn=Configuration,dc=X” #configurationNamingContext
Now, obviously the Apple-OSXStuff.LDF is the LDF file to import, the server is where I want to import this to (either AD on port 389, or ADAM on port 50001), followed by the authentication info… But what do I put in for the distinguished name? How critical is this? Right now my test domain is just testbed.com, so do I just put in “dc=testbed,dc=com”? And finally, do I need to do anything with the #configurationNamingContext part?
If anyone can give me a bit of assistance I’d be glad to document the procedure with screenshots (part of what I have to do for the company anyway) and post it back to the site for other users to benefit.
Thanks in advance for any assistance offered
Jeff
June 23, 2008 at 6:04 am #373217Micah
ParticipantHello,
I have sort of the opposite problem. I know how to import a schema but I can’t seem to get the LDF file built to import. What steps do you take to connect to a Leopard OD server to “suck” the schema out of it? I tried connecting with ADSchemaAnalyzer but it won’t connect to my OD server. Perhaps I am using the dn wrong (I’m just putting “diradmin” in for the username)?
Thanks,
Micah
EDIT: I tried with nothing but the server name and it worked fine. I was making it more complicated than it needed to be. 😀
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed