Wednesday, May 28, 2014

High Volume of Event ID 6941 during DirSync Runs

With Directory Sync tool v1.0.6385.0012 and higher, administrators may notice a large volume of Error-level entries in the event log during Sync runs. These entries have a Source of FIMSynchronizationService, an EventID of 6941 and a Description generally starting with “ECMA2 MA export run caused an error”.

This is expected behavior. In old versions of DirSync, these events were suppressed by the tool, but the new version of the synchronization engine now logs this information to the event log. This is the same set of information that is sent to the Technical Notification Contact via e-mail.

Office 365 Domain Limit

Microsoft has increased the maximum number of domains per tenant allowed in Office 365 by 50%, from 600 domains to 900 domains.
The increase is automatic, so administrators do not need to do anything to take advantage of this improvement. Up to 900 domains can be added from the Office 365 admin portal or via remote PowerShell.

Thursday, May 15, 2014

Message Trace Extended for 90 Days in Exchange Online

The lack of Message Tracking Logs in Exchange Online has been a concern for some organizations in their adoption of Office 365. Although Message Trace provided a good source of data for investigations, it was limited to the last 7 days of e-mail traffic, meaning administrators would have to frequently extract this data so it could be used later if needed.
 
Not anymore! Exchange Online Protection (EOP) and Exchange Online administrators can now check message trace information for the last 90 days.
 
To access this feature, in the Exchange admin center, click Mail flow and then click on Message trace. When we search for a message sent in the past seven days, we can view the results immediately. However, when searching for older messages, we have to submit a request for an extended message trace. To do this, simply choose the custom date range option and specify any date range in the past 90 days:
 
 
When we create a new extended trace request, we opt to receive an e-mail notification when the trace has been completed by entering an e-mail address in the Notification email address field:
 
 
 We can also choose to receive a summary list report or a detailed message trace report:
  • Summary list report displays basic information about the messages traced, such as time, whether it was delivered, its subject, number of bytes, and so on;
  • Detailed message trace report provides more details about messages than the summary list. To get a detailed report, when creating a new trace request, select the Include message events and routing details with report check box. In a detailed trace, all key events with all details that are available in the message tracking logs are exposed, providing an excellent data source for detailed investigations.
 
Typically, trace requests are processed within hours. The list of submitted requests and their status is displayed on the pending or completed traces page in the Exchange admin center (by clicking on View pending or completed traces under message trace) making it easy to check if a request has been completed:
 
 
Once a message trace request has completed processing, you can click Download this report in the right-hand side to view the results in a downloadable CSV file.

Wednesday, May 14, 2014

Exchange 2013 Platform Options

For BDMs and architects, this model describes the available platform options for Exchange 2013. Customers can choose from Exchange Online with Office 365, Hybrid Exchange, Exchange Server on-premises and Hosted Exchange. The poster includes details of each architectural option, including the most ideal scenarios for each, the license requirements and IT Pro responsibilities.

Get the poster now on PDF or Visio format from the Download Center here.
 
 

Wednesday, May 7, 2014

Exchange Cmdlet History in Exchange 2010/2013

Having a list of all Exchange cmdlets we ran is always useful. Besides the usual methods of getting these from the PowerShell window history (by pressing the F7 key) or from the administrator audit logs, for example, the Event Log also has a list of these cmdlets!

Both in Exchange 2010 and 2013, most cmdlets are recorded under the Applications and Services Logs -> Microsoft -> MsExchange Management event log.

In here we have entries under the MSExchange CmdletLogs source and with an EventID of 1 (cmdlet ran successfully) and/or 6 (cmdlets that failed).

For example, by running the following cmdlet: Add-MailboxPermission Mota –User Nuno –AccessRights FullAccess –InheritanceType All

We get this entry in the event log: Cmdlet Add-MailboxPermission, parameters {Identity=Mota, User=Nuno, AccessRights={FullAccess}, InheritanceType=All}.

NOTE: cmdlets started with Get-* do not get logged.