Enforcement Provisioning Policy


  • Hi,

    I am trying to understand how this damm Service Plan works.

    The documentation is terrible.

    When I create a new organization, I use a unique template for all organizations. After that, I run the Set-RecipientEnforcementProvisioningPolicy to set the organizations quota.

    Until now, always works fine. I can create all the users in the organization, but when I remove one mailbox and I try to create another I receved a message that I cannot create the mailbox because I reached my quota.

    I don´t understand, if I deleted a mailbox and I try to create another my quota will keep the same. So, why this issue happened?

    Somebody, has any explanation?


    Fabrizio Zavalloni
    Monday, February 14, 2011 5:11 PM

All replies

  • I have 2 environments with the same issue.

    I thought I made some mistake, but didn´t find.

    Moreover, in Microsoft Web site this topic is not already done.

    Fabrizio Zavalloni
    Wednesday, February 16, 2011 1:41 PM
  • I built another test environments and I disabled the Mailbox retention from the databases and the behavior was the same.


    Fabrizio Zavalloni
    Saturday, February 26, 2011 12:31 AM
  • Let me understand your issue better here.

    You have reached the limit and you can't create the mailbox. So, you tried to remove one mailbox and then try to create another one, but it still fail, am I right?


    Regards, Kip Ng -
    Tuesday, March 01, 2011 7:42 AM
  • Hi Kip,

    Yes, You are right.

    I built 3 test environments and the behavior was the same.

    In my last test, I created a organization using only the template file and happened the same.

    Can you simulate this?

    Did you know if this issue is a bug or anything else?

    Fabrizio Zavalloni
    Tuesday, March 01, 2011 1:38 PM
  • I will attempt the repro later.

    A couple of questions,

    1. How many DC do you have in your environment?

    2. Are you able to create user after a short wait?

    3. What about after you restarted your server?

    Regards, Kip Ng -
    Tuesday, March 01, 2011 1:43 PM

    1- I have one DC

    2- No, I waited one day and the behavior was the same.

    3- Even I restarted the system, no solution.

    Fabrizio Zavalloni
    Tuesday, March 01, 2011 1:49 PM
  • Ok. I tried that.

    At a quick glance, it seems like when it hits the limit, you need to reduce the number of mailboxes down and then restart the msexchangeis. There is a cache there or wait for 2 hours. If you wait for a whole day and it isn't working, check the number of mailboxes that you have there in that Org. It is possible that the DiscoverMailbox is also counted as one.

    Regards, Kip Ng -
    Tuesday, March 01, 2011 8:55 PM
  • You are right.


    When I reduce the mailbox number, made logoff and restarted the msexchangeis. It works.


    I think, the problem is in Offline Address Book.


    I made some tests and I saw that when I deleted a mailbox and after I run the command below, we avoid restart the msexchangeis and solve the problem immediately.


    #Get-OfflineAddressBook -Organization orgname | Update-OfflineAddressBook


    I reproduced that in my 2 environments.


    What do you think if I decrease the schedule time for the update offline address book to 15 minutes?


    I asking this because in our production environment, we are forecasting that could have ~ 5000 mailboxes and I don´t know if I could have a problems in the future.

    Fabrizio Zavalloni
    Wednesday, March 02, 2011 1:10 AM
  • I have to say, I am not sure if it is the OAB. I will need to look further into this.

    Regards, Kip Ng -
    Wednesday, March 02, 2011 3:59 AM
  • I give up!

    I could´t find a specific situation where this happens.

    Sometimes updating OAB it works but other times it doens´t work :(



    Fabrizio Zavalloni
    Thursday, March 03, 2011 1:05 PM
  • Add more information.

    The procedure that I mentioned (update OAB) only works when I remove 2 or more mailboxes.

    If I remove only one, it doen´t work.


    Fabrizio Zavalloni
    Thursday, March 03, 2011 2:14 PM
  • Honestly, I won't imagine it checks the OAB but it is interesting that you get it to work. I was suspecting the store cache but who knows, perhaps the OAB update process may have kicked in the store cache refresh.

    Anyway, you said when you remove 2 or more mailboxes work, can you count the number of mailboxes, including the discovery mailbox?

    Regards, Kip Ng -
    Monday, March 07, 2011 3:26 PM
  • yes, When I ran the get-mailbox -organization xxxx, I can count all the mailboxes including the discovery mailbox.

    If my organization mailbox quota is 3, it show me 4 mailboxes, including the discovery mailbox.

    I removed the discovery search mailbox and the behavior was the same, with one difference. I can create 4 mailboxes, even the quota keeping 3.

    Fabrizio Zavalloni
    Wednesday, March 09, 2011 10:02 PM
  • helo,


    I made a video with my issue to help the understanding.


    Fabrizio Zavalloni
    Tuesday, March 15, 2011 10:57 PM
  • Hmm, that's interesting. I took a quick look (it is hard to find time nowadays). I think there are 2 things here,

    1. The max number seems to be mailbox quota + 1.

    2. However once you hit the limit, you will have to reduce it below the limit.

    For example,

    1. Say, if I have a Quota of 15.

    2. I can create the number of mailbox up to 16 (including the discovery mailbox).

    3. Once I reach that limit, I have to remove at least 2 mailboxes in order to allow creation again, as in, move it to 14 (including the discovery mailbox). Do a Get-Mailbox -Organization <orgid> | Measure-Object

    4. What's interesting is this, when my mailbox count is back to 14, I always fail in trying to create a new mailbox the first time. On second attempt, it always work and I don't need to restart the store.

    I haven't had much time to look into this but when it goes back below the quota, it seems that a new mailbox creation or could be some other cmdlets trigger the reset and it allows you to create new mailbox again.

    Yes, I don't disagree, I think there maybe some calculation concerns here.

    I don't have the time to look too much into this at the moment but if this seriously concern you, my suggestion is that you open a case with Microsoft to investigate further this behaviour.

    Regards, Kip Ng -
    Wednesday, March 16, 2011 4:28 PM
  • Helo Kip,

    I reported this issue to Micrososft. So I will wait to a hotfix for it.


    Fabrizio Zavalloni
    Monday, May 23, 2011 5:38 PM