K B
asked on
Office 365: Hybrid Migration from Exchange (Retention Policies)
Do Retention Policies/Tags (and items - do they retain their tags?) migrate from Exchange 2010/2013/2016 to Office 365?
If you match 1:1 (in other words create the same retention Tags/Policies in Office 365 that you had in Exchange On-Premises) ...
1. Policy Names (create same policy names in cloud as on-prem, is this necessary?)
2. RPTs
3. DPTs
4. Personal Tags
...in a new policy in Office 365 will the tags (that are applied to items) be maintained from On-Premises? Will the retentions reset to the day they are migrated?
Thank you.
If you match 1:1 (in other words create the same retention Tags/Policies in Office 365 that you had in Exchange On-Premises) ...
1. Policy Names (create same policy names in cloud as on-prem, is this necessary?)
2. RPTs
3. DPTs
4. Personal Tags
...in a new policy in Office 365 will the tags (that are applied to items) be maintained from On-Premises? Will the retentions reset to the day they are migrated?
Thank you.
When you migrate the Mailbox to O365 retention hold would be applied on O365 so in this case Mailboxes would have the retention policy reset and whatever policy you have on O365 will be applied.
No, they dont. On-prem and O365 tags dont relate. You need to export/import the tags (make sure the GUIDs) match, then you can rest assured that everything will be in order.
ASKER
Thank you Vasil.
few questions if I may please...
1. Why do the GUIDs matter - does "something" migrate that uses those GUIDs?
2. How do the GUIDs match? between on-prem and cloud?
3. Which commands would I use to export and then import?
4. If prior to a user's migration - in a user's on-prem mailbox:
a. an email message is to be deleted in 1 day (after 6 of the 7 days retention)
b. then all email is migrated to Office 365
i. is that email message now going to get be tagged to be deleted with a 7-day tag, correct?
ii. Will the email be deleted after 1 day or 7 days?
Thank you
few questions if I may please...
1. Why do the GUIDs matter - does "something" migrate that uses those GUIDs?
2. How do the GUIDs match? between on-prem and cloud?
3. Which commands would I use to export and then import?
4. If prior to a user's migration - in a user's on-prem mailbox:
a. an email message is to be deleted in 1 day (after 6 of the 7 days retention)
b. then all email is migrated to Office 365
i. is that email message now going to get be tagged to be deleted with a 7-day tag, correct?
ii. Will the email be deleted after 1 day or 7 days?
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow that is really helpful information.
Thank you!
Thank you!
ASKER
Vasil,
So when the mailbox is migrated... the cloud mailbox will have no Retention Policy..correct?
Then once the migration is finalized I simply apply the policy to the mailbox. Then the GUIDs will match up... Is that right?
Also, this would have no effect on Personal Tags created by end users, right? Just Server-Based?
So when the mailbox is migrated... the cloud mailbox will have no Retention Policy..correct?
Then once the migration is finalized I simply apply the policy to the mailbox. Then the GUIDs will match up... Is that right?
Also, this would have no effect on Personal Tags created by end users, right? Just Server-Based?
When a mailbox is migrated, it will automatically be assigned the Default retention Policy in ExO, and the tags defined therein.
Personal tags are still created by admins, so it will work for them too.
Personal tags are still created by admins, so it will work for them too.
ASKER
I suppose PowerShell written in 2009 is not going to be perfect importing data into Exchange Online..
Do you have a updated version of this script by chance?
I am getting messages like this, "The following retention policies aren't in the file and will be deleted: Default MRM Policy.. Do you want to continue? [Y] Yes [N] No"
Granted I still think I can use this script.. I commented out lines that were trying to use older parameters.. otherwise I would get errors like this:
A parameter cannot be found that matches parameter name 'MessageFormatForJournalin g'. etc...
Here are the lines I commented out...for other's future reference:
Also need to run this in Exchange Online
Do you have a updated version of this script by chance?
I am getting messages like this, "The following retention policies aren't in the file and will be deleted: Default MRM Policy.. Do you want to continue? [Y] Yes [N] No"
Granted I still think I can use this script.. I commented out lines that were trying to use older parameters.. otherwise I would get errors like this:
A parameter cannot be found that matches parameter name 'MessageFormatForJournalin
Here are the lines I commented out...for other's future reference:
# $tagExists.LabelForJournaling -eq $tag.LabelForJournaling -and
# $tagExists.MessageFormatForJournaling -eq $tag.MessageFormatForJournaling -and
# LabelForJournaling = $tag.LabelForJournaling
# MessageFormatForJournaling = $tag.MessageFormatForJournaling
Also need to run this in Exchange Online
Enable-OrganizationCustomization
Get a newer Exchange Server media? :) Just checked the Exchange 2013 SP1 DVD, the script there seem to be from 2014 or so. Havent bothered comparing them to older versions.
ASKER
aah much better.. thanks Vasil!
I was down that rabbit hole and forgot to take a breath and think
I was down that rabbit hole and forgot to take a breath and think
ASKER
As long as I dont delete the Retention Policies Default MRM Policy & ArbitrationMailbox.. can I safely delete every single Retention Policy Tags (as long as nobody is using them?)
Will the renaming of TAG allow the GUID to follow the message... speaking of renaming a cloud tag and the mailbox already lives in the cloud.
Will the renaming of TAG allow the GUID to follow the message... speaking of renaming a cloud tag and the mailbox already lives in the cloud.
Are you sure nobody is using them? The fact that they are not added to a Retention policy doesnt mean that users cannot assign them directly (there's a self-service option for this in OWA).
Tag names are just for display purposes, they dont change a thing.
Tag names are just for display purposes, they dont change a thing.
ASKER
So if they are not assigned to a policy .. users can find it in Outlook and use it? regardless of which policy user is assigned?
Yes, but that's for Personal tags only. If you want to prevent them from doing this, remove the MyRetentionPolicies role from the corresponding Role Assignment Policy.
ASKER
good to know.. but in 365 this doesnt occur in my test anyway.. is it different in cloud?
Nope, works like that in ExO too.
ASKER
So does each item in Outlook (that is tagged with a retention tag/guid - viewable with MFCMAPI) not care about the policy that tagged it? That way, when importing tags, we don't have to worry about the fact that Default MRM Policy will not carry the GUID from onprem?
If correct, I suppose the process would be to rename (or delete) the existing (target location) tags that are in the Default MRM Policy and allow the scripts to import the tags (and link them) from on-prem (I don't think the script overwrites tags that are named the same from source to destination). Then (at least for the Default MRM Policy) you will be left with this in the cloud (or any target):
Default MRM Policy (Original cloud/target GUID)
tag01 (GUID from on-prem)
tag02 (GUID from on-prem)
etc..
If correct, I suppose the process would be to rename (or delete) the existing (target location) tags that are in the Default MRM Policy and allow the scripts to import the tags (and link them) from on-prem (I don't think the script overwrites tags that are named the same from source to destination). Then (at least for the Default MRM Policy) you will be left with this in the cloud (or any target):
Default MRM Policy (Original cloud/target GUID)
tag01 (GUID from on-prem)
tag02 (GUID from on-prem)
etc..
The policy doesnt matter as long as the same tags with the same GUIDs are available in the tenant. If the tag is migrated (same GUID) but not added to the policy, items will remain stamped with it and MFA will process them as usual. But if a tag is not found (by GUID) next time the mailbox is processed by the MFA, it will be replaced with the default tag.
ASKER
So I am realizing some crucial element I left out.. that you already said above.
These users that ALL have OnPremPolicy01 on premises, they will receive automatically the Default MRM Policy when migrated to cloud. Is that correct?
I can't just set the imported OnPremPolicy01 as the default policy in the cloud and expect the migrated users will receive it?
The problem is that they migrated 150 users and those 150 users all have Default MRM Policy in the cloud. We have renamed all the cloud retention tags linked to Default MRM Policy so as to not conflict with our retention policy/tag imports.
Must I now...
1. Create another Policy CLOUDRetPolicy01
2. Link the tags that are linked to the cloud Default MRM Policy to CLOUDRetPolicy01
3. Assign all current 150 cloud users the Retention Policy CLOUDRetPolicy01
4. Delete all links from Default MRM Policy
5. Link the imported tags to Default MRM Policy - that match the Retention Policy they have in the cloud
6. Migrate the remaining 2000 mailboxes (they will get the Default MRM Policy with the imported tags)
Am I missing something? How do you migrate a large enterprise with say, 20 policies with 10 unique tags each to Exchange Online when every migrated user will end up with Default MRM Policy?
OR Is there time before the MFA runs and you can just Set-Mailbox -RetentionPolicy and assign the proper cloud retention policy?
These users that ALL have OnPremPolicy01 on premises, they will receive automatically the Default MRM Policy when migrated to cloud. Is that correct?
I can't just set the imported OnPremPolicy01 as the default policy in the cloud and expect the migrated users will receive it?
The problem is that they migrated 150 users and those 150 users all have Default MRM Policy in the cloud. We have renamed all the cloud retention tags linked to Default MRM Policy so as to not conflict with our retention policy/tag imports.
Must I now...
1. Create another Policy CLOUDRetPolicy01
2. Link the tags that are linked to the cloud Default MRM Policy to CLOUDRetPolicy01
3. Assign all current 150 cloud users the Retention Policy CLOUDRetPolicy01
4. Delete all links from Default MRM Policy
5. Link the imported tags to Default MRM Policy - that match the Retention Policy they have in the cloud
6. Migrate the remaining 2000 mailboxes (they will get the Default MRM Policy with the imported tags)
Am I missing something? How do you migrate a large enterprise with say, 20 policies with 10 unique tags each to Exchange Online when every migrated user will end up with Default MRM Policy?
OR Is there time before the MFA runs and you can just Set-Mailbox -RetentionPolicy and assign the proper cloud retention policy?
ASKER
So I did everything in the above comment.
Turns out that if a user had a Retention Policy on-prem and the mailbox was migrated .. it kept the same retention policy.
If the mailbox on prem had no Retention Policy it would get the Default MRM Policy.
Turns out that if a user had a Retention Policy on-prem and the mailbox was migrated .. it kept the same retention policy.
If the mailbox on prem had no Retention Policy it would get the Default MRM Policy.
I'm really starting to loose the thread here :) One of the differences between on-prem and ExO as you noted is that in ExO every mailbox gets stamped with the Default policy, by default. If it was stamped with a different policy on-prem, info about the policy will be synced with the move, however the next time the MFA processes the mailbox it might cause trouble if the relevant tags included in said policy are not found in ExO. Thus the need to sync the tags, and the policy (that is basically a grouping of the tags).
ASKER
Thank you Vasil. This task was completed perfectly yesterday thanks to your help!