Hello echoDreamz, 

We currently have a custom build that addresses this issue. I have opened a support ticket for you so you can also get this build. 

Kind Regards, 

Zach, can you add the custom build to ticket #135-2F04EB61-0011

Hello echoDreamz, 

I went ahead and sent over a link to the custom build in the ticket provided.

Regards,

Appreciate it, Ray!

The custom build (9124) which we were given and installed on 12/24, did indeed fix the disk size reporting problem.  One customer that only has about 8 TB of consumption, was showing in the admin console as nearly 40 TB prior to installing the custom build and new inbound mail was being rejected due to "over quota" for the domain.  Fortunately, as soon as the service started up after installing 9124, the consumption figures went back to normal without further admin intervention.

 

The error you @JayDubb were seeing while running the disk usage report has been resolved and was related to another fix that was causing the account list in this poster's case to fail. So, the custom build provided should do the trick for you as well I believe! I recommend reaching out to support to get the ball rolling :) Alternatively the fix will be included in our next public release so you can wait for that as well if you prefer. 

We can confirm as well, the custom build does resolve the issue. Thanks ST for getting that taken care of :)

Heard a lot of good things about our recent custom build. We've released it now, containing just the two fixes we heard the most about or had big impacts. We've got more in the pipeline but decided to keep this particular release focused on these fixes as we went through the holidays.

Things were pretty smooth around here and hopefully everyone had a good set of holidays and are enjoying the new year. Here's the 2 fixes and if you're running the custom build we've been handing out recently, you don't have to upgrade.

FIXED: Internal user information duplication causing domain sizes to appear incorrect.
FIXED: Licensed users for MAPI/EWS could occasionally reset.


Cheers!

Hi Matt,

To be sure, Is this the same build we received 26th december to fix an API issue with " GET /api/v1/settings/domain/list-users" returning {"message":"An item with the same key has already been added. Key: 10012","success":false}. ?

Kind regards.

Yea, the duplicate user info was causing sizes to exaggerate and some areas failed to load like user disk usage reports and some API calls to fail.

The public release is exactly the same build, the custom build we gave out starting christmas eve.