Groupware Connecter/Exchange Server

Hi All,
We are thinking about using the Groupware connector for MS Exchange server.  The installation guide instructs to store the contact information in Public folder but Public folders are going away.  Yes we can use the private folders but then synchronization becomes uni-directional.  Is there a way not to use Public folders and still be able to synchronize data both ways?  Any solution that SAP is coming up with since Public folders may go away in MS Exchange Server 2007?
Thanks,
Rutul

Hi,
Is there a way to integrate SAP CRM to MS Sharepoint?  We use MS Exchange server 2007 and Outlook with business contact manager to store the data to Sharepoint, and then integrate Sharepoint with SAP CRM.  that's a lot of effort i think but still an option.
Thanks,
Rutul

Similar Messages

  • Receive email delay one hour using Mac Mail client (Mountain Lion) connect Exchange Server 2010

    Hi all,
    My boss use iPhone, iPad, MacBook Air (Mac Mail client), MacPro (Mac Mail client) connect Exchange Serve 2010 to receive emails. All clients are okay except MacBook Air, the Mac Mail client cannot receive the latest emails from Exchange Server, but it can receive (sync) the emails after one hour. The other clients can receive the latest email after Exchange Server receive new emails immediately.
    In this period, the MacBook Air can receive the other IMAP, POP3 and webmail from ISP normally. I tried to set 5 mins to check emails or manual check email from Exchange Server. However, the latest email still delay one hour.......... .
    I dumped a screenshot for Mac Mail setting for Exchange Server and a Log file.
    could anyone help me to solve this issue?
    Thanks

    I am not sure what the user has the check for new messages set for but mail does arrive as short as 2 minutes.  It does however arrive on his iphone immediately first.

  • Outlook 2010 not connecting exchange server

    We have Exchange server on remote site. we have installed win7 SP1 and office 2010 SP2 and updated the system as well. but
    outlook 2010 is always "asking password" or it shows "trying to connect" in status bar and then it got disconnect.  i have tryied configured  NTLM authentication, https proxy settings everything i have tryied as mentioned in
    blogs but it doesn't worked out to me but outlook is working fine in other system with same settings and H/W and S/W.  can any one kindly help me on this

    Hi,
    You can first use Remote Connectivity Analyzer to test if you can connect to the Exchange server:
    https://testconnectivity.microsoft.com/
    We may need to repair the Outlook profile to fix the problem:
    In Outlook, click the arrow next to Account Settings on the
    File tab, and then click Account Settings.
    In the Account Settings dialog box, select your account on the
    E-mail tab, and then click Repair. Follow the instructions in the repair wizard.
    When the repair is finished, restart Outlook.
    As you mentioned, Outlook always asks for password. If the issue persists, check this setting:
    Go to File tab -> Info -> Account Settings -> Account Settings…
    Highlight your Exchange account and click Change button.
    Click on More Settings button.
    Select the Security tab.
    Under the User Identification, make sure the “Always prompt for logon credentials” option is not selected.
    Outlook may continuously asks for password due to the corrupted credentials, we can try the following steps as well:
    Go to Control Panel, and then click Credential Manager.
    Note If View by is set to Category, click User Accounts first, and then click Credential Manager.
    Locate the set of credentials that has Outlook in the name.
    Click the name to expand the set of credentials, and then click Remove from Vault.
    Repeat step 3 for any additional sets of credentials that have the word Outlook in the name.
    I hope the information is helpful.
    Regards,
    Melon Chen
    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.

  • Cann't connect exchange server

    I cann't use out look to open  exchange account the problem appears when i use outlook on the client PC 

    Hi ,
    I think your ost file is corrupted .
    Take a backup of your ost file and delete it
    Then try to configure a new profile in outlook with cached mode and it will gives you a fresh ost file.
    Thanks & Regards S.Nithyanandham

  • Microsoft Exchange Server Auth Certificate Error

    I have new install the Exchange server 2013. I accidentally assigned the IIS service to the Microsoft Exchange Auth Certificate. now i'm facing problem to connect exchange server from outlook.
    The Error shows
    "There is a problem with the proxy server's security certificate.  The name on the security certificate is invalid or does not match the name of the target site
    name.  Outlook is unable to connect to the proxy server. (Error Code 10)."
    Certificate shows error
    "This CA root Certificate is nit trusted because it is not in the Trusted Root Certificate Authorities store"
    Please help me...
    Thanks

    HI Winnie,
    if i use root CA from AD CA can solve this issue?
    Please see the result:
    [PS] C:\Windows\system32>Get-ExchangeCertificate | FL
    AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule}
    CertificateDomains : {DBH-EX01, DBH-EX01.deltabrac.com}
    HasPrivateKey      : True
    IsSelfSigned       : True
    Issuer             : CN=Microsoft Exchange Server Auth Certificate
    NotAfter           : 12/19/2018 12:37:13 PM
    NotBefore          : 12/19/2013 12:37:13 PM
    PublicKeySize      : 2048
    RootCAType         : None
    SerialNumber       : 30F29F3C289D448A4244C95D267B9976
    Services           : IMAP, POP, SMTP
    Status             : Valid
    Subject            : CN=Microsoft Exchange Server Auth Certificate
    Thumbprint         : 514DDBBDAB0878766B9D305A0D500CBEA334E109
    AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule}
    CertificateDomains : {}
    HasPrivateKey      : True
    IsSelfSigned       : True
    Issuer             : CN=Microsoft Exchange Server Auth Certificate
    NotAfter           : 12/18/2018 3:51:00 PM
    NotBefore          : 12/18/2013 3:51:00 PM
    PublicKeySize      : 2048
    RootCAType         : None
    SerialNumber       : 2AAA1A565B385794473CE3AC8D3A85F4
    Services           : IIS, SMTP
    Status             : Valid
    Subject            : CN=Microsoft Exchange Server Auth Certificate
    Thumbprint         : 5E6026E8C9CC18BFE3684E58CD2876AC97A2514D
    AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule}
    CertificateDomains : {DBH-EX01, DBH-EX01.deltabrac.com}
    HasPrivateKey      : True
    IsSelfSigned       : True
    Issuer             : CN=DBH-EX01
    NotAfter           : 12/11/2018 7:25:05 PM
    NotBefore          : 12/11/2013 7:25:05 PM
    PublicKeySize      : 2048
    RootCAType         : Registry
    SerialNumber       : 1C611FA9102B64B3462A0100FEF74A12
    Services           : IMAP, POP, IIS, SMTP
    Status             : Valid
    Subject            : CN=DBH-EX01
    Thumbprint         : 2FD1A8D2141DCA036F3DD5BE1191FD1FB6966EE9
    AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule,
                         System.Security.AccessControl.CryptoKeyAccessRule}
    CertificateDomains : {WMSvc-DBH-EX01}
    HasPrivateKey      : True
    IsSelfSigned       : True
    Issuer             : CN=WMSvc-DBH-EX01
    NotAfter           : 12/9/2023 5:03:46 PM
    NotBefore          : 12/11/2013 5:03:46 PM
    PublicKeySize      : 2048
    RootCAType         : Registry
    SerialNumber       : 4013857FC4683FA940C6DCC87A83A05F
    Services           : None
    Status             : Valid
    Subject            : CN=WMSvc-DBH-EX01
    Thumbprint         : BAE5A99C48FDFDBDBDE1E158833F862BB977DC01

  • Integrate Sharepoint task list with exchange server

    First question is it possible or not? I have tried to search a lot on this topic but does not find a way to achieve this. I know how to integrate task list with outlook but I want to integrate it with exchange
    server. Any help in this regard would be highly appreciated.

    Hi  ,
    In SharePoint Server 2010 , tasks lists are blindly synced to the local Outlook desktop application. You can see SharePoint Tasks only on the client computer to which the SharePoint task list was downloaded.
    If you log on to another device, you must sync the SharePoint task list to that device in order to see the tasks.
    But in SharePoint Server 2013, SharePoint Server 2013 task lists use Exchange Server to sync, tasks are updated in real time and can be seen on any device that you use to access Microsoft Outlook. When SharePoint
    Server is connected to Microsoft Exchange Server, and all client computers are connected to Exchange Server, client computers receive information from the task lists directly from Exchange Server.
    For a workaround, you can use 3rd Party tool  to connect Exchange Server to SharePoint task lists. For  more  information, you can refer to the blog:
    http://www.layer2solutions.com/en/community/FAQs/BDLC/Pages/How-to-connect-SharePoint-lists-to-Exchange.aspx
    Reference:
    http://support.microsoft.com/kb/2876938
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • "Connection to server failed" error with Gmail exchange server

    Hi,
    I upgraded my iPhone 4 to iOS 4.3 on Friday and now I can't access my Gmail account using the Microsoft Exchange settings, I just get a "Connection to server failed" error.
    I also have a Google Apps email account for my website and I am able to access it using exchange... it's just my regular Gmail account that I can't access (and that's where all my contacts are stored).
    I can access the account using the regular Gmail email settings but that doesn't sync my contacts over the air, which is the advantage of using Exchange that I love the most.
    I don't know if it is related or not, but I had a really hard time upgrading to iOS 4.3. I guess the update file was corrupt and it put my phone into restore mode. I had to use a different computer for the upgrade to finally work. Because I was using a different computer I had to restore it as a new phone rather than restoring from a backup, so maybe that has something to do with my email problem.
    Message was edited by: KJones75

    I seem to have solved the problem. I deleted my Gmail account from the phone and then changed my Gmail password from my computer, and then tried adding the account to my phone again... and surprise, surprise, it worked.
    I'm not sure why changing the password fixed the problem, but I'm glad it's working again.

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • How do i connect to exchange server remote desktop

    Hi, hope someone can point me in the right direction.
    I have recently purchased a macbook pro and wish to
    connect to our office server which is a windows exchange server (remote desktop).
    Which steps do I need to take.
    Many Thanks,
    Rob K.

    Anyone able to help ?
    I used to be abale to access my company email when the URL for webmail was "email.COMPANY.co.uk" but recently it was changed to "webmail.COMPANY.co.uk" and now my iphone cannot verify my account.
    Any ideas ?
    I have the following info (selected pieces removed for privacy.
    Mailbox owner: XXXXX
    User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; chromeframe/18.0.1025.58)
    The required version of Silverlight is installed: Yes
    Required version of Silverlight: 2.0.31005.0
    Outlook Web App experience: Premium
    User language: English (United Kingdom)
    User time zone: (UTC) Dublin, Edinburgh, Lisbon, London
    Exchange mailbox address:XXXX
    Host address: https://webmail.COMPANY.co.uk/owa
    Version: 14.2.247.5
    Host name: webmail.COMPANY.co.uk
    S/MIME control: not installed
    Exchange Client Access server name: XXXX
    Exchange Client Access server .NET Framework version: 2.0.50727.5446
    Client Access server operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1
    Client Access server operating system language: en-US
    Client Access server version: 14.2.247.0
    Client Access server language: en-US
    Client Access server time zone: (UTC) Dublin, Edinburgh, Lisbon, London
    Client Access server platform: 64bit
    Mailbox server name: XXXX.XXXX.local
    Mailbox server Microsoft Exchange version: 14.2.247.0
    Other Microsoft Exchange server roles currently installed on the Client Access server: Hub Transport
    Authentication type associated with this Outlook Web App session: Kerberos
    Public logon: Yes
    Internal POP setting:
         Server name: XXXX.XXXX.local
         Port: 995
         Encryption method: SSL
    Internal IMAP setting:
         Server name: XXXX.XXXX.local
         Port: 993
         Encryption method: SSL
    Custom Forms: loaded
    Segmentation settings: fffffffeefc3ffff
    Restricted functionality settings: fffffffeefc3ffff

  • Mac computers in the office are not able to connect to our exchange server.

    We started facing this problem about a month ago in our office where the apple computers can not connect to the exchange server via outlook or applemail or anything for that matter. All the other computers can connect to the exchange server with no problems
    and the apple computers can even access the exchange server via OWA but the outlook and applemail apps would not connect to exchange. We have tried even deleting and re-creating some accounts on the apps but they still would not connect. At this point I am
    at a complete loss and I looked everywhere through google to find out if anyone else has faced this problem but to no avail.
    A little background information. This specific problem started happening after there was an un-expected series of power outages to the servers and they were shut down un-expectedly. I personally restored the servers and turned on all the services and made
    sure everything was up and running after the power outages and everything was working fine. Also the first instance of the problem with the mac computers only happened two days after the servers were back up and running again and they had no issues in those
    two days.
    Right now we do not have that many mac users in our offices (only 3-4 users) and I have instructed them to use the OWA in the meanwhile but it is however an inconvenience to them. By now you may have realized that I am not a very experienced server admin
    and I would really really appreciate any help. I extend my thanks in advance for any insight.

    Hi Martin,
    Thanks for the reply.
    Right now I have Apple mail and Outlook installed on my mac laptop and both the applications do not connect to the exchange server. Apple Mail simply does a long process when I give my credentials to create my account and then it gives an error saying it
    could not find the server while outlook quickly tells me that either the username or password is incorrect. At the same time I can connect to the server through outlook on my windows computer without any problems whatsoever.
    From your reply, I gather that the VIA headers only affect Apple mail and should not affect Outlook app on the mac but right now, neither apps are connecting to the exchange server.
    Either way I am trying to find out how to remove the VIA headers because it does not seem that we are using Kemp on the exchange server. Right now I do not have the in depth knowledge that I need because I was not involved in the implementation of our server
    system, that was taken care of by a service provider and I was put in charge of mostly simple admin work. Now we are out of contract with the service provider so  pretty much everything has fallen onto my shoulders.
    If possible, would you mind pointing me in the right direction to finding out if I am using a L7 load balancer and how I would go about removing the VIA headers?

  • Windows Server 2008 R2 Standard "Certificate Authority Service" / Exchange Server 2010 EMC not starting and no AD connectivity for authentication.

    Hello,
    I am a new IT Manager at this company and need assistance big time. Their environment looks as follows:
    Server 1. Domain Controller Server (Windows Server 2008 R2 Standard) running active directory.
    Server 2. Email Server (Windows Server 2008 R2 Standard) running Exchange Server 2010 .
    * Note. No back ups to work with aside from whats mentioned below.
    DC had a virus infection causing a lot of issues on the shared network drives 2 days ago locking up all the files with a crypto ransom virus. Running Avast suppressed the infection. Had to recover the file shares which luckily had a back up. 
    The issue is that the Exchange Server 2 post this lost connectivity with the AD Server 1. Exchange Server 2 when launching EMC could not launch the console stating the following:
    "No Exchange servers are available in any Active Directory sites. You can’t connect to remote
    Powershell on a computer that only has the Management Tools role installed."
    Shortly after I found that it is possible the EMC launcher was corrupt and needed to be reinstalled following another blog post. I deleted the exchange management console.msc  per instructions only to discover I couldnt relaunch it because there was
    no way how. So I copied another msc file that happened to be on the DC Server 1  back to Exchange Server 2 and got it to launch again. 
    Another post said that it might be an issue with the Domain Account for the Computer, so to delete it in the AD Server 1 only to find that rejoining it from Exchange Server 2 using Computer>Properties> Chage Settings > Change is greyed out because
    it is using the Certificate Authority Service.
    I tried manually re-adding the computer in AD and modeling permissions after another server in group settings but no go. After this I was unable to login to the Exchange Server 2 with domain accounts but only local admin, receiving the following Alert:
    "The Trust Relationship between this workstation and primary domain failed."
    I tried running the Power Shell tools on Exchange Server 2 to rejoing and to reset passwords for domain accounts as noted in some other blogs but no luck as the Server 2 could not make the connection with Server1 or other errors it kept spitting out.
    I also during the investigation found the DNS settings were all altered on both the Server 1 and Server 2 which I luckily was able to change back to original because of inventorying it in the beginning when I started. 
    I need help figuring out if I need to rejoin the Exchange Server 2 manually by disabling the Certificate Authority Service (or removing the CA as listed here:
    https://social.technet.microsoft.com/Forums/exchange/en-US/fb23deab-0a12-410d-946c-517d5aea7fae/windows-server-2008-r2-with-certificate-authority-service-to-rejoin-domain?forum=winserversecurity
    and getting exchange server to launch again. (Mind you I am relatively fresh to server managing) Please help E-Mail has been down for a whole day now!
    Marty

    I recommend that you open a ticket with Microsoft Support before you break things more.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • How do I get the Windows 8.1 Mail/Calendar/People apps to connect to my company's Exchange server?

    I have a Surface Pro 2 on my organization's domain, and while I have Outlook 2013 running fine on the desktop side, I'd really like to connect the Mail, Calendar, and People apps to my work Exchange account if possible.
    First, a little background on my company's Exchange configuration, which is "extra secure" variety. Obviously, I'm using generic placeholders here. My email address is
    [email protected], but our actual Exchange server is exchange.internaldomain.com, and my actual username is lasfir (first 3 of last name, first 3 of first name). I'm not 100% clear on our certificate process,
    but from what I understand from talking with our Systems team, it's a self-signed certificate.
    Anyway, when I try to add my account, I get the usual email address and password prompts. I enter
    [email protected] and my password, which don't resolve. The app returns "we couldn't find settings for
    [email protected] Provide us with more info and we'll try connecting again."
    So I add the internaldomain as the domain and lasfir as my username and click Connect again. This time it returns "we still couldn't find settings for
    [email protected] Providing this additional info may help. If you don't know this information, search online or check with your provider."
    So I enter exchange.internaldomain.com as my server address and click Connect again. This time it returns "to connect to this account, you need a valid certificate on this PC. Contact your system administrator for more info." That tells me at least
    it's finding my Exchange server, but I have no idea about the certificate thing. I reached out to our Exchange admin and our Systems guys, and they just weren't sure about the certificate process.
    As one of the few people in my organization running Windows 8x, I'm a bit of a guinea pig for stuff like this. Any advice how to get this working?
    - Greg

    It doesn't sound like the Exchange environment is configured in a manner to support these types of clients very well.  Have your Exchange team look at the following
    http://blogs.technet.com/b/exchange/archive/2012/11/26/supporting-windows-8-mail-in-your-organization.aspx
    http://blogs.technet.com/b/exchange/archive/2013/10/18/supporting-windows-mail-8-1-in-your-organization.aspx
    From the latter article: "Communications applications can connect to a corporate Exchange service
    configured to require certificate-based authentication. User authentication certificates can be provisioned to Windows 8.1 devices by administrators or end-users can browse to certificate and install to user certificate storage."
    You might want to:
    Ask your Exchange team the public URLs (ExternalURL) for Exchange OWA & ActiveSync
    Open the OWA URL in your Internet Explorer from your Surface
    If you get a Certificate warning, open the certificate and select Install (NOTE: You may have to install the entire certificate chain).  Your desktop support team should be able to support this because it is the SAME process for standard Windows 8x
    desktops.
    Confirm that you can open OWA on your surface with no more certificate or security warnings.  NOTE: The Exchange team will have to configured OWA properly.
    Once confirmed, repeat the same steps for the activesync URL that they provided.
    When done, try using the OWA OR ActiveSync URL value in your settings of your Mail client.
    Good Luck

  • Outlook connection to exchange server problem

    We have a new domain and an existing exchange server. The problem is if i log in with a local computer account i can autodiscover and connect in cached mode to exchange no problem. If i then login with a domain user account the same computer (tried on other
    workstations) will fail to auto discover, fail to connect to exchange even with manual settings. I cant find anything obvious in Group policy.
    The server is setup with the latest 2013 Group policy templates with office 2013 templates
    Users not logged in with the new AD server can connect to exchange 
    Users not logged into the domain can access exchange server
    My feeling is its a local setting that is missing or needs to be changed in Group Policy but i am at a loss as to what it could be
    I have disabled roaming profiles too and it makes no difference.
    Any help would be greatly appreciated.
    Steve

    Hi,
    Sorry for my delay. According to your description, I summarize your issue to the following points:
    1. No problem when the user logs in Outlook with a local computer account in Cached mode.
    2. Can’t connect to Exchange from an cache mode enabled Outlook 2013 client when using a domain user account on the same computer automatically or manually.
    3. Can connect to Exchange from an online mode enabled Outlook 2013 client when using a domain user account on the same computer automatically or manually.
    It is right? If I misunderstand, please feel free to point it out. Additionally, I noticed that the server is setup with the latest 2013 Group policy templates with office 2013 templates. Please confirm
    if the Outlook cache mode is disabled by OTC or GPO. If there is following registry key applied on the machine:
    Software\Microsoft\Office\15.0\Outlook\Cached Mode
    Meanwhile, please try to install an Outlook 2013 with a fresh ISO file(Don’t use any template such as OCT template), see if the Cached mode Outlook can connect to Exchange server.
    Waiting for your updates.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Problem connecting to godaddy exchange server via outlook client

    I am pretty much having a very similar problem here:
    https://social.technet.microsoft.com/Forums/exchange/en-US/437c5f8d-3a42-4689-90b4-13fd2749373f/go-daddy-ucc-certificate-exrca-can-only-validate-the-certificate-chain-using-the-root-certificate?forum=exchangesvr3rdpartyappslegacy
    When I set up in outlook, I have noticed this in advanced connection settings:
    the URL is required
    mail.ex4.secureserver.net
    Then check connect SSL only
    Only connect to proxy servers with this principal name
    msstd:mail.ex4.secureserver.net
    When I use the connect principal, it works fine, but otherwise if it is not checked, it won't connect to the server.
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26423254.html
    However, when I restart outlook, because I have multiple exchange accounts, they keep becoming "unchecked".
    Everything worked fine about 48 hours ago, and now... all these problems.
    Here is my log from the testing site:
    Connectivity Test Failed
    Test Details
        Testing Outlook connectivity.
         The Outlook connectivity test failed.
        Additional Details
    Elapsed Time: 3897 ms.
        Test Steps
        Testing RPC over HTTP connectivity to server mail.ex4.secureserver.net
         RPC over HTTP connectivity failed.
        Additional Details
    HTTP Response Headers:
    Content-Type: text/html
    Server: Microsoft-IIS/7.5
    WWW-Authenticate: Negotiate,NTLM
    X-Powered-By: ASP.NET
    Date: Fri, 13 Feb 2015 01:07:27 GMT
    Content-Length: 58
    Elapsed Time: 3897 ms.
        Test Steps
        Attempting to resolve the host name mail.ex4.secureserver.net in DNS.
         The host name resolved successfully.
        Additional Details
    IP addresses returned: 72.167.83.115
    Elapsed Time: 95 ms.
        Testing TCP port 443 on host mail.ex4.secureserver.net to ensure it's listening and open.
         The port was opened successfully.
        Additional Details
    Elapsed Time: 110 ms.
        Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
        Additional Details
    Elapsed Time: 461 ms.
        Test Steps
        The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.ex4.secureserver.net on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
        Additional Details
    Remote Certificate Subject: CN=mail.ex4.secureserver.net, O="Starfield Technologies, LLC.", L=Scottsdale, S=AZ, C=US, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository,
    O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
    Elapsed Time: 356 ms.
        Validating the certificate name.
         The certificate name was validated successfully.
        Additional Details
    Host name mail.ex4.secureserver.net 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=mail.ex4.secureserver.net, O="Starfield Technologies, LLC.", L=Scottsdale, S=AZ, C=US.
         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 OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
    Elapsed Time: 39 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 = 11/29/2012 8:39:18 PM, NotAfter = 11/29/2015 8:39:18 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: 232 ms.
        Testing HTTP Authentication Methods for URL https://mail.ex4.secureserver.net/rpc/rpcproxy.dll?mail.ex4.secureserver.net:6002.
         The HTTP authentication methods are correct.
        Additional Details
    The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM
    HTTP Response Headers:
    Content-Type: text/html
    Server: Microsoft-IIS/7.5
    WWW-Authenticate: Negotiate,NTLM
    X-Powered-By: ASP.NET
    Date: Fri, 13 Feb 2015 01:07:27 GMT
    Content-Length: 58
    Elapsed Time: 146 ms.
        Attempting to ping RPC proxy mail.ex4.secureserver.net.
         RPC Proxy was pinged successfully.
        Additional Details
    Elapsed Time: 224 ms.
        Attempting to ping the MAPI Mail Store endpoint with identity: mail.ex4.secureserver.net:6001.
         The attempt to ping the endpoint failed.
          Tell me more about this issue and how to resolve it
        Additional Details
    The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
    Elapsed Time: 2626 ms.

    Here is another test from the autodiscover:
        The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
         Autodiscover was tested successfully.
        Additional Details
    Elapsed Time: 1745 ms.
        Test Steps
        Attempting each method of contacting the Autodiscover service.
         The Autodiscover service was tested successfully.
        Additional Details
    Elapsed Time: 1745 ms.
        Test Steps
        Attempting to test potential Autodiscover URL https://MYDOMAIN.com:443/Autodiscover/Autodiscover.xml
         Testing of the Autodiscover URL was successful.
        Additional Details
    Elapsed Time: 1745 ms.
        Test Steps
        Attempting to resolve the host name MYDOMAIN.com in DNS.
         The host name resolved successfully.
        Additional Details
    IP addresses returned: xx.168.xx.74
    Elapsed Time: 59 ms.
        Testing TCP port 443 on host MYDOMAIN.com to ensure it's listening and open.
         The port was opened successfully.
        Additional Details
    Elapsed Time: 60 ms.
        Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
        Additional Details
    Elapsed Time: 197 ms.
        Test Steps
        The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server MYDOMAIN.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
        Additional Details
    Remote Certificate Subject: CN=MYDOMAIN.com, OU=Domain Control Validated, Issuer: CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
    Elapsed Time: 132 ms.
        Validating the certificate name.
         The certificate name was validated successfully.
        Additional Details
    Host name MYDOMAIN.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=MYDOMAIN.com, OU=Domain Control Validated.
         One or more certificate chains were constructed successfully.
        Additional Details
    A total of 2 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
    Elapsed Time: 27 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: 4 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 = 7/2/2014 2:30:01 AM, NotAfter = 7/2/2015 2:30:01 AM
    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: 673 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: 754 ms.
        Test Steps
        The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://MYDOMAIN.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>[email protected]</DisplayName>
    </User>
    <Account>
    <AccountType>email</AccountType>
    <Action>settings</Action>
    <Protocol>
    <Type>IMAP</Type>
    <Server>MYDOMAIN.com</Server>
    <Port>993</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>on</SSL>
    <DomainRequired>off</DomainRequired>
    <SPA>off</SPA>
    <AuthRequired>on</AuthRequired>
    <LoginName>[email protected]</LoginName>
    </Protocol>
    <Protocol>
    <Type>SMTP</Type>
    <Server>MYDOMAIN.com</Server>
    <Port>465</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>on</SSL>
    <DomainRequired>off</DomainRequired>
    <SPA>off</SPA>
    <AuthRequired>on</AuthRequired>
    <LoginName>[email protected]</LoginName>
    </Protocol>
    </Account>
    </Response>
    </Autodiscover>
    HTTP Response Headers:
    Keep-Alive: timeout=15, max=256
    Connection: Keep-Alive
    Content-Length: 1227
    Content-Type: application/xml; charset="UTF-8"
    Date: Fri, 13 Feb 2015 01:14:56 GMT
    Server: Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips DAV/2 mod_bwlimited/1.4 mod_fcgid/2.3.9
    Elapsed Time: 754 ms.

  • You must connect to Microsoft Exchange with your current profile before you can synchronize your folders with your outlook data file (.ost).... OWA works but outlook 2013 does not, exchange server 2013 on Server standard 2012

    I have read a lot of articles and tried a lot of things, but I cannot get outlook to connect to my exchange server. This is a test environment, I have tried making my own certificate and signing it through my own CA to no avail. I have completely disabled
    windows firewall and stopped the service. I can ping between the two just fine by name or IP. I've tried not using cached mode, creating new profiles in outlook etc. I tried setting my CertPrincipalName to my FQDN in exchange powershell.
    I am not an expert with exchange at all, but I feel like this should work with little to no configuration, instead I've wasted days on this. Half of the articles I've read don't seem to have solutions, and the other half have solutions that are not working
    for me.
    I can access OWA and send emails on a client computer through OWA with no problems.
    I am running a test domain on the same network as my current exchange 2003/sbs 2003 active environment, I don't know why this would be an issue, but if it is I cannot figure out why. The only thing I can see holding me back right now is not having a signed
    certificate from digicert etc, and an official internet domain set up, but I don't think either of those things matter in my situation. 
    Any help is greatly appreciated and I'll gladly provide any other information requested to solve this issue, thank you.

    I have a similar setup and also have the same error. Did you find a solution for this?
    In the managed availability - monitoring log I see the following errors:
    EMSMDB.Connect() step of ComplianceOutlookLogonToArchiveRpcCtpProbe/Mailbox Database 0326619395 has failed against BESRVCOTEXCH001 proxying to BESRVCOTEXCH001 for [email protected].
    Latency: 00:01:58.0150000
    ActivityContext: 
    Outline: [15] RpcProxy connectivity verification; [117999][FAILED!] EMSMDB.Connect(); 
    Likely root cause: HighLatency
    Details: 
    Error: Error 0x71a (The remote procedure call was cancelled) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall RPC EEInfo is not enabled or there is no error on this thread.
    Log:     RpcProxy connectivity verification
        Task produced output:
        - TaskStarted = 8/5/2014 7:47:11 AM
        - TaskFinished = 8/5/2014 7:47:11 AM
        - ErrorDetails = 
        - Latency = 00:00:00.0153816
        - RpcProxyUrl = https://besrvcotexch001.hq.corp.cotrain.lan/rpc/[email protected]:6001
        - ResponseStatusCode = OK
        - RequestedRpcProxyAuthenticationTypes = ntlm
        - RespondingHttpServer = BESRVCOTEXCH001
        - RespondingRpcProxyServer = BESRVCOTEXCH001
        - WebHeaderCollection = Persistent-Auth: true
    X-DiagInfo: BESRVCOTEXCH001
    X-BEServer: BESRVCOTEXCH001
    Content-Length: 20
    Content-Type: application/rpc
    Date: Tue, 05 Aug 2014 05:47:11 GMT
    Server: Microsoft-IIS/8.0
    X-Powered-By: ASP.NET
    RpcProxy connectivity verification completed successfully.
        Mailbox logon verification
            EMSMDB.Connect()
            Task produced output:
            - TaskStarted = 8/5/2014 7:47:11 AM
            - TaskFinished = 8/5/2014 7:49:09 AM
            - Exc
    and 
    EMSMDB.Connect() step of OutlookRpcCtpProbe/Mailbox Database 0326619395 has failed against BESRVCOTEXCH001 proxying to BESRVCOTEXCH001 for [email protected].
    Latency: 00:01:58.0250000
    ActivityContext: 
    Outline: [13] RpcProxy connectivity verification; [118011][FAILED!] EMSMDB.Connect(); 
    Likely root cause: HighLatency
    Details: 
    Error: Error 0x71a (The remote procedure call was cancelled) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall RPC EEInfo is not enabled or there is no error on this thread.
    Log:     RpcProxy connectivity verification
        Task produced output:
        - TaskStarted = 8/5/2014 7:23:20 AM
        - TaskFinished = 8/5/2014 7:23:20 AM
        - ErrorDetails = 
        - Latency = 00:00:00.0132417
        - RpcProxyUrl = https://besrvcotexch001.hq.corp.cotrain.lan/rpc/[email protected]:6001
        - ResponseStatusCode = OK
        - RequestedRpcProxyAuthenticationTypes = ntlm
        - RespondingHttpServer = BESRVCOTEXCH001
        - RespondingRpcProxyServer = BESRVCOTEXCH001
        - WebHeaderCollection = Persistent-Auth: true
    X-DiagInfo: BESRVCOTEXCH001
    X-BEServer: BESRVCOTEXCH001
    Content-Length: 20
    Content-Type: application/rpc
    Date: Tue, 05 Aug 2014 05:23:20 GMT
    Server: Microsoft-IIS/8.0
    X-Powered-By: ASP.NET
    RpcProxy connectivity verification completed successfully.
        Mailbox logon verification
            EMSMDB.Connect()
            Task produced output:
            - TaskStarted = 8/5/2014 7:23:20 AM
            - TaskFinished = 8/5/2014 7:25:18 AM
            - Exc

Maybe you are looking for

  • New iPod update has messed up my Artist list!!!

    I would greatly appreciate if anyone could help me out, as this problem is causing a great deal of annoyance & frustration. My iPod recently that there was a new update to download, which I did. However, once I did this, this has greatly messed up my

  • Reg Soft error on SATA SSD with smartctl command

    Hi, When we run smarcli on SSD disk , we are seeing the below message from dmesg    (command :- ./smartctl -a -d sat /dev/rdsk/c0t500A0751093F1E6Fd0) SATA SSD disk is connected to system via SAS backplane dmesg ==================== Nov 18 06:52:41 mo

  • SQL Server Configuration Manager 2008 - Slow to bring back SQL Services

    HI WMI queries are taking ~ 1 minute to bring up SQL Server services using the SQL server Configuration manager 2008. The cluster is a two node cluster with ~ 6 instances installed. Each node is running Windows 2008 R2 64 Bit and has been configured

  • Reg RFC to JDBC scenario

    Hi Techies, This is inregard of RFC to JDBC Scenario. Iam having an old RFC to JDBC scenarion which is working fine. I want to call other BAPI programme using the same RFC connection. I have changed  BAPI and ABAP Programmes. But Still in my integrat

  • Howto disable the firewall in AEBS Airport Extreme Base Station

    Is there any way to do that? Motivation: I don't want to reroute ports to a DHCP address which changes constantly. Plus: Editing the port reroute list is a pain! I have no problems with my Asus WL500gP but this thing just doesn't get printing right w