Link to home
Start Free TrialLog in
Avatar of Jim Nicolis
Jim NicolisFlag for Australia

asked on

How to remove a corrupt mailbox from a user in Exchange 2013 SP1

I have a user with a corrupt mailbox. All other mailboxes are ok.
How do I disconnect or delete the mailbox without deleting the user from active directory and assigning a new mailbox?
ASKER CERTIFIED SOLUTION
Avatar of Gareth Gudger
Gareth Gudger
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Great. Let me know if you have any further questions.
Avatar of Jim Nicolis

ASKER

This might sound like a silly question but here goes.

I have recently upgraded from Exchange 2003 to Exchange 2013. Big Jump
So I don't have much experience in the versions between these.
I am a IT professional so have managed to get everything going.

Couple of things aint working.

Mobile phone not connecting via activesync
POP or IMAP not accessible either, have checked firewall and windows firewall all set ok
DNS records are ok.

and 1 more dumb question

I am used to the exchange 2003 way of connecting e.g outlook 2007 to exchange where you just enter the exchange server and the user and it finds both in AD and completes the connection. Does this work the same way or do you have to use the connect to exchange using http under the Outlook anywhere section.
It should just automatically configure the Outlook clients for you. Did you crate an autodiscover record externally and internally?

One great tool to check ActiveSync problems is the Exchange Remote Connectivity Analyzer. This is pretty good at pinpointing what is wrong. Check the ActiveSync test.
https://testconnectivity.microsoft.com/
I did create a external autodiscover record but not a internal. I assume just a A record pointing to the exchange server IP?
Its more if you have split-brain DNS in place. Where you have a copy of your external namespace but internally on your internal DNS servers. If you have that, then yes, you will need an internal autodiscover A record pointing to the internal IP of the CAS server.