Microsoft re-releases update rollups for Exchange 2007 and Exchange 2010

 

Microsoft Re-Releases Exchange 2010 SP2 Rollup 4, Exchange 2010 SP1 Rollup 7, Exchange 2007 SP3 Rollup 8

 

After users complains Microsoft has re-released the latest rollups update for Exchange 2010 and Exchange 2007.

Last updates address an issue in which digital signatures on files produced and signed by Microsoft will expire prematurely.

This problem is described in:
Microsoft Security Advisory 2749655 

 

New version of Exchange 2010 SP2 rollup 4 also includes an additional fix:

2756987: Outlook only returns one result after you click the “Your search returned a large number of results. Narrow your search, or click here to view all results” message.

 

The updates can be found here:

 

As always we recommend to to test new rollups in Exchange test environment, and also to wait few days or weeks before install in Exchange production environment.

 

 

Exchange 2010 database create free space (white space)

 

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:

Continue reading

Oultook 2010 Autocomplete problem

 

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.

Continue reading

Exchange 2010 list mailboxes with Full Access or Send As permissions assigned

 

In previous post Exchange 2010 Mailbox Folder Permissions we explained how to add permissions to mailbox or mailbox folder.

After a while, when you add permissions to mailbox you will forget mailbox, permissions and users.

 

Exchange 2010 get list of mailboxes with assigned permissions

 

If you want to get list of all mailboxes with assigned Full Access permisions you need to use example like below:

Get-Mailbox -Server “MX01” -ResultSize Unlimited | Get-MailboxPermission | where {($_.AccessRights -eq “FullAccess”) -and ($_.IsInherited -eq $false) -and ($_.User.ToString() -ne “NT AUTHORITY\SELF”)}

Above example will list all mailboxes on server MX01 and check assigned permissions to those mailboxes. If any of those mailboxes will have assigned Full Access permission which is not Inherited and permission is not for user “NT Authority\Self” (it means for mailbox owner) then you will receive list of mailboxes with user account name and permissions.

 

We can also check belowed permissions instead of Full Access:

Continue reading

Exchange ActiveSync problems after upgrading IPhone or IPad to iOS6

 

Lot of users reports problems with Exchange ActiveSync after upgrading IPhone or IPad to iOS6.

If you have IPhone or IPad and you upgrade your device to iOS 6, then if you want to create new ActiveSync profile on your device it fail.
The new iOS 6 has problem with populate all fields required for automatic profiles setup.

But if you already have a ActiveSync profile on your IPhone/IPad and then upgrade to iOS 6, everything works fine.

There is also another bug iOS6 with Exchange meeting invitations.

The issue appear when user with iOS 6 decline a meeting invitation.
After user decline, iOS 6 is sending meeting cancellation notices to the entire distribution list, what causes canceling the invitation for all attendees.

So users with iOS 6 are being asked no to accept or decline calendar appointments until the problem has been resolved.

Some companies are requesting theirs emloyees not upgrade to iOS 6 until a bug with Microsoft Exchange meetings invitations will be fixed.

 

 

Exchange 2010 SP1 Mailbox Folder Permission

 

Sometimes in Microsoft Exchange environment we need to add user permission to other user mailbox.

We can add Full Access permission to mailbox like below:

Add-MailboxPermissions -Identity Mailbox1 -User JSmith -AccessRights FullAccess -InheritanceType all

 

But what if we don’t want to add permissions to all folders in mailbox but only to a one mailbox folder.

With Microsoft Exchange 2010 SP1 we can add permission to specified folder for user or Security Group, (Add-MailboxFolderPermission) we can remove (Remove-MailboxFolderPermission) and also we can change this permissions (Set-MailboxFolderPermission).

To add Reviewer permissions to User1 on Inbox folder of mailbox “John Smith” we can use:

Add-MailboxFolderPermission -identity j.smith@domain.com:\Inbox -User User1 -AccessRights ReadItems

 

Now we can check permissions to John Smith Inbox folder like below:

Get-MailboxFolderPermission -Identity j.smith@domain.com:\Inbox

 

We can change permissions for User1 to mailbox Inbox folder using Set-MailboxFolderPermission from Reviewer to FolderVisible:

Set-MailboxFolderPermission -Identity j.smith@domain.com:\Inbox -User User1 -AccessRights FolderVisible

Continue reading

Remove specific messages from Exchange 2010 Server

 

Sometimes Exchange administrator need to remove messages that fit specific criteria from large number of mailboxes or from Exchange transport queues.

Removing messages from Exchange mailboxes:

To perform remove message operation from mailboxes, in Exchange 2010 RBAC Mailbox Export Import role must be assigned to the admin account. To remove messages from Exchange 2010 mailboxes we will use Search-Mailbox cmdlet.

Account used to export data from mailboxes must be:

  • an Exchange Server Administrator
  • member of local Administrators group of target server
  • Full Access permission assigned to the mailboxes

 

To add RBAC role to user Admin:

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User “Admin”

 

Sometimes you will need to add necessary permissions for user Admin to all mailboxes, then we can use:

Get-Mailbox -ResultSize unlimited | Add-MailboxPermissions -User Admin -AccessRights FullAccess -InheritanceType all

After completed removing operations, we have to remove this permissions like below:

Get-Mailbox -ResultSize unlimited |Remove-MailboxPermissions -User Admin -AccessRights FullAccess -InheritanceType all

 

To search all messages with specified subject like “Important Message” of all mailboxes on server MBX1 we have to use example like below:

Get-Mailbox -Server  "MBX1" -ResultSize Unlimited | Search-Mailbox -SearchQuery 'Subject:"*Important Message*" -targetmailbox "*SearchMailbox*" -targetfolder "*SearchFolder*" -logonly -loglevel full

Continue reading

Exchange 2010 quota warning messages issue

 

In Microsoft Exchange 2010 environments, Exchange sends a quota message to mailbox owners when mailbox size exceeds:

  • IssueWarningQuota – the lowest storage quota
  • ProhibitSendQuota – the middle storage quota
  • ProhibitSendReceiveQuota – the highest storage quota

 

All Quotas limits can be configured at mailbox or database level.

We can define time when messages are sent by specifying QuotaNotificationSchedule for Mailbox Database.

 

If we want to check QuotaNotificationSchedule use:

Get-MailboxDatabase | select name, QuotaNotificationSchedule

Continue reading

Exchange 2010 Queues export, resubmit messages

Sometimes in your Microsoft Exchange environment you can experience a problem with HUB or Edge Transport servers, when often messages stuck in Queues.

When you resolve problem with any Exchange server, sometimes it takes few minutes for Exchange to resubmit all emails, time depends on how many messages are in queues.

Until messages have one of the below status, we can manually resubmit them to the Exchange Submission Queue if queue hasn’t Suspended state:

  • mailbox Delivery queues or Remote delivery queues with status Retry
  • emails in Unreachable queue
  • emails in Poison queue

 

To manually resubmit messages in queues, you can use the following methods:

  • use the Retry-Queue cmdlet with parameter -Resubmit
  • export messages from queue to .eml message files and resubmit them by placing in the Replay directory. For Exchange 2010 default location:
    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Replay
  • open Queue Viewer or Resume-Message cmdlet to resubmit messages in poison message queue.

 

Exchange 2010 export message copy from Queue:

Continue reading

Microsoft Exchange 2010 SP3 (Service Pack 3) – announcing

The Exchange Team announced that in the first half of calendar year 2013 will be released Service Pack 3 (SP3) for Microsoft Exchange 2010.

 

New Service Pack (SP3) for Microsoft Exchange 2010 will contain new features like:

 

  • Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.
  • Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.
  • Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing

Before you will install Service Pack 3 for Exchange 2010, to add new features, you will need to update Active Directory Schema.