Exchange Server Pro » Client Access

Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade

Paul Cunningham — Tue, 06 Dec 2011 12:40:52 +0000

While attempting to upgrade an Exchange Server 2010 Client Access server to Service Pack 2 you may encounter the following error message.

The ‘IIS 6 WMI Compatibility’ component is required. Install the component via Server Manager.

Error message upgrading Exchange 2010 Client Access server to SP2

This error occurs because a new feature of Exchange 2010 SP2 called Outlook Web App Mini requires that IIS component to be installed on Client Access servers.

You can install the component manually by opening a PowerShell window and running the following commands.

PS C:\> Import-Module servermanager

PS C:\> Add-WindowsFeature Web-WMI

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True    No             Success   {IIS 6 WMI Compatibility}

Click Retry on the Readiness Checks dialog box above, or if you’ve already cancelled the installation simply start it again.

You can also avoid the error by installing the Service Pack 2 upgrade from the command line. Open a command prompt and navigate to the folder where the Exchange 2010 SP2 files have been extracted, and run the following command:

C:\Admin\ex2010sp2>setup /mode:upgrade /installwindowscomponents

This will automatically install the required components for you when the upgrade process runs.

Get more Exchange Server tips at ExchangeServerPro.com

Exchange 2010 FAQ: How to Minimise Downtime During Mailbox Migration from Exchange 2007

Paul Cunningham — Tue, 27 Sep 2011 11:00:15 +0000

Q: How can the mailbox migration from Exchange 2007 to Exchange 2010 be done with the minimum down time possible? Do users have to be offline during mailbox migration?

Exchange Server 2010 introduced the concept of online mailbox moves. An online mailbox move is a move operation during which the end user is able to connect to their mailbox for almost the entire move, except for the very end.

Online mailbox moves are only available when moving a mailbox from Exchange 2007 SP2 to Exchange 2010, or from Exchange 2010 to Exchange 2010.

The benefit of online mailbox moves is the minimal end user impact during the move. There are a lot of different scenarios in which the end user experiences an online move depending on the specific scenario and the method the user is connecting with at the time. You can read the full list of scenarios here.

For migrating from Exchange 2007 to Exchange 2010 online mailbox moves can be used to minimise the downtime for end users.

During an online mailbox move from Exchange 2007 SP2 to Exchange 2010 the end user is not locked out of the mailbox for the full duration of the move. Instead, the Exchange server performs the move and then only at the final stage does the end user get locked out for the move request to be completed.

This can dramatically shorten the amount of time that the user mailbox, particular larger mailboxes, is unavailable during the migration.

Mailbox move requests are initiated using the Exchange 2010 management tools. Launch the Exchange Management Console and navigate to Recipient Configuration/Mailbox.

You can hold the CTRL key to select multiple mailboxes to move if you want to.

In the Actions pane click on New Local Move Request.

Click the Browse button to choose a target mailbox database.

Select the mailbox database to move the pilot group to and then click OK. Click Next to continue.

On the Move Settings dialog you’ll notice the option to suspend moves when they are ready to complete. This option allows you to more precisely manage the timeframe in which the user is unable to access their mailbox, thanks to how the online mailbox moves work.

If you choose to suspend the move when it is ready for completion you can begin the mailbox move request at any time, and then have it sit in a suspended state until you are ready for it to be completed.

For this example I will check the box to suspend the moves to demonstrate this process. However if you wish to have the move requests continue to completion on their own do not check the box.

Review the list of mailboxes that will be moved and then click New to create the move requests.

Click Finish to close the wizard.

The move requests are created and will be processed by an Exchange 2010 Client Access server. While the mailbox is being moved the end user can continue to access it and send/receive email.

You can view the status of the move requests in the Exchange Management Console under Recipient Configuration/Move Request.

Right-click a move request and choose Properties to see the status of that move request.

When the move request is in this suspended state the user can still continue to access their mailbox on the original server. You can then notify them of the time you will be completing the move request, at which point they will be locked out of the mailbox and will need to restart Outlook afterwards.

When you are ready simply right-click on the move request and choose Complete Move Request. You can also hold the CTRL key to select multiple move requests and complete them all at once.

Again you can monitor the status of the move requests in the Exchange Management Console.

If the end users are still connected with Outlook they will see a message similar to this, and will need to restart Outlook to connect to their mailbox on the Exchange 2010 server.

When the user restarts Outlook they’ll be connected to their mailbox in the new location.

As you can see using online mailbox moves in conjunction with suspending mailbox move requests allows you to perform a mailbox migration from Exchange 2007 to Exchange 2010 with minimal user downtime.

Get more Exchange Server tips at ExchangeServerPro.com

Exchange 2010 Local Move Request Fails with No Available Mailbox Replication Service Error

Paul Cunningham — Sat, 13 Aug 2011 15:18:59 +0000

When you attempt to create a new local move request in Exchange Server 2010 to move a mailbox you may encounter this error:

There are no available servers running the Microsoft Exchange Mailbox Replication service.

Mailbox move requests are handled by the Microsoft Exchange Mailbox Replication service which is part of the Client Access server role. In order for a move request to be successfully created at least one Client Access server within the same Active Directory site must have a running Mailbox Replication service.

Start the MRS on at least one Client Access server. If it will not start the issue may be that the Net.Tcp Port Sharing service is disabled on the Client Access server. If that is the case then run the following command on the Client Access server in a PowerShell window.

PS C:\> Set-Service NetTcpPortSharing -StartupType Automatic

Restart the Client Access server, or manually start the MRS, and then retry the move request again.

Get more Exchange Server tips at ExchangeServerPro.com

How to Block Non-Cached Mode Outlook Clients with Exchange 2010

Paul Cunningham — Mon, 18 Jul 2011 10:29:39 +0000

In Exchange Server 2010 the administrator can choose to block non-cached mode Outlook clients from connecting to Exchange.

Blocking non-cached mode Outlook connections is useful in some scenarios, such as:

Reducing server workload to get better perform from server and disk resources
Reducing network bandwidth utilization for remotely connecting users

Online Outlook clients can be blocked on a per-user basis using the Set-CASMailbox command. For example:

[PS] C:\>Set-CASMailbox kelly.chatir -MAPIBlockOutlookNonCachedMode $true

You can see the setting for a user by running Get-CASMailbox.

[PS] C:\>Get-CASMailbox kelly.chatir | fl name,mapi*

Name                          : Kelly.Chatir
MAPIEnabled                   : True
MAPIBlockOutlookNonCachedMode : True
MAPIBlockOutlookVersions      :
MAPIBlockOutlookRpcHttp       : False

You can also apply the change to multiple users at once. For example, to block non-cached mode for all users in the Branch Office location:

[PS] C:\>get-mailbox | where {$_.office -eq "Branch Office"} | set-casmailbox -MAPIBlockOutlookNonCachedMode $true

To locate all mailbox users that have non-cached mode blocked run this command:

[PS] C:\>get-casmailbox | where {$_.mapiblockoutlooknoncachedmode -eq "True"}

Name                 ActiveSyncEnabled OWAEnabled           PopEnabled          ImapEnabled         MapiEnabled
----                 ----------------- ----------           ----------          -----------         -----------
Aisha.Bhari          True              True                 True                True                True
Andy.Crossley        True              True                 True                True                True
Carol.Tubby          True              True                 True                True                True
David.Marriott       True              True                 True                True                True
Dukh.Morgan          True              True                 True                True                True
Georgie.Jeyapragasam True              True                 True                True                True
Hilary.Shortt        True              True                 True                True                True
Jennifer.Sparks      True              True                 True                True                True
Judith.Woodland      True              True                 True                True                True
Kelly.Chatir         True              True                 True                True                True
Lorraine.Rideout     True              True                 True                True                True
Marcia.Barnett       True              True                 True                True                True
Meena.Salt           True              True                 True                True                True
Neville.Sherwin      True              True                 True                True                True
Pauline.Taylor       True              True                 True                True                True
Robert.Henderson     True              True                 True                True                True
Sharnjit.Mcilroy     True              True                 True                True                True
Suki.Murray          True              True                 True                True                True
Valerie.Andrews      True              True                 True                True                True
Wendy.Fyson          True              True                 True                True                True

Finally, to locate all users who are not blocked from using Outlook in non-cached mode, you would run the same command but check for “False” instead.

[PS] C:\>get-casmailbox | where {$_.mapiblockoutlooknoncachedmode -eq "False"}

Get more Exchange Server tips at ExchangeServerPro.com

Installing an Exchange 2007 Client Access Server on Windows Server 2008

Paul Cunningham — Wed, 25 May 2011 00:00:42 +0000

The Exchange Server 2007 Client Access server role is responsible for all non-MAPI client communications. This includes:

Outlook Web Access (OWA)
Outlook Anywhere (RPC-over-HTTPS)
Exchange ActiveSync (mobile devices)
POP3/IMAP4
Exchange Web Services (EWS)

Outlook clients connect directly to the Mailbox server for mailbox and public folder access and do not use the Client Access server, however Outlook 2007 and above clients do connect to the Client Access server for Autodiscover and Autoconfiguration.

This tutorial demonstrates how to install an Exchange Server 2007 Client Access server on Windows Server 2008. It is assumed that you have already extended the Active Directory schema for Exchange 2007.

Installing Exchange 2007 Client Access Server Pre-Requisites on Windows Server 2008

On Windows Server 2008 the pre-requisite roles and features for the Exchange 2007 Client Access server role can be installed using ServerManagerCmd.exe.

Launch an elevated command prompt and run the following command.

ServerManagerCmd -i PowerShell Web-Server Web-ISAPI-Ext Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression RPC-over-HTTP-proxy

Next download the Windows Installer 4.5 file from Microsoft and install it on the server. The Windows6.0-KB942288-v2-x64.msu file is the correct one for a 64-bit Windows Server 2008 server.

A restart will be required before you proceed to the next step.

Installing the Exchange 2007 Client Access Server Role

To install the Exchange 2007 Client Access server role download the Exchange Server 2007 SP3 setup files from Microsoft and extract them to a folder on the server’s hard disk.

Launch an elevated command prompt and run the following command.

setup /m:install /r:c,t

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be installed
    Management Tools
    Client Access Role

Performing Microsoft Exchange Server Prerequisite Check

    Client Access Role Checks        ......................... COMPLETED

Configuring Microsoft Exchange Server

    Copying Exchange files           ......................... COMPLETED
    Exchange Management Tools        ......................... COMPLETED
    Client Access server role        ......................... COMPLETED

The Microsoft Exchange Server setup operation completed successfully.
Setup has made changes to operating system settings that require a reboot to tak
e effect. Please reboot this server prior to placing it into production.

Reboot the server before proceeding to apply the latest updates and configure the server for your environment.

Get more Exchange Server tips at ExchangeServerPro.com

Poll: Should CAS Arrays be Deployed in all Exchange 2010 Sites?

Paul Cunningham — Fri, 20 May 2011 01:00:45 +0000

Exchange 2010 CAS Arrays are a great high availability feature, but are organizations making the best use of them?

One of the best practices when deploying Client Access Server Arrays is to establish the CAS Array first before configuring mailbox databases in the same site. Or at the very least, making sure you update each existing mailbox database with the correct “RPCClientAccessServer” attribute before migrating users to them.

The advantage of this is that Outlook profiles get automatically configured with the name of the CAS Array rather than the real name of a Client Access server in that site.

Considering the benefits of this, such as:

making it easy to scale out the CAS Array name to multiple Exchange 2010 Client Access servers
making it simpler to replace a Client Access server with a new one of a different name
migrating the MAPI endpoint to future versions of Exchange Server

…does it make it a sensible best practice to always configure CAS Arrays for AD Sites that contain Exchange 2010 mailbox servers, even when only one Client Access server is deployed?

Update: Microsoft now recommends that you always create a CAS Array in each site, even if you have only one Client Access server in the site.

Please give your opinion by voting in this poll. If you wish to expand on your vote in more detail please leave a comment below.

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server 2010 Error: Outlook Web App Didn’t Initialize

Paul Cunningham — Thu, 12 May 2011 13:27:33 +0000

When connecting to Outlook Web App (OWA) for Exchange Server 2010 users may report the following error in their web browser.

Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.
Couldn’t find a base theme (folder name=base)

This can be caused by missing OWA theme files in \ClientAccess\Owa\14.1.287.0\themes sub-folder of the Exchange 2010 installation path. By default this is C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\14.1.287.0\themes.

To resolve the error you can perform a restore of the files to the Client Access server from a previous backup.

If that is not available to you then you can also restore the files by re-running Exchange Server 2010 SP1 setup in upgrade mode.

C:\Admin\Exchange2010SP1>setup /m:upgrade

Welcome to Microsoft Exchange Server 2010 Unattended Setup

Preparing Exchange Setup

    Copying Setup Files                           COMPLETED

The following server roles will be upgraded
Languages
Hub Transport Role
Client Access Role
Management Tools

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Language Pack Checks                                      COMPLETED
    Hub Transport Role Checks                                 COMPLETED
    Client Access Role Checks                                 COMPLETED

Configuring Microsoft Exchange Server

    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Languages                                                 COMPLETED
    Hub Transport Server Role                                 COMPLETED
    Client Access Server Role                                 COMPLETED
    Exchange Management Tools                                 COMPLETED
    Finalizing Setup                                          COMPLETED

The Microsoft Exchange Server setup operation completed successfully.

You should now see the restored files in the correct location, and OWA will begin working again.

Get more Exchange Server tips at ExchangeServerPro.com

How to Publish POP3 Client Settings to Users with Exchange 2010 SP1

Paul Cunningham — Fri, 18 Mar 2011 12:37:06 +0000

When you are deploying POP3 for Exchange Server 2010 it is useful to have a way to publish the correct server settings that users should configure their email client to use. Exchange Server 2010 SP1 has a neat way of publishing this information in the Exchange Control Panel (in OWA).

The first thing you’ll need to know is the POP and SMTP server settings that you want clients to use. In this example we’ll use these server names:

pop.exchangeserverpro.net
smtp.exchangeserverpro.net

These names will both need public DNS records created on your DNS servers. The POP3 server name (pop.exchangeserverpro.net in this case) should also have a valid SSL certificate installed and enabled for POP with a matching name so that you can use secure POP3 access.

Checking the Client Access server in this example I can see that the X509 certificate name configured for POP3 is not the correct one I want.

[PS] C:\>Get-PopSettings | fl x*

X509CertificateName : esp-ho-ex2010a

To change it we can use the Set-POPSettings cmdlet.

[PS] C:\>Set-PopSettings -X509CertificateName pop.exchangeserverpro.net

Next we need to look at the SMTP server. On the Hub Transport server there are two Receive Connectors configured by default.

[PS] C:\>Get-ReceiveConnector

Identity                                Bindings                                Enabled
--------                                --------                                -------
ESP-HO-EX2010A\Client ESP-HO-EX2010A    {:::587, 0.0.0.0:587}                   True
ESP-HO-EX2010A\Default ESP-HO-EX2010A   {:::25, 0.0.0.0:25}                     True

It might seem logical to use the “Default ” connector because it is bound to TCP port 25 (SMTP). However is actually the “Client ” connector that is intended for this use. Here is what TechNet says about these two Receive Connectors.

Client Servername – This Receive connector accepts SMTP connections from all non-MAPI clients, such as POP and IMAP.

Default Servername – This Receive connector accepts connections from other Hub Transport servers and any Edge Transport servers you have.

The “Client ” Receive Connector is bound to TCP port 587. It is also configured by default to respond to new connections with the FQDN of the server itself.

[PS] C:\>Get-ReceiveConnector "Client ESP-HO-EX2010A" | fl fqdn

Fqdn : esp-ho-ex2010a.exchangeserverpro.net

We can change that to the desired name using the Set-ReceiveConnector cmdlet.

[PS] C:\>Set-ReceiveConnector "Client ESP-HO-EX2010A" -Fqdn smtp.exchangeserverpro.net

Now that all of the information has been gathered and the correct settings applied we can publish the information to users in Exchange Control Panel. This is what a user would normally see in ECP.

When they click on the link there are no settings displayed by default.

We can see that no external connection settings have been configured to be published.

[PS] C:\>Get-PopSettings | fl external*

ExternalConnectionSettings : {}

[PS] C:\>Get-ReceiveConnector "Client ESP-HO-EX2010A" | fl adv*

AdvertiseClientSettings : False

To publish the settings to this location we can run the following commands.

[PS] C:\>Set-PopSettings -ExternalConnectionSettings {pop.exchangeserverpro.net:995:ssl}

In the example above the port and security settings from the previous article on securing POP3 for Exchange 2010 have been used.

[PS] C:\>Set-ReceiveConnector "Client ESP-HO-EX2010A" -AdvertiseClientSettings $true

To apply the change reset IIS on the Client Access server.

[PS] C:\>iisreset

Attempting stop...
Internet services successfully stopped
Attempting start...
Internet services successfully restarted

Now when we return to the Exchange Control Panel the users can see the published settings.

Get more Exchange Server tips at ExchangeServerPro.com

How to Export Mailboxes with Exchange Server 2010 SP1

Paul Cunningham — Tue, 15 Mar 2011 11:51:37 +0000

Exchange Server 2010 Service Pack 1 introduced a new method for exporting mailboxes called Mailbox Export Requests. This new method replaces the previous Export-Mailbox command.

Before we look at how to create a new mailbox export request in Exchange 2010 SP1 there are a few things that you should understand.

Firstly, no accounts are granted the rights to export mailboxes by default. You need to explicitly grant these rights, even to accounts that are organization administrators.

Secondly, the mailbox export request is processed by the Client Access server role. Because multiple Client Access servers can exist in a site the request could be processed by any one of them. To ensure that the path to the export PST file is valid for any Client Access server it has to be a UNC path to network share, not a local path.

Granting User Rights for Mailbox Exports in Exchange 2010 SP1

The first step is to grant the right to export mailboxes to an account in your organization. In the Exchange Management Shell run the following command.

New-ManagementRoleAssignment –Role "Mailbox Import Export" –User Administrator

If you’re logged with that user already simply restart your Exchange Management Shell session to be granted access to the new cmdlets.

Creating a Network Share for Mailbox Exports in Exchange 2010 SP1

Next we need to create the network share that will be used as the file path for the exported PST files. All that is required here is a network share that the Exchange Trusted Subsystem group has read/write permission to.

Exporting a Mailbox with an Exchange Server SP1 Mailbox Export Request

With everything configured properly we can now use New-MailboxExportRequest to start the mailbox export. The only two required parameters for the command are the file path to the export PST file, and the name of the mailbox to export.

[PS] C:\>New-MailboxExportRequest -Mailbox alan.reid -FilePath \\esp-ho-ex2010a\pst\alan.reid.pst

Name                                           Mailbox                                        Status
----                                           -------                                        ------
MailboxExport                                  exchangeserverpro.net/Company/Users/Head Of... Queued

To view the status of the request use the Get-MailboxExportRequest cmdlet.

[PS] C:\>Get-MailboxExportRequest

Name                                           Mailbox                                        Status
----                                           -------                                        ------
MailboxExport                                  exchangeserverpro.net/Company/Users/Head Of... InProgress

You can also see more detail about the mailbox export request with Get-MailboxExportRequest.

[PS] C:\>Get-MailboxExportRequest -Name MailboxExport | fl

RunspaceId     : c48a9069-e572-4c65-80ea-773e61e5337e
FilePath       : \\esp-ho-ex2010a\pst\alan.reid.pst
SourceDatabase : MB-HO-01
Mailbox        : exchangeserverpro.net/Company/Users/Head Office/Alan.Reid
Name           : MailboxExport
RequestGuid    : 9de3a722-0c82-4e34-98bf-0ff624c47c16
RequestQueue   : MB-HO-01
Flags          : IntraOrg, Push
BatchName      :
Status         : InProgress
Protect        : False
Suspend        : False
Direction      : Push
RequestStyle   : IntraOrg
OrganizationId :
Identity       : exchangeserverpro.net/Company/Users/Head Office/Alan.Reid\MailboxExport
IsValid        : True

An easy way to see the progress of all mailbox export requests is to pipe Get-MailboxExportRequest into the Get-MailboxExportRequestStatistics cmdlet.

[PS] C:\>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

Name                                   Status                    SourceAlias                           PercentComplete
----                                   ------                    -----------                           ---------------
MailboxExport                          InProgress                Alan.Reid                             20

Exporting an Archive Mailbox with Exchange Server SP1 Mailbox Export Request

You can also export a user’s Personal Archive using mailbox export requests simply by adding the -IsArchive parameter to the command.

[PS] C:\>New-MailboxExportRequest -Mailbox alan.reid -FilePath \\esp-ho-ex2010a\pst\alan.reid.pst -IsArchive

Completing the Mailbox Export Request

When a mailbox export request is completed it remains on the server until it is removed by an administrator using Remove-MailboxExportRequest.

To see all of the completed mailbox export requests run this command.

[PS] C:\>Get-MailboxExportRequest | where {$_.status -eq "Completed"}

Name                                           Mailbox                                        Status
----                                           -------                                        ------
MailboxExport                                  exchangeserverpro.net/Company/Users/Head Of... Completed

And to clear all completed mailbox export requests from Exchange run the following command.

[PS] C:\>Get-MailboxExportRequest | where {$_.status -eq "Completed"} | Remove-MailboxExportRequest

Get more Exchange Server tips at ExchangeServerPro.com

How to Enable or Disable POP3 Access for Exchange 2010 Mailboxes

Paul Cunningham — Sat, 12 Mar 2011 11:59:30 +0000

When you are using POP3 for Exchange Server 2010 you may wish to enable or disable it for specific mailbox users in your organization.

You can determine if a mailbox is enabled or disabled for POP3 using the Get-CASMailbox cmdlet.

[PS] C:\>Get-CASMailbox john.smith

Name                 ActiveSyncEnabled OWAEnabled           PopEnabled          ImapEnabled         MapiEnabled
----                 ----------------- ----------           ----------          -----------         -----------
John Smith           True              True                 True                True                True

To disable POP3 for a mailbox user use the Set-CASMailbox cmdlet.

[PS] C:\>Set-CASMailbox john.smith -PopEnabled:$false

To enable POP3 access again run the same command with a value of $true.

[PS] C:\>Set-CASMailbox john.smith -PopEnabled:$true

You can also enable or disable POP3 for multiple mailboxes at a time. For example to disable POP3 on all mailboxes run this command.

[PS] C:\>Get-Mailbox | Set-CASMailbox -PopEnabled:$false

Of course it may be easier to just disable POP3 entirely, but in some cases you might want a few people to still have access to it.

To find all mailbox users with POP3 enabled use this command.

[PS] C:\>Get-CASMailbox | where {$_.PopEnabled -eq $true}

Name                 ActiveSyncEnabled OWAEnabled           PopEnabled          ImapEnabled         MapiEnabled
----                 ----------------- ----------           ----------          -----------         -----------
Alan.Reid            True              True                 True                True                True
John Smith           True              True                 True                True                True

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server Pro » Client Access

Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade

Related posts:

Exchange 2010 FAQ: How to Minimise Downtime During Mailbox Migration from Exchange 2007

Related posts:

Exchange 2010 Local Move Request Fails with No Available Mailbox Replication Service Error

Related posts:

How to Block Non-Cached Mode Outlook Clients with Exchange 2010

Related posts:

Installing an Exchange 2007 Client Access Server on Windows Server 2008

Installing Exchange 2007 Client Access Server Pre-Requisites on Windows Server 2008

Installing the Exchange 2007 Client Access Server Role

Related posts:

Poll: Should CAS Arrays be Deployed in all Exchange 2010 Sites?

Related posts:

Exchange Server 2010 Error: Outlook Web App Didn’t Initialize

Related posts:

How to Publish POP3 Client Settings to Users with Exchange 2010 SP1

Related posts:

How to Export Mailboxes with Exchange Server 2010 SP1

Granting User Rights for Mailbox Exports in Exchange 2010 SP1

Creating a Network Share for Mailbox Exports in Exchange 2010 SP1

Exporting a Mailbox with an Exchange Server SP1 Mailbox Export Request

Exporting an Archive Mailbox with Exchange Server SP1 Mailbox Export Request

Completing the Mailbox Export Request

Related posts:

How to Enable or Disable POP3 Access for Exchange 2010 Mailboxes

Related posts: