Solved

Exchange 2007 missing Mailbox, user still in AD

Posted on 2013-06-17
3
347 Views
Last Modified: 2013-06-17
So I have a handfull of users who are suddenly not in my EMC/ OAB, but her profile is still in AD. I did change a few of the AD FSMO roles on Friday... is that related perhaps?
I already tried running the clean-mailboxdatabase command, and the mailboxes aren't in the disconnected mailbox folder.

UPDATE: So it indeed seems to be AD related. The DC/ main AD server has the users in users and computers, but the older AD server does not. Is there a way I can force exchange to pull from my main AD server? Or can I update this older one from the new server? (I plan to decommission it, but not during business hours.)

This is a high priority for me, so I appreciate any response.
0
Comment
Question by:biofishfreak
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 52

Accepted Solution

by:
Manpreet SIngh Khatra earned 500 total points
ID: 39254165
So I have a handfull of users who are suddenly not in my EMC/ OAB, but her profile is still in AD. I did change a few of the AD FSMO roles on Friday... is that related perhaps? - No only if replication issues between DC's

Dont change DC's but try to resolve the AD replication issue .... ideally i would get the FSMO roles back and then check whats wrong with the other server not updating

- Rancy
0
 
LVL 3

Author Comment

by:biofishfreak
ID: 39254195
I ultimately want to decommission this problem prone server- do I need to resolve these replication issues first, or can I just demote as a AD server?
0
 
LVL 3

Author Comment

by:biofishfreak
ID: 39254652
Alright, so I figured out that the reason was indeed that exchange was pointing to DC2, which is having replication issues. I've begun working through the process of mitigating that error (the clocks are synced!), but I needed a more immediate fix. The solution was to manually exclude the DC2 using
set-exchangeserver $XCNGSRVR -StaticExcludedDomainControllers:DC2

Open in new window

where $XCNGSRVR is the exchange server name
and where DC2 is the domain controller to be excluded
I figured out that I can remove the setting by running the same command, but change DC2 to "$Null".

This is for the next poor soul who comes across this. In reality though, you're right Rancy- I need to clean up my $hit in AD.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question