LookupAccountSID 返回错误的域名
MSDN 说： LookupAccountSid 函数返回找到 SID 的第一个域的名称。
如果用户从域A迁移到域B，并且我们使用LookupAccountSid查询用户的旧SID从域 A 的任何计算机上运行函数，我们获取域 A 的域名而不是域 B。
似乎即使在迁移用户后，Active Directory 仍保留用户信息域A。即使重新启动域A的计算机（包括域控制器），该问题也没有解决。
我需要用户的新域名称。您能建议如何解决这个问题吗？
MSDN says: LookupAccountSid function returns the name of the first domain on which SID is found.
If a User is migrated to domain B from domain A and we query the old SID of user by using LookupAccountSid function from any machine of domain A, we get domain name of domain A instead of domain B.
It seems that even after migrating the user, Active directory is keeping user info on domain A. This problem is not resolved even after restarting the machines of domain A including domain controller.
I need name of new domain of User. Can you suggest how to resolve this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
大多数Win32 API 被设计为工作在一个帐户有一个sid 的环境中。 Active Directory 支持
sidHistory属性，该属性可以保存额外的SID。如果您要使用 Active Directory API（例如 ADSI ）或LDAP API 您可以找到主用户名、主 SID 以及您需要的所有其他属性。回答您的问题时最大的问题是您没有描述您的组织中计划和使用的域迁移方案。您计划何时关闭旧域控制器？您是否计划清除文件系统、共享或注册表中保存的旧 SID？
了解完整的域迁移场景非常重要，这样您现在编写的程序才能继续执行域迁移的后续步骤。我建议您与组织的域迁移项目的管理员或项目经理交谈，以了解具体计划做什么。
The most Win32 API are designed to work in the environment where one account has one sid. Active Directory supports
sidHistoryattribute which can save additional SIDs. If you would use Active Directory API (for example ADSI) or LDAP API you can find the main users name, primary SID and all ather attributes which you need.The most problem in answering on your question is that you don't describe the domain migration scenario which are planned and used in your organisation. When you plan to switch off the old domains controllers? Do you plan to clear the old SIDs saved in the file system, shares or in the registry?
It is important to know the full domain migration scenario, so that the program which you now write will continue to work on the next steps of domain migration. I recommend you to speak with administrators or the project manager of the domain migration project of your organization to understand what is exactly planned to do.