Re: Best replacement for "de-emphasized" shared mailboxes in 2007?
- From: cjg.groups@xxxxxxxxx
- Date: Fri, 7 Dec 2007 11:37:47 -0800 (PST)
On Dec 4, 4:04 am, Brendan Erofeev <bren...@xxxxxxxxxxx> wrote:
cjg.gro...@xxxxxxxxx wrote:
On Nov 28, 5:08 pm, "Mark Arnold [MVP]" <m...@xxxxxxxx> wrote:
On Wed, 28 Nov 2007 13:58:49 -0800 (PST), cjg.gro...@xxxxxxxxx wrote:
Hello, what is the best practice for creating Exchange 2007 mailboxesHmm. To be honest I would just carry on as you are. It's a safe
which allow access to multiple users? ie: How to create the address
i...@xxxxxxxxxxxxx which many users will be responsible to read and
reply as?
Shared mailboxes seem perfect for the job, but Microsoft considers
them de-emphasized. They recommend resource mailboxes or SharePoint,
neither of which fit my need. Also, I'd prefer to have my shared
mailboxes accessible in the Management Console, though shared
mailboxes are not.
Is there anything wrong with emulating shared mailboxes with user
mailboxes assigned to disabled user accounts? I could assign
permission to the actual users who are responsible for the account.
And it would be visible and manageable through the Console, not
forgotten in the Shell.
Why would MS de-emphasize such an important account type? Thanks for
your input.
business solution in that it's what you know and if there isn't a need
to change or the other options aren't suitable for you then just going
on as you are is perfecty fine.
Thanks. I will create user mailboxes, then disable the underlying
user, and give the real users access to the mailbox. I hate to misuse
the "user mailbox" type when "shared mailbox" is made for that job.
But if shared mailboxes don't show up in the Console, then they will
be harder to keep track of.
If anyone can think of a reason to use true shared mailboxes, please
reply. Thanks.
Maybe I am wrong, but doesn't a users mailbox become inaccessible when
you disable the associated account?
From the TechNet description of a Shared mailbox:"The Active Directory user that is associated with a shared mailbox
must be a disabled account."
http://technet.microsoft.com/en-us/library/bb201680.aspx
Now, that's a specific type of mailbox, different from a User
mailbox. Since a Shared mailbox doesn't show up in EMC, I'm trying to
emulate that using a User mailbox; disabling the underlying account
and all. But is that a recommended practice?
My test Exchange server is not complete enough for me to test this. I
simply changed the permissions on a general user mailbox to provide
access to actual users. Here is the process:
ADUnC > Create new user whose name matches the general e-mail address
username.
EMC > Recipient > New Mailbox > Existing user > Browse for it > add to
proper storage group and database.
ADUnC > disable the user.
EMS > Add-MailboxPermission -Identity "<generalaccount>" -User
<realuser> -Accessright Fullaccess -InheritanceType all
EMC is Exchange Management Console
EMS is Exchange Management Shell
.
- References:
- Re: Best replacement for "de-emphasized" shared mailboxes in 2007?
- From: Brendan Erofeev
- Re: Best replacement for "de-emphasized" shared mailboxes in 2007?
- Prev by Date: Re: Urgent!
- Next by Date: Exchange 2007: How to create a regular expression in a transport rule that EXCLUDES a pattern string?
- Previous by thread: Re: Best replacement for "de-emphasized" shared mailboxes in 2007?
- Next by thread: Exchange 2007 - message tracking on HT - problem when searching by sender address
- Index(es):
Relevant Pages
|