We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Orphaned Mailbox After Exchange Upgrade

joelrob
joelrob asked
on
Medium Priority
574 Views
Last Modified: 2007-12-19
I upgraded from Exchange 5.5 to 2000 SP3 over the weekend on a single Windows 2000 server. All but one mailbox transfered over just fine. The one that will not is still there, it's visible in the folder list, but the user cannot log onto it, the receive permission denied popup. It shows that the box was logged onto by the Administrator (me or server) at 4:00 am this morning, though I was not here. Is there any way to assign the permissions to this particular mailbox to her account? If I create a new mailbox with the same name, it just creates another mailbox, it does not access the existing one. I have a pre-upgrade backup of all mailboxes, can I restore it to the new mailbox being created?

Help!
Comment
Watch Question

Commented:
Try using exmerge to extract the data from that mailbox into a PST and import it into a new one.

XADM: Microsoft Exchange Mailbox Merge Program (Exmerge.exe) Information
http://support.microsoft.com/default.aspx?scid=kb;EN-US;174197

OneHump

Author

Commented:
exmerge does not list the mailbox. The only place I can see the mailbox is in System Manager, under Servers > SERVERNAME > First Storage Group > Private Information Store > Mailboxes.

There's no red X beside it, so Cleanup Agent won't let me at it either.

Commented:
Wow, that very strange. Even disconnected mailboxes show up in exmerge.  If you look at the supposed attached account's attributes in ADSIEdit, do you see values for:

msExchHomeServerName
msExchMailboxGuid
msExchMasterAccountSid


OneHump

Author

Commented:
That's just it, I don't know what account Exchange is saying owns this mailbox. It says that Administrator has logged onto it, but Administrator has it's own mailbox, so it doesn't own this one too. But just to be sure I checked the Administrator account, it only has one mailbox, Administrator, not USERNAME.

Is it possible this mailbox never transfered over from the 5.5 location? Is there a way to find out the GUID of the orphaned mailbox and manually set the new account?

Commented:
I don't know about finding the GUID.  It might be possible with MDBView, but that's a bit of a pain.

Are those attributes blank then for that user object?

OneHump

Author

Commented:
No, I went ahead and enabled a temporary mailbox for her, so those attributes point to that mailbox now. If I find a way to access her old files I will have to export one (the old or the new) into a .pst file and bring it into the other.

I have the backup, but of course that was made before the upgrade, so they're all 5.5 files on the tape. Is there a way to restore those to another location and create a .pst file from there?
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
I went through most of these tips and no effect. Most of them depend on there being a red X beside it in the Information Store. I don't know what happened, but this morning I came in and checked it and today there was a red X. I disconnected the user from the temporary mailbox, connected them to the old one and it came up fine.

I appreciate the time you spent helping out with this.

Commented:
Interesting.  It looks like cleanup is stuck.  You may want to test disconnecting a mailbox to see if cleanup runs within 5 minutes or so to make sure you don't have a problem there.

I'm glad you are fixed.

OneHump
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.