Exchangepedia Blog is read by visitors from all 50 US States and 150 countries world-wide
Background: Exchange Server 2003 SP2 allows raising the Store size limit. If you're using Exchange Server 2003 Standard Edition, the default is raised from 16 Gb to 18 Gb, and the maximum size of a Store has been raised to 75 Gb. To raise the Store size limit, you need to insert the Database Size Limit DWORD value in:
HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<servername>\Private-<ObjectGUID of the store>
(Refer to
"Database Size Limit Configuration and Management", Exchange Server 2003 Technical Reference Guide)
Issue: You want to raise the storage limit of a Store.
When you go to the Registry, the name of the subkey looks something like this:
Private-e633bea6-9daf-4752-b5a9-efffae29af2b
When you check the objectGUID attribute of a Store (in ADSIEdit), it looks like this:
A6 BE 33 E6 AF 9D 52 47 B5 A9 EF FF AE 29 AF 2B
The objectGUID is an octet string - the octets will appear reversed.
One way of finding out the GUID is to go to the Microsoft Exchange System Objects container, finding the SystemMailbox{GUID} object - where the GUID matches the registry subkey, and checking the object's homeMDB attribute. This reveals the name of the Store that GUID belongs to.
GetStoreGUIDs.vbs script will dump Store name, the distinguishedName, objectGUID (in a readable format, the way it shows up in the registry), and the legacyExchangeDN of all Stores in an Exchange Organization.
Download:
GetStoreGUIDs.zip
3/4/2006: Script shows Organization name, Store type (Public/Private) and Server name.
12/27/2006: Added link to Database Size Limit Configuration and Management, and images showing GUID in registry and ADSIEdit.
8/7/2007: Note about downloading ArrayConvert.exe and registering ADS.DLL added.
HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<servername>\Private-<ObjectGUID of the store>
(Refer to
"Database Size Limit Configuration and Management", Exchange Server 2003 Technical Reference Guide)Issue: You want to raise the storage limit of a Store.
When you go to the Registry, the name of the subkey looks something like this:
Private-e633bea6-9daf-4752-b5a9-efffae29af2b
When you check the objectGUID attribute of a Store (in ADSIEdit), it looks like this:
A6 BE 33 E6 AF 9D 52 47 B5 A9 EF FF AE 29 AF 2B
The objectGUID is an octet string - the octets will appear reversed.
One way of finding out the GUID is to go to the Microsoft Exchange System Objects container, finding the SystemMailbox{GUID} object - where the GUID matches the registry subkey, and checking the object's homeMDB attribute. This reveals the name of the Store that GUID belongs to.
GetStoreGUIDs.vbs script will dump Store name, the distinguishedName, objectGUID (in a readable format, the way it shows up in the registry), and the legacyExchangeDN of all Stores in an Exchange Organization.
Download:
GetStoreGUIDs.zipBesides the above script, you will also need a Microsoft DLL file that converts data types (variants). Download ArrayConvert.exe from KB 250344: SAMPLE: ARRAYCONVERT.EXE Variant Conversion Functions.
- Expand ArrayConvert.exe into a folder
- Navigate to the folder where you expanded the files
- Use the following command to register the DLL on the computer that you'll run the script on:
regsvr32 ads.dll
3/4/2006: Script shows Organization name, Store type (Public/Private) and Server name.
12/27/2006: Added link to Database Size Limit Configuration and Management, and images showing GUID in registry and ADSIEdit.
8/7/2007: Note about downloading ArrayConvert.exe and registering ADS.DLL added.
Labels: Administration, Scripts
7 Comments:
Thanks for posting these great scripts on your blog - this makes it easier for a lot of us.
Spent some time trying to figure this one out. Your script made it so easy! Thanks - and awesome blog!
The download link does not work. Can anyone repost the link?
Thanks
It says the script output for objectGUID will be displayed "the way it shows up in the registry". What did I do wrong if the script output for the GUID is an octet string, or reversed?
What I meant in the post is - it's hard to find out which GUID corresponds to a particular Store from the registry (if you have multiple Stores), and when you actually take a look at the objectGUID attribute of the actual Store that you want to modify the limits for, it doesn't look like what shows up in the registry.
The script lists Stores and the corresponding GUID that you can then look for in the registry and modify the size easily.
Is the script not producing the right output? You can email me offline (firstname lastname at hotmail) to tell me what you see in the registry, and what the objectGUID attribute of your Store(s) shows.
Hi
I'm having trouble using you code.
I'm searching for the Store GUID and with your tool i get this:
{A9C5C707-29FF-1745-8B94-F76E9565AC49}
If I use LDP.EXE and looks at the mailbox store and the property objectGUID it is:
{07c7c5a9-ff29-4517-8b94-f76e9565ac49}
Do you have any idea of what could cause the problem?
If I try to get the objectGUID it is displaying "?????|?????"
Outstanding script. Thank you, thank you.
Post a Comment
Links to this post:
Create a Link
<< Home