Exchange 2010 install error

I got the following error below when trying to install Exchange 2010 Mailbox role.

Mailbox Role
Failed
Error:
The following error was generated when "$error.Clear(); $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1); if ($arbUsers.Length -ne 0) { $mbxname = $arbUsers[0].name; $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if ($dbs.Length -ne 0) { enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity; } } }" was run: "The LdapRecipientFilter "(&mailnickname=*) " on Address List or Email Address Policy "New recipient policy" is invalid. Additional information: The attribute type '&mailnickname' or its syntax is not defined in the schema.".

The LdapRecipientFilter "(&mailnickname=*) " on Address List or Email Address Policy "New recipient policy" is invalid. Additional information: The attribute type '&mailnickname' or its syntax is not defined in the schema.

The attribute type '&mailnickname' or its syntax is not defined in the schema.

Any help anyone can give to get past this error would be great.
SpiegelMcdAsked:
Who is Participating?
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.

Glen KnightCommented:
This would indicate that the domain had not been prepared for exchange 2010

run the following commands from the Exchange 2010 DVD using setup.com

setup /PrepareLegacyExchangePermissions
setup /PrepareSchema
setup /PrepareAD
0
SpiegelMcdAuthor Commented:
I actually did that before I ran the install. I could try running it again?
0
Glen KnightCommented:
Yes please.
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.

SpiegelMcdAuthor Commented:
One more thing. Since exchange 2010 is installed, I wouldn't have to uninstall exchange to re run the prep?
0
Glen KnightCommented:
No you can just run it.
0
SpiegelMcdAuthor Commented:
Well I re ran
setup /PrepareLegacyExchangePermissions
setup /PrepareSchema
setup /PrepareAD

And I still get the same error. Any other suggestions?
0
thecricketCommented:
Did you ever come to a conclusion as to what the fix was here?  I'm getting the exact same errors and I did run the following:

setup /PrepareLegacyExchangePermissions
setup /PrepareSchema
setup /PrepareAD

Thank you!
0
Satya PathakLead Technical ConsultantCommented:
0
thecricketCommented:
Using the adsiedit tool I was able to find the referecnes in the recipient policy per SatyaPathak link above.  It worked great.  Now if only I had the ability to mark his answer as the acceptable solution.  Guess that is down by the original question owner?
0
SpiegelMcdAuthor Commented:
What I had to do was delete a global policy that was from exchange 2003.
0

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
sndmnsixCommented:
After checking the link that SatyaPathak pointed out, Exchange 2010's mailbox role seems to complain if the recipient policy has an unusual filter or one that doesn't make much sense.  I deleted the attribute filter and recreated it for the recipient policy in a much more simply fashion.  Re-ran the mailbox role install and then it was happy to do it for me.  I could definitely see how just deleting the recipient policy would work as well especially if it just isn't needed.
0
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
Exchange

From novice to tech pro — start learning today.