When a shared mailbox is created, a user account is created and automatically disabled. The password is unknown since the intent is not to use that account, but give 'shared' access to other email users.
You're going to either have to create an AD account with an Exchange mailbox, or you might be able to get away with a "Mail User" recipient object, but you'll still need to create an AD ac
I tried a Mail Contact on one of my servers before replying to your question; sorry I didn't elaborate. When I tried to add an object to a shared mailbox, I could not add a Mail Contact; it won't find the object. What I did find was you could add a Mail User, as well as obviously someone with a full mailbox. I didn't complete the entire task because the only 'mail user' we have is one of the System Mailboxes. It should be a quick process for y
There are no options to set client connectivity for a mail user; at least not through the EAC. Very limited options via shell: https://technet.microsoft.com/en-us/library/aa996335(v=exchg.150).aspx
I don't think using a 'mail user' is the option you're looking for; you might need to create an AD account and then a regular user mailbox. You can allow OWA access from anywhere and they can open the 'shared mailbox' as another user's ma
There are no options to set client connectivity for a mail user; at least not through the EAC. Very limited options via shell: https://technet.microsoft.com/en-us/library/aa996335(v=exchg.150).aspx
I don't think using a 'mail user' is the option you're looking for; you might need to create an AD account and then a regular user mailbox. You can allow OWA access from anywhere and they can open the 'shared mailbox' as another user's ma
Since a 'mail user' doesn't truly have an Exchange mailbox, they can't use OWA. You need a mailbox to utilize OWA, then once you're signed in, you can use the "Open another mailbox..." functionality to access the shared mailbox.Sorry how do you mean by no options to set client connectivity? Isn't by having an AD account the user would be able to login via the OWA?
Sorry how do you mean by no options to set client connectivity? Isn't by having an AD account the user would be able to login via the OWA?
Since a 'mail user' doesn't truly have an Exchange mailbox, they can't use OWA. You need a mailbox to utilize OWA, then once you're signed in, you can use the "Open another mailbox..." functionality to access the shared mai
Here's an excerpt from a TechNet article:
"The Enable-MailUser cmdlet mail-enables an existing user in Active Directory by adding the attributes required by Microsoft Exchange. The user's identity and an external email address are required. Mail-enabled users have an email address at the Exchange organization (for example, john@contoso.com), but they don't have an Exchange mailbox. Email messages addressed to the mail-enabled user are sent instead to the specified external email address."