Exchange

Exchange Server 2010 Prerequisites on Windows Server 2008 R2

In order to install Exchange server 2010 with Client Access, Hub Transport, and Mailbox server roles:
1- Servers that will host the Hub Transport or Mailbox server roles require the Microsoft Filter Pack which can be downloaded here: http://go.microsoft.com/fwlink/?linkid=137042

2- After installing the Filter Pack run the ” Import-Module ServerManager “ command from Windows PowerShell console.

3- Run the following command from Windows Power Shell:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

4- After the restart run ” Set-Service NetTcpPortSharing -StartupType Automatic “ command from Windows PowerShell console.

5- After installing Exchange Server 2010 prerequisites, run Microsoft Update to verify the latest updates are applied to the server before continuing with the Exchange Server 2010 installation.

Exchange 2010 – 1 Week to production

For several weeks / days I have been actively working on migrating our internal Exchange 2007 infrastructure to Exchange 2010.  In my lab setup I can say that Exchange 2010 is an awesome continuation in Microsoft flagship email product..

I will be documenting several of the things I’ve discovered about the process  and share with you all.  So please stop back or subscribe to my RSS for updates.

Export-Mailbox

Information: The Export-Mailbox cmdlet exports all message types, including messages, calendar items, contacts, distribution lists, journal entries, tasks, notes, and documents. However, the Export-Mailbox cmdlet does not export rules.

To export data from a .PST file, you must run the Export-Mailbox cmdlet on a 32-bit computer that has the 32-bit version of the Exchange management tools and Outlook 2003 Service Pack 2 (SP2) or Outlook 2007 installed.

Please be aware that there are prerequisites to exporting mailboxes.  You need a location to export the mailbox to  along with permissions set on the mailbox.

In the example below I will show you how:

First add permission to the users mailbox

Add-MailboxPermission -identity user Accessrights FULLACCESS -User admin

Now we export the mailbox

Export-Mailbox -identity user -PSTFolderPath c:user.pst

Now you should be safe to remove the email boxes and free up space

 

Exchange Database Size and Limits

In the dream time hours of the night one of the exchange data-stores went offline.  The steps to resolve the issue were put in place and handled swiftly by the administrator on duty; but what was the cause.

After some digging I arrive at the reason why the data-store went offline.  Found in the Windows Application event ID 9630 the database had reached the logical side equal to the physical size of the data base and that being 250GB.  Thus the database size had exceed the size limit of 250GB

Exchange then dismounted the database preventing further access.   My take on this is that Microsoft expects users with large dB’s to have multiple storage servers.  Well I am balling with a budget here so that is not happening anytime soon.

So how does one get around this?

Well simple; You follow the steps here on Microsoft Technet.  And the procedure in below:

  1. Start Registry Editor (regedit).
  2. Locate the following registry subkey:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeIS<SERVER NAME>Private-<database GUID>
    Note
    You can get the GUID of a database by running the following command in the Exchange Management Shell: Get-MailboxDatabase -Identity "<server name><storage group name><database name>" | Format-Table Name, GUID
  3. If the Database Size Limit in GB DWORD exists for the subkey, change its value to the desired size in gigabytes.
  4. If the Database Size Limit in GB DWORD does not exist for the subkey, create a new DWORD with that name, and then set its value to the desired size in gigabytes.

Use the Exchange Management Shell to determine the GUID of the database

Run the following command to determine the GUID of the mailbox database that you want to configure. The sample returns the GUID of the mailbox database BOX1 on server myExchange.

Get-MailboxDatabase -Identity “myExchangeBOX1” | Format-List GUID

Run the following command to determine the GUID of the public folder database that you want to configure. The sample returns the GUID of the public folder database PF1 on server myExchange.

Get-PublicFolderDatabase -Identity “myExchangePF1” | Format-List GUID

DIY: Black Holes (in Exchange Server)

Create a distribution group

Be sure that there are no members in this distribution list/group.

Add the SMTP addresses of the ex-employees or address to the distribution list/group, if account exists.  Add them as secondary SMTP addresses to the distribution list/group address.

*note* enter the properties and change the delivery reports; and set it not to send.
*note* you may want to hide the new distribution list/group from the address list