Using ADAM for AD integration?

Hello 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