Share your Knowledge

Monday, March 9, 2015

collaboration mailbox types

site mailboxes, public folders, shared mailboxes for collaboration

site mailbox - requires exchange 2013 for emails and sharepoint for document storage portion

documents viewable via outlook 2013 or sharepoint vis web

The emails and documents kept in separate storage locations are accessible through the same client interface.

a site mailbox has sharepoint 2013 site membership (owners and members)
shareed storage through exchange and sharepoint
end-user clients using outlook 2013 or shaerpoint 2013 but not OWA

shared mailboxes

_Public Folder mailbox

became dumping ground for data

with exchange 2013 you need to first create a public folder mailbox

legacy exchnage required the creation of public folder database

within the publlc folder mailbox you create public folders that contain the actual content

replication of public folder not needed. Can't bring public folders to close to users. User access public folder mailbox on the exchange server it resides.. Now, DAG protects mailbox.

the first public folder mailbox contains the master heirchy information

you can mail enable a public folder so that email can be sent directly to it and establish quotas.

scenario

create public folder mailbox and 3 public folders based on location (Trindad, Miami, London),. Mail-enable Trinidad public folder.

Note that this public folder mailbox contains the primary heirarchy information.

default quota will be based off the mailbox database so if it is tied to the user mailbox database the default quota maybe too small for a public folders. A seperate mailbox database could be creaated to be used for public folder mailbox with appropriate quota.

create public folders

Now you can create sub-folders

public folder permissions

delegate and establish administrative level of the folder

Now a user can create and manage public folder.

Outlook access to the public folder

user has owner permissions

Clients and mobile management

client management = policies

exchange includes a variety of different methods to control features for example through virtual directories or through polices (outlook web app policies and Mobile Device Mailbox policies)

virtual directories

client protocls used for access to 2013 can be controlled through virtual directories

a virtual directory is used by IIS to control access through ActiveSync connections, OWA, Autodisciover and so on.

You can manage authentication, security and reporting settigs

you can mamage virtual directoired through the EAC, EMC, IIS Manager (depending on task)

Virtual directory settings vs Policy Settings

virtual directory settings are made through the servers feature

policies might be under the permissions feature for OWA or Mobile feature for Mobile Device Mailbox policies

polices override virtual directory settings
no authentication confilcts
there are default OWA and ActiveSync (aka Mobile Device) policies created when you install Exchange
Only one policy (one for OWA and one for ActiveSync) can be applied to a mailbox at a time and if no policy is applied the virtual directory settings apply

Outlook Web App Virtual Directory and Policy Features

conflicts may occur

virtual Directory Property Tabs