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

Exchange 2010 Sp1 Calendar Permission issue with imported pst mailbox

Hi gurus,

I have an odd permission issue with an Exchange user...I had to do the below to resolve a task view issue.

Originally,
1) I had exported the user's data to a pst file via mailbox-exportrequest in Exchange Shell.
2) disabled the mailbox and removed the exchange data
3) recreated an emtpy mailbox and used exchange shell importrequest to restore the data from pst file

Now, I have a weird issue where the user can't cancel previously created meetings/items even though he's the owner of the mailbox...If I add delegates with full permission access, they can't delete stating the permissions are set for behalf of user.

I'm 99% sure it's an issue with mismatch AD guid mailbox of the old mailbox with the new mailbox.

Is there a way to fix?
0
jetli87
Asked:
jetli87
  • 4
  • 4
1 Solution
 
AmitIT ArchitectCommented:
I guess, add custom X500 connector with old legacyexchangedn value and see if that fix the issue.

Or you can try same steps with a test mailbox and note down, what is changed. This will help to point out the root cause
0
 
jetli87Author Commented:
can you elaborate on how to do that?  or give me sample steps?
0
 
AmitIT ArchitectCommented:
Hi Jetlli87,

Can you post the error user is getting while cancel meeting request.
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
jetli87Author Commented:
The permission error has gone away, but when the user, PaulS deleted the previously created meeting, it seems to send cancellation to old inbox.


Delivery has failed to these recipients or groups:

Paul Smith <mailto:IMCEAEX-_O%3DSCompany_OU%3DFirst%2B20Administrative%2B20Group_cn%3DRecipients_cn%3DPaulS@Company.com>
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.


 
0
 
AmitIT ArchitectCommented:
ok So adding X500 should work here. In the bounce back message you can see the old legacyexchangedn value. It will look like this

/o=ExampleAB/ou=Organizationalunit1/cn=Recipients/cn=Username

Steps are give here
http://support.microsoft.com/kb/313324

Add this wait for replication and try again.
0
 
jetli87Author Commented:
Just want to be clear that this will work for Exchange 2010 sp1?  

Note, the original account was migrated from an Exchange 2003 box before I purged and rebuilt the inbox.
0
 
jetli87Author Commented:
I applied the x500 record and so far I looks fixed...I'll give it another few days and I'll reward points...thanks!
0
 
AmitIT ArchitectCommented:
Thanks for the update.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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