Add a new Calendar, choose Synchronise appointments from remote calendar, then pop in the Exchange iCalendar URL:įinally let’s not forget Outlook users from Outlook 2007 onwards iCalendar subscriptions are supported. Although I don’t use Google Calendar I do use iGoogle and it allows me to see my Exchange calendars on my homepage via the Google Calendar widget.) (In my case – this is one aspect I personally like about the feature. You’ll see below I’m subscribing to two Exchange 2010 SP1 calendars – my personal one and my team’s: They pop in the iCalendar URL, and it shows up in the recipients Google Calendar.
![save ics file to outlook 2010 save ics file to outlook 2010](https://www.msoutlooktools.com/img/blog/edit-name-of-calendar.png)
To add the shared calendar to Google Calendar, the end user chooses “Add” then “Add by URL”. For our first example, let’s have a look at Exchange’s primary competitor, Google Apps. Opening the calendar by the recipient is easy enough. The user can now either copy the links from this page, or via “Share” choose “Send Links to This Calendar…” which opens a new email with the two URLs attached. If they’re using Outlook 2010 ( beta ), the user right clicks the calendar they want to share, chooses “Share” and again, it’s listed as “Publish This Calendar…”Īfter clicking “Publish This Calendar…” via OWA or Outlook, the options can be chosen including the detail to show, the date range and the type of access:Īfter clicking “Start Publishing”, the links are generated: Exchange 2010 SP1 doesn’t disappoint as the feature is listed in both OWA and Outlook in the same place as other calendar sharing options.įor an OWA user, they select the calendar they want to share, then choose “Share”, and the option is listed as “Publish This Calendar…” If a feature is going to work well it has to be easy for a user to find and configure. Now you know a little more about the new feature, let’s take a look at how it comes together from a user perspective, and how it’s configured by the admin. So there is some risk in enabling the facility, but by default no user’s calendars are shared, and there are a number of controls available to user and admin to pull the feature in line with the business and individual user’s requirements. 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.
![save ics file to outlook 2010 save ics file to outlook 2010](https://mthomas.co.uk/uB3x4Y8WrnJzNbEKfR9Z/wp-content/uploads/2011/01/Appointment.png)
Getting back to the anonymous part, there are two options.
#SAVE ICS FILE TO 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.
![save ics file to outlook 2010 save ics file to outlook 2010](https://www.softwarepro.org/blog/wp-content/uploads/2018/11/1.png)
![save ics file to outlook 2010 save ics file to outlook 2010](https://www.taskmanagerfix.com/screens/pst-xtractor/pst-conv-4.png)
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.