Because you need delegate access to the calendar, or full access to the mailbox to access it in that format.
Calendar Internet publishing is the only solution I can think of without a mailbox / AD user object within the org. http://technet.microsoft.com/en-us/library/ff607475(v=exchg.141).aspx Sent from my iPhone > On Nov 20, 2013, at 7:56 PM, "Curt Finley" <[email protected]> wrote: > > I received a couple of suggestions that looked promising > > https://email.server.com/owa/[email protected]/?cmd=contents&module=calendar > > and > > https://exchange2010.mycompany.com/owa/[email protected] > > When I try those I get > > This mailbox can’t be opened. For more information, contact your helpdesk. > > The mailbox I’m working with is a resource mailbox. Is that what is causing > the problem? Any workarounds? > > Thanks for your help. > > Curt > > From: [email protected] [mailto:[email protected]] > On Behalf Of Curt Finley > Sent: Wednesday, November 20, 2013 11:10 AM > To: [email protected] > Subject: [Exchange] Calendar access > > I have a user who does not have a mailbox. However, he needs write access a > calendar in an Exchange 2010 mailbox. The way I used to handle this on my > Exchange 2003 server was to give the user permissions to the mailbox and then > have them go to > > https://exchange2003.mycompany.com/exchange/mailboxalias/Calendar > > When prompted they logged on with their own domain account instead of the > credentials for mailboxalias. Since they had permissions to the mailbox they > were allowed access. > > I had my user try > > https://exchange2010.mycompany.com /exchange/mailboxalias/Calendar > > He logged on but it tells him the URL isn’t valid. > > Is there a URL that would work with this technique? Is there an alternate > approach for users who don’t have a mailbox of their own but need to have > write permissions to a resource calendar that is not his own? I have > Internet Calendar sharing enabled for people who just need to view the > calendar but this guy needs to make changes to it. > > Thanks for your help. > > Curt
