Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Adding other user's Mailboxes on outlook clients

Status
Not open for further replies.

Lowkick

IS-IT--Management
Sep 6, 2007
3
GB
Right!
Situation is, none of our Outlook clients can add other user's mailboxes following our move from Exchange 5.5 to 2003.

This was possible with our old Exchange 5.5 server with Outlook 2000 as the client.

The same methodology is used:

Right click your own Mailbox
Go to Advanced
Go to the Advanced Tab on the next Menu
Add mailboxes in "Open these Additional Mailboxes"

Permissions have been given on Exchange so it's not that either.

The message we get is "Outlook cannot find the specified folder location" - How can we get our Outlook clients to "locate" other folders?

Ta!
Matt
 
Well, it's all pretty much the same in 2000/2003/2007, not that you wanted to hear that.
Take a look at the folder permissions in Outlook. It's far better to do this kind of thing on the client side (even if you use a server side tool to modify client side permissions (did that even make sense?))
What does Outlook say the permissions are?
What actions did you do on the server? (There is more than one way to skin this cat)
 
Outlook hasn't got any permissions specified - as far as I was aware they werent needed? On our old 5.5 server we had to give permissions on exchange then add the mail box on the outlook client and it went straight through.

Actions I took on the server were to add the user who i wanted to give access Owner permissions.

I've since been told that someones got it to work by adding Delegates!

Guess that one's solved.
 
Owner permissions"?
Granting "Full Mailbox Access" in ADU&C is one way of doing it but you open the entire mailbox completely.
"Delegates" is another way of opening it up but really a delegate is used to grant a user to "Send on Behalf of"

It might be an opportunity to assess what is actually required. If you've got one of those environments where everyone gets access to everything then the "Full Mailbox Access" route is fine (note that it grants Send As rights as well). If you just have an environment where the odd person in a team wants to access another guys folder or calendar or whatever else then you might want to just use folder permissions rather than centrally set.

Not that there was anything bad in how it was, there just might be a better/different way.
 
The basic premise of this is that every manager wants to be able to see everyone in their team's mailbox to monitor what they're sending.

The "Owner" permissions on outlook sounded like they'd work, but when trying to open another users folder, it came back to us with the "unable to locate folder" message.

Delegates is the only way we've been able to get remote access so far.
 
Since you've got quite a few to set you might as well get SetPerm: and do this centrally.
If the managers aren't all Domain Admins you shouldn't have a problem. Are they all just plain old users? I'd undo everything in AD first because of a little "quirk" in that membership of some domain groups writes a Deny which then goes and trumps any Permit you manually set.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top