On TechNet websites you can find two new online videos about Microsoft Exchange Server 2013.
Both videos are about an hour long.
Watching these videos you can get familar with Exchange Server 2013.
Fist video: What´s new in Exchange 2013? explains what’s new in Microsoft Exchange 2013 like new architecture, HA, and features.
Microsoft has confirmed problems with message delivery to BlackBerry mobile devices after installation of Rollup 4 for Microsoft Exchange 2010 SP2.
This issue occurs only in specific Microsoft Exchange and BlackBerry Enterprise Server environment.
In this scenario:
You can encounter one or more of the following issues:
Currentl there is no HotFix to resolve those problems. Probably Rollup 6 for Exchange 2010 SP2 will fix this.
But Microsoft recommend below workaround:
Method 1
Install Exchange Server Service Pack 2 RU 6 when it becomes available.
Method 2
Add more agents on the BES if they are not already at the max of 15 agents.
Method 3
Temporarily reduce the number of folders in the mailbox of the user.
Method 4
Move all users who have high folder counts (>500) to their own instances of BESAgent.exe.
More informations you can find here:
With previous versions of Microsoft Exchange (2007 and 2003) when we created mailbox we had to specify mailbox database for this mailbox.
In Microsoft Exchange 2010 during mailbox creating we can let exchange to choose the database for new mailbox, or we have to select option that we want to select mailbox database.
This feature is called Automatic Mailbox Distribution – this feature allow Exchange to choose mailbox database for newly created mailbox if we don’t specify mailbox database.
By default in Microsoft Exchange 2010 all mailbox databases are enabled for provisioning, but we can disable them by setting mailbox database parameters IsExcludedFromProvisioning or IsSuspendedFromProvisioning.
IsExcludedFromProvisioning – we should use this setting to permanently exlude mailbox database from automatic mailbox distribution
IsSuspendedFromProvisioning - we should use this setting to temporarily exclude mailbox database from automatic mailbox distribution.
To check provisioning settings for mailbox databases we can use:
Get-MailboxDatabase | select name, *provisioning
Few days ago Steve Goodman published new version of Get-ExchangeEnvironmentReport.ps1 script on his Blog.
This script is really cool, and using it you can easly create report of your Mircosoft Exchange environment.
New version supports Microsoft Exchange 2013 and fixes bugs reported by users.
We think that every Exchange administrator should has this script.
Executing the script is straightforward – the only setting you need is to specify where to write the HTML file:
.\Get-ExchangeEnvironmentReport -HTMLReport c:\report.htmlIf you want it to email the results, the follow parameters are available to allow the report to be sent directly from the script:
.\Get-ExchangeEnvironmentReport -HTMLReport c:\report.html -SendMail:$true -MailFrom:you@example.com -MailTo:you@example.com -MailServer:smtp.example.com
Read more about this script: Steve Goodman Blog
You can download this script here: Get-ExchangeEnvironmentReport.ps1
When you expirience the following issues in your Microsoft Exchange environment:
and in Event Log you can find:
Event ID: 3
Description:
WebHost failed to process a request.
Event ID: 1031
Description:
The service configuration file could not be loaded for the following reason: System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize —> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config line 134) at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
Event ID: 1002
Description:
Unable to start the Microsoft Exchange Mail Submission service: System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize —> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config
This mean that you have installed KB2756920, you can read about it more here: KB2756920 .NET Framework Update.
To fix those issues you need to install HotFix: KB2637518 Hotfix for Microsoft .NET Framework 3.5.1 on Windows 7 RTM and Windows Server 2008 R2 RTM
When you are trying to remove or wipe mobile device connected to mailbox, you can get error like below:
The ActiveSyncDevice Cannot be Found
You will get this error when you are trying to remove mobile device which were connected to user mailbox, and after user account was moved to other OU in Active Directory.
It’s caused because EMC can’t find “path” to old mobile device.
You can easly check this using two powershell commands:
Get-ActiveSyncDevice
Get-ActiveSyncDeviceStatistics
If you run CMDlet Get-ActiveSyncDeviceStatistics for some mailbox like below:
Get-ActiveSyncDeviceStatistics -mailbox JSmith | select DeviceId, Identity
you will get:
DeviceID Identity -------- -------- androidc1640524549 domain.local/Users/Test1/Smith John/..... androidc2040902280 domain.local/Users/Test2/Smith John/.....
next try to run CMDlet Get-ActiveSyncDevice for the same mailbox:
Get-ActiveSyncDevice -Mailbox JSmith | select DeviceId, Identity
you will get:
DeviceID Identity -------- -------- androidc1640524549 domain.local/Users/Test2/Smith John/..... androidc2040902280 domain.local/Users/Test2/Smith John/.....
Searching message tracking logs with cmdlet Get-MessageTrackingLog can take long time when you need to search few Hub Transport Servers.
Below command will search all transport logs on all Exchange Hub Transport servers and find only messages with subject “Important *”:
Get-TransportServer | Get-MessageTrackingLog -resultsize unlimited -start (get-date).adddays(-2) -end (get-date) -eventid Deliver | ? {$_.messagesubject -like "Important *"}
You can speed up this search by using remoting Powershell using CMDlet Invoke-Command.
You need to modify command like below and add Invoke-Command:
Get-TransportServer | Invoke-Command {Get-MessageTrackingLog -resultsize unlimited -start (get-date).adddays(-2) -end (get-date) -eventid Deliver | ? {$_.messagesubject -like "Important *"}}
Symantec released new version of Enterprise Vault, number of this version 10.0.3
New version can be downloaded from https://fileconnect.symantec.com/ where you need to type serial number.
How to obtain the installation download and license keys for Enterprise Vault
PDF file with compatibility list you can download from here:
compatibility_charts.pdf
Whats new in Symantec Enterprise Vault 10.0.3 ?
New version supports Exchange 2013, SharePoint 2013 and Outlook 2013.
Below you can find few informations whats new in this version:
When we want to check DAG (Database Availability Groups) status we should use two below powershell CMDlet’s:
Get-MailboxDatabaseCopyStatus will check and show status of all mailbox databases in all the DAG’s in Microsoft Exchange environment.
Test-ReplicationHealth check all aspects of replication and replay, or to provide status for a specific Mailbox server in a database availability group (DAG).
To check copy status of all mailbox databases we should use:
(Get-DatabaseAvailabilityGroup) | ForEach {$_.Servers | ForEach {Get-MailboxDatabaseCopyStatus -Server $_}}If you are using mobile devices with Windows Phone 8, and you sync mail with Exchange 
Server, you can get Error Code 86000C29
This problem is caused by Microsoft Exchange ActiveSync policy which prevent to sync your mailbox with mobile device with Windows Phone 8
When your mobile device is trying to sync mailbox from Exchange Server, first ActiveSync policy is enforced for this device. If device can’t pass policy requirements than it can’t sync mailbox.
Because mostly ActiveSync policy Require Encryption on Storage Card.
So to resolve this issue you need to open EMC, Organization Configuration, Client Access, tab Exchange ActiveSync Mailbox Policies.
English 
polski