Database encryption supported in Exchange 2013?

hi,
according to this: 
http://technet.microsoft.com/en-us/library/aa998022(v=exchg.80).aspx
MS doesn't support storing Exchange databases on  EFS volumes.
Is the recommendation the same for Exchange 2013?
Is there any support for encrypting databases in an Exchange 2013 environment other than in transit traffic?
Thanks,
rudif

Yes Bitlocker
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Windows BitLocker (volume encryption)
Windows BitLocker is a data protection feature in Windows Server 2008. BitLocker protects against data theft or exposure on computers that are lost or stolen, and it offers more secure data deletion when computers are decommissioned.
Supported: All Exchange database and log files.
Supported: All Exchange database and log files. Windows failover clusters require Windows Server 2008 R2 or Windows Server 2008 R2 SP1 and the following hotfix:
You cannot enable BitLocker on a disk volume in Windows Server 2008 R2 if the computer is a failover cluster node. Exchange volumes with Bitlocker enabled are not supported on Windows
failover clusters running earlier versions of Windows.
For more information about Windows 7 BitLocker encryption, see
BitLocker Drive Encryption in Windows 7: Frequently Asked Questions.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • Is smb 3.0 already supported for exchange 2013

    Hello,
    We are looking to deploy exchange 2013. We have a netapp storage and vmware environment.
    I was wondering if smb 3.0 is already supported for exchange 2013. I read in a blog of 2012 that it wasn't supported at the time. We would like to use it instead of a iscsi lun.

    Hi,
    Based on my knowledge, it is still not supported for Exchange 2013 up to now.
    Here is an article for your reference, please refer to the "Exchange storage requirements" section.
    Exchange 2013 Virtualization
    http://technet.microsoft.com/en-us/library/jj619301.aspx#BKMK_Prereq
    Another related article for your reference.
    Exchange 2013 Storage Configuration Options
    http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Is Windows Azure officially supported for Exchange 2013?

    Though Exchange 2013 can be installed on Windows Azure, however can somebody help me in knowing that if its officially supported with it OR can live environment of Exchange be setup on Windows Azure?

    Hinte is correct.
    You can set up a Exchange 2013 lab in Azure. You may have seen that Henrik Walther has done just that:
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/deploying-exchange-2013-hybrid-lab-environment-windows-azure-part1.html
    But this is just for practice / training.
    Besides lack of support, cost of sufficient resources to run E2K13 correctly would be greater than simply using O365 / Exchange Online.
    Please 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.

  • Support for TLS 1.2 over Exchange 2013 on Server 2012?

    Greetings,
    We're trying to roll out TLS 1.2 in our test environment and can't seem to get Exchange to work with the protocol.
    We've been using this method to enable TLS 1.2 (and disable the other protocols - TLS1.0, SSL2.0, SSL3.0, PCT1.0): http://www.adminhorror.com/2011/10/enable-tls-11-and-tls-12-on-windows_1853.html
    We originally tried using Exchange 2010 on 2008 R2, but then I ran across this article saying that it is not supported: http://support.microsoft.com/kb/2709167/en-us
    We've since tried to set it up with Exchange 2013 on Server 2012. Still no luck. The only time Exchange wants to work is when TLS1.0 is enabled.
    I suspect that TLS1.1 and TLS 1.2 are also not supported on Exchange 2013, or that I'm changing the wrong registry keys, but I wanted to find confirmation. I've searched extensively and can't find any documentation leading me to believe one way or the other
    if it's supported.
    Any help or insight would be greatly appreciated. Thanks!
    --Aric

    hi All,
    Even i have tried enabling TLS 1.2 on Exchange 2013 from registry. i followed the below article.
    http://jackstromberg.com/2013/09/enabling-tls-1-2-on-iis-7-5-for-256-bit-cipher-strength/
    When i check OWA in chrome and check the connection information it says "The connection uses TLS 1.2.
    However when i run the below command to check for TLS 1.2 i get the following O/P.
    Command: java -jar TestSSLServer.jar ns-ex13.gtestexchange.com 443
    O/P:
    Supported versions: SSLv3 TLSv1.0 TLSv1.1
    Deflate compression: no
    Supported cipher suites (ORDER IS NOT SIGNIFICANT):
      SSLv3
         RSA_WITH_RC4_128_MD5
         RSA_WITH_RC4_128_SHA
         RSA_WITH_3DES_EDE_CBC_SHA
      TLSv1.0
         RSA_WITH_RC4_128_MD5
         RSA_WITH_RC4_128_SHA
         RSA_WITH_3DES_EDE_CBC_SHA
         RSA_WITH_AES_128_CBC_SHA
         RSA_WITH_AES_256_CBC_SHA
         TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
         TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
      (TLSv1.1: idem)
    Server certificate(s):
      1979e6bdbd9b8e197d00c45534959eaba82b6f40: CN=ex10.gtestexchange.com, OU=Domain
     Control Validated
    Minimal encryption strength:     strong encryption (96-bit or more)
    Achievable encryption strength:  strong encryption (96-bit or more)
    BEAST status: vulnerable
    CRIME status: protected
    ===================================================
    It doesnt says anything about TLS 1.2.
    Any suggestions from your side?

  • Maximum database size Exchange 2013 Standard

    Hi,
    Does anybody is aware of database size limitation for Exchange 2013 Standard. I remember in older version there was a registry tweak to increase database limits.
    Thank you 
    alfa21

    Hi,
    This is the official answer :
    Supported: Approximately 16 terabytes.
    Best practice:
    2 terabytes or less.
    Provision for 120 percent of calculated maximum database size.
    https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
    Cordialement,
    Mickaël LOPES
    Blog : http://lopes.im 
      

  • SOFS support for Exchange Server 2013

    Hi all,
    I am aware of the following factors:
    1. Exchange only supports block-level storage
    2. Using SoFS as DAG FSW is not supported.
    But may I confirm whether Microsoft supports the scenario below?
    ==============================================
    My client has one set of Windows 2012 R2 Scale-Out File Servers to support their hyper-V farm. Storage is Dell MD3000 with Windows 2012 R2 Storage Space. Is it supported by Microsoft to run Exchange Server 2013 and Exchange Server 2010 in the virtual machines
    which are running on SoFS? Assume IOPS has been properly sized.
    ==============================================
    Regards,
    William
    William Yang

    Hi,
    There is no official documents talked about whether the Windows server 2012
    Scale-Out File Server is supported for Exchange 2013 and Exchange 2010.
    Generally, the supported storage configuration in Exchange 2013 is listed in the article below:
    https://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
    Hope it helps.
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Support for OIM11g

    Guru's,
                    I want to know the OIM11g Support for Exchange 2013 Connector, is any one configured the exchange 2013 with OIM?
    Thanks,
    Caddick.

    Oracle Identity Manager
    You can use one of the following releases of Oracle Identity Manager:
    Oracle Identity Manager 11g Release 1 (11.1.1.5.6) or later
    Oracle Identity Manager 11g Release 2 (11.1.2.0.6) or later
    Target systems
    The target system can be any one or a combination of the following:
    Microsoft Exchange 2007 SP1, SP2, SP3 (64-bit)
    Microsoft Exchange 2010 RTM, SP1, SP2, SP3 (64-bit)
    Microsoft Exchange 2013 RTM (64-bit) For the Exchange 2013 support, Patch 17239236 must be applied on Release 11.1.1.6.0 of the Exchange connector. This Patch can be obtained from My Oracle Support under Patches and Updates.
    Download Exchange-11.1.1.6.0 connector and then Apply patch 17239236 for Exchange 2013

  • Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

    Greetings all, I hope someone can help.
    I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
    Internal mail flow is fine (external email addresses can send to the domain).
    External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
    There are two multi-role Exchange servers that are members of the DAG.
    I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
    No SSL certificates have been purchased or installed yet.
    Exchange URLs have not been changed since default configuration at install.
    OWA and ECP works both internal and external.
    External DNS works with SPF and PTR records correctly configured
    Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
    Send Connectors are the default ones created during install. Receive connector is standard configuration with  - * - 
    When sending email to an external address, I receive a failure notice
    ServerName.test.corp.int gave this error:
    Unable to relay 
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    More Info - 
    ServerName.test.corp.int
    Remote Server returned '550 5.7.1 Unable to relay'
    I have been troubleshooting this for many hours with no progress.
    I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
    I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
    I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
    I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
    I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
    Can someone please assist before I lose my sanity.
    Thanks in advance,
    Terry

    Greetings all, I hope someone can help.
    I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
    Internal mail flow is fine.
    Incoming mail from external senders is also fine. - 
    external email addresses can send to the domain).
    External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
    There are two multi-role Exchange servers that are members of the DAG.
    I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
    No SSL certificates have been purchased or installed yet.
    Exchange URLs have not been changed since default configuration at install.
    OWA and ECP works both internal and external.
    External DNS works with SPF and PTR records correctly configured
    Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
    Receive Connectors are the default ones created during install. Send connector is standard configuration with  - * - 
    When sending email to an external address, I receive a failure notice
    ServerName.test.corp.int gave this error:
    Unable to relay 
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    More Info - 
    ServerName.test.corp.int
    Remote Server returned '550 5.7.1 Unable to relay'
    I have been troubleshooting this for several days with no progress.
    I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
    I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
    I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
    I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
    Even more info - Further troubleshooting -
    I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
    hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/ 
    The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
    I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
    when you domain name is apple.com - But through extensive research I still can't resolve the issue.
    Can someone please assist before I lose my sanity.
    Thanks in advance,
    Terry

  • EXMON "exchange server user monitor" for Exchange 2013?

    Hello,
    it Looks like EXMON is not supported for Exchange 2013. Is this correct or can i use it with Server 2012 R2 and Exchange 2013 (CU6++)  ?
    Is there any alternative to check high log growth rate to see which user is responsable for this?
    Thanks for Feedback.
    best,
    Martin

    Hi Martin,
    Yes, ExMon is not supported for exchange 2013.
    Except the suggestion above, here is an exclusive application for you reference, it could retrieve statistics for all or selected mailboxes in a specified database and server, it may give you some help:
    Exchange Server Mailbox Statistics Tool - v1.6.2
    The tool retrieves mailbox statistics which includes Folder Count, Total Items, Associated Items, Deleted Items, Total Items Size, Deleted Items Size, Oldest Item Date, Newest Item Date, Items Age, Mailbox Age and Quota details. It also includes an additional
    option named "Archive Statistics Planner" which will let you search mailboxes and provide statistics report with specific dates. 
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Installing Exchange 2013 on Windows Server 2012 R2

    Now that SP1 has been released, it is supported to run Exchange 2013 on Windows Server 2012 R2
    But since it is not yet possible to download Exchange 2013 with integrated SP1 (slipstreamed), is the following installation procedure supported:
    - Install Exchange 2013 (without SP1) on Windows Server 2012 R2
    - Install SP1 on top of Exchange 2013
    If this is not supported, can someone tell me when the Exchange 2013 with integrated SP1 (slipstreamed) download will be released?

    yes the SP1 is the full product. if you need step by step instruction to migrate to this new version you can get info here : http://buenoflex.com/install-exchange-2013-sp1/
    Arnaud Buonaccorsi - GSX Groupware Solutions
    http://www.buenoflex.com
    http://www.gsx.com <= The monitoring solution for Exchange and Sharepoint

  • Exchange 2013 / 2010 coexistence with different public domains

    Currently in my organization
    1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
    1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
    1x Exchange 2010 Standard w/SP3 - Mailbox
    In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
    miles away. We have no IT staff in any of our field locations.
    We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
    domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
    domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
    domain.local - Our internal Active Directory domain.
    We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
    severely underutilized.
    Goals for the Exchange migration
    My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
    final topology is:
    2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
    2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
    1x VM with Exchange 2013 Standard w/SP1 - Client Access
    1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
    I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
    We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
    until Exchange 2013 SP3 is released.
    Deployment Plan
    Install Exchange 2013 on new VMs.
    Create CAS Array object.
    Configure Exchange 2013 to publish under the new namespace.
    Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
    Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
    Unknowns
    My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
    since we'll be using the new domain for each mailbox we move.
    My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

    Hi,
    From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013. 
    About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
    About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
    About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
    Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
    Checklist: Upgrade from Exchange 2010
    Install Exchange 2013 in an Existing Exchange 2010 Organization
    Upgrade from Exchange 2010 to Exchange 2013
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

    Hi,
    we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
    With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
    As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
    there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
    On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
    We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
    Thanks, Paula

    Hi,
    Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
     Is it right?
    You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
     If possible, please switch this Outlook client from cached mode to online mode to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Basic Authentication in Exchange 2013

    Dear All,
    I am facing issue regarding basic authentication in exchange 2013 I run all the command and from Server setting I set the outlook anywhere on Basic Authentication but when I configure outlook client after successfully run the wizard the setting
    of outlook in Exchange proxy setting its show NTLM. I run all the below commands and done with the srver setting but outlook will configured only on NTLM. Externally and Internally both are same through autodiscover.
    Set-OutlookAnywhere -Identity: "servername\rpc (Default Web Site)" -ExternalClientAuthenticationMethod Basic
    Set-OutlookAnywhere -Identity "servername\rpc (Default Web Site)" -SSLOffloading $false
    Set-OutlookAnywhere -Identity "servername\rpc (Default Web Site)" -IISAuthenticationMethods Basic
    Set-OutlookAnywhere -Identity "servername\rpc (Default Web Site)" -IISAuthenticationMethods Basic,NTLM
    I just need to confrim that there is no more Basic Authentication support in Exchange 2013 or is there any work around ?
    Danish Khan DK

    Hi Danish,
    Basic authentication is supported on Exchange 2013, you can use the following cmdlet to set it.
    Set-OutlookAnywhere -Identity "servername\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Basic
    What's more, it is recommended to set the IISAuthenticationMethods to: {Basic, Ntlm, Negotiate}.
    For your reference:
    Set-OutlookAnywhere
    https://technet.microsoft.com/en-us/library/bb123545(v=exchg.150).aspx
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 homeMTA attribute missing

    Hi all,
    I noticed if I create a user mailbox on exchange 2013 and check the users properties in ADSI Edit, the homeMTA attribute is missing? Is this normal?
    If a user mailbox is create on exchange 2007 I can see the homeMTA attribute. But as soon as I migrate the mailbox over to exchange 2013 it disappears?
    Why is there no homeMTA attribute for mailboxes on exchange 2013?
    Environment:
    Windows Server 2008 SP2 Domain Controller
    Exchange 2007 + SP3
    Exchange 2013 + CU3
    Thank you

    Hi,
    We are in the process of configuration BES 5 with 2013 and got stuck during the installation. We are new to Exchange environment as we are now migrating from Lotus Domino. We have followed the same documents mentioned by Steve but could not succeed with
    the installation as it is stuck at MAPI setting page. We also could not complete few steps mentioned in the pre-requisites and was told by our service provider that we are getting stuck because of this missing pre-requisites. We were not able
    to complete the Task1 and Task 3 as mentioned in
    KB33413. In Task 1 we are not able to set the value for IISAuthenticationMethods       {Basic, Ntlm, Negotiate}Ntlm .
    Have applied the commands as advised at the end of the Task 1, restarted the services and server but no luck. It is showing blank in our case. In Task3 we were having the
    HomeMTA attribute as not set and was supposed to copy the attributes from the other two fields. Would like to clarify how we could copy these two values to one field, is it one after another with a comma or space?
    Also, we were told by the Service provider that they have limited support for Exchange 2013 SP1 version. Can somebody please verify if it works with the same? Kindly help.

  • GSSAPI with IMAP on Exchange 2013 SP1

    We are setting up Exchange 2013 SP1 in our Exchange 2010 test environment to verify our upcoming migration. I have found out that for some reason I can't get the IMAP service in Exchange 2013 to work with Kerberos (GSSAPI) authentication with Thunderbird
    as a client. It does work fine in Exchange 2010 SP3 though.
    Exchange 2010 SP3 response in Thunderbird:
    * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
    Exchange 2013 SP1 response in Thunderbird:
     * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
    AUTH=GSSAPI is missing and therefore I can't blame Thunderbird from complaining about this. If I compare the output from Get-ImapSettings I can't find anything that would indicate why I shouldn't work. EnableGSSAPIAndNTLMAuth is $true on both server
    and LoginType is SecureLogin.
    On
    http://technet.microsoft.com/en-us/library/jj619283(v=exchg.150).aspx I found out that NTLM is not supported on Exchange 2013 for POP3 and IMAP4 but Kerberos (GSSAPI) and Plain Text Authentication with SSL still is.
    Has anyone got IMAP to work with Kerberos authentication on Exchange 2013 SP1?

    Hello,
    According to your description, we are unable to see the AUTH=GSSAPI in Exchange 2013.
    My environment is Exchange 2013 CU1. I get the same result as yours. Looks Like Exchange 2013 IMAP does not support GSSAPI as authentication mechanism.
    Cara Chen
    TechNet Community Support

Maybe you are looking for