Lync 2013 presence in Exchange 2013 OWA - 0xc3e93d6a SIPPROXY_E_CONNECTION_UNKNOWN_SERVER

Single Lync 2013 server on Server 2012 R2
Single Exchange 2013 server on Server 2012
Latest patches and updates installed on both servers
Internal Certificate Authority issued certificates
Subject name on EX13 certificate is same as hostname and configured on SMTP, IIS, POP, IMAP, and UM services (Do I even need UM installed?)
I have been working on this for a few days now. I have tried all the blogs and TechNet articles I could find. I even created a list of commands to configure the Exchange and Lync servers.
**Exchange Server
Configure-EnterprisePartnerApplication.ps1 -AuthMetaDataUrl
https://c2nsi-svr-lync1.cantrelloffice.home/metadata/json/1 -ApplicationType Lync
Get-ExchangeCertificate | where-object {$_.services -like “*iis*” } | fl subject, issuer, services, thumbprint
Get-OwaVirtualDirectory -ShowBackEndVirtualDirectories -server c2nsi-svr-ex13.cantrelloffice.home | Set-OwaVirtualDirectory -InstantMessagingEnabled $true -InstantMessagingType OCS -InstantMessagingCertificateThumbprint E32937A41A7658AB8277BE6BD9BEF28D4DC43BFC
–InstantMessagingServerName c2nsi-svr-lync1.cantrelloffice.home
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory –InstantMessagingEnabled $True -InstantMessagingType OCS
Notepad "E:\Program Files\Exchange\V15\ClientAccess\Owa\web.config"
<add key="IMCertificateThumbprint" value="E32937A41A7658AB8277BE6BD9BEF28D4DC43BFC" />
<add key="IMServerName" value="c2nsi-svr-lync1.cantrelloffice.home" />
C:\Windows\System32\Inetsrv\Appcmd.exe recycle apppool /apppool.name:"MSExchangeOWAAppPool"
**Lync Server
Get-Cspool | where-object {$_.services –like “*UserServer*”} | fl site, fqdn
Set-CsOAuthConfiguration -Identity global -Realm "cantrelloffice.home" -ExchangeAutodiscoverUrl "https://c2nsi-svr-ex13.cantrelloffice.home/autodiscover/autodiscover.svc
New-CsPartnerApplication -identity Exchange -ApplicationTrustLevel Full -MetadataUrl
https://c2nsi-svr-ex13.cantrelloffice.home/autodiscover/metadata/json/1
New-CsTrustedApplicationPool -Identity c2nsi-svr-ex13.cantrelloffice.home -Registrar c2nsi-svr-lync1.cantrelloffice.home -Site CantrellOffice -RequiresReplication $False
New-CsTrustedApplication -ApplicationId OutlookWebAccess -TrustedApplicationPoolFqdn c2nsi-svr-ex13.cantrelloffice.home -Port 5199
Enable-CsTopology
Anyone able to help me?

Excerpt from OCSLogger SIPStack log file:
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026d8 (SIPStack,LiteralToIPv6Context::Clear:IPv6Literal.cpp(272))( 00000034F1EBDE60 ) Clear
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026d9 (SIPStack,LiteralToIPv6Context::Append:IPv6Literal.cpp(191))( 00000034F1EBDE60 ) Not an IPv6 literal: 192.168.1.213
TL_NOISE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.000026da ((Shared),CSIPGenericParamList::GetParamValue:SIPGenericParam.cpp(231))( 00000034F35DFBE0 ) Enter
TL_VERBOSE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.000026db ((Shared),CSIPGenericParamList::GetParamValue:SIPGenericParam.cpp(266))( 00000034F35DFBE0 ) Exit - param=[ms-received-ipv6] not found. Returned 0xC3E93C34(SIPPROXY_E_FIELD_NOT_EXIST)
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026dc (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(437))( 00000034F71F0438 ) Enter - current header [00000034F35DF9D8]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026dd (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(469))( 00000034F71F0438 ) Exit - returns header [0000000000000000]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026de (SIPStack,CSIPMessage::GetNextHeader<CSIPHeader>:SIPMessage.h(2545))( 00000034F71F0070 ) Exit - no more headers found
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026df (SIPStack,LiteralToIPv6Context::Clear:IPv6Literal.cpp(272))( 00000034F1EBDE60 ) Clear
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e0 (SIPStack,CSIPUrl::AppendLiteralToIPv6Mappings:SIPUrl.cpp(1659))( 00000034F35D8F10 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e1 (SIPStack,CURI::AppendLiteralToIPv6Mappings:SIPUrl.cpp(420))( 00000034F35D8F10 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e2 (SIPStack,LiteralToIPv6Context::Append:IPv6Literal.cpp(191))( 00000034F1EBDE60 ) Not an IPv6 literal: 127.0.0.1
TL_VERBOSE(TF_COMPONENT) [1]11DC.1678::04/08/2014-01:15:49.882.000026e3 (SIPStack,CSIPRequest::ValidateInboundHeaders:SIPRequest.cpp(1612))[3583893925]( 00000034F71F0070 ) Exit
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e4 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(381))( 00000034F71F0438 ) enter. headerID[0xf]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e5 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(413))( 00000034F71F0438 ) exit. header[00000034F35DC150]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e6 (SIPStack,CMaxForwardsHeader::Parse:MaxForwardsHeader.cpp(42))( 00000034F35DC150 ) enter.
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e7 (SIPStack,CMaxForwardsHeader::Parse:MaxForwardsHeader.cpp(46))( 00000034F35DC150 ) exit. already parsed.
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026e8 (SIPStack,HeaderSigner::GatherRouteHeaders:SIPMessage.h(174))( 00000034F71F0070 ) Exit - header 00000034F35DC150 found
TL_NOISE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.000026e9 (SIPStack,NegotiateLogic::ParseRequireHeader:NegotiateLogic.cpp(737))[1353035682]( 00000034F5E7A178 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026ea (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(381))( 00000034F71F0438 ) enter. headerID[0x23]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026eb (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(390))( 00000034F71F0438 ) exit. no headers
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026ec (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(381))( 00000034F71F0438 ) enter. headerID[0x2d]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026ed (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(413))( 00000034F71F0438 ) exit. header[00000034F35D8D00]
TL_INFO(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.000026ee (SIPStack,NegotiateLogic::ParseRequireHeader:NegotiateLogic.cpp(758))[1353035682]( 00000034F5E7A178 ) Found legacy compression request
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026ef (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(381))( 00000034F71F0438 ) enter. headerID[0x2d]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f0 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(413))( 00000034F71F0438 ) exit. header[00000034F35D8D00]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f1 (SIPStack,CSIPMultiEntryHeader::Parse:GenericMultiEntryHeader.cpp(88))( 00000034F35D8D00 ) Unparsed is [LZ77-8K]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f2 ((Shared),FindCharNotQuoted:parseutil.cpp(975))could not find character:","(0x2c).
TL_NOISE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f3 (SIPStack,CSIPMultiEntryHeader::Parse:GenericMultiEntryHeader.cpp(154))( 00000034F35D8D00 ) exit.
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f4 (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(437))( 00000034F71F0438 ) Enter - current header [00000034F35D8D00]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f5 (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(469))( 00000034F71F0438 ) Exit - returns header [0000000000000000]
TL_NOISE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.000026f6 (SIPStack,NegotiateLogic::ParseRequireHeader:NegotiateLogic.cpp(846))( 00000034F5E7A178 ) Exit. Returned 0x03E93C01(SIPPROXY_S_MESSAGE_CONSUMED)
TL_NOISE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.000026f7 (SIPStack,NegotiateLogic::ProcessPeerFeatureInfo:NegotiateLogic.cpp(1256))( 1353035682 )( 00000034F5E7A178 ) Enter - 00000034F71F0070
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f8 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(381))( 00000034F71F0438 ) enter. headerID[0x27]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026f9 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(413))( 00000034F71F0438 ) exit. header[00000034F35D8768]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026fa (SIPStack,CSIPMultiEntryHeader::Parse:GenericMultiEntryHeader.cpp(88))( 00000034F35D8768 ) Unparsed is [NewNegotiate]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026fb ((Shared),FindCharNotQuoted:parseutil.cpp(975))could not find character:","(0x2c).
TL_NOISE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.000026fc (SIPStack,CSIPMultiEntryHeader::Parse:GenericMultiEntryHeader.cpp(154))( 00000034F35D8768 ) exit.
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026fd (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(437))( 00000034F71F0438 ) Enter - current header [00000034F35D8768]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026fe (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(469))( 00000034F71F0438 ) Exit - returns header [00000034F35D8978]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.000026ff (SIPStack,CSIPMultiEntryHeader::Parse:GenericMultiEntryHeader.cpp(88))( 00000034F35D8978 ) Unparsed is [ECC]
TL_VERBOSE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002700 ((Shared),FindCharNotQuoted:parseutil.cpp(975))could not find character:","(0x2c).
TL_NOISE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.00002701 (SIPStack,CSIPMultiEntryHeader::Parse:GenericMultiEntryHeader.cpp(154))( 00000034F35D8978 ) exit.
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002702 (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(437))( 00000034F71F0438 ) Enter - current header [00000034F35D8978]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002703 (SIPStack,CHeadersHash::GetNextHeader:HeadersHash.cpp(469))( 00000034F71F0438 ) Exit - returns header [0000000000000000]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002704 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(381))( 00000034F71F0438 ) enter. headerID[0x5]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002705 (SIPStack,CHeadersHash::GetHeader:HeadersHash.cpp(413))( 00000034F71F0438 ) exit. header[00000034F35DB448]
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002706 (SIPStack,CFromToHeader::Parse:FromToHeader.cpp(82))( 00000034F35DB448 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002707 (SIPStack,SIPHeaderUriParam::ParseHelper:SIPHeaderUriParam.cpp(46))( 00000034F35DB448 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002708 (SIPStack,SIPHeaderUriParam::ParseHelper:SIPHeaderUriParam.cpp(51))( 00000034F35DB448 ) Exit - already parsed
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.00002709 (SIPStack,CFromToHeader::Parse:FromToHeader.cpp(90))( 00000034F35DB448 ) Exit
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.0000270a (SIPStack,HeaderSigner::GatherRouteHeaders:SIPMessage.h(174))( 00000034F71F0070 ) Exit - header 00000034F35DB448 found
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.0000270b (SIPStack,CFromToHeader::Parse:FromToHeader.cpp(82))( 00000034F35DB448 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.0000270c (SIPStack,SIPHeaderUriParam::ParseHelper:SIPHeaderUriParam.cpp(46))( 00000034F35DB448 ) Enter
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.0000270d (SIPStack,SIPHeaderUriParam::ParseHelper:SIPHeaderUriParam.cpp(51))( 00000034F35DB448 ) Exit - already parsed
TL_NOISE(TF_PARSE) [1]11DC.1678::04/08/2014-01:15:49.882.0000270e (SIPStack,CFromToHeader::Parse:FromToHeader.cpp(90))( 00000034F35DB448 ) Exit
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.0000270f (SIPStack,CIpAddress::SetIp:IpAddress.cpp(42))( 00000034F1EBE970 ) Enter
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002710 (SIPStack,CIpAddress::SetIp:IpAddress.cpp(55))Enter
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002711 (SIPStack,CIpAddress::SetIp:IpAddress.cpp(55))Exit - SIPRtlIpv6StringToAddress failed (WINERROR=C000000D). Returns E_FAIL
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002712 (SIPStack,CIpAddress::GetIPv4FromStringA:IpAddress.cpp(288))Enter
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002713 (SIPStack,CIpAddress::GetIPv4FromStringA:IpAddress.cpp(301))Exit - SIPRtlIpv4StringToAddress failed (WINERROR=C000000D). Returns E_FAIL
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002714 (SIPStack,CIpAddress::SetIp:IpAddress.cpp(80))( 00000034F1EBE970 ) Exit FALSE: c2nsi-svr-ex13.cantrelloffice.home is not an IP Address
TL_NOISE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.00002715 ((Shared),CSIPGenericParamList::GetParamValue:SIPGenericParam.cpp(231))( 00000034F35DB478 ) Enter
TL_VERBOSE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.00002716 ((Shared),CSIPGenericParamList::GetParamValue:SIPGenericParam.cpp(266))( 00000034F35DB478 ) Exit - param=[ms-fe] not found. Returned 0xC3E93C34(SIPPROXY_E_FIELD_NOT_EXIST)
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002717 (SIPStack,PeerCertificateKey::CacheDisplayName:PeerIdentityKey.cpp(450))( 00000034F5E7A198 ) Exit - cert name [c2nsi-svr-ex13.cantrelloffice.home]
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002718 (SIPStack,CPeerIdentityKey::SetDnsFqdn:PeerIdentityKey.cpp(810))( 00000034F5E7A198 ) Exit - set DNS FQDN to [c2nsi-svr-ex13.cantrelloffice.home]
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002719 (SIPStack,NegotiateLogic::ProcessPeerIdentity:NegotiateLogic.cpp(1143))( 1353035682 )( 00000034F5E7A178 ) Enter - peer=[c2nsi-svr-ex13.cantrelloffice.home]
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.0000271a (SIPStack,CConnection::ValidatePeerIdentity:Connection.cpp(544))( 1353035682 )( 00000034F5E68790 ) Enter
TL_NOISE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.0000271b (SIPStack,CPeerIdentity::FindLogicalPeer:PeerIdentity.cpp(86))( 1353035682 )( 00000034F1906F10 ) Enter
TL_NOISE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.0000271c (SIPStack,CPeerIdentity::LookupLogicalPeer_NonEP:PeerIdentity.cpp(124))( 1353035682 )( 00000034F1906F10 ) Enter
TL_VERBOSE(TF_STACKTRACE) [1]11DC.1678::04/08/2014-01:15:49.882.0000271d (SIPStack,KSTImpl::QueryFirstByFqdn:KSTImpl.cpp(895))( 00000034F18FEF80 ) No matches for FQDN=[c2nsi-svr-ex13.cantrelloffice.home]
TL_VERBOSE(TF_COMPONENT) [1]11DC.1678::04/08/2014-01:15:49.882.0000271e (SIPStack,RichResult::InternalAppendContext:RichResult.h(491))[1353035682]( 00000034F1EBE570 ) Context[0] is set to result [0xC3E93D6A(SIPPROXY_E_CONNECTION_UNKNOWN_SERVER)]
TL_VERBOSE(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.0000271f (SIPStack,CPeerIdentity::LookupLogicalPeer_NonEP:PeerIdentity.cpp(154))( 1353035682 )( 00000034F1906F10 ) Exit - no match for the peer identity [c2nsi-svr-ex13.cantrelloffice.home]. Returned
0xC3E93D6A(SIPPROXY_E_CONNECTION_UNKNOWN_SERVER)
TL_ERROR(TF_NETWORK) [1]11DC.1678::04/08/2014-01:15:49.882.00002720 (SIPStack,NegotiateLogic::ProcessPeerIdentity:NegotiateLogic.cpp(1155))( 1353035682 )( 00000034F5E7A178 ) Exit - failed to validate peer with S2S FQDN. Returned 0xC3E93D6A(SIPPROXY_E_CONNECTION_UNKNOWN_SERVER)
TL_ERROR(TF_CONNECTION) [1]11DC.1678::04/08/2014-01:15:49.882.00002721 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(389))[1353035682] $$begin_record
Severity: error
Text: The peer is not a configured server on this network interface
Peer-IP: 192.168.1.213:14339
Transport: TLS
Result-Code: 0xc3e93d6a SIPPROXY_E_CONNECTION_UNKNOWN_SERVER
Data: fqdn="c2nsi-svr-ex13.cantrelloffice.home"
$$end_record

Similar Messages

Lync Server Integration with Exchange 2013

Hello,
I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled.
So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
Thanks and Regards,
Nash Burns

Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Weird emails showing in Outlook 2013 Inbox after Exchange 2013 PST Import

Hi there,
I've just done an Import PST from Exchange 2013 using the GUI, and when it is finished, I then open Outlook 2013 I am seeing a few strange emails in the Inbox.
The PST's were from Outlook 2007, and were previously used in with POP mail.
The message is like this:
Subject: Undeliverable: Not read: RE: Re: information
Your message did not reach some or all of the intended recipients.
Subject: Not read: RE: Re: information
Sent: 20/04/2014 11:08 p.m.
The following recipient(s) cannot be reached:
Big John on 20/04/2014 11:11 p.m.
Diagnostic code = MailRecipientUnknown; Reason code = TransferImpossible; Status code = 511
< #5.1.1 smtp;550 5.1.1 RESOLVER.ADR.RecipNotFound; not found>
The date and time of the message is during the import process.
Does anyone have any suggestions?
From a PST of around 8GB, I ended up with about 50 of these type of messages, mostly to the same recipients, but there were some different ones. From a mailbox of about 3GB, I got about 5 of these messages. From the smaller mailboxes I got none.
Thanks in advance,
Steve.

Hi Steve,
Please verify whether this issue occur in OWA.
If everything is OK in OWA, it seems the .pst import completed successfully. Let's perform troubleshooting on the Outlook client side.
1. Please run Outlook under the safe mode to avoid some AVs and add-ins.
2. Please try to re-create profile to refresh the caches.
3. Please also check whether the missing messages in others' folders or subfolders.
I want to know that why you exported to .pst from Outlook 2007 and imported it into Exchange 2013. Did you migrated Exchange server from 2007/2010 to 2013?
If it is the case, I suggest moving mailbox from Exchange 2007/2010 to Exchange 2013.
Please correct me if there is any misunderstanding.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Problem with Outlook (client) 2010/2013 profiles on Exchange 2013

We have recently started migrating to Exchange 2013 and have come across a problem with some of our accounts. This problem exists in both migrated mailboxes and natively created 2013 mailboxes.
basically we have a lot of "shared" accounts. We create a user object in AD, give it a mailbox, then give a security group "Full Access" (and often "send-as") permissions on the account. We then Disable the
account in AD (to prevent directly using the password) and then add/remove group members to manage access. everyone uses their own credentials to get to the account.
For the most part this works fine. Users can access OWA and get to these shared mailboxes, they can also 'add' the mailbox to their Outlook client by going into Account Settings->Properties of the Exchange user->More Settings... ->Advanced Tab->"Open
these additional mailboxes:" and adding the mailbox.
However what has happened is that some users were setting up a separate profile instead of adding a mailbox. (Pretty much these
instructions: )
When this is done an error occurs. :
Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost).
Connecting with a profile set up as yourself first does not clear the error, whenever the shared mailbox folder is selected you get this. The exception is if you go into the account properties and turn off Cached mode. the error then becomes:
Cannot open your default e-mail folders. the file c:\users\[user]\appdata\local\microsoft\outlook\[datafile].ost is not an Outlook datafile (.ost).
Which is weird since migrated accounts had working OST files which were functional prior to migration and outlook creates the new OST for new accounts. This message appears to be a red herring and the problem is still sync access but it throws this
error instead.
In the end is creating a new profile for a mailbox you have Full Access to no longer supported in 2013 or is there something we can do to fix this problem?

Hi AD-Tester,
According to your description and I do an test, however I cannot reproduce the problem.
I want to confirm some points, please help to collect answers for following questions:
1. Check all account or some special user face this problem.
2. Try this command to check Atodiscover, Exchange Web services, Availability service, Offline Address Book services works well:
Get-ClientAccessServer | Test-OutlookWebServices -Identity 'e-mail address'
If it works on OWA, problem may point to outlook client. Please try to re-create a outlook profile for testing.
Note: please make sure set properly setting for Outlook anywhere.
Additional, we can recreate an account and enable-mailbox, then disable in AD and try to login outlook account again.
Best Regards,
Allen Wang

Exchange 2013 CU7 OWA 400 Bad Request after successful login

Scenario:
Exchange 2007/2013 Migration
One
Exchange 2007 Server [removed]
One
Exchange 2013 Server Std, Windows 2012
All mailboxes moved to 2013
- November 27-30 2014
All public folders moved to
2013 - December 2, 2014
Exchange
2007 is still running and has not been removed from the domain, yet. [update]
Exchange
2007 removed from domain - 12-13-14
SSL
Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com
Applied
CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).
User
logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.
[update]
CU7 applied 12-11-2014
All
users can connect using Outlook 2013 or Mobile (iPhone & Android)
Exchange
Admin Center (ECP) still works!
Browsers
tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7
Attempted:
https://ex13.ExtDom.com/owa
https://ex13.IntDom.com/owa
https://ex13.ExtDom.com/owa?ExchClientVer=15
https://ex13.IntDom.com/owa?ExchClientVer=15
https://localhost/owa
(on Ex 2013 server)
https://localhost/owa?ExchClientVer=15
(on Ex 2013 Server)
Fixes
attempted:
remove
| create Virtual Directories for OWA
Change
authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic
reverted
since change didn’t work.
Run
UpdateCas.ps1
Run
UpdateConfigFiles.ps1
IISReset
(iisReset /NoForce fails)
OWA
(Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)
Links
used for troubleshooting:
http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp
https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-request-when-logging-in-to-owa-exchange-2013?forum=exchangesvrclients
http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/
https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exchange-2013-owa-error-400-bad-request?forum=exchangesvradmin
http://support.microsoft.com/kb/2871485/en-gb

Hi,
Does it work if you disable the FBA and only use the basic authentication?
Please also let us know the authentication settings on the Default Web site.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 SP1 & Custom OWA Theme

On Friday of last week we updated from Exchange 2013 CU2 to Exchange 2013 SP1. Since updating our custom OWA theme no longer works. We configured it according to the following guide:
http://technet.microsoft.com/en-us/library/bb201700(v=exchg.150).aspx
The theme we customized was stored in the following location:
\Client Access\OWA\version\Owa2\resources\themes\"title of our theme"
Themes no longer appear to be stored in this location and I am uncertain as to where they have moved and how to apply them. Has anyone else run into this issue?

Hi,
Can we try to re-importing the theme again?
Thanks
Mavis
Mavis Huang
TechNet Community Support

Lync Online vs Exchange 2013 On Premise

We have Lync 2013 Online and Exchange 2013 SP1/Outlook 2013 SP1 on premise. All work well with RPC over HTTP.
We are trying to get MAPI over HTTP (Outlook 2013 SP1 / Exchange 2013 SP1). But it seems that the MAPI over HTTP no longer respects the Internet Explorer Bypass Proxy List. Therefore the Outlook client tries to connect to the on-premise
Exchange Server CAS via the proxy server. Outlook 2013 Connection status shows DISCONNECTED and AUTHN FAILED.
To reconnect Outlook we can either;
1. Turn off the Proxy Server in IE (Outlook then connects but we cannot browse the web).
2. Remove the Microsoft Online Services assistant (again Outlook then connects, but Lync does not).
To troubleshoot this we've used the Process Monitor and can see Outlook actively reading the registry key (HKCU\software\microsoft\windows\currentversion\internet settings\proxyoverride). Problem is it doesn't appear to use them.
Has anyone else seen this behaviour with MAPI over HTTP and the Online Services Sign In Assistant (MSOIDCLI)?

This is a known issue with MAPI/HTTP at this moment. Outlook Team is investigating it for a root cause & possible fix. No ETA is available at this time. I will update this post when we have an update.
Issue: If an Outlook 2013 SP1+ user has 'Bypass proxy server for local addresses' setting enabled in Internet Explorer (Internet Options | Connections | LAN Settings), then Outlook does not connect over MAPI/HTTP to a mailbox on Exchange
2013 SP1+ server. This issue does not happen connecting over RPC/HTTP in the same setup.
I see another known issue mentioned here thus wanted to quickly confirm that as well. Another known issue with MAPI/HTTP is as described below. This issue has been fixed and fix is planned to be deployed in Office 365/Exchange Online soon & is currently
planned to be included with E2013 SP1 CU6 (tentative).
Issue: User1 has full access to User2’s mailbox, User2 also has an Archive mailbox. Using Outlook 2013 SP1+ User1 connects over MAPI/HTTP to Exchange 2013 SP1+. User2’s Primary mailbox is then accessible to User1 in his Outlook thru Auto-mapping,
but User1 cannot see User2’s Archive mailbox. If User1 connects over RPC/HTTP, he does not see this issue.
Sr. Program Manager, Product Quality, Exchange Client Access Server

ADFS-WAP-Exchange 2013 SP1

Hello guys,
i will setup a new infrastructure with exchange 2013 account forest.In this new forest, users will authenticate by WAP and ADFS.
The accounts user are in other with a exchange 2003 that i'll migrate.
My question is how adfs will authenticate owa's user and do i need to setup a adfs server in account forest ?
Concerning my adfs certificate, do i need to put the UPN from the exchange forest or to put also the account forest
Thanks for you advice
Jérôme

Hi,
I find 2 related blog for your reference, hope they are what you want:
Setting up Windows Application Proxy for Exchange 2013
http://blogs.technet.com/b/jrosen/archive/2013/12/28/setting-up-windows-application-proxy-for-exchange-2013.aspx
Configuring Exchange 2013 SP1 to Accept AD FS Claims
http://blogs.technet.com/b/platformspfe/archive/2014/03/12/configuring-exchange-2013-sp1-to-accept-ad-fs-claims.aspx
Thanks
Mavis Huang
TechNet Community Support

Outlook 2013 with Exchange 2013: Mails stuck in Outbox

Hi everybody,
I am using Outlook 2013 connecting an Exchange 2013 server. After sending a mail, all outgoing mails remain in the outbox. After removing the cache files it works for a while until the problem occurs for the next time (approx. once every two days).
I already re-installed Windows 8 to test it on a completely clean environment...OWA works fine, the problem only exists with Outlook.
Additional note: It might be interesting that after sending a mail, the "Send/Receive progress" window states "sending [email protected] - complete" but the Mail is still in the outbox and was not delivered to the recipient. Safe mode doesn't work
for me. Other users connecting with Outlook 2010 don't have a problem with this exchange server.
Do you have any ideas? If I can provide you with further information, please let me know.
Greets,
Basti

Thanks for your answer. Here are the requested information:
>What addins are you using?
No 3rd party addins, at the moment "Microsoft Exchange Add-In", "Microsoft VBA for Outlook Addin",
"OneNote Notes about Outlook Items" and "Outlook Social Connector 2013" are activated. But the problem also occurs if no addin is active (or even in Safemode).
>Antivirus
scanners can prevent Outlook from moving messages to the sent folder.
I will try to deactivate the virus scanner the next time. (Avira is used)
>Can
any address trigger this behavior or does it happen with certain addresses?
No, it does happen with any address by random. Once the problem occurs, I can try to send as much mails as I want to
any address - nothing leaves the outlook client.
>Is
this your mailbox or a shared/secondary mailbox?
It is a user's mailbox, nothing shared.

Exchange 2013 - RCA reports RPC Proxy can't be pinged (404)

Hi, I've searched extensively and spent hours trying to fix my problem and nothing in the forums has addressed yet.
I have a new exchange server 2013 SP1 and Outlook 2013 clients can't connect. Outlook states Exchange Server is Unavailable.
This led me to Microsoft RCA. RCA reported that the RPC Proxy can't be pinged with a 404 error. But I CAN visit the server RCA references a step or two above and am treated to a white page, no 404. (
https://xch.domain.com/rpc/rpcproxy.dll?xch.domain.com:6002 )
I have set ExternalAuthenticatoin to Negotiate and internal to NTLM, I have set outlookProvider to
[PS] C:\Windows\system32>Get-Outlookprovider
Name Server CertPrincipalName TTL
EXCH msstd:*.domain.com 1
EXPR msstd:*.domain.com 1
WEB
1
The SSL Certificate is a trusted one, the External URL is set properly in the server settings via ECP as well.
Any ideas would be greatly appreciated. I'm tired and incapable of listing all of the steps I've tried, but if you know of any tips for troubleshooting and fixing RPC Ping issues, I would love to hear them.
Thanks!

Hi,
How about OWA, does it works well?
1. If OWA doesn't work, please check wether the Outlook Anywhere has been enabled.
It seems you have configured Outlook Anywhere as below. If not, please change the configuration.
Does the whole error message like this:
Attempting to ping RPC proxy mail.contoso.co.nz.
RPC Proxy can't be pinged.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Please make sure the configuration as below:
Set-OutlookAnywhere
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : NTLM
IISAuthenticationMethods : {basic, ntlm, negotiate}
Set-OutlookProvider
Name                       Server                      CertPrincipalName            TTL
EXCH
msstd:*.contoso.co.nz     1
EXPR
msstd:*.contoso.co.nz      1
WEB                                                                                                1
More details in the following link:
Exchange 2013 Outlook Anywhere (RPC) Settings
http://infused.co.nz/2013/05/13/exchange-2013-outlook-anywhere-rpc-settings/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
2. If the method 1 doesn't help, please collect some related error message in App Log without sensitive information for the further troubleshooting.
3. If OWA works well, just Outlook doesn't work, I suggest try to run 'Test-OutlookConnectivity' command in EMS to verify the connectivity between Exchange server and Outlook client. Please paste the details without sensitive information if there is any
abnormal.
4. Please also run 'Test E-mail AutoConfiguration' on Outlook to verify whether there is anything abnormal.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013: Correcting mailbox delegation - Full Access

Not sure how to correct this issue. I have an Admin that setup the Exchange 2013. The admins account is now added to every new account (Resources, shared mailboxes etc.) I know how to remove the auto mapping so it does not show in the admin
OWA and outlook.
I would like to just correct the setting so the account is not automatically added. (Tester is not the real name of the account.)

Hi Friday77,
Check the AdminAuditLogs to see by who and when it is getting added.
View the administrator audit log
Search the role group changes or administrator audit logs
Search-AdminAuditLog -StartDate 05/04/2015 -EndDate 10/04/2015 -ObjectID contoso.com/Users/NewUSerName1
Search-AdminAuditLog -Cmdlets Add-MailboxPermission -Parameters AccessRights -StartDate 05/04/2015 -EndDate 10/04/2015
Normally this wouldn't be the case, however you might want to have a look at this as well.
Get-CmdletExtensionAgent "Mailbox Permissions Agent"
Cmdlet extension agents are components in Microsoft Exchange Server 2013 invoked by Exchange 2013 cmdlets when the cmdlets run.
Agents can modify, replace, or extend functionality of Exchange Management Shell cmdlets. An agent can provide a value for a required parameter that isn't provided on a command, override a value provided by a user, perform other actions outside of the cmdlet
workflow while a cmdlet runs, and more.
You can use the Scripting agent cmdlet extension agent in Exchange 2013 to insert your own scripting logic into the execution of Exchange cmdlets. Using the
Scripting agent, you can add conditions, override values, and set up reporting.
Every Exchange 2013 server includes the file ScriptingAgentConfig.xml.sample in the <installation path>\V15\Bin\CmdletExtensionAgents folder. This file must be renamed to ScriptingAgentConfig.xml on every Exchange 2013 server if you enable
the Scripting Agent cmdlet extension agent.
If its still .xml.sample, no need to worry about it.
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 DAG / client access

Hello
I'm in the planning of a new Exchange 2013 infrastructure. The infrastructure will be located in a datacenter and should host about 1000 mailboxes. I have read many whitepapers and tutorials, but some things are still unclear to me.
- Microsoft suggests multi-role servers for this amount of users because client access is no more than a reverse proxy in EX2013. Is this correct? I've read that one users with 200 mails/day needs 8.5 MCycles with only DB and 10.63 MCycles with DB and CAS
on the same server. So I plan to start with 2 multi-role servers in a DAG. What's your oppinion on this?
- Client connections: I assume the clients connect to the cluster IP of the DAG. How do they get directed to the server on which their database is online? Does each server need to have the cluster IP and a public IP to which the clients connect?
- SMTP: As I understand the documentation, mails are sent from the server which the user is active on. (Which makes sense for high availability.) What is best practice regarding the protocol logs? Do the support employees need to search in the files on 2
servers?
Thank you very much for your input!

Hi
I would use the firewall for load balancing unless there is a technical reason why this is not possible. NLB is not recommended as it is not service aware - you cannot configure a probe to test OWA is working for example - so if you already have something
better that would be my choice.
In the choice between IIS ARR and NLB or CAS and NLB I would go for IIS ARR as this reduces you license costs, but neither of these is better than the appliance/firewall option.
I've never used NLB for load balancing other than on TMGs so I cannot say what the performance is like behind a firewall, in theory your assumption would be correct.
The load balancer doesn't make this decision it just spreads the load between the active servers, the CAS role connects the use session to the correct mailbox server:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Steve

Exchange 2013 and 2007 coexistence and redirects

Hi all,
I'm settings up the coexistence but i've got a problem.
I've got 3 sites:
Site A: Exchange 2013 cas and mailbox
Site B: Exchange 2007 hub/cas and mailbox
Site C: Exchange 2007 hub/cas and mailbox
The problem is the owa and active sync redirect. I can open a mailbox located in site B where the legacy.domain.com dns record points, but i cannot open a mailbox from the exchange 2013 nor 2007 owa from site B to C.
I configured only the internal url leaving the external one blank.
How do i redirect all the requests to a mailbox located in site C from site A and B?
Thanks,
D.

You need to have External URL too, so that redirection can take place.
http://blogs.technet.com/b/mbaher/archive/2009/12/17/exchange-2010-proxy-or-redirect.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

Here is our current scenario,
Exchange 2007
2 - Hub Transport Servers
2 - CAS servers (cluster NLB)
2 - Mailbox servers (clustered)
Exchange 2010
2 - Huib Transport Servers
3 - CAS servers (array NLB)
2 - Mailbox servers (1 DAG)
We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

Hi,
As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
For more information, you can refer to the following article:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 with CU3 and silent redirection to different AD site

After updating
Exchange 2013 CU2 to Exchange 2013 CU3, OWA silent site redirection feature become not available. The customer has two Exchange 2013 sites. Before we updated to CU3, user whose mailbox located on site A, could be automatically redirected to OWA on
site A, after he logged on to OWA on site B. IE gives Error page and bring out link to the OWA page on site A. Here is screenshot about issue workaround.
Hopefully someone will help with some hint because it is quite anoying.
All other stuff works good, Outlook anywhere, autodiscover, only this remained.
Thanks in advance,
Fajar

Hi Angela,
According to your description, OWA request cannot be automatically redirected after upgrade.
YESS after upgrade Exchange 2013 CU2 to CU3. CU2 not problem.
1. Will OWA work well if you manually click the OWA URL in the web page?
If i click manual, OWA Url in web page, OWA work well...
PS Command "Get-OWAVirtualDirectory | fl CrossSiteRedirectType"
ONLY HAVE ON EXCHANGE 2010 NOT ON EXCHANGE 2013.
2. Do you can login OWA in site A?
My Mailbox on Site-A, if i login OWA Site A (owa-A.domain.com), OWA work well & i can access my email.
But... if i login from OWA Site-B (owa-B.domain.com), OWA not automatic silent redirect to Site-A, and i must click link below "Use following link to open to mailbox with the best performance https://owa-a.domain.com/owa/auth.owa
My friend Mailbox on Site-B, if he login to OWA Site B (owa-B.domain.com), OWA-B work well & he can access email.
But.. if he login from OWA Site-A (owa-A.domain.com), OWA not automatic silent redirection to Site-B, and he must click link below "Use following link to open to mailbox with the best performance https://owa-b.domain.com/owa/auth.owa
3. Check the IIS log on site B CAS server and find if there is any error about the redirection.
whether there is a bug in CU3?
Hopefully someone will help with some hint because it is quite anoying on our custommer.
Regards,
Fajar

Lync 2013 presence in Exchange 2013 OWA - 0xc3e93d6a SIPPROXY_E_CONNECTION_UNKNOWN_SERVER

Similar Messages

Maybe you are looking for