Remove recurring calendar event created by account that no longer exists

We recently did a full network migration that included moving an off-line exchange database to a new exchange server using Lepide Exchange migration tool.  It read all the mail items in the old .edb file and moved the items into the new mailbox associated with that user.

Of course, the new AD and mail database has all new user accounts, so for the recurring events that were moved over the originator of the event no longer really exists in the database, and the user can not delete the meeting and can not send a cancellation notice because they aren't the 'original' creator, as far as AD is concerned.

Is there any 'easy' way to delete this recurring event?
LVL 1
Sys_Admin1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jamie McKillopIT ManagerCommented:
Hello,

I recommend you setup the Calendar Repair Assistance to run on a schedule. This should eliminate these orphaned meetings.

http://technet.microsoft.com/en-us/library/ee633469%28v=exchg.141%29.aspx

-JJ
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sys_Admin1Author Commented:
Thanks, I will set that up.

I was able to remove the recurring event by giving myself full access to the mailbox, then opened the users calendar and removed the recurrence of the meeting.  I guess that since I 'took' full access it gave my account full rights to all the items in the mailbox even though the user of the mailbox didn't have rights to that calendar item because it wasn't created by their new account in the new domain.

Certainly a brute force method, but it worked.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.