Error updating public folder with busy machine slow when kasperky is updating
You can then add your department group or individual people from within your organization for whom you’ll grant appropriate Read and/or Write permissions to your Calendar so only they can see you availability and, if set, your whereabouts.
If you are in an Exchange 2010 or earlier environment with Outlook 2003 support enabled (basically any environment with Public Folders enabled), then legacy Free/Busy information is also published to the Public Folders and can be read by Outlook 2003 clients.
RPC-over-HTTPS with the server's external DNS name specified as proxy (this is what autodiscover defaults to, but also when manually configured) - no free/busy information shown for any user, same as from outside.
After setting EWS to NTLM authentication Outlook 2007 clients started seeing everything, but Outlook 2003 problem remains - free/busy information is available only for users created after migration.