Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1371
  • Last Modified:

Outlook mapped mailbox showing unread but unable to see them

Hello EE,

We have a few meeting rooms which we have converted from user type to room type account on exchange 2010. This used to work when everything was on exchange 2003.

Anyway, to the point, after the migration, users are unable to view any unread emails eventhough it says there's unread emails in the Inbox.

We are running Outlook 2007 and Exchange 2010 (Migrated from Exchange 2003).

I hope someone can help us out.

Cheers,
Goraek
0
goraek
Asked:
goraek
  • 4
  • 4
1 Solution
 
PartnerTekCommented:
Can you see the messages in OWA?
0
 
MegaNuk3Commented:
Those items are probably marked as 'Private' and therefore cannot be read/seen when the mailbox is accessed as an additional mailbox.

If they create another outlook profile and attach to the mailbox as a primary mailbox can the items then be seen?

Do the users have Full Mailbox access to the room mailboxes?
0
 
MegaNuk3Commented:
Have a look at this link:
http://www.msoutlook.info/question/58
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
goraekAuthor Commented:
Users have full access to the room mailboxes.
They should be able to see everything as if its their own mailbox.

However, when they receive an email they cant seem to see it... weird..
0
 
goraekAuthor Commented:
I have tried the link that MegaNuk3 has provided, still not able to see....

Any other ideas?
0
 
MegaNuk3Commented:
What happens if a new Outlook profile is created with the resource mailbox as the primary mailbox can the unread items be seen then?
0
 
goraekAuthor Commented:
We have found the solution - we needed to upgrade the exchange compoents after the migration from exchange 2003. It was left untidied and wasn't cleaned up properly.
Thanks for all your assistance.
0
 
MegaNuk3Commented:
Did you upgrade to Exchange 2010 SP1 or something?
0
 
goraekAuthor Commented:
Nope, we just had to upgrade the components via the shell command line (it only works via shell). Once we have done that, we needed to reconfigure the mailboxes and applied appropiate permissions to match our requirement.

If this was a new Exchange 2010 installation, this would not happen, you only need to do the upgrade when you migrate from previous version of Exchange - its a bit weird, but you can read up on the Microsoft Technet site for more detailed instructions.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now