Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 581
  • Last Modified:

E-mail Address Polciyies

I just finished setting up Exchange 2010.  We still have Exchange 2003 servers as well.  Now my e-mail address policies are not working.

I have 40 e-mail address policies that assign e-mail addresses based on OU and now that is not working.

When I modify or create new policies I receive the following message:
You can't specify the recipient container because legacy servers are detected.

I use to be able to do this.

Thanks,
Ray
0
mestek
Asked:
mestek
  • 4
  • 2
1 Solution
 
mestekAuthor Commented:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01


Edit anemostat.com (Carson)
Failed

Error:
You can't specify the recipient container because legacy servers are detected.

Exchange Management Shell command attempted:
set-EmailAddressPolicy -IncludedRecipients 'AllRecipients' -ConditionalDepartment @() -ConditionalCompany @() -ConditionalStateOrProvince @() -ConditionalCustomAttribute1 @() -ConditionalCustomAttribute2 @() -ConditionalCustomAttribute3 @() -ConditionalCustomAttribute4 @() -ConditionalCustomAttribute5 @() -ConditionalCustomAttribute6 @() -ConditionalCustomAttribute7 @() -ConditionalCustomAttribute8 @() -ConditionalCustomAttribute9 @() -ConditionalCustomAttribute10 @() -ConditionalCustomAttribute11 @() -ConditionalCustomAttribute12 @() -ConditionalCustomAttribute13 @() -ConditionalCustomAttribute14 @() -ConditionalCustomAttribute15 @() -RecipientContainer 'mestekcorp.com/USA/CA/Location/Users' -EnabledEmailAddressTemplates 'X400:c=US;a= ;p=MestekCorporate;o=Exchange;','SMTP:%1g%s@company.com' -Name 'domain.com (Company)' -Identity 'domain.com (Company)'

Elapsed Time: 00:00:01
0
 
RepilCommented:
You can convert the Recipient Policies to Exchange Server 2010 Email Address Policies. This article will be of your help

http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
nipponsoulCommented:
If 2003 servers are not decommissioned yes do NOT follow any instruction about deleting the  CN=server via ADSIEdit.

Check this out too by the way:


http://terenceluk.blogspot.com/2011/08/modifying-exchange-2010-e-mail-address.html
0
 
mestekAuthor Commented:
Repil, thinks for the link.  I believe this is the process that caused my the problem. That the last thing I did before having issues.
0
 
mestekAuthor Commented:
I resolved my issue by recreating the policies in Exchange 2003.  Thanks for the links and information.
0
 
mestekAuthor Commented:
Solved by recreating policies on Exchange 2003.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now