drm256
asked on
Exchange migration - calendar entries and maintaining organiser
When migrating users from an Exchange 2007 organisation to a Exchange 2010 organisation, we export the data to pst via powershell and import into the new account.
The issue is calendar entries, in that the user cannot modify their own entries any more as they are not the owner / organiser. So they cannot change the time / date / guests etc.
Is there any work around for this aside from recreating?
The issue is calendar entries, in that the user cannot modify their own entries any more as they are not the owner / organiser. So they cannot change the time / date / guests etc.
Is there any work around for this aside from recreating?
No work around that I can see - any reason why you chose to do the PST migration option instead of simply moving mailboxes across the servers or are these servers in different AD Forests?
ASKER
They're in different forests.
I've tried exporting and importing as iCal. That seems to solve the edit issue, so the cal entries can me modified, but the recipients within the exchange organisation see them as new entries.
We've also looked at adding edit rights to the cal entries via powershell.
I'll reply again when we have more information.
I've tried exporting and importing as iCal. That seems to solve the edit issue, so the cal entries can me modified, but the recipients within the exchange organisation see them as new entries.
We've also looked at adding edit rights to the cal entries via powershell.
I'll reply again when we have more information.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There's no perfect solution to this.
Migrating via PST results in the imported calendar entries retaining old Contact info which then, when replying / updating will bounce (as expected). That then results in the old contact being cached and the user incorrectly sending mails to that contact (bouncing).
The best 'compromise' I found was to export the calendar as an ical and then import it back in. From there the user could modify the recipients.
Migrating via PST results in the imported calendar entries retaining old Contact info which then, when replying / updating will bounce (as expected). That then results in the old contact being cached and the user incorrectly sending mails to that contact (bouncing).
The best 'compromise' I found was to export the calendar as an ical and then import it back in. From there the user could modify the recipients.