TechShizz | All posts tagged 'Exchange 2010'

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 clientarray.adatum.com in the Maffra site, use the following command:

 

New-ClientAccessArray –FQDN clientarray.adatum.com –Site Maffra –Name "clientarray .adatum.com"

 

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 clientarray.adatum.com

Outlook Anywhere (RPC over HTTP)

On the Server Configuration > Client Access node, you can right click on the Exchange server and Enable to Outlook Anywhere feature.

Enable Outlook Anywhere

 

You must then enter the external URL that will be able to access the exchange server. 

 

External Host name - Outlook Anywhere

 

This can be enabled in EMS:

Enable-OutlookAnywhere –Server 'CAS1' –ExternalHostname 'mail.adatum.com' –DefaultAuthenticationMethod 'NTLM'

 

Configuring RPC Client Access

 

In Outlook > File > Account Settings > Account Settings > Select account > Change > More > Advanced > HTTP Proxy Settings 

 

The settings here should match what was setup in the enabling Outlook Anywhere feature.

The settings should pull through automatically anyway.

Microsoft Exchange Proxy Settings

 


Auto discover & Active Sync

AutoDiscover

 

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

Autodiscover

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 http://adatum.com/mail -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.

 

 


Client Throttling Policy

Client throttling policies allow you to manage Client Access server performance by monitoring how users consume resources and enforcing bandwidth limits where necessary. Client throttling policies allow you to stop users from intentionally or unintentionally degrading Client Access server performance when they use a disproportionate amount of Client Access server resources. When you first deploy Exchange Server 2010, a default throttling policy is applied. You can view the properties of this policy by using the Get-ThrottlingPolicy cmdlet in the EMS. Throttling policies apply to the following Exchange components:

 

  • Exchange ActiveSync
  • Exchange Web Services
  • IMAP
  • OWA
  • POP
  • Windows PowerShell

 

You manage throttling policy settings using the following EMS cmdlets:

 

  • Get-ThrottlingPolicy - Get the properties of existing throttling policies
  • Set-ThrottlingPolicy - Configure the properties of an existing throttling policy 
  • New-ThrottlingPolicy - Create a new throttling policy
  • Remove-ThrottlingPolicy - Remove an existing throttling policy

List of mailbox sizes

 

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


OR


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