问题描述
您好，我的公司AD用户管理有麻烦.
Hello, I have trouble with my company AD user management.
当员工更换职位时，有一个策略，通过该策略，域中的当前用户条目将重命名为samaccountname并标记为已禁用.然后管理员使用与旧帐户相同的samaccountname创建新的用户条目.因此，用户已移至 新职位失去了他的旧权限，但使用他的旧名称登录.
When employee changes position, there is a policy, by it in domain current user entry gets renamed samaccountname and marks as disabled. Then administrator creates new user entry with samaccountname same as it was on old account. So user, moved to the new position loses his old permissions, but logins with his old name.
问题是，如果该用户尝试登录到SP门户，则其旧的内部条目将被静默删除，并生成新的条目.之后，对已删除用户的所有查找将不会被删除，但将是无效的，并且在交互时会生成异常.
The problem is when that if that user try to login to the SP portal, his old internal entry will be silently removed, and generated new one. After that all lookups to on removed user wont be removed but will be invalid, generating exceptions when interacted.
我试图通过使用Move-SPUser命令将spuser移动到原样的帐户名来解决此问题.但是SP什么也没做，甚至没有抛出任何异常.输入下一个用户后，当前用户条目将被删除，并生成新的条目.
I tried to resolve this issue by moving spuser with Move-SPUser command, to the same account name as is was. But SP did nothing, even did not throw any exception. After next user enter current user entry gets deleted and new one generates.
有人可以帮我解决这个问题吗?
Could someone help me with this problem?
推荐答案
这篇关于Sharepoint 2013不要移动spuser的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！