How can I configure Microsoft ADAM to be similar to Active Directory?

Question

I want to put users into an instance of ADAM so that ADAM looks similar to a typical, real, Active Directory server.

I'm developing an application that integrates with LDAP. I've tested with OpenLDAP and its core.schema. Now I'd like to test with with Active Directory, but the closest I can get to that using my equipment is by testing with Microsoft ADAM.

I don't know exactly how to begin with ADAM. Zero experience with it and Active Directory. I'm guessing I need to import the MS-AdamSchemaW2K3.LDF because I see "sAMAccountName" in there, and I think I want that to be like Active Directory?

---

Added after reading a couple answers...

The answers so far aren't specific enough for what I'm looking for. I did get ADAM to work and my app can talk to it, but what I want to do is to have ADAM working the way a typical (if there is such a thing) Active Directory installation would work, same schema, authentication, even though I'm just using ADAM in a workgroup network, on Windows XP.

Answer 1

http://windowsitpro.com/article/articleid/43772/q-how-can-i-install-active-directory-application-mode-adam.html

http://technet.microsoft.com/en-us/library/cc197506.aspx

Look into Windows Server 2003 resources.

Thanks

Answer 2

Hi, I am only aware of importing MS-Users file. I see ther is a step-step guide

http://www.microsoft.com/downloads/details.aspx?FamilyID=5163b97a-7df3-4b41-954e-0f7c04893e83&DisplayLang=en

Answer 3

I'm not sure what you mean by not being able to use your equipment to run an Active Directory instance instead of mucking around with ADAM. I've run test AD servers in virtual machines with as little as 256 MB of RAM. Seems to me that ADAM is never going to be an adequate test depending on what your doing.

I'd spend time trying to get an proper AD up and running instead.

Answer 4

ADAM isn't really a complete replacement for Active Directory. For example, ADAM doesn't understand different group types, and doesn't include a RootDSE by default. You could test against ADAM but you may run into slight differences in your query structures.

If you are developing an application that will depend on Active Directory then you really should be building your application against an Active Directory. I have been able to get several Domain Controllers running just fine in Virtual PC (free) using only 300mb of memory and a free evaluation version of Windows Server.

If, however, you are building an application that simply needs an LDAP directory and isn't going to be using Active Directory than ADAM may work out just fine. The schema extension file you mentioned (MS-AdamSchemaW2K3.LDF) would work just fine but you would want to setup RootDSE for easier binds.

Lastly, Microsoft AD/AM isn't really Admin friendly, especially in terms of troubleshooting. I ended up writing an application to help troubleshoot AD/AM issues that you may find useful.

Answer 5

The best approach would be to install Windows 2003 server with Active Directory loaded as a domain controller. You cannot 100% duplicate AD characteristics using ADAM alone.

Answer 6

use Virtual Box from SUN, instead of using VMware, as Vbox is free...

Concerning the ADAM, I'm also trying it to be able to use on WinXP as an AD DC on Server.

But I'm not clear which can be use like this...

I read here http://technet.microsoft.com/en-us/library/cc756986%28WS.10%29.aspx