• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 416
  • Last Modified:

Get-MailboxPermission cmdlet failing after moving users to new OU

I recently "organized" my AD structure by moving some departmental OUs around.  They were originally created at the top of the domain tree, so I created a new top-level OU named "Domain Users" and moved the other OUs under that one.

For example, mycompany.com/Finance is now at mycompany.com/Domain Users/Finance

Since I made that move a few days ago, I cannot manage mailbox permissions, as the Get-MailboxPermission cmdlet is pointing to the old location for the user object, even though the current one is displayed if I view the properties of the mailbox in the EMC.

How do I get Exchange (2007) to point to the new location for the OUs containing the user objects?  I read that disabling/enabling a user fixed it for one person who had the same problem, but it didn't work for me.

Thanks, in advance.
0
RAHopkinson
Asked:
RAHopkinson
  • 2
1 Solution
 
RAHopkinsonAuthor Commented:
BTW, if I re-create the department OU at the top level and move a user object back, the Get-MailboxPermission cmdlet works fine for that user.
0
 
dsnegi_25decCommented:
Did you check where is your  DC pointing  may be replication issue.

Can you reboot the DC & Exchange both & then check

& please check user  location through ADSIEDIT
0
 
RAHopkinsonAuthor Commented:
Replication did not seem to be the issue, as all DCs had the effected changes successfully replicated.  Restarting the DCs did not solve the issue, but once we restarted the Exchange Server, the problem cleared.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now