Recent content by szeller

This was working for Outlook 2010 for the one user that upgraded to Outlook 2013. The other two users did a fresh install of Outlook 2013 and were pointed to the same directory that all of the extant Outlook 2010 users have successfully been using for a year or so.

We are pursuing other solutions with calendaring since my queries to Microsoft were not immediately helpful: http://answers.microsoft.com/thread/42a89c5b-fb18-4e31-935b-f8855daa0f6a...

The original FreeBusy directory resided on a share from a Windows 7 Pro VM running under Hyper-V on Windows Server 2012. That share had been having some network connectivity issues, but resolving those made no difference (i.e. .vfb files still were not appearing). I then moved the FreeBusy...

After finding this article, I had one user change their settings from 'file:\\' to 'file://\\', but that made no difference. Their .vfb file has yet to appear.

The third user is also noticing the problem with the Publishing textbox field not persisting any changes. One user downloaded the latest Microsoft updates and the problem persists. Thanks for looking into this!

A third user (also with a fresh 2013 install) appears to have everything set up correctly, but is not generating a .vfb on the workgroup share. This user is also seeing values not persist for the Publish field. In fact, he changed it from 335 to 36, OK'd out and restarted Outlook only to find...

Thank you for confirming that IFB (what we're using) is a different beast (I'm not always sure given the frequency of technology rebranding) than the Public Folders FB. Of the two that are on Outlook 2013, only one (who upgraded from 2010, rather than a fresh install of 2013) is have a...

When all of the users in our workgroup (no Windows domain in our office) were running Outlook 2010, we set up a FreeBusy shared folder on a common network share. This worked very well. Some of us have begun to migrate to Outlook 2013 and the Free/Busy functionality has stopped working for...