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
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

BusbarSolutions ArchitectCommented:
no it will not affect them, just right click and upgraaaaaaaaaaade
majdesberAuthor Commented:
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 'msExchDynamicDistributionList' -or ObjectClass -eq 'group'
-or ObjectClass -eq 'publicFolder'))}

kindly check it and advice.
majdesberAuthor Commented:
the second one for converting Address list I know, but i will apply them after.
what do you think?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

BusbarSolutions ArchitectCommented:
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
majdesberAuthor Commented:
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?
M. E
BusbarSolutions ArchitectCommented:
let us split it into 2 parts:
1- if you upgraded the AL, then both admins in both domain will be able to create users and update the GAL.
2- you didn't update the AL, users can be created only on the Exchange 2003, GAL will be updated.
Hope that it is clear now. :)

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
majdesberAuthor Commented:
Clear Sir, so I will upgraded so both systems can update the GAL..
tomorrow i will accept the solution after doing it.
M. E
BusbarSolutions ArchitectCommented:
you welcome
majdesberAuthor Commented:
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
majdesberAuthor Commented:
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 /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
BusbarSolutions ArchitectCommented:
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
majdesberAuthor Commented:
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.

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

From novice to tech pro — start learning today.