Newly created AD users are not showing up in Exchange 2016

JuMa 0 Reputation points
2023-04-29T04:58:23.54+00:00

This issue just started happening after I migrated my Public Folders from Exchange 2010 to 2016. Not quite sure if it is related, but I thought it was worth mentioning.

For some reason, when I create a new AD user it no longer shows up in EAC.

Anyone has any ideas what could be causing this?

I've checked syncing between my 2 domain controllers and syncing is good.

I also checked the current domain controller Exchange is using and that also looks good.

Any help would be greatly appreciated.

Thank you,

Joan

Exchange | Exchange Server | Other
Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Kael Yao 37,746 Reputation points Moderator
    2023-05-01T01:28:26.4366667+00:00

    Hi @Joan,

    Did you create the new AD user in Active Directory or in Exchange Admin Center/Exchange Management Shell?

    If the user was created in AD, by default he doesn't have an Exchange mailbox, thus he would not be displayed in
    Exchange.

    Please try creating a new user in EAC and see if the issue persist.

    How to: Create user mailboxes in Exchange Server


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Limitless Technology 44,766 Reputation points
    2023-05-02T15:30:19.49+00:00

    Hi,

    I'd be happy to help you out with your question. Sorry for the inconvenience caused.

    There are several possible causes of this issue. The first thing to check is whether the Exchange Address Book Service is running on your server. You can verify this by opening the Services console and looking for the Microsoft Exchange Address Book service. If it's not running, start it and see if that resolves the issue.

    Another possible cause is that the user object in Active Directory may not have an email address associated with it. Exchange relies on email addresses to identify and display user accounts, so it's important to make sure that the user has an email address.

    It's also possible that the new user is not showing up in the appropriate Address List in Exchange. You can verify this by checking the Address Lists in Exchange and making sure that the new user is listed in the appropriate Address List.

    If the user is missing Exchange attributes, that could also be causing the issue. You can use the Exchange Management Shell to check whether the user has the necessary Exchange attributes, and if they are missing, you can use the Set-User cmdlet to add them.

    Another possible cause is an issue with Active Directory replication. You should verify that replication is working correctly between your domain controllers.

    If you're using Exchange 2016 in a coexistence scenario with an earlier version of Exchange, you should also check the Recipient Update Service to make sure it's running and configured correctly.

    Lastly, it's possible that the user is hidden from the Global Address List (GAL). You can use the Exchange Management Shell to check whether the user is hidden from the GAL.

    If you have any other questions or need assistance with anything, please don't hesitate to let me know. I'm here to help.

    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.