When adding users in AD no not all mail addresses get populated on some accounts despite creating an Exchnage mailbox?


Just some background, We moved our Mailbox location from  C: to E: due to space on C:

When creating users in Ad ive oticed that not all mail addresses get populated despite selecting to add an Exchange mailbox. I created four users yesterday and they were fine, but some of the users from today dont have all mail addresses. the confusing part is some work and some don't. They should have the one linking it to the domain I.E. dom1.local and then we add another SMTP email which is there email account.

Is this something to worry about or is it nothing and it will appear randomly.
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.


This sounds like a RUS problem, did you look in event viewer / application, what's there.
YellowbusTeamAuthor Commented:
There is one error in the event viewer / application that i think may be related to the issue?

Source: MSExchangeAL
Event ID: 8026

LDAP Bind was unsuccessful on directory DBDSVR!.dbdom1.local for distiguished name ". Directory returned error:(0x51) Server Down.

does this give you any ideas?
Here are some articles from another site,also with kb articles and solutions:
This error indicates a problem with the domain controller, try to switch the DC.

- Error code: 0x51 - As per Microsoft: "The Recipient Update Service (RUS) is configured to use the DC that you demoted. When RUS tries to query the DC for an update, it cannot reach the DC". See M272552 to fix this problem.

As per Microsoft: "Lightweight Directory Access Protocol (LDAP) allows you to query and manage directory information using TCP/IP. This event indicates that an LDAP connection failed. The error code/error message will indicate the underlying cause". See MSEX2K3DB for additional information on this event.

Anonymous (Last update 5/10/2004):
If the RUS is configured to point to a DC that does not have the FSMO role of "Infrastructure Master", then the RUS cannot update AD. Microsoft best practices for FSMO role placement (M223346) say that "as a general rule, the infrastructure master should be located on a nonglobal catalog server". This might be counter-intuitive and lead to the mistake of configuring the RUS to use a GC that is not an IM.  

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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

YellowbusTeamAuthor Commented:

Will this be causing the exchange email tab in AD not to display the user email address with the domain?
that also but the articles above explain this in more depth
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.