majdesber
asked on
Convert Recipient Policies from Exhcange 2003 to Exchange 2010
Hi Guys,
I have Exchange 2010 coexists with 2003, am planning to convert the Recipients Policies of Exchange 2003 to Exchange 2010, I have one forest with 3 tree domains, two of the trees are not migrated to Exchange 2010, as you know the recipient policy is an Exchange Organization level setting, so if i will convert this policy form Exchange 2003 to Exchange 2010 is this going to impact the other trees that are not migrated to exchange 2010 and still using exchange 2003 back-end servers?
Thanks and regards,
M. E
I have Exchange 2010 coexists with 2003, am planning to convert the Recipients Policies of Exchange 2003 to Exchange 2010, I have one forest with 3 tree domains, two of the trees are not migrated to Exchange 2010, as you know the recipient policy is an Exchange Organization level setting, so if i will convert this policy form Exchange 2003 to Exchange 2010 is this going to impact the other trees that are not migrated to exchange 2010 and still using exchange 2003 back-end servers?
Thanks and regards,
M. E
no it will not affect them, just right click and upgraaaaaaaaaaade
ASKER
Thanks Busbar, for double check: i can't right click and update i have to use the following Powershel cml
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} |
Set-EmailAddressPolicy –IncludedRecipients AllRecipients
Set-AddressList “All Users” –IncludedRecipients MailboxUsers
Set-AddressList “All Groups” –IncludedRecipients Mailgroups
Set-AddressList “All Contacts” –IncludedRecipients MailContacts
Set-AddressList “Public Folders” –RecipientFilter {RecipientType –eq “PublicFolder”}
Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact'
-or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistribution List' -or ObjectClass -eq 'group'
-or ObjectClass -eq 'publicFolder'))}
kindly check it and advice.
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} |
Set-EmailAddressPolicy –IncludedRecipients AllRecipients
Set-AddressList “All Users” –IncludedRecipients MailboxUsers
Set-AddressList “All Groups” –IncludedRecipients Mailgroups
Set-AddressList “All Contacts” –IncludedRecipients MailContacts
Set-AddressList “Public Folders” –RecipientFilter {RecipientType –eq “PublicFolder”}
Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact'
-or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistribution
-or ObjectClass -eq 'publicFolder'))}
kindly check it and advice.
ASKER
the second one for converting Address list I know, but i will apply them after.
what do you think?
M.E
what do you think?
M.E
to apply email address onthe migrated users or newly created Exchange 2010 users you will need to upgrade the address policy, so if you are sure that you will not create new users until you upgrade the Address POlicy then you can do that after completing the migration
ASKER
Thanks Busbar,
Actually this is my core question form the beginning I have two domain will not be migrated to Exchange 2010 now they will be later, so these people they will be able to create users and update the GAL?
regards,
M. E
Actually this is my core question form the beginning I have two domain will not be migrated to Exchange 2010 now they will be later, so these people they will be able to create users and update the GAL?
regards,
M. E
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Clear Sir, so I will upgraded so both systems can update the GAL..
tomorrow i will accept the solution after doing it.
thanks.
M. E
tomorrow i will accept the solution after doing it.
thanks.
M. E
you welcome
ASKER
Hi Busbar,
i applied this at my lab environment and it moved the recipient policies successfully, but when i try to create a new policy at the Exchange 2010 i have received an error
" you can't create ............ because Legacy Exchange has been detected"
this is not the exact message but the last five words are correct.
so, now i can't create new policy until i decommission the legacy exchange server, i can't apply this at the live environment, because i might need it.
i have applied this command "Set-EmailAddressPolicy –IncludedRecipients AllRecipients "
please advice..
M. E
i applied this at my lab environment and it moved the recipient policies successfully, but when i try to create a new policy at the Exchange 2010 i have received an error
" you can't create ............ because Legacy Exchange has been detected"
this is not the exact message but the last five words are correct.
so, now i can't create new policy until i decommission the legacy exchange server, i can't apply this at the live environment, because i might need it.
i have applied this command "Set-EmailAddressPolicy –IncludedRecipients AllRecipients "
please advice..
M. E
ASKER
Hi Busbar,
I have one suggestion about this:
for recipient policy, I believe it is normal behavior that you are not able to change the settings as Legacy Exchange is still there.
When we do the "Set-EmailAddressPolicy –IncludedRecipients AllRecipients " this will allow Exchange 2010 to update the clients with current policies, but the ownership of the Recipient Policy will remain with Exchange 2003, which is reasonable as the Exchange 2003 will not understand the Exchange 2010 recipient polices.
PS: when we do Setup.com /preparelagacypermissions one of the changes is to give Exchange 2003 the required permissions to control the recipient policy.
so what do you think?
M. E
I have one suggestion about this:
for recipient policy, I believe it is normal behavior that you are not able to change the settings as Legacy Exchange is still there.
When we do the "Set-EmailAddressPolicy –IncludedRecipients AllRecipients " this will allow Exchange 2010 to update the clients with current policies, but the ownership of the Recipient Policy will remain with Exchange 2003, which is reasonable as the Exchange 2003 will not understand the Exchange 2010 recipient polices.
PS: when we do Setup.com /preparelagacypermissions one of the changes is to give Exchange 2003 the required permissions to control the recipient policy.
so what do you think?
M. E
Hi Majd,
this is strange since you can upgrade the EAP normally without an issue this will not affect the old exchange servers.
I have done zillions ofupgrades and never faced such an issue, can you tell me the exact error message.
when you do the upgrade the owner will be the exchange server 2007 not the 2003
this is strange since you can upgrade the EAP normally without an issue this will not affect the old exchange servers.
I have done zillions ofupgrades and never faced such an issue, can you tell me the exact error message.
when you do the upgrade the owner will be the exchange server 2007 not the 2003
ASKER
Hi Busbar,
please give me some time i will comeback to you, am doing some tests at my lab and i will tell you about the results.
M.E
please give me some time i will comeback to you, am doing some tests at my lab and i will tell you about the results.
M.E