Exchange 2013 & Exchange 2007 Co-exist - Problems with Outlook anywhere proxy

Hi,
Got EX13 and EX07 in co-exist. Pointed all the external URL to EX13. ActiveSync proxies to 2007 and OWA redirects to legacy url with SSO. Working perfectly!
But with Outlook Anywhere it does not work. Mailboxes on EX13 works good, but not for EX07 user.
Error message from MRCA:
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server "internalFQDN ofbackend EX07 server"
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

Hi,
We need to change the Authenticaion on the Outlook Anywhere to NTLM
Set-OutlookAnywhere -Identity "xxx\Rpc (Default Web Site)" –InternalHostName mail.domain.com
 -InternalClientsRequireSsl $True -ExternalHostName mail.domain.com
 -ExternalClientsRequireSsl $True -InternalClientAuthenticationMethod NTLM 
-ExternalClientAuthenticationMethod NTLM -IISAuthenticationMethods 
Basic, NTLM, Negotiate 
Please first backup the Outlook Anywhere settings then do the above changes.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

  • Exchange 2013, Outlook 2007 clients Problems with Outlook Anywhere connection

    Hi everyone,
    I have a mail system Exchange 2013 SP1, on Windows Server 2012 R2.
    I have only one mail server with the Client Access and Mailbox roles Server. 
    I have a Wildcard certificate type *. Mydomain.com. 
    All connections to the Outlook Anywhere Outlook 2010, Outook 2013 work correctly. 
    The ActiveSync connections are working properly, too. 
    But Outlook 2007 clients connecting with Outlook Anywhere asking for credentials continuously fail continuously. 
    How can I solve this? 
    thank you very much
    Microsoft Certified IT Professional Server Administrator

    Hi,
    Based on my experience, we need to set Outlook provider with the domain name if it's wildcard certificate:
    Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
    http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
    Thus, I recommend you try the above configuration and test the Outlook connection again.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Can Exchange 2007 to be integrated with SharePoint 2013

    Can Exchange 2007 to be integrated with SharePoint 2013?

    In the sense of using Incoming and Outgoing email, absolutely. But not for other things, like Site Mailboxes, which require Exchange 2013.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • 2 exchange 2013 multirole server and 1 addess for Outlook Anywhere. How to?

    Hello everybody.
    I'm coming to you with a question about my new Exchange 2013 infrastructure. 
    I have 2 Exchange 2013 SP1 servers. Both are multirole (CAS + MBX). My servers are Server12 and Server13. 
    I created a DAG which IP adderss is 192.168.3.30 (Servers IP are 3.31 and 3.32). Everything's working fine. 
    For CAS High Availability, I followed this thread : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
    On my firewall, I use NAT to send https flow from my public IP address (mail.domain.fr, external domain
    published on internet) to point to mail.domain.org (internal domain, non published on Internet). The mail.domain.org alias is my record defined in my internal DNS to
    point to my 2 multirole server, as shown in the tutorial above.
    I encounter a problem with external outlook anywhere. My problem comes with Outlook Anywhere which is not working fine when I redirect https flow to my cluster IP address (192.168.3.30) (DAG's address, corresponding to my servers). If I do the same redirection,
    but pointing to only one of my servers, it's working fine. In Exchange, external outlook Anywhere directory points to mail.domain.fr
    But anyway, if this servers goes down, I have to change manually the NAT on my firewall. And I don't want to :). 
    How can I do ? Can I do something without a physical load-balancer? 
    Thanks

    You cannot point Outlook Anywhere to your DAG cluster IP address. It must be pointed to the actual IP address of either server.
    For no extra cost DNS round robin is the best you will get, but it does have some drawbacks as it may give the IP address of a server you have taken down for maintenance or the server has an issue.
    You could look to implement a load balancer but again if you are doing this for high availability then you want more than one load balancer in the cluster - otherwise you've just moved your single point of failure.
    Having your existing NAT and just remembering to update it to point to the other server during maintenance may suit your needs for now.
    If you can go into more detail about what the high availability your business is looking to achieve and the budget we can suggest the best method to meet those needs for the price point.
    Have a great day
    Oliver
    Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

  • Migrating to 2013 from 2007 with Outlook Anywhere disabled

    Hello
    I'm in the middle of a migration from 2007 With Outlook anywhere disabled.
    After I installed 2013 I added the external url to both inside and outside url's on CliantAccess, o-anywhere url and Virtual catalogs.
    When I configured the External Access domain on the 2013 it also added this on the external url's on the 2007 server. On the 2007 server i manuelly changed the external url's to the Legacy name which is mail.domain.com. The New server is webmail.domain.com
    both internally and externally. The servers real name is xxmail.domain.internal
    After this, when I configure an Outlook Client With a user on the old server With autodiscover it configures it With Outlook anywhere, not mapi, but With the external name of the New server, webmail.domain.com under http Proxy settings. When I then
    moved this user to the New server it stopped working in Outlook.
    Is the best approch to enable Outlook anywhere on the 2007 server before migrating the users or can I og from mapi/rpc to rpc over http in 2013 without Outlook problems?
    Regards

    Hi,
    Firstly, I’d like to explain, all users in Exchange 2013 use Outlook Anywhere. The information of Exchange proxy settings tab is automatically updated by Autodiscover.
    I recommend you the following troubleshooting:
    1. Check the Autodiscover configuration on both Exchange 2007 and Exchange 2013 servers:
    Get-clientaccessserver |fl autodiscoverserviceinternaluri
    2. Check if there is any DNS entry about the legacy name points to Exchange 2007 IP address.
    3. Check if you can logon OWA with both Exchange 2007 and Exchange 2013 server.
    Best regards,
    Angela Shi
    TechNet Community Support

  • Some Outlook clients getting internal FQDN of newly installed Exchange 2013 CAS server as Outlook Anywhere Proxy address

    Hello Folks,
    I have this problem and is making me crazy if anyone have any idea please shed some light on this:-
    1. Working Outlook 2010 and 2013 clients with webmail.xyz.com as Outlook Anywhere proxy address.
    2. Installed new Exchange 2013 server (server02)with CAS and Mailbox role, Exchange install wizard finished and server is rebooted.
    3. Server came up online started changing internal and external FQDN's of Virtual Directories and Outlook Anywhere to webmail.xyz.com
    4. As soon as Fqdn's changed some outlook clients create support request that Outlook suddenly white's out and after reopening it is giving error  cannot connect to exchange. upon checking Clients Exchange Proxy address is set to http://server02.xyz.com,
    even though OA/OWA/ECP/OAB/EWS/Autodiscover/ActiveSync FQDN's Point to webmail.xyz.com, on all servers if i create new outlook profile for same user it picks up correct settings through autodiscover and connects fine, this is happening to about 20% of outlook
    clients every time i am introducing new Exchange 2013 server in Organization. we have around 2000 users and planning on installing 4 exchange servers to distribute load and everytime changing outlook profile of close to 150-200 users is not possible.
    Any help is greatly appreciated.
    Thanks
    Cool

    Here are the EXCRA results
    Here IP (x.x.x.x) returned is my Load Balancer IP (Webmail.xyz.com).    
    Connectivity Test Successful with Warnings
    Test Details
         Testing Outlook connectivity.
         The Outlook connectivity test completed successfully.
              Additional Details
         Elapsed Time: 9881 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
         Autodiscover was tested successfully.
              Additional Details
         Elapsed Time: 2063 ms.
              Test Steps
              Attempting each method of contacting the Autodiscover service.
         The Autodiscover service was tested successfully.
              Additional Details
         Elapsed Time: 2063 ms.
              Test Steps
              Attempting to test potential Autodiscover URL https://xyz.com:443/Autodiscover/Autodiscover.xml
         Testing of this potential Autodiscover URL failed.
              Additional Details
         Elapsed Time: 186 ms.
              Test Steps
              Attempting to resolve the host name xyz.com in DNS.
         The host name couldn't be resolved.
           Tell me more about this issue and how to resolve it
              Additional Details
         Host xyz.com couldn't be resolved in DNS InfoNoRecords.
    Elapsed Time: 186 ms.
         Attempting to test potential Autodiscover URL https://autodiscover.xyz.com:443/Autodiscover/Autodiscover.xml
         Testing of the Autodiscover URL was successful.
              Additional Details
         Elapsed Time: 1876 ms.
              Test Steps
              Attempting to resolve the host name autodiscover.xyz.com in DNS.
         The host name resolved successfully.
              Additional Details
         IP addresses returned: x.x.x.x
    Elapsed Time: 338 ms.
         Testing TCP port 443 on host autodiscover.xyz.com to ensure it's listening and open.
         The port was opened successfully.
              Additional Details
         Elapsed Time: 173 ms.
         Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
              Additional Details
         Elapsed Time: 318 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
              Additional Details
         Remote Certificate Subject: CN=webmail.xyz.com, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
    Elapsed Time: 219 ms.
         Validating the certificate name.
         The certificate name was validated successfully.
              Additional Details
         Host name autodiscover.xyz.com was found in the Certificate Subject Alternative Name entry.
    Elapsed Time: 1 ms.
         Certificate trust is being validated.
         The certificate is trusted and all certificates are present in the chain.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,.
         One or more certificate chains were constructed successfully.
              Additional Details
         A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 36 ms.
         Analyzing the certificate chains for compatibility problems with versions of Windows.
         Potential compatibility problems were identified with some versions of Windows.
              Additional Details
         The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature
    isn't enabled.
    Elapsed Time: 5 ms.
         Testing the certificate date to confirm the certificate is valid.
         Date validation passed. The certificate hasn't expired.
              Additional Details
         The certificate is valid. NotBefore = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 PM
    Elapsed Time: 0 ms.
         Checking the IIS configuration for client certificate authentication.
         Client certificate authentication wasn't detected.
              Additional Details
         Accept/Require Client Certificates isn't configured.
    Elapsed Time: 289 ms.
         Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
         The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
              Additional Details
         Elapsed Time: 756 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xyz.com:443/Autodiscover/Autodiscover.xml for user [email protected].
         The Autodiscover XML response was successfully retrieved.
              Additional Details
         Autodiscover Account Settings
    XML response:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
    <DisplayName>Test Exch1</DisplayName>
    <LegacyDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1</LegacyDN>
    <DeploymentId>4ec753c9-60d9-4c05-9451-5b24e2d527a7</DeploymentId>
    </User>
    <Account>
    <AccountType>email</AccountType>
    <Action>settings</Action>
    <Protocol>
    <Type>EXCH</Type>
    <Server>[email protected]</Server>
    <ServerDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
    <ServerVersion>73C0834F</ServerVersion>
    <MdbDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <PublicFolderServer>webmail.xyz.com</PublicFolderServer>
    <AD>DC-03.domain.xyz.com</AD>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>off</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXPR</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>on</ServerExclusiveConnect>
    <EwsPartnerUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsPartnerUrl>
    <GroupingInformation>Default-First-Site-Name</GroupingInformation>
    </Protocol>
    <Protocol>
    <Type>WEB</Type>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <Internal>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://webmail.xyz.com/owa/</OWAUrl>
    <Protocol>
    <Type>EXCH</Type>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    </Protocol>
    </Internal>
    <External>
    <OWAUrl AuthenticationMethod="Fba">https://webmail.xyz.com/owa/</OWAUrl>
    <Protocol>
    <Type>EXPR</Type>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    </Protocol>
    </External>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    </Account>
    </Response>
    </Autodiscover>HTTP Response Headers:
    request-id: 9d325a80-f1fd-4496-ac48-2be6bb782c28
    X-CalculatedBETarget: Server01.domain.xyz.com
    X-DiagInfo: Server01
    X-BEServer: Server01
    Persistent-Auth: true
    X-FEServer: Server01
    Content-Length: 11756
    Cache-Control: private
    Content-Type: text/xml; charset=utf-8
    Date: Mon, 25 Aug 2014 19:12:25 GMT
    Set-Cookie: X-BackEndCookie=S-1-5-21-1293235207-2459173341-1304346827-14544=u56Lnp2ejJqBypqcnsfJx5nSy8ucnNLLnJzP0sfKz8/Sy5nHmsiamZrMyZrLgYHPxtDNy9DNz87L387Gxc7Nxc3J; expires=Thu, 25-Sep-2014 00:12:26 GMT; path=/Autodiscover; secure; HttpOnly
    Server: Microsoft-IIS/8.5
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 756 ms.
         Autodiscover settings for Outlook connectivity are being validated.
         The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
              Additional Details
         Elapsed Time: 0 ms.
         Testing RPC over HTTP connectivity to server webmail.xyz.com
         RPC over HTTP connectivity was verified successfully.
              Additional Details
         HTTP Response Headers:
    request-id: 835acf95-78b7-40ae-b232-117318d1577e
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
    X-Powered-By: ASP.NET
    X-FEServer: Server01
    Date: Mon, 25 Aug 2014 19:12:26 GMT
    Content-Length: 0
    Elapsed Time: 7817 ms.
              Test Steps
              Attempting to resolve the host name webmail.xyz.com in DNS.
         The host name resolved successfully.
              Additional Details
         IP addresses returned: x.x.x.x
    Elapsed Time: 107 ms.
         Testing TCP port 443 on host webmail.xyz.com to ensure it's listening and open.
         The port was opened successfully.
              Additional Details
         Elapsed Time: 180 ms.
         Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
              Additional Details
         Elapsed Time: 303 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server webmail.xyz.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
              Additional Details
         Remote Certificate Subject: CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 224 ms.
         Validating the certificate name.
         The certificate name was validated successfully.
              Additional Details
         Host name webmail.xyz.com was found in the Certificate Subject Common name.
    Elapsed Time: 0 ms.
         Certificate trust is being validated.
         The certificate is trusted and all certificates are present in the chain.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,
         One or more certificate chains were constructed successfully.
              Additional Details
         A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 34 ms.
         Analyzing the certificate chains for compatibility problems with versions of Windows.
         Potential compatibility problems were identified with some versions of Windows.
              Additional Details
         The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature
    isn't enabled.
    Elapsed Time: 5 ms.
         Testing the certificate date to confirm the certificate is valid.
         Date validation passed. The certificate hasn't expired.
              Additional Details
         The certificate is valid. NotBefore = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 PM
    Elapsed Time: 0 ms.
         Checking the IIS configuration for client certificate authentication.
         Client certificate authentication wasn't detected.
              Additional Details
         Accept/Require Client Certificates isn't configured.
    Elapsed Time: 298 ms.
         Testing HTTP Authentication Methods for URL https://webmail.xyz.com/rpc/[email protected]:6002.
         The HTTP authentication methods are correct.
              Additional Details
         The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic, Negotiate, NTLMHTTP Response Headers:
    request-id: 835acf95-78b7-40ae-b232-117318d1577e
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
    X-Powered-By: ASP.NET
    X-FEServer: Server01
    Date: Mon, 25 Aug 2014 19:12:26 GMT
    Content-Length: 0
    Elapsed Time: 296 ms.
         Attempting to ping RPC proxy webmail.xyz.com.
         RPC Proxy was pinged successfully.
              Additional Details
         Elapsed Time: 454 ms.
         Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 0 ms.
    Elapsed Time: 1007 ms.
         Testing the MAPI Address Book endpoint on the Exchange server.
         The address book endpoint was tested successfully.
              Additional Details
         Elapsed Time: 2177 ms.
              Test Steps
              Attempting to ping the MAPI Address Book endpoint with identity: [email protected]:6004.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 906 ms.
    Elapsed Time: 918 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         The test passed with some warnings encountered. Please expand the additional details.
           Tell me more about this issue and how to resolve it
              Additional Details
         The address book Bind operation returned ecNotSupported. This typically indicates that your server requires encryption. The Microsoft Connectivity Analyzer will attempt the Address Book test again with encryption.
    NSPI Status: 2147746050
    Elapsed Time: 825 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         Check Name succeeded.
              Additional Details
         DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
    Elapsed Time: 433 ms.
         Testing the MAPI Referral service on the Exchange Server.
         The Referral service was tested successfully.
              Additional Details
         Elapsed Time: 1808 ms.
              Test Steps
              Attempting to ping the MAPI Referral Service endpoint with identity: [email protected]:6002.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 953 ms.
    Elapsed Time: 949 ms.
         Attempting to perform referral for user /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1 on server [email protected].
         We got the address book server successfully.
              Additional Details
         The server returned by the Referral service: [email protected]
    Elapsed Time: 858 ms.
         Testing the MAPI Address Book endpoint on the Exchange server.
         The address book endpoint was tested successfully.
              Additional Details
         Elapsed Time: 626 ms.
              Test Steps
              Attempting to ping the MAPI Address Book endpoint with identity: [email protected]:6004.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 156 ms.
    Elapsed Time: 154 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         Check Name succeeded.
              Additional Details
         DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
    Elapsed Time: 472 ms.
         Testing the MAPI Mail Store endpoint on the Exchange server.
         We successfully tested the Mail Store endpoint.
              Additional Details
         Elapsed Time: 555 ms.
              Test Steps
              Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 234 ms.
    Elapsed Time: 228 ms.
         Attempting to log on to the Mailbox.
         We were able to log on to the Mailbox.
              Additional Details
         Elapsed Time: 326 ms.

  • Sync problems with outlook 2007 calender

    I am new in this type of comms.
    BUT: I have a Palm Tungsten T5; have Palm Desktop 6.2.2 with the update for Windows7.
    I have a sync problem with outlook 2007 calender; contacts, ToDo, memos all ok.
    HotSynLog says: there are multi-day repeating records. [i knew that they do not sync, hence i deleted them PRIOR to syncing]
    I found the listed records BUT either on dif days and they are "no timed" ones! and NOT multi-days ones.
    I deleted them anyway - did a re-sync. With no different result. Still listed - though deleted and now non-existent.
    Error code: OLERR: 03-000F (0xaf604005) and others - if this means anything.
    Post relates to: Palm TX

    Hello,
    I receive email on my device from two addresses: 1) @sprint.blackberry.net and 2) @charter.net.  When I was having problems similar to those you are experiencing, I had these two addresses listed under Default Services - Calendar (CICAl) - Messaging (CMIME).  These addresses were @sprint.blacberry.net and @charter.net. Once I followed the steps previously referenced, only one email address(@sprint.blackberry.net) appeared under the (CICAI) and (CMMIE) default setting.  Reference to @charter.net was removed.  My syncs have worked correctly since then; however, I only two way synce with the device and Outlooks.  I also continue to get emails from both addresses without a problem.
    If you don't mind giving up the Yahoo calendar, I would do the same.  If you want to continue using the Yahoo calendar, I'm guessing that it must be selected in the Default Services - Calendar (CICAI) before performing a sync.  Likewise for your @sprint.blackberry.net address; it also must be selected in the Default Services prior to performing a device to Outlook sync.
    I hope this helps.
    Tres

  • I use Exchange to sync my iphone4S with Outlook.  On my iphone, my contacts are split into multiple records if they have more than one email address - how can I consolidate them on the iphone

    i use Exchange to sync my iphone4S with Outlook.  On my iphone, my contacts are split into multiple records if they have more than one email address - how can I consolidate them on the iphone

    I have loaded my Firefox bookmarks into Internet Explorer Favorited. I also uninstalled Safari.
    I go to iTunes on my phone and see no wat to connect my iPhone to my laptop. I see Music, Shows, etc., the kind of stuff I would expect, but no clue as to how to proceed.
    Would you please be so kind to fill me in on how to "That syncing is done via iTunes. Connect the device to iTunes, select it, then go to the Summary page and select to sync bookmarks."?
    I am not sure what you mean by "Summary Page"
    Thank you

  • Having email imap synchronization problems with outlook 365 proplus

    Hello,
    I have email imap synchronization problems with outlook 365 proplus.
    If I sent emails , my sent items box does not synchronized.
    This is really a bug, because I see more problems like this on internet.
    Please make ASAP a solution , this is not professional
    JMR

    Hi JMR,
    Assuming you are referring to Outlook 2013 by "outlook 365 proplus". This is actually because Outlook 2013’s IMAP implementation has changed when compared to previous versions of Outlook.
    While configuring the IMAP account, Outlook will talk to the IMAP server for the correct folders first. If Outlook 2013 can’t find the correct folder for the Sent Items in your mail server, it will create a folder which doesn’t sync with the mail server.
    To sync the Sent Items folder with IMAP server, we can try to root the mailbox:
    Go to FILE->Account Settings->Account Settings…
    Double click on your IMAP account.
    Click More Options… button, then Advanced tab
    Type "Inbox" as the "Root folder path"
    Hope this helps.
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Problems with outlook and address book contacts: my outlook contacts had around 3,000 entries. Outlook duplicated by itself and now outlook and address book have each over 340,000. What should I do?

    Problems with outlook and address book contacts: my outlook contacts had around 3,000 entries. Outlook duplicated entries and have now 340,000. I reinstalled microsoft office and, thus, outlook, and reinstalled mac OS X system and applications. While I managed to delete outlook contacts so that I can re-sync with my blackberry, the contacts at Mac Address Book were not deleted and still have over 340,000 entries. I do not mind deleting all contacts since I have back up, but I have not been able to delete them. Also, when I go at Address Book and try to delete or merge duplicated entries, the system takes forever and never ends because of such large amount of entries. Worse, when I do so I run out of RAM memory.
    My Macbook pro is just 2 months old.
    What should I do? Is there a way to delete my Mac Address Book without having the problem above?
    Many thanks
    Regis

    zlatan24 wrote:
    For solving out troubles connected with corrupted or lost address book you may use address book recovery. It owns various features such as restoring wab files, it working under any Windows OS. The utility has modern and easy to use interface due to almost every experienced users.
    If it is a windows problem it's not going to run on the OP's MacBook Pro

  • Remote Resources: "A problem with the system proxy caused the connection to fail: End of file"

    Hi, I am trying to use "Remote Resources" on the current version of the Microsoft Remote Desktop for Android app, I can input the webfeed and it even shows the apps that I have configured on the server for "Remote App", sadly whenever
    I try to load any of the RemoteApps, I receive an error stating " A problem with the system proxy caused the connection to fail. End of File".
    I don't know what I can do to fix this, I've tried many things to no avail, also, normal Remote Desktop connections from the Microsoft Android app work flawlessly to the server.
    The relevant log is the following:
    [2014-Jan-09 04:40:54] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jan-09 04:40:54] RDP (0): Final rdp configuration used: memory bookmark [
    label 
    hostname DIAZSERVER
    port 3389
    loadbalanceinfo 
    ui.swapmousebutton false
    remote.program ||ZWaveUtil
    remote.workingdirectory 
    remote.name ZWave Adapter Utility
    remote.args 
    rail true
    soundmode 0
    connect_to_console false
    redirectsdcard true
    performance_flags 134
    arc.sessionid 0
    anonymous_username 
    authentication_level 2
    use_redirection_server_name false
    username administrator
    gateway [
      host = DIAZSERVER
      port = 443
      bypass = false
    connect info[
      hostnames = [localhost]
      gatewayHost = DIAZSERVER
      gatewayPort = 443
      routingToken = Cookie: mstshash=administrator
      redirectionGUID = 
      proxyHost = 200.5.68.10
      proxyPort = 8080
      sessionId = -1
    [2014-Jan-09 04:40:54] RDP (0): Using HttpConnect proxy at 200.5.68.10:8080
    [2014-Jan-09 04:40:54] RDP (0): Using Basic Authentication with username ''
    [2014-Jan-09 04:40:54] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    AsioEndpointContext (0): startup(): starting up down context
    [2014-Jan-09 04:40:54] RDP (0): Resolved '200.5.68.10' to '200.5.68.10' using NameResolveMethod_DNS(1)
    [2014-Jan-09 04:40:54] RDP (0): Resolved '200.5.68.10' to '200.5.68.10' using NameResolveMethod_DNS(1)
    ASIOSocketAdapter (9): readSomething error. message: End of file. instance: 0x5d39d5c0
    RpcOverHttp (9): Stream error in endpoint 0x5abbc170 : A problem with the system proxy caused the connection to fail: End of file
    [2014-Jan-09 04:40:55] RDP (0): Error message: A problem with the system proxy caused the connection to fail: End of file
    [2014-Jan-09 04:40:55] RDP (0): Error message: A problem with the system proxy caused the connection to fail: End of file
    [2014-Jan-09 04:40:55] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    ASIOSocketAdapter (9): handleRead(): exception: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : Failed to read from channel: -1. instance: 0x5d39d5c0
    [2014-Jan-09 04:40:55] RDP (0): Disconnect initiated by client
    RpcOverHttp (9): Exception in endpoint 0x5abbc170 : Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
    [2014-Jan-09 04:40:55] RDP (0): Exception caught: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
    [2014-Jan-09 04:40:55] RDP (0): Exception caught: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
        User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    [2014-Jan-09 04:40:57] RDP (0): ------ END ACTIVE CONNECTION ------

    My problem is that the "proxy" is the proxy set up by my 3G configuration so, I tried connecting to the remote resources through my work wifi and I get the following:
    [2014-Jan-14 16:58:13] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jan-14 16:58:13] RDP (0): Final rdp configuration used: memory bookmark [
    label 
    hostname DIAZSERVER
    port 3389
    loadbalanceinfo 
    ui.swapmousebutton false
    remote.program ||chrome
    remote.workingdirectory 
    remote.name Google Chrome
    remote.args 
    rail true
    soundmode 0
    connect_to_console false
    redirectsdcard true
    performance_flags 134
    arc.sessionid 0
    anonymous_username 
    authentication_level 2
    use_redirection_server_name false
    username Administrator
    gateway [
      host = DIAZSERVER
      port = 443
      bypass = false
    connect info[
      hostnames = [localhost]
      gatewayHost = DIAZSERVER
      gatewayPort = 443
      routingToken = Cookie: mstshash=Administrator
      redirectionGUID = 
      proxyHost = 
      proxyPort = 0
      sessionId = -1
    [2014-Jan-14 16:58:13] RDP (0): Not using any proxy
    [2014-Jan-14 16:58:13] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    AsioEndpointContext (0): startup(): starting up down context
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d474090
    RpcOverHttp (9): Stream error in endpoint 0x5d46b678 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d445158
    RpcOverHttp (9): Stream error in endpoint 0x5d49fa30 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 16:58:17] RDP (0): Disconnect initiated by client
    [2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    [2014-Jan-14 16:58:17] RDP (0): ------ END ACTIVE CONNECTION ------
    Now, I know the host can be resolved because: if I connect to the same host but on a full remote desktop (as opposed to just RemoteApp on it) I have no trouble either through 3G OR through my work connection.
    Moreover, I also tried directly inputting the IP as opposed to the web address of my server, I get the same error, that is the Remote Resources tab is able to access the feed (because it shows the available RemoteApps) but when I click an app it says it can't
    find the Host, here's the log for the connection directly to the IP address/rdweb/feed/webfeed.aspx :
    [2014-Jan-14 17:09:27] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jan-14 17:09:27] RDP (0): Final rdp configuration used: memory bookmark [
    label 
    hostname DIAZSERVER
    port 3389
    loadbalanceinfo 
    ui.swapmousebutton false
    remote.program ||chrome
    remote.workingdirectory 
    remote.name Google Chrome
    remote.args 
    rail true
    soundmode 0
    connect_to_console false
    redirectsdcard true
    performance_flags 134
    arc.sessionid 0
    anonymous_username 
    authentication_level 2
    use_redirection_server_name false
    username administrator
    gateway [
      host = DIAZSERVER
      port = 443
      bypass = false
    connect info[
      hostnames = [localhost]
      gatewayHost = DIAZSERVER
      gatewayPort = 443
      routingToken = Cookie: mstshash=administrator
      redirectionGUID = 
      proxyHost = 
      proxyPort = 0
      sessionId = -1
    [2014-Jan-14 17:09:27] RDP (0): Not using any proxy
    [2014-Jan-14 17:09:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    AsioEndpointContext (0): startup(): starting up down context
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d372f28
    RpcOverHttp (9): Stream error in endpoint 0x5dd6b168 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d378de0
    RpcOverHttp (9): Stream error in endpoint 0x5e9cc1f0 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    [2014-Jan-14 17:09:31] RDP (0): Disconnect initiated by client
    [2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    AsioEndpointContext (0): shutdown(): shutting down context
    AsioEndpointContext (0): shutdown(): context shut down
    [2014-Jan-14 17:09:31] RDP (0): ------ END ACTIVE CONNECTION ------
    I'm really puzzled here, I've tried checking if ports where open, and ports 443 and 3389 are wide open, I don't know what else it could be.

  • Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist

    Hi all,
    Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
     When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
    The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
    Why would I get this error? The install itself was problematic so I am concerned something is broke.
    Thank you in advance.

    Hello,
    Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
    Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
    And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
    If you have any feedback on our support, please click
    here
    Cara Chen
    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 Server Std 2007 mailbox store problem with a single account email showing

    Under Exchange mailbox store there is no existent account name who is receiving and sending email without any errors.
    Account was not hidden and was always working. Email client of this account works properly with Outlook 2007. Accounts listing in Exchange management snap-in does not contain his email record. We found that address book of other client does not display his
    name and tried to find his record to uncheck hidden but there was no any records in the list. How to find and fix this problem if no errors encountered with the delivery of his mail and replies back?

    Hi,
    From your description, I recommend you check if this problematic user is existed in ADUC. What's more, I recommend you create a same email account in your Exchange server and check if there is any error.
    Best regards,
    Amy Wang
    TechNet Community Support

  • SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

    We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server. 
    Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one? 
    Old Server:
    SBS2008 running Exchange 2007
    New Server:
    Server 2012
    Exchange 2013
    Any help is appreciated!

    Hi Dave,
    It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
    you in the past).
    For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model.  In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
    up to 2 Virtual Machines on same host).
    There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration. 
    You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration.  But the high points are in here. If it looks
    like something you would be comfortable with then you should research more.
    http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
    Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
    and migrate your workstations out of old domain into new domain.  Whether this is more or less work at your workstation count is dependent upon a lot of variables.
    If you have more questions about the process, update the thread and we'll try to assist.
    Hopefully this info answered your original question.
    Cheers,
    -Jason
    Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Maybe you are looking for