Outlook connection question

Currently we are running Outlook 2007 with Exchange 2010, I am about to install Exchange 2013 and we are not going to upgrade Office 2007 yet. So my question is can I still use a MAPI connection to exchange 2013 and NTLM? If so how would I go about that,
Thanks.
MSB

Hi,
From your description, I would like to clarify the following thing:
RPC over HTTP Proxy component, which Outlook Anywhere clients use to connect, wraps remote procedure calls (RPCs) with an HTTP layer. In Exchange 2013, Outlook Anywhere is enabled by default, because all Outlook connectivity takes place via Outlook Anywhere.
The only post-deployment task you need to perform to successfully use Outlook Anywhere is to install a valid SSL certificate on your Client Access server. Mailbox servers in your organization only require the default self-signed SSL certificate.
For your reference:
Outlook Anywhere
https://technet.microsoft.com/en-us/library/bb123741(v=exchg.150).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

  • Outlook Connectivity Question

    Hello  All:
          In our client case they have Outlook installed in laptops, etc. But their exchange server is outside of the company. So they connect to it through some proxy using HTTP. Does it have any problem working with SBO outlook addon? My understand of it always is that outlook addon only look at outlooks, wether how outlooks connect to it's server or other servers is not a concern! Is that true? Thank You!
    Sincerely Yours

    Bo,
    You can start with this link ... https://websmp205.sap-ag.de/~sapidb/011000358700007392752004E.
    Once you are here, you will need to click on SAP Business One Products > Updates > SAP Business One 2005A > SAP Business One 2005A > Entry by Component, then either SAP B1 - SP00 Patches or SAP B1 - SP01 Patches, the appropriate B1 add-on.
    Sorry .. there is not a direct link to it and you will need your "S" number to log into the portal.
    HTH,
    Eddy

  • Outlook connection status window explained

    (this may be an already discussed topic, in that case feel free to answer with a hyperlink to another technet forum topic)
    Dear all,
    I am looking for a technet blog post, that explains all the tiny little details of the "Connection status" window, that is accessible if I CTRL+right click on the Outlook 2010 tray bar. I would like to receive some very professional and at
    least Level 300 explanation of all the possible information visible in this troubleshooting window. Unfortunately there are hundreds of hits for this search term, I find it nearly impossible to find that single article that is right for me.
    Richard
    PS: I think my question wasnt posted in the best topic, I would like to ask an admin to move it into the proper category under Exchange server

    Servername: pretty obvious :)
    Type:
    Directory => what is the server providding the answer to DSQUERY command / rpc proxy for authentification (therefore it is normal to see your exchange server when using outlook anywhere if you would use a direct mapi connection the "real"
    DC/GC name would show). This one is normally there twice , once for GC once for DC.
    Mail => you mailbox store server
    Public folder => if you still have a public folder store, that will identify what is the PF you are connected to.
    Interface: the local network interface used for the connection so either your wired connection or the wireless card
    Conn: HTTPS or MAPI, if you are using Exchange 2013 you will always see HTTPS. for older version, MAPI can only be on the local network.
    Status: current status of the connection type, you will see that changing if you start outlook /rpcdiag from at home.
    req/fail: number of current request/number of current request failed
    Avg Resp: delay of response (in ms) can be usefull to troubleshoot for long request (with exmon) or network bottleneck
    Authn: NTLM, KERBEROS, certificate etc...
    from the complet article about the change of outlook connectivity, here is also the explanation to the field that were not in previous outlook version (http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx):
    Field
    Value
    Protocol
    HTTP (v/s RPC/HTTP for Outlook Anywhere)
    Proxy Server
    Empty
    Server name
    Actual server name (v/s GUID for Outlook Anywhere connections)
    I hope that answer your question, however nowadays aside to check the current connection status of the client, you will get more usefull troubleshooting info from the exchange logs.
    Regards,
    Eric
    Please“Vote As Helpful”if you find my contribution useful or “MarkAs Answer” if it does answer your question.
    That will encourage me - and others - to take time out to help you.

  • ITunes 10 vs Outlook, some questions

    I haven't had that issue on my home PC where I use Thunderbird but I'm hesitant to upgrade to 10 on my work machine where I HAVE to use outlook.
    A few questions for some people to reply to to help me see what's up, if you don't mind.
    1) Do you have "sync to Outlook" enabled, if yes, what happens if you turn that option off, close iTunes & Outlook & then retry to open Outlook with iTunes running, do the same issues occur?
    2) If that solves the issue does it recur if you re-enable outlook syncing?
    My feeling is that there is an issue with the Outlook connection that iTunes is using to perform the syncing, this has occurred in the past & may be cropping up again.

    Hi,
    This article: http://support.apple.com/kb/TS3500 addresses this issue and provides a fix of renaming the "OutlookChangeNotifierAddIn.dll" file.
    -Jason

  • Microsoft Test Agent appears to be blocking Outlook connectivity to Exchange

    Core Problem
    The problem I am having is that connectivity to Exchange from Outlook is blocked while executing an integration test through the Microsoft Test Agent (i.e. Outlook
    is in the disconnected state). The test is launched through Microsoft Test Manager.
    Below is the code for the integration test I am having problems with and I simplified the code as much as possible to rule out code within the integration test
    causing the problem. I also eliminated all other tests from running.
    [TestMethod]
    public void LaunchOutlook()
    Process.Start(new ProcessStartInfo(@"C:\Program Files (x86)\Microsoft Office\Office14\Outlook.exe"));
    Thread.Sleep(120000);
    I can change how long Outlook is blocked by changing the Thread.Sleep timeout. While the test is running, I can restart Outlook and Outlook is still blocked.
    After the test ends while Outlook is still running, connectivity to Exchange is restored. This happens for Outlook 2010 and Outlook 2013. If I run the integration test within a console app, Outlook connectivity is not blocked. If I run the test code manually
    through MSTest.exe, Outlook connectivity is not blocked.  The only way it’s blocked is if the integration test is executed by the Microsoft Test Agent which is the required approach for integration testing.
    More details on the problem
    Outlook is running on a machine that is part of a Hyper-V Lab with network isolation enabled. There are other machines within the same lab that have Outlook
    instances pointed against the same Exchange server. Executing the test on one machine causes Outlook connectivity issues with other machines within the same lab where the Outlook instances are pointed at the same Exchange server.
    I have small Hyper-V lab with network isolation enabled which is very similar to the lab mentioned above. The major difference is that it only has one machine
    with Outlook installed. This Outlook is able to connect to Exchange while executing the test above through Microsoft Test Manager. It is very clear that this is an environmental issue since it works in one lab and not the other. Both labs have the same Exchange
    server installed, and the same Microsoft Test Agent installed on all machines within the lab.
    I have ruled out the Outlook version as being the issue since the larger lab contains the same Outlook version as the Outlook version in the smaller lab.
    During test run
    Notice that Outlook is in the disconnected state.
    After test run.
    Notice that Outlook is not connected to Exchange.
    Environment Information
    Outlook 2010 Version: (14.0.7113.5000) SP2 (14.0.1740.5002) 64-bit or 32-bit Outlook 2013 Version: (15.0.4667.1000) MSO (15.0.4675.1002) 64-bit or 32-bit Windows
    7 Version: 6.1 (Build 7601: Service Pack 1)
    Exchange 2013 Version: 15.0 ‎(Build 847.32)‎ Windows Server 2008 R2 Version: 6.1 (Build 7601: Service Pack 1) Microsoft Test Manager 2013 Version: 12.0.31101.0
    TFS 2013 Update 4 Version: 12.0.31101.0 Microsoft Test Agent Version: 12.0.31101.0 Update 4
    Troubleshooting Steps
    I launched procmon and looked for failed TCP and UDP operations for indication of network failures and found none.
    I turned on enable troubleshooting logging in Outlook and nothing within the logs looks obvious.
    Pinging the Exchange server while the test is running still works.
    I ran the integration test through the command line using MSTest.exe and outlook connectivity is not blocked.
    Requesting Help
    Can you please help me troubleshoot this problem? I see two approaches to identifying the problem.
    Looking for differences between the two environments
    Obtaining logs or other information that would expose the core problem.
    I am open to suggestions or ideas especially if you have a different approach to solving the problem. Feel free to ask for other information related to the problem
    like logs, PowerShell commands, and registry values.
    If you are short on time, can you at least post some suggestions or ideas related to resolving this problem?
    Thanks, Keith

    After installing fiddler I figured out what the problem was. The Microsoft Test Agent was activating a proxy server which was blocking connectivity to exchange. The proxy server was activated due to having the ASP.Net Client Proxy for IntelliTrace and Test
    Impact turned on. 
    Below is a link to the article with the exact same problem.
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/ecc0b342-8e4d-436c-90c2-5f11bce1e9d8/proxy-server-settings-being-set-automatically-which-is-causing-me-not-to-be-able-to-run-manual-test?forum=vsmantest

  • Server and mailbox name check popup when opening Outlook connecting to Exchange 2010

    Everytime our users open Outlook 2007 or 2010
    this box pops up asking to verify the Microsoft Exchange server name and mailbox name. The user's information is automatically filled in and clicking ok makes the box go away but it will eventually pop up again or when outlook is closed and re-opened. 
    When "cached mode" is disabled the problem goes away (but "cached mode" is necessary for our users).
    The problem began when we deleted an old Exchange 2003 server (we are now using only Exchange Server 2010). 
    Outlook user's profile has been recreated : does not fix.  Users having that problem with Outlook 2010 dot not experience it with the OWA interface.
    How to fix that problem ?
    sti_cartem

    Hello,
    The issue seems related to the oab.
    I suggest you use EXRCA to test outlook connectivity.
    https://www.testexchangeconnectivity.com/ 
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange msstd: setting in outlook connection for Outlook Anywhere

    I currently have the Exchange Provider for EXPR set to $null, however I still seem to get msstd:mail.mydomain.com set in my Outlook connection string setting on all machines. Where is this setting coming from? We do push the Outlook Anywhere settings
    via GPO and have the ProxyServer string defined set to mail.mydomain.com. The flags are set to ensure SSL is defined on the connection.
    We are in the process of moving from Exchange 2007 to Echange 2013. Will it be a problem moving from a UCC cert with a friendly name of mail.mydomain.com to a wild card SSL cert on the 2013 servers with *.mydomain.com set, if the
    "connect to proxy servers that have this principal name in their certificate is selected? I'm concerned that msstd:mail.mydomain.com  does not match msstd:*.mydomain.com?
    Thanks in advance

    Hi,
    We can run the following command to set with Ed’s suggestion:
    Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.mydomain.com
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 SP1 - Unable to test Mapi-over-HTTP Outlook Connectivity

    I've configured MAPI over HTTP in my testing environment. It is working fine. But i'm unable to test this configuration using the Powershell Test-OutlookConnectivity CMDlet.
    Outlook is working fine and is using MAPI over HTTP, so i'm pretty sure there are no configuration problems. But the CMD-let gives me the following output:
    [PS] C:\Windows\system32>Test-OutlookConnectivity -RunFromServerId <myserver> -ProbeIdentity OutlookMapiHttpSelfTestProbe
    WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the probe result for
    invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id 241.
    Failed to find the probe result for invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id
    241.
        + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], InvalidOperationException
        + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.Tasks.TestOutlookConnecti
       vity
        + PSComputerName        : <fqdn of my serer>
    Does anyone have a sollution for this?

    Hello @all,
    I got the same issue. The configuration is functional (Outlook connects over http). But the test-cmdlet raises this error. Is there any solution?
    Greetings from Germany

  • OutlookProvider EXCH/EXPR questions for 2007/2013 CoExistence, Outlook connectivity issue

    Hi Everyone-
    Can anyone give me advice on how to configure my Outlook providers for my environment?
    Single 2007 Server in coexistence with separate CAS/MBX 2013 Sp1.
    It currently looks like this:
    I changed the EXPR CertPrincipleName after coexistence due to a cert pop-up that was occurring in Outlook (2010) while connected to a 2007 mailbox.  
    All connectivity and mail flow is working fine, EXCEPT, connecting Outlook to a 2013 mailbox.  It finds the user/mb but fails at login.
    Thank you for your time!

    Hi Andrew
    There is nothing much complicated to think if we use Exchange Server Deployment assistant as it an perfect guide.
    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-EgBEAgAAQAAAAQECAQAAAAg%7e
    To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure Outlook Anywhere on all of the Exchange 2007 servers in your organization. 
    Users with mailboxes still on 2007 will be connecting to CAS 2013 and then will be proxied to CAS 2007
    Exchange 2013 will coexist easily with 2007 mailboxes by using ActiveSync.  As soon as the DNS entry for 2007 CAS points to the 2013 Client Access Server, 2007 mailboxes that use ActiveSync will be able to sync through the 2013 Client Access server without
    any configuration changes.  This is assuming that if the 2007 CAS Servers are using a default configuration such as SSL (443) with basic authentication. Integrated authentication by default should remain enabled on the Proxy folder that is located beneath
    the Microsoft-Server-ActiveSync Folder.
    During coexistence the 2013 OAB will be the default OAB.Run below command to check
    get-mailboxdatabase | fl identity,*offline*
    Run below command to change Activesync virtual directory
    Get- ActiveSyncVirtualDirectory –Server “Exchange 2013 ServerName” | Set-ActiveSyncVirtualDirectory -InternalUrl "https://abc.com/Microsoft-Server-ActiveSync" –ExternalUrl "https://abc.com/Microsoft-Server-ActiveSync"
    Run below command to change the autodiscover url
    Get-ClientAccessServer –Identity “2013 Server name” | Set-ClientAccessServer –AutodiscoverServiceInternalUri “https://abc.com/autodiscover/autodiscover.xml”
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

  • Outlook Connection

    Hi,
    MS Outlook 2010 was working fine on my Windows Server 2012 with Exchange Server 2013 installed on a virtual machine up until a couple of weeks ago.  Each time I launch Outlook, I get the error "The connection to Microsoft Exchange is unavailable. 
    Outlook must be online or connected to complete this action."  I have the option of clicking "OK" and if I do, I get the Microsoft Exchange dialog box which shows boxes: 1) the "Microsoft Exchange
    Sever" with the following text inside of it "[email protected]" and 2) the "Mailbox" with the following text inside of the box "=SMTP:[email protected]" 
    I tried many things that are suggested online to fix the issue but to no avail.  Any step-by-step to fix the issue would be greatly appreciated.
    Thanks,

    Were any changes made recently in your environment either to Group Policy or the Exchange Server?  Also do you have a load balancer in place?  Can you try going directly to an Exchange Server?
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • E71: annoying confirm connection question before s...

    hello
    how can I disable the confirm question before a synchronization?
    I'm synchronizing over a bluetooth connection. The user guide tells me to click on authorize but I can't find the opportunity to choose this option. Is this done on the E71 or in the Nokia PC Suite application?
    thanks for any hints

    hello,
    do you have any idea how to sync my e71 offline with outlook emails/inbox. there's no checkbox for emails on the synchronisation set-up screen (only contacts, tasks, calendar). I've been doing this for years with my Palm Treo. I can't believe it's not a function on this high-end Nokia?
    thanks
    james

  • Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

    Hi,
    After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
    same. Outlook was working fine before the upgrade.
    Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
    Already applied the transport fix.
    Thanks in advance!

    Hi,
    According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
    To narrow down the issue, I’d like to recommend the following troubleshooting:
    1. Check if the issue happens on all Outlook users
    2. Check the Outlook Anywhere connectivity by using ExRCA:
    https://testconnectivity.microsoft.com/
    Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
    If you have any question , please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Database connection question...

    i am using Java 1.5.0_06 and to connect to MySQL database i use Connector/J and the following code:
    try {
    Class.forName("com.mysql.jdbc.Driver");
    } catch(java.lang.ClassNotFoundException e) {
    System.err.print("Main: ClassNotFoundException: ");
    System.err.println(e.getMessage());
    return;
    try {
    con = DriverManager.getConnection(dburl);
    ps = con.prepareStatement(
    I was told i should be using a DataSource to do connection pooling and i have read over the info and downloaded jdbc2_0-stdext.jar and i am using MySQL and windows XP pro.
    the code looks like this
    Context ctx = new InitialContext();
    DataSource ds = (DataSource)ctx.lookup("jdbc/InventoryDB");
    Connection con = ds.getConnection("myUserName", "myPassword");
    then i just use con as i have already in my code.
    Can someone please point me in the right direction to get this working.
    I read this:
    A systems administrator or someone working in that capacity deploys a DataSource object. Deployment, which involves setting the DataSource object's properties and then registering it with a JNDI naming service, is generally done with a tool. As part of the registration process, the systems administrator will associate the DataSource object with a logical name. This name can be almost anything, usually being a name that describes the data source and that is easy to remember. In the example that follows, the logical name for the data source is InventoryDB . By convention, logical names for DataSource objects are in the subcontext jdbc , so the full logical name in this example is jdbc/InventoryDB .
    i have goggled but can't seem to find out exactly what i need to do next.
    I can't find the "tool" and have to be honest i am lost lol.
    can the The JDBC 2.0 Optional Package work with Java 1.5.0_06?

    i am using Java 1.5.0_06 and to connect to MySQL database i use Connector/J and the following code: i updated it to use manual connection pooling like so:
    final String dburl = "jdbc:mysql://localhost/......";
    Connection con = null;
    try {
    Class.forName("com.mysql.jdbc.Driver");
    } catch(java.lang.ClassNotFoundException e) {
    System.err.print("Main: ClassNotFoundException: ");
    System.err.println(e.getMessage());
    return;
    try {
    DataSource dataSource = setupDataSource(dburl);
    con = dataSource.getConnection();
    con.close();
    public static DataSource setupDataSource(String connectURI) {
    ObjectPool connectionPool = new GenericObjectPool(null);
    ConnectionFactory connectionFactory = new DriverManagerConnectionFactory(connectURI,null);
    PoolableConnectionFactory poolableConnectionFactory = new PoolableConnectionFactory(connectionFactory,connectionPool,null,null,false,true);
    PoolingDataSource dataSource = new PoolingDataSource(connectionPool);
    return dataSource;
    so i compiled and ran it and it worked no problem but my question is that this is a server that does some db work upon starting and then waits for clients like so:
    while (listening)
         new PSMultiServerThread(serverSocket.accept()).start();
    so once i am in PSMultiServerThread what exactly do i need to do?
    i know i don't need to do this again:
    Class.forName("com.mysql.jdbc.Driver");
    but do i need to do this again:
    DataSource dataSource = setupDataSource(dburl);
    i geuss i have to to declare the variable lol.
    and do i include this code in the PSMultiServerThread
    public static DataSource setupDataSource(String connectURI) {
    ObjectPool connectionPool = new GenericObjectPool(null);
    ConnectionFactory connectionFactory = new DriverManagerConnectionFactory(connectURI,null);
    PoolableConnectionFactory poolableConnectionFactory = new PoolableConnectionFactory(connectionFactory,connectionPool,null,null,false,true);
    PoolingDataSource dataSource = new PoolingDataSource(connectionPool);
    return dataSource;
    --------------------------------------------------------------------------------------

  • 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

  • Multiple DB connection question.

    I have a MDB that currently processes a message and updates a Oracle DB say Database A. Now we want that MDB to check some flags on a different Oracle database instance, say Database B before it updates the Database A.
    Basically, the during the processing of a message the MDB has to access Database A, Database B and Database A again in that order. My question is whatever I am trying to do is reccommended? Since I need connection to Database A again after I do some woek with Database B, can I still keep that connection around or do I have to close that right away?
    I am using wls 8.1.
    Any suggestions?
    Thanks
    JB

    <p>The short answer is that you can keep both connections around at the same time, without any issues. Just be careful with any cleanup where you close connections, and make sure that both get dealt with regardless of any exceptions that might occur.</p>
    <p>But depending on the number of MDBs in your configured pool, it might be a more efficient use of database connections to create a smaller pool of stateless session beans to hold those database connections and expose utility methods for the queries (which could use prepared statements)</p>
    Kevin Powe<br>
    Senior Consultant
    Message was edited by:
    kevinpowe

Maybe you are looking for