asked on

Calendar Publishing from unfederated Exchange 2010 server (hosted)

Hi Folks,

I have a need to publish a customers calendar in order for it to be viewed (only) by another user within a separate exchange organisation - they also don't share a common server hosting, one in UK one in Paris. For discussion here lets call User1@company1.com the person I need to publish the calendar for and user2@company2.com the user who needs to view it.

I'm advised that it is possible to publish user1's calendar either through OWA or Outlook for access by User2 using a WebDav server. However I can't find much about how to establish a WebDav server for this need.

Can anyone confirm that this is possible and:
1. Point me at the suitable supplier of WebDav serves . . . dropbox or Box ????
2. State what the limitations of publicly sharing a caledar in this way are.
3. Clarify how WebDav differs from CalDav and perhaps how i could acheive the above using this technology/protocol.

I only seem to get negative reports when I google these topics . . should I be wary ???

In Outlook 2016 I see I can publish my own Exchange 2010 based calendar to the internet using WebDav and I'm prompted to provide the location where the files should be placed. I'm assuming I can't just use any old webspace here, it has to have a WebDav service operational? Confirmation and more besides would be helpful.

Regards

Jackie Man

It is not an easy task but it is technically feasible.

How to get a free WebDav?

1. Use any browser and sign up for a free MS account at signup.live.com using the email address of User1@company1.com.

Essentially, it is the same MS account to access MS Apps Store and Win 10.

2. Signon MS account and goto onedrive.live.com and it is a Free 5GB OneDrive and it is more than enough for a public folder.

In the URL of your browser, you will see https://onedrive.live.com/?id=root&cid=################

where ################ is the unique identifier in MS Live, the 16 characters after id=

3. Add OneDrive as a Network Drive

Briefly, head to OneDrive, open any of your folders and copy ################. Then head to This PC in your File Explorer. In the Computer tab, click Map network drive. Where it says Folder:, paste in the characters you just copied and preface them with this URL: https://d.docs.live.net/ The result should look like in the screenshot below. Make sure both Reconnect at sign in and Connect using different credentials are selected, then click Finish, and log in with your OneDrive username and password.

In case you set up two-factor authentication for your Microsoft account, remember that you need an app password for this to work.

4. The new network drive is the location where the files should be placed for the publish of Exchange 2010 based calendar.

5. There are two options, but I have not tested the second yet.

The first option will work for sure as you can just give the credential for accessing onedrive.live.com to the other organization.

The second option is to create a folder within onedrive and share that folder to the MS account of the other organization.

6. The other organization can do Step 3 and map the onedrive as a network drive in their computer and ask Outlook to open the Exchange 2010 based calendar saved at that location.

Reference:

http://www.makeuseof.com/tag/substitute-onedrive-placeholders-windows-10/

https://blogs.msdn.microsoft.com/robert_mcmurray/2014/09/30/using-the-webdav-redirector-with-onedrive-part-1-standard-security/

Jian An Lim

just want to make sure you know there is an inbuilt tool via http

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-internet-calendar-sharing-exchange-server-2010-service-pack-1-part2.html

you don't really need a WEBDAV server and webdav is old protocol and not forward compatible.
this method also valid to exchange 2013/16

SOLUTION

Trevor White

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jian An Lim

that will seems a it hard if it is hosted exchange

first, you need to able to access to the server and follow this first part

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-internet-calendar-sharing-exchange-server-2010-service-pack-1-part1.html

If you can follow it, then you are dead in the water anyway, WEBDAV will require more changes.

TrevorWhite

ASKER

Hi Jian,
Since this is Hosted Exchange we have no access to the Server - There are SysAdmins that support the service but it would be impractical for specific changes to be made just for us as these may not be compatible with other user needs.

I think this is why WebDav exists and is available for when a non EXchaneg server is in use or when the EXchange server is hosted and/or Unfederated - and I still don't know what 'Unfederated' means in terms of Exchange Server config limitations.

Regards

SOLUTION

Jackie Man

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jian An Lim

There is no cloud in place as it is just a exchange hosted environment

anyway,

you need to setup a new WEBDAV server
and given that, this only works between Outlook and Webdav, and your end user need to manually pushlish it on every changes

https://blogs.msdn.microsoft.com/spike/2011/10/25/how-to-publish-a-calendar-from-outlook-to-iis-and-webdav/

It is not the best but at least deliver something

TrevorWhite

ASKER

Outlook states that the default server publish frequency can be used. We haven't finished testing yet but will advise if this is indeed an issue (auto updating)

REgards

ASKER CERTIFIED SOLUTION

TrevorWhite

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

TrevorWhite

ASKER

Apart from Jackie's link to help define what unfederated meant the other submissions weren't really helpful. I did state that we were on a hosted Exchange platform and as such it should have been obvious that there would be little scope to configure a shared server (if at all)

I hope my findings help someone in a similar situation.

Regards