TechShizz | All posts tagged 'Exchange 2010'

List of mailbox sizes


Get-MailboxStatistics -Database "DB1" | Select DisplayName, ItemCount, TotalItemSize | Sort-Object TotalItemSize -Descending | Export-CSV C:\MBSizes.csv


Another we could use is:

get-mailboxstatistics | Sort-Object TotalItemSize -Descending | Select-Object DisplayName, @{label="TotalItemSize (MB)";expression={$_.TotalItemSize.Value.ToMB()}}, ItemCount | Export-CSV c:\filename.csv

Client Access Array

 A client access array is a collection of load balanced Client Access servers. There can be one client access array per active directory site, and a single client access array cannot span multiple sites. Client access arrays are created using the New-ClientAccessArray cmdlet.

For example, to create a new client access array named in the Maffra site, use the following command:


New-ClientAccessArray –FQDN –Site Maffra –Name "clientarray"


Once the client access array is created, you assign the client access array to mailbox databases using the Set-MailboxDatabase cmdlet with the RpcClientAccess parameter. For example, to configure mailbox database ALPHA to use client access array clientarray.adatum. com, use the following command:


Set-MailboxDatabase ALPHA –RpcClientAccess

Clone Edge Transport Server

In a production environment we would want to have the same configuration on each edge transport server. Rather than do this manually, we can use a special script to export the configuration of the first Edge transport server. The following is copied over when this is implemented:

  • Send and Receive connectors
  • Accepted Domains
  • Remote Domains
  • IP Allow/Block Lists
  • Anti Spam: Content filter/recipients filter/address rewrite entries and attachment entries.


To Clone


  1. Install the Edge transport role on the target server.
  2. Run: ./ExportEdgeConfig -cloneconfigdate:"C:\cloneconfigdata.xml"  on the source edge server. These scripts can be found at c:\Program Files\Microsoft\Exchange Server\V14\Scripts"
  3. Move the created XML file to the target edge server
  4. On the target server, create the reference XML by running  ./ImportEdgeConfig -cloneconfigdata:"c:\cloneconfigdata.xml" -isimport $false -cloneconfiganswer:"C:\cloneconfiganswer.xml"
  5. You will need to edit the XML to contain:
    1. Data and log file paths
    2. Source IP addresses for send connectors
    3. Network bindings for each connector.
  6. After editing the XML, run ./ImportEdgeConfig -cloneconfigdata:"c:\cloneconfigdata.xml" -isimport $true -cloneconfiganswer:"C:\cloneconfiganswer.xml" on the target server.

Auto discover & Active Sync



The Autodiscover service provides clients running Outlook 2007, Outlook 2010, and mobile

phones running Windows Mobile 6.1 or later with user profile configuration settings. To

use Autodiscover, it is necessary to either provide the user’s email address and password or

have the user’s domain credentials.


You can use the Test-OutLookWebServices cmdlet from the EMS to verify that the


service settings are working properly


Test-OutlookWebServices –ClientAccessServer CAS01


Active Sync


ActiveSync allows users to sync their Windows Mobile devices with their Exchange mailboxes.

ActiveSync is optimized to work across high-latency, low-bandwidth networks, such as those

likely to be encountered across a mobile phone data connection. Exchange ActiveSync is

enabled automatically when you install the Client Access server role.


Can be configured from Server Configuration\Client Access > selecting Exchange ActiveSync on the lower-middle page, right-clicking on the Client Access server that you want to modify, and then clicking on Properties.

Active Sync


Internal URL - The URL that ActiveSync devices on the internal network use to access the Client Access server.

External URL  - The URL that ActiveSync devices on the Internet use to access the Client Access server.



On the Authentication tab, in a production environment the following should be selected if the devices have been provisioned with certificates. If they have not this will prevent all devices from connecting.

Authentication Tab



You can test ActiveSync connections with the following EMS cmdlet:


Test-ActiveSyncConnectivity –ClientAccessServer CAS01 –URL -MailboxCredential "Kim_Akers"



ActiveSync device policies


  • To create a policy go to Organization Configuration\Client Access node
  • In the Actions pane, click on New Exchange ActiveSync Mailbox Policy



Allow nonprovisionable devices: Allow devices that do not support all policies to sync with Exchange.

ActiveSync device policies


Once the policy is created you can edit the policy using the Set-ActiveSyncMailboxPolicy cmdlet.



Accepted and Remote Domains

An accepted domain is a specified domain that we want to accept mail as.

So if we enter, we can accept mail AS We then select if the exchange server will be Authoritative for that domain, or if it will be an internal or an external domain.


New Accepted Domain


A remote domain is an SMTP organization that is remote to your domain. We can use this to control rich content between the our domain and the domains listed here.


In the properties we can say if we want to allow Out of Office emails to leave the exchange.

Accepted Domain Properties

We can also control if we want to allow auto replies, auto forwards, delivery reports and much more to the domains in this list.

Accepted Domain - Message Format Tab