ExchangeBlog »

Monthly Archives: March 2014

Office Mobile now for free for Android and IPhone

  By Remigiusz Szatkowski | 30/03/2014 - 21:27 |
Leave a comment

The world has changed, Microsoft gives us something for free and for all of us.Office Mobile

Few days ago Microsoft released an update for Office Mobile for Androids and IPhone devices. But this update makes that Office Mobile is now free for home use for all users.

You can get an application from Apple App Store or Google Play.

Now you can not only read but also edit Microsoft documents.

For Android devices you need to have at least Android 4.0, and you can install Office Mobile to your smartphones not tablets.

Someone says that Microsoft had to give Office Mobile for free because Apple gives iWorks for mobile devices for free and also Google gives QuickOffice.

Exchange 2013 SP1 transport agents issues – KB2938053

  By Remigiusz Szatkowski | 07/03/2014 - 11:04 |
Leave a comment

After you install Microsoft Exchange Server 2013 Service Pack 1 (SP1) or you upgrade an existing Microsoft Exchange Server 2013 installation to Exchange Server 2013 SP1, third-party or custom-developed transport agents cannot be installed correctly.

Additionally, the Microsoft Exchange Transport service (MSExchangeTransport.exe) cannot start automatically. Specifically, you cannot enable third-party products that rely on transport agents. For example, you cannot enable anti-malware software or custom-developed transport agents.

Products experiencing the issue are:

  • TrendMicro ScanMail
  • McAfee Email Security (GroupShield)
  • Symantec Mail Security for Exchange
  • AVG for Servers
  • ESET Mail Security for Exchange
  • CodeTwo Exchange Rules

This problem occurs because the global assembly cache (GAC) policy configuration files contain invalid XML code.

Microsoft published article about this issue KB2938053 where you can download script which will repair xml files Exchange2013-KB2938053-FixIt.zip.

 

 

Exchange 2013 SP1 not accepting emails

  By Remigiusz Szatkowski | 05/03/2014 - 14:03 |
Leave a comment

After installing SP1 for Microsoft Exchange 2013, you can expect some issues.

One of them is that after applying SP1 your Exchange server will stop accepting inbound emails and connections to port 25.

If you check Event Log, in Applications Log you will find entries with ID 7012 with source MSExchangeFrontEndTransport and with information:

“The service state for frontedn transport is inconsistent. Current state – Inactive. Expected state – Active.”

Using Powershell you can check state of this component:

Get-ServerComponentState servername01 -Component FrontendTransport

But you will see that this component is Active.

Also you can test inbound external email using Microsoft Remove Connectivity Analyzer, where you can find information about connection error to TCP port 25.

To resolve this issue you need to restart Microsoft Exchange Frontend Transport service.

You can do this using Powershell:

Restart-Service MSExchangeFrontendTransport

or just restart service in Services.msc.

When you do this, your server should now accept connections to port 25, and also you shouldn’t see warnings in Application Log.

 

 

Exchange 2013 SP1 MAPI/HTTP not working

  By Remigiusz Szatkowski | 04/03/2014 - 10:54 | ,
Leave a comment

Installation of SP1 for Microsoft Exchange 2013 introduces new protocol for Outlook to Exchange connections.
You can use MAPI/HTTP instead of RPC/HTTP.

First, you need to meet some requirements:

 

But sometimes when you do all of those requirements, you can’t still connect to Exchange 2013 SP1 using MAPI/HTTP.

To check protocol used by Outlook to connect to Exchange Server just hold Ctrl key and clik right on Outlook icon in System Tray and select Connection Status:

RPCHttp

Continue reading →

Exchange 2013 SP1 new features

  By Remigiusz Szatkowski | 03/03/2014 - 14:33 | ,
Leave a comment

Last time we metion about Service Pack 1 for Microsoft Exchange 2013.

Below we present new features and improvements included in Service Pack 1:

Exchange Admin Center Command Logging

Finally Exchange 2013 will “tell” you how to use Powershell.
Like in Exchange 2010 EMC now in Exchange 2013 SP1 EAC you can see Powershell command for operation which was made in EAC.

The feature can be found in the top-right corner of the EAC, when clicking the question mark button, select Show Command Logging

ShowCommandLogging1

ShowCommandLogging

You can see up to 500 command executed in the EAC user interface.

 

Support for Windows Server 2012 R2

Exchange 2013 SP1 adds Windows Server 2012 R2 as a supported operating system and Active Directory environment for both domain and forest functional levels.

Better text editor in OWA

In OWA Exchange Team added rich text editing features. Now you can easly add or modify tables, more paste options, previews to linked content.

Continue reading →