Yes, I was able to follow your instructions and set this up. Not sure if it
matters, but are an on-premise EX2013/EX2010 hybrid shop right now. But
everything I did, I did it on the EX2013 side.  Also, I didn't have to do
step 2 as I logged into a VM as user U and setup the mail profile with
Outlook 2010.  Instead of prompting me for a username/password, it just
used my logged in credentials because user U has full access to the
resource mailbox R.  If you wanted, you could also add user U directly to
resource mailbox R directly with EMS to see if that works:

Add-MailboxPermission "resource R" -User "user U" -AccessRights FullAccess



On Fri, May 30, 2014 at 5:23 PM, Curt Finley <[email protected]> wrote:

>  I have a situation where I'd like to give some users who don't have a
> mailbox of their own *write* access to a resource calendar.  I've been
> able to accomplish this in Exchange 2010 as follows:
>
>
>
> Create a mail enabled security group (called G).
>
> Create a user in Active Directory but no mailbox for that user (username
> U).
>
> Add user U to security group G.
>
> Create a resource mailbox (called R).
>
> Give group G full access permissions to resource mailbox R.
>
> Create an Outlook profile as follows
>
> 1)      Open the profile creation wizard.  When prompted to enter name,
> e-mail address, ... put in the info for R but don't enter a password.
>
> 2)      When it prompts for credentials, put in username G and the
> password for G.
>
>
>
> VoilĂ !  You can open the profile and create calendar entries.
>
>
>
> I've tried the same technique with Exchange 2013 but it doesn't work.
> (Actually my test is in Office 365 but Office 365 is Exchange 2013 isn't
> it?)  I tried making U a mail enabled user but that still doesn't work.  Is
> there something that can be done to give a user *without a mailbox*
> *write* access to a resource mailbox?  I know it seems like it would be
> simpler just to give U a mailbox.  I'll spare you the details but in this
> situation it creates complications I'd rather avoid.
>
>
>
> Thanks for your help.
>
>
>
> Curt
>

Reply via email to