Mailbox Moves in Exchange August 8, 2012Posted by vbry21 in Exchange 2010.
Tags: Microsoft Exchange 2010
add a comment
We were having a look at Mailbox moves today in Exchange 2010 SP2.
A mailbox move in its simplest form moves a users mailbox from one Exchange Database to another. We do this for all sorts of reasons.
Transition When you transition an existing Exchange 2007 or Exchange Server 2003 organization to Exchange 2010, you move mailboxes from the existing Exchange servers to an Exchange 2010 Mailbox server.
Realignment You can move mailboxes for realignment purposes. For example, you may want to move a mailbox from one database to a database that has a larger mailbox size limit.
Investigating an issue If you need to investigate an issue with a mailbox, you can move that mailbox to a different server. For example, you can move all mailboxes that have high activity to another server.
Corrupted mailboxes If you encounter corrupted mailboxes, you can move the mailboxes to a different server or database. The corrupted messages won’t be moved.
Physical location changes You can move mailboxes to a server in a different Active Directory site. For example, if a user moves to a different physical location, you can move that user’s mailbox to a server closer to the new location.
Separation of administrative roles You may want to separate Exchange administration from Windows operating system account administration. To do this, you can move mailboxes from a single forest into a resource forest scenario. In this scenario, the Exchange mailboxes reside in one forest and their associated Windows user accounts reside in a separate forest.
Outsourcing e-mail administration You may want to outsource the administration of e-mail and retain the administration of Windows user accounts. To do this, you can move mailboxes from a single forest into a resource forest scenario.
Integrating e-mail and user account administration You may want to change from a separated or outsourced e-mail administration model to a model in which e-mail and user accounts can be managed from within the same forest. To do this, you can move mailboxes from a resource forest scenario to a single forest. In this scenario, the Exchange mailboxes and Windows user accounts reside in the same forest.
There is two types of move.
Local Move Request, this is where we move the mailbox from one database to another in the same forest.
Remote Move Request, this is also known as a cross-forest move, this would be a move where we move a mailbox from one AD forest to another forest that contains a Client Access Server, think of migrations.
Breaking the Exchange 2010 SP2 softly enforced 1TB limit August 6, 2012Posted by vbry21 in Exchange 2010.
Tags: Exchange 2010, Microsoft
add a comment
On the Exchange 2010 SP2 course (10135B), we talk about the two different editions of Exchange 2010.
These are Standard and Enterprise.
Standard allows five databases and has no software limit for the size of the storage, we are purely constrained by the hardware.
Enterprise allows one hundred databases and again has not software limit.
However in Standard edition if we want to exceed the 1TB limit we must enable this setting in the registry.
You can use Registry Editor to modify a database size limit in Microsoft Exchange Server 2010. The default database size limit for Exchange 2010 Standard Edition is 1024 gigabytes (GB). There is no default database size limit for the Exchange 2010 Enterprise Edition. The Exchange store checks any database size limits periodically and dismounts a database when the size limit is reached. You can modify the database size limit by adding or changing a value in the registry.
When you change this setting, this change is propagated to all servers that host a copy of this database.
- Start Registry Editor (regedit).
- Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\Private-<database GUID>
|You can get the GUID of a database by running the following command in the Exchange Management Shell: Get-MailboxDatabase -Identity “<database name>” | Format-Table Name, GUID|
- If the Database Size Limit in GB DWORD exists for the subkey, change its value to the desired size in gigabytes.
- If the Database Size Limit in GB DWORD doesn’t exist for the subkey, create a new DWORD with that name, and then set its value to the desired size in gigabytes.