Link to home
Start Free TrialLog in
Avatar of ostech25
ostech25

asked on

Help with "Accepted Domain" and "Email Address Policy"

So, we've added a new accepted domain and I created a new email address policy. It gave the correct priority, but the "Applied" value changed to "true". I was under the assumption that our Priority #1 "Main DOMAIN" is supposed to have the value "true", it is now "False" after we added the new email policy.

--Question, should it be turned back to "True" and applied throughout our domain? Also, when I try adding a new mailbox, the new accepted domain isn't available. Please advise. Thank you.
ASKER CERTIFIED SOLUTION
Avatar of sunnyc7
sunnyc7
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ostech25
ostech25

ASKER

This is an Exchange 2007 CCR Clustered environment. We have 29 domains and the newest one needs the lowest priority. My main concern is that when I added the new EAP it became Primary and I'm worried that this could cause an issue with our primary domain, with a priority "1".

Changing it back to "true" won't harm anything will it?
And, more importantly why won't the newly added domain show up in the @newdomain.net in the new mailbox creation.
nope it wont. @ changing back.
ok, that is all fine and well, but the new created EAP still has the value set to "true" and all other 28 EAP's are set to false. How can I get that back to "false"?
Yes, this did work, but I still need to change the newly added Email Address Policy to $False
--I followed this command:
Get-Mailbox -OrganizationalUnit "ou-name" | Set-M
ailbox -EmailAddressPolicyEnabled:$False

And the value remains true. Also, the email address is not showing up when you want to create a new user with that @newdomain.com extension.
Thanks for the points. The EAP needed to be changed to false.
I will research this and let you know...