Microsoft Outlook 2007 Clients won't connect to Exchange Server 2013






















Microsoft Outlook 2007 Clients lower than Service Pack 3 will not connect to Exchange Server 2013.

Solution:

Note: This (12.0.6665.5003 Standard SP3) build number of Outlook 2007 Service Pack 3 will work fine with Exchange 2013 Server.


You will need to install the following packages to get it done...

1. office2007sp3-kb2526086-fullfile-en-us (Service Pack 3 Bundle)2. outlookloc2007-kb2687404-fullfile-x86-glb (Hotfix)

Download links are given below;

office2007sp3-kb2526086-fullfile-en-us

outlookloc2007-kb2687404-fullfile-x86-glb


For Outlook 2010;

Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 update, link is given below.
Outlook 2010 SP1 November 2012 Hotfix



Please do not hesitate if you have any further question.

Comments

Post a Comment

Popular posts from this blog

Image
Faulting application name: hostcontrollerservice.exe, version: 16.0.775.0, time stamp: 0x5211bea8 Application Error Faulting application name: hostcontrollerservice.exe, version: 16.0.775.0, time stamp: 0x5211bea8 Faulting module name: KERNELBASE.dll, version: 6.2.9200.17637, time stamp: 0x56980227 Exception code: 0xe0434352 Fault offset: 0x000000000004b418 Faulting process id: 0x4878 Faulting application start time: 0x01d2a139409a0421 Faulting application path: D:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\hostcontrollerservice.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 80ceb831-0d2c-11e7-950e-005056be650e Faulting package full name: Faulting package-relative application ID: Solution: Stop the Microsoft Exchange Search service and Microsoft Exchange Search Host Controller (this one probably already is). Edit the file installconfig located in C: \ Program Files \ Microsoft \ Exchange Server \ V15 \ Bin \ Search \ Ceres \ Ins
Read more

How to Configure ActiveSync Virtual Directories in coexistence between exchange 2007 and 2013, when you have different external and internal namespaces

Image
In coexistence environment (exchange 2007-2013), we could set Exchange 2013 ActiveSync External URL to mail.yourexternaldomain.com and set Internal URL to mail.yourinternaldomain.com . And set Exchange 2007 Internal URL to  mail.yourinternaldomain.com  and set External URL to Null .  We could run the following commands. Set-ActiveSyncVirtualDirectory -Identity "<CAS2013>\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl "https:// mail.yourexternaldomain.com /Microsoft-Server-ActiveSync"    –InternalURL “https:// mail.yourinternaldomain.com /Microsoft-Server ActiveSync” Set-ActiveSyncVirtualDirectory -Identity "<CAS2007>\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl $Null    –InternalURL “https:// mail.yourinternaldomain.com  /Microsoft-Server-ActiveSync”
Read more

How to prevent sending external e-mail, but allow internal e-mail in Microsoft Exchange Server.

Image
Sometime may be you have internal & external domains configured in your organization and you don't want allow internal users to send emails outside the organization or to the public domains. You can achieve this using Microsoft Exchange Transport rules. Suppose you have all internal users in OU name "InternalMail" create a distribution group in the OU and add all internal users as member. Open up Exchange admin console " https://yourexchangeserver/ecp " and navigate to "mail flow" -> "Rules" Click the + button -> " Restrict messages by sender or recipient " In this example " extblk " is a distribution group. Added two conditions first is " the recipient is located " second is " the sender is a member of " Review the Rule mode is set to "Enforce" and leave other settings default and save the rule. You are done !
Read more