We have already published the list of the new PowerShell commands available in Microsoft Exchange 2013.
You can read about it here:
Exchange 2013 Powershell
It turns out that with the appearance of additional new commands to help you work with Exchange 2013 using Powershell also disappeared a few requests to use public folders. Probably has something to do with the change the organization of public folders in the new Exchange.
The following commands are no longer available in Exchange 2013:
Below that systems with which browsers support the latest solutions used in Outlook Web App (OWA)
descriptions:
When you want to find something in Microsoft Outlook you can use Search Bar.
To do this press Ctrl+E or just click in Search Bar.
The search bar in the new Microsoft Outlook 2013 allows us to select items in search:
But in Microsoft Outlook you can use more options which will help you to find something.
You have to just write specified query in search box.
like:
messagesize:>5mb – find all messages which size is more than 5MB.
subject:”some subject” – find all messages with subject some subject
also you can use logical operators like AND, NOT, OR, <, >, = to refine your search.
Remember: Logical operators must be typed in uppercase letters.
More examples of search criteria can be found below in table:
On 13th August 2012 Microsoft released next update for Microsoft Exchange 2010 SP1.
This time this is Rollup 7 (KB2743248)
To download this update Rollup 7 for Exchange 2010 SP1 visit link:
Update Rollup 7 for Exchange Server 2010 Service Pack 1 (KB2743248)
Update Rollup 7 for Exchange Server 2010 SP1 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
Full description of new update can find here:
Description of Update Rollup 7 for Exchange Server 2010 Service Pack 1
New update for Microsoft Exchange 2007 SP3 was released on August 13th 2012
This is Rollup 8 for Microsoft Exchange 2007 SP3 which can be downloaded from Microsoft Download Center:
This update contains a number of customer reported and internally found issues.
For detailed description of this update go to:
On August 13th 2012, the Microsoft Exchange team released Rollup 4 for Exchange Server 2010 SP2.
This update Rollup 4 can be downloaded from Microsoft Download Center:
This update contains a number of customer reported and internally found issues.
Detailed description of Update Rollup 4 for Exchange Server 2010 Service Pack 2 can be found here:
Remember, you only need to download the latest update for the version of Exchange that you’re running.
As is known in the Microsoft Exchange database size after removal of the mailboxes is not decreasing but remains the same.
Created the database “gap” so called White Space which tells us about the amount of available space, which can be used without the need to increase the size of the database file .edb.
Only after completing the White Space, a further increase in the size of mailboxes in the database, it will increase the file size .edb file.
In the case of Microsoft Exchange databases such solution is problematic, because in order to reduce file size .edb after removing mailboxes from the database we use the most with ESEUTIL, which have performed defrag the database.
If any of you considering installing Exchnage 2010 SP2 with RU1 or RU2 or Ru3, the following information is addressed to you.
If your Exchange Organization have many Exchange Servers with CAS roles with different Exchange version, then after upgrade any of CAS server to Exchange 2010 SP2 with RU1 or RU2 or RU3 you can have problems with CAS to CAS proxying.
In scenario where an Exchange 2010 SP2 RU1 Client Access server is proxying to an earlier version of Exchange 2010 or Exchange 2007 Client Access server, then you are affected with a problem to use OWA.
In Event Log you can find errors like:
Event ID: 4999 Log Name: Application Source: MSExchange Common Task Category: General Level: Error Description: Watson report about to be sent for process id: 744, with parameters: E12, c-RTL-AMD64, 14.02.0283.003, OWA, M.E.Clients.Owa, M.E.C.O.C.ProxyUtilities.UpdateProxyUserContextIdFromResponse, M.E.C.O.Core.OwaAsyncOperationException, 413, 14.02.0283.003.
If in the Microsoft Exchange Server 2010 we delete mailbox users by selecting the Remove or Disable, mailboxes and their contents are still stored in the Exchange database.
The difference between the operation Remove and Disable:
If you want to see a list of disconnected mailboxes in specified Exchange databasethen use the command:
Get-MailboxStatistics -Database "MailboxDatabase" | Where { $_.DisconnectDate -ne $null } | select DisplayName, DisconnectDate,TotalItemSize, TotalDeletedItemSize
to show all disconnected mailboxes in specified mailbox server:
Get-MailboxStatistics -Server MBXServer | where { $_.DisconnectDate -ne $null } | select DisplayName,DisconnectDate | sort DisconnectDate
If you use Outlook with internet mailbox or with Exchange cached mode, outlook will use .pst or .ost file to store data.
Each of this files has his own maximum data limit supported by Outlook.
If this limit is reached .pst or .ost files are permitted to add any more data.
If outlook pst, ost file reach the size limit then you will get the warning.
Below, in table you can check maximum size limit, depended on Outlook version.
Outlook 2010
| Name | Type | Valid Data Range | Default |
| MaxLargeFileSize | REG_DWORD | 0x00000001 – 0x0000C800 | 0x0000C800 51,200 (50 GB) |
| WarnLargeFileSize | REG_DWORD | 0x00000000 – 0x0000BE00 | 0x0000BE00 48,640 (47.5 GB) |
| MaxFileSize | REG_DWORD | 0x001F4400 – 0x7C004400 | 0x7BB04400 2,075,149,312 (1.933 GB) |
| WarnFileSize | REG_DWORD | 0x00042400 – 0x7C004400 | 0x74404400 1,950,368,768 (1.816 GB) |
English 
polski