Recently I had a customer request an increase in the size of their Mailbox which for us means switching them to a different 'Plan'. I was suprised to be presented with an error using the default provisioning website that comes with HMC 3.5 when attempting to save his new plan. I quickly discovered this organization was out of the space I had allocated to them.

After a little digging I found that for some reason (possible future blog entry) this particular user's Mailbox had been created on BusinessMailstore1, while every other user resided on BusinessMailstore2. I would like to understand why, but that is a different subject. I could see the organization did not have enough space allocated to it on BusinessMailstore1. So I switched over to allocate some more space for this organization using the Exchange Resource Manager web client.

It is at this point when I found what I think is a bug. Each time I would increase the space using the tool, the new megabytes would be applied to BusinessMailstore2. I messsed with running provtest against the appropriate XML files as well, but found the same behavior, which makes me think the bug is in the web service which performs provtest commands.

I then spent hours trying to get the native Exchange Move Mailbox feature to work and it would not work no matter what I tried.

The 'hack' I came up with to solve this problem is to manually increase the allocation in the ResourceManager database on MPSSQL01. After much digging and SQL Profiling I came up with right two UPDATE statements.

You will have to follow the instructions in the comments to get to your own GUID values which are right for your organization. Basically you increase the size and then also update the new total across the whole organization (both mailstores). And it seems to work great for us.

BEGINT SQL CODE

--this is the fix, for when an org is split across Mailstore1 and Mailstore2, and you need to put more space for them on Mailstore1

--this will get your resource_id value for the update on Blockmodel_ModelAllocationData
--select * from rmcore_ResourceInstance where instance_description = 'BusinessMailstore1'
--the column value you want to use is INSTANCE_ID

--and this query will get you the consumer_id you need.
--first get typeid of ExchOwningOrgConsumer
--select type_id from rmcore_consumertype where type_name = 'ExchOwningOrgConsumer'
--now you need to know your instance_name
--select instance_name from rmcore_ConsumerInstance where instance_description like 'Original path:LDAP://OU=YOUR_ORG_NAME_HERE%'
--now use the instance name to get the right consumer_id
--now get the consumer_id from the instance+id column
--select instance_id from rmcore_ConsumerInstance where instance_name = N'35AA8E01BFA5C74BAFC58AAEE662C8D4' and type_id = '90AFC37D-C583-4479-B946-08AC14E00BCC'

--increase the organizations space on businessmailstore1 from 400 to 1200MB
update  Blockmodel_ModelAllocationData
set  Actual_Used = 1200
where  resource_id = '02B6CBE0-8334-41CB-A98D-E95E3D24F9E4'
and consumer_id = 'D1252863-96FC-443D-AD3B-0109919FA4C7'

--now try to update how much space is available to org (sum of size of current mailboxes assigned to mailstore - number used above)
update  Blockmodel_ResourceCapacity
set  Actual_max = 1200000
and Actual_free = 800000
where  instance_id = '25E3A16C-609D-439F-B118-13E4CFCA21E7'