Just like the functionality of a mailbox, you would also allow users to send an email on behalf of that mail-enabled public folder. They are also assigned an email address (also known as SMTP address). What is that? Well, you could allow a folder to receive mail. Public folders also had the ability to be mail-enabled. For example, all finance people could access a certain set of folders whereas the rest of the organization would not even see those folders within Outlook, so they could not access them. Mostly all users today have access to Outlook, and this essentially would add public folders to their Outlook where they could view a set of folders they were given access to. Public folders were designed for an easy way to share content in an organization with multiple users and groups. Before we dive into the technical side of things, let’s take a look at what public folders were used for.
Many customers would actually forget they had the public folder database and then it got deleted or corrupted and they ended up with issues when it came time to migrate. The pubic folder database was never part of the database availability group (DAG), so when you did failovers, if the server was part of a DAG, then it would be down for the duration of that maintenance window. Essentially, it was just another database you had to manage on Exchange and if you had a standard license you were limited to five databases. In legacy versions, Exchange 2010 as an example, you would create a public folder database that would be stored on one server with no high availability and your public folders would live there.
Over a number of years, the way Microsoft has handled them has changed.
Public folders in Exchange have been around for a very long time.
0 kommentar(er)
