Cannot Connect Outlook 2013 to Exchange 2013

I have an exchange 2013 server running on a Windows Server 2012 R2 box that is also a domain controller and performs DNS. I have installed an SSL certificate for mail.domainname.com installed and listed as valid in ECP. When I try to connect
a local computer running Outlook 2013 on Windows 7 I get asked for login and password which it won't accept. I have tried my user and my administrator credentials, either work.
It then says that "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I can connect via OWA and don't get any certificate errors. My internal host name and external host name are both mail.domainname.com according to the Get-OutlookAnywhere | ft internalhostname,externalhostname.
Any help is greatly appreciated.
Robert

I probably should have stated from the beginning that I am not an IT professional. I am an architect. Not a network architect, but an "I design buildings" architect. I am simply the most knowlegable member of the firm when it comes to IT.
I have been administering our SBS server for the last 14 years. We just purchased a new server to replace our tired old beast and I have been working to get it read to roll out to the office. I have everything set except Outlook. We are a
very small firm, only three people, so if manual configurations are needed I can do that.
I don't understand what I am reading in the Configure Outlook Anywhere article. It looks like it is about using Outlook from a remote location without a VPN. I am trying to get configured to use Outlook internally. Not sure if they both
work the same way.
Thank you,
Robert

Similar Messages

Cannot disable a mailbox in Exchange 2013 CU6!?!?!?!

I cannot disable a mailbox in Exchange 2013 CU6. I get the following error:
Anyone seen this error? As you know, I just want to remove the Exchange attributes from the user object in Active Directory. Of course, deleting the user object works just fine but don't want to go that route.

I tried with the EMS (Powershell) and I still get an error:
[PS] C:\>disable-mailbox [email protected]
Confirm
Are you sure you want to perform this action?
Disabling mailbox "[email protected]" will remove the Exchange properties from the Active Directory user object and mark the mailbox in the database for removal. If the mailbox has an archive or remote archive, the archive will also
be
marked for removal. In the case of remote archives, this action is permanent. You can't reconnect this user to the remote archive again.
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
Y
Active Directory operation failed on LocalDCName.local.com. This error is not retriable. Additional information: The parameter is incorrect.
Active directory response: 00000057: LdapErr: DSID-0C090CB9, comment: Error in attribute conversion operation, data 0, v2580
+ CategoryInfo : NotSpecified: (:) [Disable-Mailbox], ADOperationException
+ FullyQualifiedErrorId : [Server=LA-MBX01Server,RequestId=6ed97c1e-ae68-4670-a097-c4e65f683274,TimeStamp=11/18/2014 7:50:07 PM] [FailureCategory=Cmdlet-ADOperationException] 8D6C0FEB,Microsoft.Exchange.Management.RecipientTasks.Disable
Mailbox
+ PSComputerName : LocalDCName.local.com
I captured everything with the START-TRANSCRIPT cmdlet and changed the specific values to our organization (i.e., "[email protected]" and "LocalDCName.Local.com"). I've tried this on other mailboxes and I receive the same error whether
I use EMC or EMS. I believe this might be AD schema related just not sure where.

Cannot connect from Mac Pro late 2013 to Macbook Pro

Cannot connect from Mac Pro late 2013 to Macbook Pro . I have tried via ethernet and wifi. I can connect from the MBP to the Mac Pro but not vice versa. I have tried to connect to other MBP's on the same network with no luck. I try and connect as a registered user, as I usually do, with no luck. When I enter the Username and then Password the box vibrates as if the details are incorrect, they are not however.
Thanks in advance
Jeff

It is 'just not working' again.
To answer you question. Other sharing services work. I can connect as a guest. I can share screens. I cannot air drop.
I cannot connect either way now i.e. from Mac Pro to MBP and vice versa.
I cannot connect to my wife MBP either. My wife cannot connect to my Mac Pro.
It neither works with wifi or ethernet cable.
I can connect to my Time Capsule directly and Time Machine backups are working.
The passwords are 100% correct.
The Mac Pro is a late 2013. Does anyone else have a similar problem? I have never suffered this one before. Seriously effecting my workflow
Thanks

Outlook 2013 with Exchange 2013 keeps giving read receipts

Hello experts,
We have an Exchange 2013 server. All users are joint to the domain, except one user (Windows 8.1) which is in a Workgroup, and using Outlook 2013 with IMAP protocol.
This particular user is having a problem. When he send's any email from Outlook and requests a read receipt, after that he keeps getting hundreds of read receipts in his inbox. I have tried disabling (for temporarily) the Windows server 2012 firewall, but
still having the same issue.
Is this a known bug in Outlook 2013 with Exchange 2013? Any help troubleshooting this?

Hi,
According to your description, I understand that IMPA account get hundreds of read receipts while he requests a read receipt.
If I misunderstand you concern, please do not hesitate to let me know.
Whether are all account or some special user experience this question? Please do a test in external with IMAP account to double confirm.
How about the “Request a Delivery Receipt”?
Also, please run message tracking log to get more details about message mail flow:
Get-MessageTrackingLog –Server “mailbox server” –Sender “[email protected]” –Recipient “[email protected]” –MessageSubject “Read: message subject” | Select Timestamp, ClientHostname,ServerHostname,Source,EventID,Recipients,RecipientStatus,Sender | ConvertTo-Html > “C:\Test\Test.xml”
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Lync 2013 to Exchange 2013 Oauth problem - Error:[OAuthTokenBuilder:GetAppToken] unable to continue building token; no locally configured issuer

Hi,
I am having a problem getting OAuth to work from Exchange 2013 to Lync 2013.
I have read and following the instructions online and cannot see what I am doing wrong.
On the Exchange 2013 server, I get the following error when I run:
Test-OAuthConnectivity -Service EWS -TargetUri
https://exchserver2.domainname.local/ews/ -Mailbox "Jack"
RunspaceId : 920118a3-6ab2-45dc-9b68-de68133de95e
Task : Checking EWS API Call Under Oauth
Detail : The configuration was last successfully loaded at 01/01/0001 00:00:00 UTC. This was 1059263714 minutes
ago.
The token cache is being cleared because "use cached token" was set to false.
Exchange Outbound Oauth Log:
Client request ID: 19ad80f6-7751-429f-aac5-e802105fbbc6
Information:[OAuthCredentials:Authenticate] entering
Information:[OAuthCredentials:Authenticate] challenge from
'https://exchserver2.domainname.local/ews/Exchange.asmx' received: Bearer
client_id="00000002-0000-0ff1-ce00-000000000000",
trusted_issuers="[email protected]",Negotiate,NTLM
Information:[OAuthCredentials:GetToken] client-id: '00000002-0000-0ff1-ce00-000000000000', realm: '',
trusted_issuer: '[email protected]'
Information:[OAuthCredentials:GetToken] start building a token for the user domain 'domainname.co.uk'
Information:[OAuthTokenBuilder:GetAppToken] start building the apptoken
Information:[OAuthTokenBuilder:GetAppToken] checking enabled auth servers
Error:[OAuthTokenBuilder:GetAppToken] unable to continue building token; no locally configured issuer
was in the trusted_issuer list, realm from challenge was also empty. trust_issuers was
[email protected]
Error:The trusted issuers contained the following entries
'[email protected]'. None of them are configured locally.
Exchange Response Details:
HTTP response message:
Exception:
System.Net.WebException: The request was aborted: The request was canceled. --->
Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException: The trusted issuers contained the
following entries '[email protected]'. None of them are
configured locally.
at Microsoft.Exchange.Security.OAuth.OAuthTokenBuilder.GetAppToken(String applicationId, String
destinationHost, String realmFromChallenge, IssuerMetadata[] trustedIssuersFromChallenge, String
userDomain)
at Microsoft.Exchange.Security.OAuth.OAuthTokenBuilder.GetAppWithUserToken(String applicationId,
String destinationHost, String realmFromChallenge, IssuerMetadata[] trustedIssuersFromChallenge, String
userDomain, ClaimProvider claimProvider)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.GetToken(WebRequest webRequest,
HttpAuthenticationChallenge challengeObject)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.Authenticate(String challengeString, WebRequest
webRequest, Boolean preAuthenticate)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.OAuthAuthenticationModule.Authenticate(String
challenge, WebRequest request, ICredentials credentials)
at System.Net.AuthenticationManager.Authenticate(String challenge, WebRequest request, ICredentials
credentials)
at System.Net.AuthenticationState.AttemptAuthenticate(HttpWebRequest httpWebRequest, ICredentials
authInfo)
at System.Net.HttpWebRequest.CheckResubmitForAuth()
at System.Net.HttpWebRequest.CheckResubmit(Exception& e, Boolean& disableUpload)
at System.Net.HttpWebRequest.DoSubmitRequestProcessing(Exception& exception)
at System.Net.HttpWebRequest.ProcessResponse()
at System.Net.HttpWebRequest.SetResponse(CoreResponseData coreResponseData)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Monitoring.TestOAuthConnectivityHelper.SendExchangeOAuthRequest(ADUser user,
String orgDomain, Uri targetUri, String& diagnosticMessage, Boolean appOnly, Boolean useCachedToken,
Boolean reloadConfig)
ResultType : Error
Identity : Microsoft.Exchange.Security.OAuth.ValidationResultNodeId
IsValid : True
ObjectState : New
It appears to work fine from Lync 2013 to Exchange 2013.
When I run: Test-CsExStorageConnectivity -sipuri [email protected] -Binding Nettcp -Verbose in Lync 2013 I get a successful outcome:
VERBOSE: Successfully opened a connection to storage service at localhost using
binding: NetNamedPipe.
VERBOSE: Create message.
VERBOSE: Execute Exchange Storage Command.
VERBOSE: Processing web storage response for ExCreateItem Success.,
result=Success, activityId=0bbdc565-4a05-4b57-bf95-0c75488a1ef6, reason=.
VERBOSE: Activity tracing:
2015/01/02 19:15:55.616 Autodiscover, send GetUserSettings request,
[email protected], Autodiscover
Uri=https://exchserver2.domainname.local/autodiscover/autodiscover.svc, Web
Proxy=<NULL>
2015/01/02 19:15:55.616 Autodiscover.EWSMA trace,
type=AutodiscoverRequestHttpHeaders, message=<Trace
Tag="AutodiscoverRequestHttpHeaders" Tid="30" Time="2015-01-02 19:15:55Z">
POST /autodiscover/autodiscover.svc HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/15.00.0516.004
</Trace>
2015/01/02 19:15:55.624 Autodiscover.EWSMA trace, type=AutodiscoverRequest,
message=<Trace Tag="AutodiscoverRequest" Tid="30" Time="2015-01-02 19:15:55Z"
Version="15.00.0516.004">
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<a:RequestedServerVersion>Exchange2013</a:RequestedServerVersion>
<wsa:Action>http://schemas.microsoft.com/exchange/2010/Autodiscover/Autodiscove
r/GetUserSettings</wsa:Action>
<wsa:To>https://exchserver2.domainname.local/autodiscover/autodiscover.svc</
wsa:To>
</soap:Header>
<soap:Body>
<a:GetUserSettingsRequestMessage
xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover">
<a:Request>
<a:Users>
<a:User>
<a:Mailbox>[email protected]</a:Mailbox>
</a:User>
</a:Users>
<a:RequestedSettings>
<a:Setting>InternalEwsUrl</a:Setting>
<a:Setting>ExternalEwsUrl</a:Setting>
<a:Setting>ExternalEwsVersion</a:Setting>
</a:RequestedSettings>
</a:Request>
</a:GetUserSettingsRequestMessage>
</soap:Body>
</soap:Envelope>
</Trace>
2015/01/02 19:15:55.704 Autodiscover.EWSMA trace,
type=AutodiscoverResponseHttpHeaders, message=<Trace
Tag="AutodiscoverResponseHttpHeaders" Tid="30" Time="2015-01-02 19:15:55Z">
HTTP/1.1 200 OK
Transfer-Encoding: chunked
request-id: 5917d246-64b0-48e2-ad79-f9b6cffb5bea
X-CalculatedBETarget: exchserver2.domainname.local
X-DiagInfo: EXCHSERVER2
X-BEServer: EXCHSERVER2
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=FTFXWUQWWRJVBMNBG; expires=Sat, 02-Jan-2016 19:15:55 GMT;
path=/;
HttpOnly,X-BackEndCookie=actas1(sid:S-1-5-21-3691024758-535552880-811174816-113
5|smtp:[email protected]|upn:[email protected])=u56Lnp2ejJqBx8jIn
sqbxpvSz8rHx9LLzp7O0sbOzcnSzcqcmZqem8aempmcgYHNz87K0s/N0s/Oq87Gxc7KxcrK;
expires=Sun, 01-Feb-2015 19:15:55 GMT; path=/autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: EXCHSERVER2
Date: Fri, 02 Jan 2015 19:15:55 GMT
</Trace>
2015/01/02 19:15:55.704 Autodiscover.EWSMA trace, type=AutodiscoverResponse,
message=<Trace Tag="AutodiscoverResponse" Tid="30" Time="2015-01-02 19:15:55Z"
Version="15.00.0516.004">
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action
s:mustUnderstand="1">http://schemas.microsoft.com/exchange/2010/Autodiscover/Au
todiscover/GetUserSettingsResponse</a:Action>
<h:ServerVersionInfo
xmlns:h="http://schemas.microsoft.com/exchange/2010/Autodiscover"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<h:MajorVersion>15</h:MajorVersion>
<h:MinorVersion>0</h:MinorVersion>
<h:MajorBuildNumber>1044</h:MajorBuildNumber>
<h:MinorBuildNumber>21</h:MinorBuildNumber>
<h:Version>Exchange2013_SP1</h:Version>
</h:ServerVersionInfo>
</s:Header>
<s:Body>
<GetUserSettingsResponseMessage
xmlns="http://schemas.microsoft.com/exchange/2010/Autodiscover">
<Response xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<ErrorCode>NoError</ErrorCode>
<ErrorMessage />
<UserResponses>
<UserResponse>
<ErrorCode>NoError</ErrorCode>
<ErrorMessage>No error.</ErrorMessage>
<RedirectTarget i:nil="true" />
<UserSettingErrors />
<UserSettings>
<UserSetting i:type="StringSetting">
<Name>InternalEwsUrl</Name>
<Value>https://exchserver2.domainname.local/EWS/Exchange.asmx</Value>
</UserSetting>
<UserSetting i:type="StringSetting">
<Name>ExternalEwsUrl</Name>
<Value>https://exchserver2.domainname.co.uk/EWS/Exchange.asmx</Value>
</UserSetting>
<UserSetting i:type="StringSetting">
<Name>ExternalEwsVersion</Name>
<Value>15.00.1044.000</Value>
</UserSetting>
</UserSettings>
</UserResponse>
</UserResponses>
</Response>
</GetUserSettingsResponseMessage>
</s:Body>
</s:Envelope>
</Trace>
2015/01/02 19:15:55.704 Autodiscover, received GetUserSettings response,
duration Ms=88, response=NoError
2015/01/02 19:15:55.706 Lookup user details,
sipUri=sip:[email protected], [email protected],
sid=S-1-5-21-3691024758-535552880-811174816-1135, [email protected],
tenantId=00000000-0000-0000-0000-000000000000
VERBOSE: Items choice type: CreateItemResponseMessage.
VERBOSE: Response message, class: Success, code: NoError.
VERBOSE: Item: Microsoft.Rtc.Internal.Storage.Exchange.Ews.MessageType, Id:
AAMkADAwNWZkZWI0LWM5NGYtNDUxNy05Nzk3LWZhZjRiY2Y4MTU4NwBGAAAAAADLP1MgTEXdQ7zQSlb
qPl++BwBauhRZTfLbTYZ+hBWtK784ANcdmUYqAACSqIurRqgYSZwMhT/IBw89AACnT6G9AAA=,
change key: CQAAABYAAACSqIurRqgYSZwMhT/IBw89AACnip6b, subject: , body: .
VERBOSE: Is command successful: True.
Test passed.
All my certificates on the Exchange 2013 and Lync 2013 servers are from my local CA.
I use APP with the public certificates as my reverse proxy for people connecting from outside the network.
In Lync, the OAuthTokenIssuer certificate created through the Lync deployment wizard is issued to domainname.local (my primary sip domain) and the Subject Alternative names include domainname.co.uk
I then exported this certificate to the Exchange Server and use the Set-AuthConfig to use this certificate for OAuth.
from what I read this was what I was supposed to do.
is this correct?
I have tried so many things I don't know what do to next.
Should the OAuth certificate in exchange be the one exported from Lync?
In Lync, should the OAuthTokenIssuer certificate include the servername or lyncserver.domainname.local or just be domainname.local like it is at the moment?
thank-you
jack

Thomas,
thanks for giving this the time. I have run the Configure-EnterpriseApplication.ps1 script following by remove-PartnerApplication so many times that I was wondering if there are other setting that
Configure-EnterpriseApplication.ps1 creates that aer not removed when you run
remove-PartnerApplication.
is there a way to completely remove everything that is confirmed when you run
Configure-EnterpriseApplication.ps1 so I can run Configure-EnterpriseApplication.ps1 without there being any configurations left from when I previously run that command?
thanks
jack
[PS] C:\Windows\system32>Get-PartnerApplication |fl
RunspaceId : cb2fb328-769d-4b32-8b7b-1fa35e2994f5
Enabled : True
ApplicationIdentifier : 00000004-0000-0ff1-ce00-000000000000
CertificateStrings : {MIIGcDCCBVigAwIBAgITPgAAARIHL+ig32UAAQAAAAABEjANBgkqhkiG9w0BAQUFADBcMRUwEwYKCZIm
iZPyLGQBGRYFbG9jYWwxHTAbBgoJkiaJk/IsZAEZFg1HdWlkZUNsb3RoaW5nMSQwIgYDVQQDExtHdWlkZ
UNsb3RoaW5nLUFQUFNFUlZFUjEtQ0EwHhcNMTUwMTEwMTIxODIzWhcNMTcwMTA5MTIxODIzWjB7MQswCQ
YDVQQGEwJHQjEPMA0GA1UECBMGTG9uZG9uMQ8wDQYDVQQHEwZMb25kb24xHzAdBgNVBAoTFkd1aWRlIEN
sb3RoaW5nIExpbWl0ZWQxCzAJBgNVBAsTAkhRMRwwGgYDVQQDExNHdWlkZUNsb3RoaW5nLmNvLnVrMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyzDzaLsjJfktsbwIJ998ihsZM/0rKGdIt8rIx00oc
HA7w0uVyz2UqnP9a8uRi6HkA7djbynlmGG0hKSUUQngXxz7q2dY6q9rcY5Rw2mJOMeppounx44FFp4+4e
5HQKviLTYo+3DBGIR0mYDqxanKPS00d0f7HDLvmVb90hjdrbE372JBdcNNHs2OHRqg37bN2fAbwd22c9x
2kvi0rESFnr+KcIGECVInCTHLJ7fwVqvi4hvRqtz7KLZsMXprpgeVDs45EMMRtwJ5Hw8uZR4CFz4dHSlo
dIVgDPn8Ns2vGhcUK0JU4WkDbjnqo1SJzHlqtNjiu//wGcn77PAiM0yhyQIDAQABo4IDCjCCAwYwCwYDV
R0PBAQDAgWgMCEGCSsGAQQBgjcUAgQUHhIAVwBlAGIAUwBlAHIAdgBlAHIwEwYDVR0lBAwwCgYIKwYBBQ
UHAwEwHQYDVR0OBBYEFOY3whPicRAXNsTDSIg3FexpaCKdMHUGA1UdEQRuMGyCH0x5bmNTZXJ2ZXIyLkd
1aWRlQ2xvdGhpbmcuY28udWuCH0x5bmNTZXJ2ZXIyLkd1aWRlQ2xvdGhpbmcubG9jYWyCE0d1aWRlQ2xv
dGhpbmcuY28udWuCE0d1aWRlQ2xvdGhpbmcubG9jYWwwHwYDVR0jBBgwFoAUDHst3gUSMGwvkiNTPavmi
UEWgtQwggEuBgNVHR8EggElMIIBITCCAR2gggEZoIIBFYaBzWxkYXA6Ly8vQ049R3VpZGVDbG90aGluZy
1BUFBTRVJWRVIxLUNBLENOPURvbVNlcnZlcjIsQ049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2V
zLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9R3VpZGVDbG90aGluZyxEQz1sb2NhbD9jZXJ0
aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGQ
2h0dHA6Ly9jcmwuZ3VpZGVjbG90aGluZy5sb2NhbC9jcmxkL0d1aWRlQ2xvdGhpbmctQVBQU0VSVkVSMS
1DQS5jcmwwgdUGCCsGAQUFBwEBBIHIMIHFMIHCBggrBgEFBQcwAoaBtWxkYXA6Ly8vQ049R3VpZGVDbG9
0aGluZy1BUFBTRVJWRVIxLUNBLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2
aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPUd1aWRlQ2xvdGhpbmcsREM9bG9jYWw/Y0FDZXJ0aWZpY2F0Z
T9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwDQYJKoZIhvcNAQEFBQADggEBAD
87GUPi02czEMO2Op0CeKBBpGwsfjYR9+RlC2uKAoH8PbWAxYNP3Ke6BtPeFy+95GGAJd5Z0+6LpO/AagA
+zeY/tocZQjy0pYaU4/TPZgD+ZB/8sU982msu+8waO316ipBcf/87n9ZW3Jjk5DcVbtwrZErrGRe9DEn8
QArN0jroLfaRtbDumse1Lp76+dxFuVhlLWcUXtIKaxm+UU9DS94EwJMtN54lDm3EG6hVdiGUR7TYqZU0K
HGm7HciIhuO+2rhAazOBiIAAW6wZRUpFKZONSVD6bKrQCzL12LvynQ7XC6Itgr4JGzNCmoN43dXwVCkWo
amTDdZY4h+QBqUvvY=}
AuthMetadataUrl : https://lyncserver2.domainname.local/metadata/json/1
Realm : domainname.local
UseAuthServer : False
AcceptSecurityIdentifierInformation : True
LinkedAccount : domainname.local/Users/LyncEnterprise-ApplicationAccount
IssuerIdentifier :
AppOnlyPermissions :
ActAsPermissions :
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
DistinguishedName : CN=LyncEnterprise-786f61476b634278a3c9b9e4ec08b660,CN=Partner
Applications,CN=Auth Configuration,CN=domainname,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domainname,DC=local
Identity : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
Guid : 07495125-ccd4-4443-82d9-74fc3b955cdf
ObjectCategory : domainname.local/Configuration/Schema/ms-Exch-Auth-Partner-Application
ObjectClass : {top, msExchAuthPartnerApplication}
WhenChanged : 10/01/2015 17:14:55
WhenCreated : 10/01/2015 17:14:55
WhenChangedUTC : 10/01/2015 17:14:55
WhenCreatedUTC : 10/01/2015 17:14:55
OrganizationId :
Id : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
OriginatingServer : DomServer2.domainname.local
IsValid : True
ObjectState : Unchanged

Outlook keep connecting and disconnecting from exchange 2013

hi, currently im having microsoft exchange 2013 in server 2012 standard. when i running my outlook 2007/2010/2013 , it will keep showing connecting and disconnected. once i restart microsoft exchange rpc client access and it will be working fine for temporary,
around 10 min later and it will happend again, can advise?

Hi,
You can raise it via Regedit:
http://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx
Thanks,
Simon Wu
TechNet Community Support

Outlook advanced search & Exchange 2013 - "Sent to...." field doesn't work correctly in online mode?

Hello,<o:p></o:p>
We've come across what seems to be a problem with advanced find in Outlook in online mode, when used with Exchange 2013.
Using the "Messages" tab of "Advanced Find", anything typed into the "Sent to...." field produces no search results. If the field is populated by clicking
"Sent to..." and selecting a name from a contact list or GAL, results are returned.
eg.
Sent items contains messages to "Charlie" who has the email address
[email protected] and sender is
"Dave" who has the email address
[email protected]
Entering "charlie" or
[email protected], (or any previously acceptable partial term such as "charl" or "@contoso.com") into the "Sent to"" field produces no results. If the user exists in a contact
list and is selected from it, the search works fine. The same is true searching the inbox, using the local user's id of "Dave" or
[email protected]
We've confirmed this issue occurs at four client's sites, plus our own internal Exchange 2013 CU3 system. Four of the sites have been transitioned from Exchange 2010, the fifth was a completely new installation. The problem occurs with Outlook
2007, 2010 and 2013.
This works fine in cached mode (not a solution as our clients are predominantly Citrix/RDS). Exchange search doesn't report any issues and the index states are all "healthy",
we've also tried rebuilding the indexes with no improvement.
Any ideas would be appreciated, or even if someone else can confirm they see the same thing.
Thanks.

Hi Winnie,
Thanks for your reply, and I'm sorry I've not responded earlier. While this problem is one that's annoying several of our clients, and while I have been doing further testing and investigation, it's had to take a back seat to other more pressing issues
until now.
OWA search works fine, as does using "From:" in instant search, and the "From" query on the Advanced tab in Advanced Find. The search services have been restarted, indexing state and copy status etc are all healthy, the indexes
have been rebuilt/reseeded, and I've gone through the diagnostics again. Nothing is logged in event viewer, and the only error that comes up when checking failed index docs for a user are for unsupported format handlers (.png etc).
The issue seems purely to be with the "Sent to..." field on the Messages tab, it's as if it gets completely ignored. The search returns instantly with "There are no items to show in this view". Just to make sure I wasn't losing
my marbles, I've compared searches on Exchange 2007 and 2010, and on those I can enter as little as a single letter or email domain and receive the expected results. On 2013 I get nothing whatsoever whatever I enter, unless I pick an address from a contact
list.
At this point, I thought that since Office 365 is Exchange 2013 based it'd be worth testing that, and sure enough I got exactly the same issue. I setup an Office 365/Outlook 2010 profile on a machine that is currently in an existing Exchange 2010
environment where search works correctly, searching Office 365 doesn't work on that either.
EDIT - Ignore this bit, a fresh install of Windows 7 and Office 2010 doesn't work with Office 365 either. I am exploring another avenue. I setup a fresh Windows 7 VM, installed Office 2010 and connected that to Office 365, search worked fine,
so I'm now looking into what the difference with that VM and the servers and workstations out "in the wild" could be. For example, the test VM isn't on a domain, it's not fully patched, it has no additional software installed etc. Outside
of Microsoft applications and operating systems and having similar configurations, I haven't isolated a common link across all of our client sites that are affected, there's no single 3rd party application or anti-virus solution in place at all of them for
example.
I'll update with any findings, but if you or anyone else has any idea in the meantime I'd be grateful for your input.
Regards.

Outlook 2003 and Exchange 2013

We have just installed Exchange 2013 servers in our organization alongside existing Exchange 2007 servers. No mailboxes have been migrated yet and we are about ready to point our client access namespace to the Exchange 2013 servers and go into the co-existence
stage.
We still have some Outlook 2003 clients and I know these need to be updated to 2007 SP3 or 2010 Sp1 or 2013 before those mailboxes are migrated to Exchange 2013.
However, I am curious as to whether we would hit any problems at all if we pointed our namespace to E2K13 before upgrading the Outlook 2003 clients, as long as none of the Outlook 2003 clients use Outlook Anywhere and the mailboxes those clients
connect to remained on Exchange 2007 for the time being ?
Clearly, Outlook 2003 is not 'supported' but the wording in the following link...
http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
says " Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013"
Would the situation I'm thinking of be one of those 'compatible but unsupported' scenarios. i.e I can't think of any reason why the Outlook 2003 clients would have a need to connect to an E2K13 CAS server ...
I'd be interested to hear other people experiences/opinions on this. Thanks!

Hi,
Based on my knowledge, for internal users whose mailboxes exist on Exchange 2007, it is ok to still use Outlook 2003 as clients. Because
they will still connect to the Exchange 2007 Mailbox server instance hosting the mailbox. If the user is moved to Exchange 2013, please upgrade the Outlook client to higher version. Because Exchange 2013 doesn’t support Outlook 2003 client.
For Outlook 2003 clients connected to Exchange 2007, they doesn’t support autodiscover service to get some Exchange services such as free/busy information, OAB. Outlook 2003 would connect to Public Folder in Exchange 2007 to retrieve these
services. For OWA and ActiveSync service, it is not related to Outlook 2003 client, the CAS2013 would redirect the service request or send to CAS2007 for necessary data.
Regards,
Winnie Liang
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.

Can't add multi exchange account on outlook 2010 with exchange 2013 Sp1

I did install exchange 2013 with DAG group successful, the exchange work fine now
Outlook can connect to exchange automatically and working fine
The problem appear when i need create the second exchange account by go to control panel/Mail add new profile and add new exchange profile
How can i solve the problem ?

This Problem in exchange generally appear when users mistakenly create the wrong account type or Outlook upgrades an older account profile.In these situations you need to remove that wrong account and create a New account .
When you have the wrong type of account configured in Outlook you can easily remove the account and create the correct type of account.
1 Go to Control Panel, search for the Mail. If you are using 64-bit Windows and 32-bit Outlook, it will be named as “Mail (32-bit)”
2 Double click on Mail (or Mail (32-bit)).
3 Click Email account button
4. Select the wrong account and click Remove. (If you only have one account listed in your profile,But you may need to create a New account first, set it as default then remove the wrong account.)
5. Click New, select Email Account for POP3 or IMAP accounts, or select other then the correct account type.
6. Fill in your preferred display name, email address and password on the Add New Account dialog.
Outlook will look for published account configuration for the domain and setup the account automatically.
In this event if your email provider does not publish autodiscover information, you’ll need to set up the account yourself. Check your mail providers support site for the proper configuration and then check the box to Manually configure the account at the bottom
of the Add New Account dialog.

Outlook Clients for Exchange 2013 Prompt for Password

I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem:
- Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows:
RunspaceId : b43cd829-a81f-4b00-bb4d-73389c9df50d
ServerName : EXCH-HTCA13
SSLOffloading : False
ExternalHostname : webmail.first.pt
InternalHostname : exch-htca13.first.pt
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
Can anyone help me identify the problem?

Hi,
Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
In addition, I recommend you refer to the following article:
Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
Thanks.
Note: 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.
Niko Cheng
TechNet Community Support

Outlook disconnects from Exchange 2013 several times an hour.

[Edit: I did figure out a little more of the issue. I have figured out that what is causing this is the IIS Application Poll that The Exchange 2013 installer creates by default when installing called "MSExchangeRpcProxyAppPool". The server is recycling
the RPC Application Pool every 20 - 30 minutes or so. I have recycling completely turned off on this pool yet it still restarts which leads me to believe it may be a code problem since it only should recycle if the poll crashes. Short of a bug in the
code somewhere, I for the life of me can not find why the Application Pool keeps restarting. This is the only pool out of all the ones Exchange created during installation that is recycling constantly. It is frustrating because our Outlook Anywhere clients
keep getting disconnection messages several times an hour because of this. The event logs I listed below are the only event logs I can find that trigger when the pool recycles, so as you can see, they give me no useful information in debugging the
problem.]
This problem only applies to outlook clients using RPC over HTTP. ActiveSync, OWA and EWS are working fine.
There is a problem with the RPC over HTTP tunnel on our server. Every 20-30 minutes, sometimes more sometimes less, but usually with in that 20-30 minute timeframe, the RPC over HTTP tunnel drops and all Outlook Anywhere clients get immediately disconnected.
IT comes back up very fast and all clients reconnect with in a matter of seconds. Not a huge deal for people using cached mode outlook but all the non-cached mode people (Thin clients are an example are not using cached mode to save diskspace). People using
non-cached mode would get a couple errors pop up and outlook stopped working.
The only relevant entries I have found in the exchange server event log are here. These same grouping of events show up everytime the RPC over HTTP tunnel shuts down and restarts. I just can't figure out why its doing it:
1-23-2013 9:21:18 AM RPC Proxy 4 (1)
-- RPC Proxy successfully loaded in Internet Information Services (IIS).
1/23/2013 9:22:41 AM WAS 5138 None
--- A worker process '75832' serving application pool 'MSExchangeRpcProxyAppPool' failed to stop a listener channel for protocol 'http' in the allotted time. The data field contains the error number.
1/23/2013 9:22:41 AM WAS 5013 None
--- A process serving application pool 'MSExchangeRpcProxyAppPool' exceeded time limits during shut down. The process id was '75832'.
I have been searching for weeks on the problem and all I really have found is that the problem can sometimes be caused by RPC timeouts so I set the RPC timeout on the server to 120 seconds via the registry. That actually helped for about 5 days and then the
problem mysteriously came back and I can not get it to go away even though the registry value is still set to 120 seconds on that RPC time out.
Does anyone else know of any thing else that causes this? Its Exchange 2013 on Server 2012 and is a pretty fresh install. Was setup in mid-December.
--Trent W.

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Thanks,
Simon Wu
TechNet Community Support
Have you had any luck diagnosing the problem?

Cannot connect to SBS 2008 Exchange with Outlook externally

Hello,
We used to be able to connect to a native Exchange account with Outlook even when we were not onsite, however this has stopped working.
If we connect onsite, it works straight away.
Outlook Web App works fine.
We are using a self-signed certificate and always have. It is still on the same certificate since it was last used successfully (i.e. it hasn't expired and been renewed).
Any thoughts? Thanks.

Plain white screen is expected result.
Lets add a registry key if not exist
1. Set DisableLoopbackCheck in registry :
2. Click Start , click Run , type regedit , and then click OK .
3. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
4. Right-click Lsa , point to New , and then click DWORD Value .
5. Type DisableLoopbackCheck , and then press ENTER.
6. Right-click DisableLoopbackCheck , and then click Modify .
7. In the Value data box, type 1 , and then click OK .
8. Quit Registry Editor, and then restart your computer.
Also Create BackConnectionHostNames
Open Registry , Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
1) Create Multi-String Value “BackConnectionHostNames”
2) Right-click BackConnectionHostNames, and then click Modify.
3) In the Value data box, type 'Externalhostname' (Note - ExternalHostname is the name that is shown in Get-Outlookanywhere result)
-RPCwithCert VD By default, all authentication methods are disabled
SSL required
Require 128-bit encryption
-On RPC virtual directory enable
Basic authentication
Windows authentication
SSL Not required
Default Authentication Settings :-
https://technet.microsoft.com/en-us/library/gg263433(v=exchg.80).aspx

My iphone 4s cannot connect to my work exchange email

I got a new/referbished phone yesterday and cannot connect my work email to my phone. This needs to happen! I have soo much work emails and calendar reminders on Exchange! HELP!!!!!

I suggest making contact with your IT department at work. It is very possible they have MAC filtering on, or there are other settings in the Exchange environment that would prevent connecting a new device to the Exchange server. They should be able to sort that out for you. You do not describe any errors that you see when trying to connect.

Unable to expand public folder in Outlook 2013 and Exchange 2013 CU6

Hello,
we have just migrated Exchange 2010 to 2013. Everything works great, except public folders, which we are not able to expand in Outlook 2013. Public folders can be added to OWA without any problem, so just the Outlook 2013 is a problem (we never tried any
other version, as all the e-mail clients installed here are Outlook 2013).
The public folders are visible under node Favorities in Outlook 2013, but whenever we click any folder, the Public folders disappear completely from the left navigation pane or the message is shown on the right pane, that the public folder cannot be opened.
When Outlook is started, a dialog is sometimes opened, which contains prefilled Microsoft exchange server, mailbox, button Check name, which is disabled. The only thing which can be done with that dialog is clicking the button Ok.
Any help is appreciated, the desperation level starts to be reaching max threshold.
Kind regards,
John.

Thank you for your quick response. I have tried removing and creating new Outlook profile many times, without any effect.
1) When I switch to the online mode, only the node All Public Folders is displayed in the left navigation pane and after I start the Outlook the dialog mentioned above is displayed. The node Favourities is not visible.
2) In offline node, node App Public folders is visible and whenever I click it, message "Cannot expand the folder" is shown. After checking Download favourities, the list of public folders is available, but whenever I click any folder, it shows
"We didn't find anything to show here." and "The folder is up to date." in the bottom status bar. The content is rendered correctly in OWA and these public folders contain many e-mails and subfolders. None of these is rendered in Outlook.
Thanks in advance for any tips and inspiration, we start to run out of ideas. I am more than sure that it will be something simple, but we can't still figure it out.

Cannot Connect Outlook 2013 to Exchange 2013

Similar Messages

Maybe you are looking for