如何将 Microsoft ADAM 配置为与 Active Directory 类似？
我想将用户放入 ADAM 实例中，以便 ADAM 看起来类似于典型的真实 Active Directory 服务器。
我正在开发一个与 LDAP 集成的应用程序。 我已经使用 OpenLDAP 及其 core.schema 进行了测试。 现在我想使用 Active Directory 进行测试，但使用我的设备最接近的方法是使用 Microsoft ADAM 进行测试。
我不知道如何从 ADAM 开始。 它和 Active Directory 的经验为零。 我猜我需要导入 MS-AdamSchemaW2K3.LDF，因为我在其中看到“sAMAccountName”，并且我想我希望它像 Active Directory 一样？
在阅读了几个答案后添加...
到目前为止的答案对于我正在寻找的内容来说还不够具体。 我确实让 ADAM 工作，并且我的应用程序可以与它对话，但我想做的是让 ADAM 以典型（如果有这样的事情）Active Directory 安装的方式工作，相同的架构、身份验证，即使我只是在 Windows XP 上的工作组网络中使用 ADAM。
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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
ADAM 并不是真正的 Active Directory 的完全替代品。 例如，ADAM 不理解不同的组类型，并且默认情况下不包含 RootDSE。 您可以针对 ADAM 进行测试，但查询结构可能会遇到细微的差异。
如果您正在开发依赖于 Active Directory 的应用程序，那么您确实应该针对 Active Directory 构建应用程序。 我已经能够让多个域控制器在 虚拟 PC（免费）仅使用 300mb 内存和 Windows Server 免费评估版。
但是，如果您正在构建一个仅需要 LDAP 目录并且不打算使用 Active Directory 的应用程序，那么 ADAM 可能会很好地工作。 您提到的架构扩展文件 (MS-AdamSchemaW2K3.LDF) 可以正常工作，但您需要设置 RootDSE 以便更轻松地绑定。
最后，Microsoft AD/AM 并不是真正的管理员友好型，尤其是在故障排除方面。 我最终编写了一个应用程序来帮助排除 AD 故障/AM 您可能会发现有用的问题。
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.
我只知道导入 MS-Users 文件。 我看到有一个分步指南
http://www.microsoft.com/downloads/details.aspx?FamilyID=5163b97a-7df3-4b41-954e-0f7c04893e83&DisplayLang=en
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
我不确定您所说的无法使用您的设备来运行 Active Directory 实例而不是使用 ADAM 是什么意思。 我已经在内存只有 256 MB 的虚拟机中运行测试 AD 服务器。 在我看来，ADAM 永远不会成为一个充分的测试，具体取决于您所做的事情。
我会花时间尝试建立并运行适当的广告。
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.
最好的方法是安装 Windows 2003 服务器，并将 Active Directory 加载为域控制器。 仅使用 ADAM 无法 100% 复制 AD 特征。
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.