On top of this, the admin can restrict via sharing policies the maximum amount of information users can publish, and sharing policies can be tied to a certain set of users. Additionally, the user can restrict what will be shown for each calendar they choose to publish. The other option is a “restricted” URL with an obfuscated URL. The end user can publish a calendar with a “public” URL that is searchable. Getting back to the anonymous part, there are two options.
Accept google calendar in outlook 2010 software#
The recipient then can simply refer to the calendar via a web browser, or by using any iCalendar compliant software or web app they can subscribe to the shared Calendar. They then receive a set of URLs that they can share via email. The ability to publish calendars with anonymous viewers (and that’s an important point, which I’ll come back to) means that should the admin enable it, the user can now go in via OWA, select the calendar they wish to share and choose to publish it. Only with open standards can this happen and with SP1 that’s now a reality.
While a workaround might be to create partner mailboxes or use third party software, it would be nice to have a solution that “just works” and enables the business to collaborate with partners easily without worrying too much about what technology each other uses.
Some organisations will move to it over the next year or two but lets face facts – some enterprises out there may move to Google Apps, Zimbra or something else, so Federated Sharing isn’t going to be an option. And this new features doesn’t replace federated sharing, however if you want to share calendars now is that the world doesn’t run Exchange 2010. So – why is this useful? Doesn’t Exchange 2010 already have improved Calendar sharing with the new federated sharing features available from RTM? Well, yes it does. One of the new features available in Exchange 2010 SP1 and higher (including SP2 and SP3) that I’m excited about (and already making use of) is the ability to share calendars from Exchange either in iCalendar or HTML format.
0 kommentar(er)
