• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 502
  • Last Modified:

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

Hi,

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.
0
YellowbusTeam
Asked:
YellowbusTeam
  • 4
  • 2
1 Solution
 
florin_sCommented:
Hi,

This sounds like a RUS problem, did you look in event viewer / application, what's there.
0
 
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

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

does this give you any ideas?
0
 
florin_sCommented:
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.  
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
YellowbusTeamAuthor Commented:
Hi,

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