Hi all, I'm migrating from Exchange 2010 to Exchange 2010 SP2 RollUp5v2 in different forests When I migrate users with shared calendars, these permissions are lost in migration. Does anyone know how to solve that? permissions need to remain shared calendars for migrated users regards Microsoft Certified IT Professional Server Administrator

Hi, How are you migrating to the new forest? I must ask since you mentioned here that you had to copy the ExchangeLegacyDN from the source mailbox to target. (That value is copied when running prepare-moverequest, so you shouldn't have to do it manually if you are running the migration with the build-in cmdlets) Martina Miskovic

Hi Martina, thanks for answering, of course, when I run the Prepare-MoveRequest.ps1 script, I copy the value in the target mailbox ExchangeLegacyDN. Then you need to create a contact for each migrated user in the source and add this value. But this is not the topic of my question in this forum. My problem is that users are sharing the calendar in the source forest, when migrated Share cease. You know how I can solve this problem. Is there any way to keep these permits in the migration process thank you very muchMicrosoft Certified IT Professional Server Administrator

I think the problem you are facing is related to your other thread. The source mailbox is converted to a Mailuser so why are you creating MailContacts in the Source ORG? Martina Miskovic

I have never had any problems with shared folders during a migration to Exchange 2010. I always prepare all users before I migrate the first mailbox. Maybe you didn't do that and that is causing the problems you are having.Martina Miskovic

Hello again, as the two share the same domain sitemas SMTP, there are two ways to keep the flow of the message enters the two organizations as these migrating. Creating Source connector for the shared domain, this approach has several problems: - If a user sends an email making mistakes when typing the address the message is bouncing in the two systems causing loops. - If we do not create contacts in the source, there are problems in the caches of clients not migrated users (OWA and Outlook). or Creating source contacts for migrated users, and thus also solves the problems of the clients cache. I think, that has nothing to do, that source in the forest instead of having a Mail Enabled User, we have a Mail Contac .. The problem I am having I think it can be for topics that Excahnge Source System does not have any service pack installed or permissions issues in domains. regardsMicrosoft Certified IT Professional Server Administrator

This is happening to me, when I make that migrated users simultaneously, ie if user1 user2 shared calendar, prepare the two users on the same lot before migrating, and migrated at the same time You had some service packs installed? regardsMicrosoft Certified IT Professional Server Administrator

Hi, If you prepare all users in the Target before you migrate the first mailbox, users will not have any problems with their cache in Outlook or OWA. The "trick" is to use an extra SMTP Domain during the migration and it will be the one you specify for -TargetDeliveryDomain I have done a lot of migration since back in RTM and the above hasn't changed since. The Target Servers has always been 100% up to date, but there have been times where the Source ORG hasn't.Martina Miskovic

Hello Martina, as there are many open threads on the forums stating these things, you are a very lucky person, never happened in any of this migration. If you prepare all users before migrating, is the same as if you set two before migrating users to share calendar, ie the fact that users do not share calendars between them are prepared, does not mean anything, does not make sense. If you add an alias X500 does not mean anything in the shared calendar, as this is managed by permission, not by alias X500. The alias is stored in ExchangeLegacyDN X500 regardsMicrosoft Certified IT Professional Server Administrator

If Exchange can't find the user that has been given permission to a shared folder during the migration (will happened if all users hasn't been prepared yet since the LegacyExchangeDN doesn't exist in the Target yet) it make perfect sense to me that it can't set that permission so hence the problem. If you have found thread with the same problem, maybe you should ask there if they had prepared all users or not before they migrated the first mailbox. I don't think they did. Martina Miskovic

Hello Martina, not if I understand correctly, if I have four users: User1, user2, user3 and user4 User1 and user2 share among themselves the calendar User3 and user4 share among themselves the calendar What I do is I prepare and migrated while user1 and user2, in the same block. and when user3 and user4 migrated and the migrated prepare together. You tell me that if I migrate user1 and user2, but I have not prepared user3 and user4, it is normal that permits shared calendars user1 and user2 not migrate because they have not prepared user3 and user4? Is that what you're trying to say? I truly believe that this is not the problem, in fact, in other migrations, have performed this procedure, and permits are shared among users migrated. regardsMicrosoft Certified IT Professional Server Administrator

Hi Martina, I just do the same procedure in a test environment, as I am doing it in production. My current environment is Exchange Server 2010 SP2 RU5v2 in the source system and the source system. I have done exactly the same procedure and I checked that the permissions are kept, therefore, adding the alias of the X500 address to the contact in the source forest is not the problem. That if I saw that I had to add back the calendar in both OWA and Outlook, but simplemete adding the calendar from the client is solved. I will do the same test in the production environment to see which is the difference regardsMicrosoft Certified IT Professional Server Administrator

I have done exactly the same procedure and I checked that the permissions are kept, therefore, adding the alias of the X500 address to the contact in the source forest is not the problem. That is the part you do that I really don't understand. When you run prepare-moverequest, the Target legacyExchangeDN is copied to the source mailbox as an X500 and the LegacyExchangeDN the Source Mailbox has is copied to the Target MailUser as an X500.Martina Miskovic

I try to explain. Obviously, when you run Prepare-MoveRequest LegacyExchangeDN parameter copies in the mailbox of the target forest. But when a user is not migrated in the source forest, send an email using the cache OWA or Outlook. As the cache uses OWA or Outlook X500 address, and the Mail Enabled User, which converts the mailbox be migrated in the source forest is not the same as the one with the mailbox, the sender receives an NDR indicating that there is the e-mail. This is solved by adding the contact source forest, the X500 address alias with the user's mailbox had when I was in the forest source not if I have explained http://msexchangeguru.com/2012/03/15/x500/ https://www.simple-talk.com/sysadmin/exchange/exchange-e-mail-addresses-and-the-outlook-address-cache/ http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_9650-NDRs-and-the-legacyExchangeDN.html regards Microsoft Certified IT Professional Server Administrator

If you would prepare all users, you wouldn't have that problem.Martina Miskovic

I have done exactly the same procedure and I checked that the permissions are kept, therefore, adding the alias of the X500 address to the contact in the source forest is not the problem. That is the part you do that I really don't understand. When you run prepare-moverequest, the Target legacyExchangeDN is copied to the source mailbox as an X500 and the LegacyExchangeDN the Source Mailbox has is copied to the Target MailUser as an X500.Martina Miskovic

If you would prepare all users, you wouldn't have that problem.Martina Miskovic