In Exchange Server environment where is a limit of ActiveSync partnership with mailbox.

When you reach this limit then you won’t be able to connect any new devices to the mailbox.

This limit is set in ThrottlingPolicy using parameter EASMaxDevices

To check current setting of EASMaxDevices, open Exchange Management Shell and run:

Get-ThrottlingPolicy | select name, EASMaxDevices, EASMaxConcurrency

As a result you will get all ThrottlingPolicies available in Exchange environment and how many mobile devices can you connect to the mailbox, and also using EASMaxConcurrency you will see how many connections in one time can be accepted to the mailbox.

(...)
Read the rest of Exchange 2010 count mailbox mobile devices partnership (255 words)

© Remigiusz Szatkowski for ExchangeBlog, 2014. | Permalink | No comment | Add to del.icio.us
Post tags: ActiveSync, EASMaxDevices, Exchange 2010, Mobile Device, ThrottlingPolicy

Feed enhanced by Better Feed from Ozh

Exchange 2010 mailboxes list with forward to address enabled:

Many times in our Exchange 2010 environment we need to forward messages from one mailbox to another.
Users always have a lot of reasons to enable Forward To option.

After a while we mostly forget which mailbox has enabled Forward To option, and we forget to disable it.

Every now and then we should check, which mailbox has Exchange 2010 Forward To option enabled and if we don’t need it anymore, disable it.

We will spend a lot of time If we would like to use Exchange Mangement Console to verify mailbox Forward To.

Much better option is to use Exchange Management Shell with Get-Mailbox CMDlet.

To get list of all mailboxes in Exchange 2010 with enabled option Forward To we need to run below command:

Get-Mailbox -server MX01 -Filter {ForwardingAddress -like '*'} | Select-Object Name, ForwardingAddress

As a result we will get list of all mailboxes on MX01 Exchange 2010 server with Forward To option enabled.
When we have many mailboxes we can write this list to file like below:

Get-Mailbox -server MX01 -Filter {ForwardingAddress -like '*'} | select-object Name,ForwardingAddress | Export-Csv "D:\Scripts\Forwarding.csv"

Exchange 2010 list of mailboxes with enabled InboxRule:

Normal user can’t enable Forwad To option for mailbox, but he can create in Outlook or OWA InboxRule which will forward or redirect emails to other mailbox.

All mailbox rules created by users are stored in Exchange 2010 mailboxes. So again from Exchange Management Shell we can check all mailboxes do they have any mailbox rules and if they have are they using to forward or redirect messages.

To check mailbox for user created Inbox Rules with option Redirect To or Forward To we need to use Get-InboxRule CMDlet like below:

(...)
Read the rest of Exchange 2010 list mailboxes with forward to address or inbox rule (94 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | No comment | Add to del.icio.us
Post tags:

Feed enhanced by Better Feed from Ozh

Before we explain how to get mailbox move history, first we will explain how to move mailbox between mailbox databases in Microsoft Exchange 2010.

Exchange 2010 move mailbox:

To move mailbox between two mailbox databases in Exchange 2010 we can use:

• EMC – Exchange Management Console
• EMS – Exchange Management Shell

EMC Exchange Management Console

To move mailbox from one database to another one, we need to open EMC, find mailbox which we want to move and then right click on it and select New Local Move Request

Next we have to select target mailbox database and choose how many bad items can be skipped during this move.

I think this move is quite simple in EMC.

EMS Exchange Management Shell

We prefer to use EMS to move any mailbox, a specially when you need to move few mailboxes. CMDlets which can be used to move mailbox you can easly use in Powershell script.

You need to have RBAC permission to move mailboxes.

Below you can find CMDlets which you can use to move mailbox, monitor mailbox move, suspend, resume, and also needed RBAC permissions:

To move mailbox you need to create move request like below:

New-MoveRequest -identity "John Smith" -TargetDatabase "MXDB03"

Above command will create move request to move John Smith to mailbox database MXDB03

(...)
Read the rest of Exchange 2010 mailbox move history (404 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | No comment | Add to del.icio.us
Post tags: Exchange 2010 Mailbox Replication Service, Exchange move mailbox history, IncludeMoveHistory, IncludeMoveReport, Move Mailbox, MRS, MSExchangeMailboxReplication.exe.config, New Local Move Request

Feed enhanced by Better Feed from Ozh

Exchange 2010 Get list of mobile devices with activesync for user:

Sometimes we want to know what kind of mobile devices uses ours users.

If we want to check only one user it’s not a problem. We can use Powershell cmdlet:

Get-ActiveSyncDeviceStatistics

If we want to know what activesync devices uses John Smith we need to run:

Get-ActiveSyncDeviceStatistics -Mailbox "John Smith" | fl

or if we want to specify the output:

Get-ActiveSyncDeviceStatistics -Mailbox "John Smith" | Select-Object @{n="Mailbox";e={$mailbox}}, LastSuccessSync, Status, DeviceID, DeviceType, DeviceUserAgent, DeviceModel, DeviceIMEI, DeviceOS

Exchange 2010 get list of all users activesync devices

Unfortunatelly mostly we want to get list of all mobile devices used by users.

This is not so easy because every user can use more than one mobile device: cell phones, tablets and other devices.

(...)
Read the rest of Exchange 2010 ActiveSync Devices list (299 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | 3 comments | Add to del.icio.us
Post tags: Exchange activesync devices, Exchange mobile devices list, Get-ActiveSyncDeviceStatistics, Get-Casmailbo, HasActiveSyncDevicePartnership, LastSuccessSync

Feed enhanced by Better Feed from Ozh

When you have Microsoft Exchange 2010 environment you can have problem with Exchange database size growing.

This is common problem and mostly caused by Exchange 2010 mailbox dumpster.

But if you have problem with mailbox databases backup, then all items deleted by users and all deleted mailboxes will not be purged until backup will end successful.

If you check size of all mailboxes in Exchange 2010 mailbox database, the sum of mailboxes can be less than mailbox database size. Yes we know that mailbox database has AvailableNewMailboxSpace but you can check that sum of mailboxes size and size of mailbox database white space can be also less then size of .edb file.

You can find informations how to reduce Exchange database size by moving all mailboxes from database to new one, or to dismount database and use Eseutil to defragment mailbox database. You can also find all disconnected mailboxes in database and purge them.

We wrote about this in post:
Microsoft Exchange 2010 how to reduce the size of the database

You can find information on Microsoft Support Website An Exchange Server 2010 database store grows unexpectedly large that if you want to stop mailbox database unexpected growth you need to install Rollup 1 for Microsoft Exchange 2010 SP2.

Unexpected growth of Exchange 2010 mailbox database can be caused by using:

• using jurnaling mailbox in Exchange 2010 environment
• using a third-party email message archival system

This issue can occur if the Microsoft Exchange Information Store service does not remove the deleted messages from the database.

Unfortunatelly when you use third-party email message archival system like Symantec Enterprise Vault, all emails moved to archive are deleted from user mailbox but they still remain in dumpster.

When you install Rollup 1 for Exchange 2010 SP2 it will probably fix this problem but it will fix only problem with new data added to archive but not clean the dirty pages or whitespace from preexisisting databases. 

More information you can find on Symantec Support Website:
Archiving of an Exchange 2010 database does not generate the expected amount of re-usable whitespace

How to resolve Exchange 2010 database growth:

When you apply Rollup 1 for Exchange 2010 SP2 you need to check few mailbox databases properties to make sure that all retentions and Quotas are configured properly.

To check Exchange 2010 mailbox database items retention like Mailbox, Deleted items and EventHistoryRetention you need to run Exchange Mangement Shell (EMS) with command:

(...)
Read the rest of Exchange 2010 Database size growing problem (790 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | 3 comments | Add to del.icio.us
Post tags: AvailableNewMailboxSpace, dumpster purge, Exchange 2010 database size grow, Exchange 2010 dumpster size problem, Exchange deleted items, search-mailbox, search-mailbox with data, search-mailbox with data, Symantec Enterprise Vault

Feed enhanced by Better Feed from Ozh

With every release of Rollup Update for Microsoft Exchange we are trying to get to know what Microsoft Exchange version we use.

When you check Microsoft Support Website Determine Exchange Version you will find out that there are two ways to get Microsoft Exchange version and build version.

Get Exchange 2007, 2010 version using Exchange Management Console:

1. Start the Microsoft Exchange Management console.
2. In the navigation pane, expand the Server Configuration objects until you locate the server object, and then select the server object.
3. On the right side, notice the Exchange version number.

Get Exchange 2007, 2010 version using Exchange Management Shell command:

1. Start the Microsoft Exchange Management shell.
2. Run the following command at the command line:

Get-ExchangeServer | select name, AdminDisplayVersion, ExchangeVersion

Unfortunatelly using both of those methods we won’t get correct Exchange 2010, 2007 version.

(...)
Read the rest of Exchange 2010 get version number, build number (109 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | No comment | Add to del.icio.us
Post tags:

Feed enhanced by Better Feed from Ozh

Installation of Rollup 4 for Exchange 2010 SP2 fails:

Few days ago Microsoft has released new versions of latest Rollups for Exchange 2010 and 2007.

All of those rollups (version 2) we can install on server without uninstalling previous version.

When you are trying to install version 2 of Rollup 4 for Exchange 2010 SP2 you can get error 0x80070643 

How to resolve issue with Rollup 4 v2 for Exchange 2010 SP2 error code 0x80070643

If during installation of Rollup 4 version 2 you will get error code 0x80070643 then you have to do following:

1. uninstall from Windows Server Windows Management Framework 3.0  (WMF 3.0) (Windows6.1-KB2506143-x64)
2. reboot server
3. install update Rollup 4-v2 for Exchange 2010 SP2
4. reboot server
5. install Windows Management Framework 3.0 after installing the Rollup 4-v2
   because of issues with installation of Rollup 5 and WMF 3.0 it’s better to not install WMF 3.0
6. reboot server

We hope it will also help to update yours environments.

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | 16 comments | Add to del.icio.us
Post tags: error code 0x80070643, Exchange 2010 SP2 Rollup 4 v2, Windows Management Framework 3.0

Feed enhanced by Better Feed from Ozh

This problem is not common but quite annoying and usually hard to understood by users.

In most cases problem occurs If you remove mailbox and re-create it with the same AD account , for an example after firing and  re-hiring of the employee after some time.

It also occurs after migrations.

When user sends an email to a recipient, to which earlier messages was delivered without any problem. Sudennly gets an Non Delivery Report with this content:

Delivery has failed to these recipients or distribution lists:: 

Test User

The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator..

Diagnostic information for administrators: 

Generating server: server01.exchange

IMCEAEX_O=Company_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT29_CN=RECIPIENTS_CN=user@xxx.xx
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

And now the question is: Why?

(...)
Read the rest of IMCEAEX i NDR (215 words)

© lukg for ExchangeBlog, 2012. | Permalink | No comment | Add to del.icio.us
Post tags: Exchange NDR, IMCEAEX, legacyExchangeDN, Outlook AutoComplete, X500

Feed enhanced by Better Feed from Ozh

Every mailbox database in Exchange 2010 has white space. It’s free space which can be used before .edb file will grow.

Sometimes we need to create free space in database right now if we want to avoid of growing of .edb file.

To get free space in mailbox database we can do the following:

• move few mailboxes from mailbox database to other mailbox database
• purge disabled mailboxes
• purge soft-deleted mailboxes

Exchange 2010 check AvailableNewMailboxSpace (white space) in database:

We can check available white space for new mailboxes in mailbox databases using powershell like below:

Get-MailboxDatabase -server MBX1 | select Name, DatabaseSize, AvailableNewMailboxSpace

or if we want to check only one mailbox database:

Get-MailboxDatabase DB01 | select Name, DatabaseSize, AvailableNewMailboxSpace

If we want to see all disabled mailboxes (disabled today) in database we have to wait for scheduled Cleanup Agent or we can run it from powershell:

Get-MailboxDatabase -server MBX1 | Clean-MailboxDatabase

When we run above command, all mailboxes disabled today, will be marked as disabled and we can find them in Disconnected Mailboxes.

Exchange 2010 list disabled mailboxes:

We can get informations about disabled mailboxes to know how much space we will get when we purge disabled or soft-deleted mailboxes.

To list all disabled mailboxes in all mailbox databases in server MBX1 run:

(...)
Read the rest of Exchange 2010 database create free space (white space) (353 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | One comment | Add to del.icio.us
Post tags: Exchange 2010

Feed enhanced by Better Feed from Ozh

Very often we meet with Microsoft Outlook autocomplete problem.

In previous versions of Outlook like 2007, autocomplete file was stored in .nk2 file in user profilename.

Outlook 2010 doesn’t use the .nk2 file anymore for maintaining your nickname cache.

With Outlook 2010 and Exchange 2010, autocomplete cache is stored with user mailbox in a hidden message.
This lets the cache roam with your Exchange mailbox so that you have to access to your cache on any client you use to access your mailbox.

But sometimes Microsoft Outlook 2010 autocomplete doesn’t work.

Fix Microsoft Outlook 2010 Autocomplete function:

You can try to fix problem following the below steps:

First if you don’t want to lose your suggested contacts, export them from Outlook to some folder on your computer.

(...)
Read the rest of Oultook 2010 Autocomplete problem (173 words)

© Remigiusz Szatkowski for ExchangeBlog, 2012. | Permalink | 2 comments | Add to del.icio.us
Post tags: Microsoft Outlook 2010 Autocomplete

Feed enhanced by Better Feed from Ozh