Exchange Server 2013 – Planning for Public Folders mailboxes according to user logon limits


Since there are some limitations for Exchange 2013 Public Folders, we will focus this little note on the User Logons supported limit, which is 2,000.

I briefly mentioned this 2,000 user logons limit on the article about Public Folder limits increase since Exchange 2013 CU8 on a previous blog post.

In Exchange 2013, you should plan for a number of PF mailboxes according to:

  • the volume of PFs you have as the limit is 100GB per PF Mailbox – and 100 PF mailboxes max – reserve 1 for hierarchy updates, that leaves 99 PF mailboxes max for content storage
  • a target number of Client Logons you’ll have

Knowing that a single user can issue more than 1 client logons at a time because these are accessing the PF Hierarchy + accessing PF content which is hosted on another PF Mailbox + other content on other PF Mailboxes … And, knowing that if a user accesses PF content that is on his “default PF Mailbox”, that counts for 1 concurrent user logon … so that’s not an easy exercise !

If you wish to know more about the difference between a “session” and a “logon”, read this blog post from the Exchange product team.

 

Exchange 2013 user logon behavior for hierarchy and content connections...

Note: in Exchange 2013, we cannot spread or duplicate a single folder contents on multiple PF mailboxes – remember in previous Exchange versions, we were able to replicate “active” content on multiple PF Databases – in E2013 we only replicate an active database hosting a PF Mailbox onto a passive database)

 

The best thing to do to assess the target number of User Logons is to analyze what you currently have on your existing Exchange environment(s).

- On each server that hosts a Public Folder database servicing users connections, collect the following performance counters during 3 to 4 days with a collection interval of 60 seconds

Below are the perfmon counters that will enable us to estimate how many user logons we have on public folders database on a server (Exchange 2003, 2007, 2010):

Category

CounterPath

Description

Microsoft Exchange Public Folder Store performance data

\\MSExchangeIS Public\Client Logons

Client Logons is the number of clients (including system processes) currently logged on.

Microsoft Exchange Public Folder Store performance data

\\MSExchangeIS Public\Active Client Logons

Active Client Logons is the number of clients that performed any action within the last ten minute time interval.

Microsoft Exchange Public Folder Store performance data

\\MSExchangeIS Public\Peak Client Logons

Peak Client Logons is the maximum number of concurrent client logons since the service started.

Note that these numbers take into account all logged on Outlook 2003 users, even these who don’t use PFs to store documents, because Outlook 2003 has to use Public Folders for system related tasks (Free/Busy, Offline Address Book, …).

Note also that even Outlook 2007/2010/2013 will connect to Public Folders by default to check for Organizational Froms, even to publish Free/Busy data, despite the fact these versions use the Availability Service as well. You can use a registry key at the client level to block PF connections for Outlook 2007/2010/2013 (nothing exists on the server level to block PF connections) – since it’s a desktop registry key, you’ll have to deploy it using GPOs – you can  target GPOs to specific security groups.

Ø ACTION : Collect perfmon data for at best 1 week (at minimum 3 days) using a 1 minute (60 seconds) sample, and then we’ll take the max in client Logons and Active Client Logons (and Peak Client Logons) and calculate how many E2013 PF Mailboxes we may need to service client logons while staying below the save 2,000 user logons limit.

IMPORTANT: as mentioned in the above schema, additional logons opened for content queries will not stay forever, which adds some relief and confidence that staying below the 2,000 user logons limit is feasible. Using the above study on existing environments before the migration will also help a lot.. Below is he explanation from our Microsoft Exchange as well as Outlook Product Groups about content logons persistence:

 

When an Outlook user opens a Public Folder to see the content, the Public Folder connection (=user logon) will likely live for around 75 minutes.

Here are some bullets to explain what’s going on:

  •   A connection lives [only] as long as an open Object (message/folder) is holding a reference on it.
  •   Navigating to a Public Folder creates a Content Folder Object, which holds a reference to the Content Mailbox.
  •   Any Folder Object, including this Content Folder Object, will be added to what’s called the Object Cache.
  •   Objects remain in the Object Cache until there is about 75 minutes of inactivity, at which time the Object will be released from the Object Cache. Before the time is up if the user navigates back to the folder the clock will restart.
  •   Once the ~75 minutes of inactivity passes the Content Folder Object is released from the Object Cache. When it is released it will release its reference on the Connection to the Content Mailbox.
  •   Having no more references holding it open, the Connection goes away.

 

Once again, thanks very much to the Exchange and Outlook Product Groups for clarifying this.

Sam.


Comments (3)

  1. B0ndoo7 says:

    Sam, I was just referred to your blog from a TechNet thread because we are in the situation you describe in this article. In the "Action" section, you mention taking the data and calculating the number of Ex2013 PF mailboxes but there is no explanation or follow-up (that I see) that explains how to do this. I know this blog is a year old, but it's still very relevant. If you could shed some light on the next steps after collection, it would be greatly appreciated.

    1. SammyKrosoft says:

      Hey B0ndoo7, yes sorry, I'll update that post soon to include this. But basically, take the Max value of what you have on the Peak Client Logons counter, divide it by 2,000 (our limits on user logons on each PF mailboxe), and you'll have the number of PF mailboxes to deploy. Don't forget to distribute your PF Mailbox to chunks of 2,000 users using Set-Mailbox and the "-DefaultPublicFolderMailbox" parameter, otherwise Exchange will distribute the PF connections to all PF mailboxes ...

Skip to main content