Unity Connection 9.1.2 - MS Exchange 2013 support for Single Mailbox?

Hello,
we are currently running a unity connection system in version 9.1.2TT1.11900 together with single mailbox enabled with our Exchange server in version 2007.
We are now planning to upgrade the exchange server to version 2013. From my understanding Exchange 2013 is supported with CUCN 9.1.2 (see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/design/guide/9xcucdgx/9xcucdg020.html).
When i go to the configuration screens I cannot choose Exchange 2013 ... Is there a special way to configure this or is 2013 not supported with Unity connection 9.1.2 ?
any hints ?
Michael

Exchange 2013 is supported.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcucumgx/9xcucumg020.html#17832
If you choose to allow Unity Connection to search for Exchange servers, then you need to select from the following two options:
– Exchange 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2007, Exchange 2010, and Exchange 2013.
– Exchange 2003, 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2003, Exchange 2007, and Exchange 2010. When the Exchange organization includes Exchange 2003 servers, Unity Connection always communicates directly with the Exchange back-end servers, it never communicates with Exchange front-end servers.
The drop down does not state 2013 but it will work fine for 2013..

Similar Messages

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

How to configure Exchange 2013 OWA with Single Sign On

Hi All ,
How to configure Exchange 2013 OWA with Single Sign On ?
Thanks .

Hi,
From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
Exchange 2013 OWA Single Sign on with Exchange 2010
https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
If that is not your case, please feel free to tell me.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 Certificates for Hybrid Deployment Clarification

I have an Exchange 2013 servers (CAS and Mailbox on separate server) which I wanted to setup for Hybrid deployment. I already have a certificate acquired from 3rd party with 3 names (mail, autodiscover and owa). the certificate was installed in the
CAS server. As per the hybrid deployment documentation I need also to install a certificate in the mailbox server, questions:
1. Can I use the same certificate for installation in the mailbox server?
2. Can I also use the same certificate in the Hybrid Configuration wizard for the "certificate to use with securing the hybrid mail transport"?
3. Do I need to include the primary smtp domain (xxxxx.com) in the certificate since current configuration points to the mail.xxx.com as the certificate common name?

Hi,
Here are my answers you can refer to:
1. It depends.
The certificate used for hybrid secure mail transport must be installed on all on-premises Exchange 2013 Mailbox and Client Access servers.
If you're configuring a hybrid deployment in an organization that has Exchange servers deployed in multiple Active Directory forests, you must use a separate third-party CA certificate for each Active Directory forest.
2. Yes. But we recommend that you use a dedicated third-party certificate for any optional AD FS server, another certificate for the Exchange services for your hybrid deployment, and if needed, another certificate on your Exchange servers for other needed
services or features.
3. Yes. Here are the minimum suggested FQDNs that should be included on certificates: domain.com, autodiscover.domain.com, edge.domain.com
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/hh563848(v=exchg.150).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Is exchange 2013 support thunderbird mail

Is exchange 2013 support thunderbird mail?
Akhilraj

Yes. add imap account for email.
Add the following addon (or the latest version of the same add-on) for calendar
http://www.1st-setup.nl/extensions/exchangecalendar-3.2.0-Beta77.xpi

Cisco support for Single Inbox Feature in Exchange 2003 for Unity Connection 8.5

Hi There,
Does Cisco support a Unity Connection 8.5 solution/design with the Single Inbox Feature (for Unified Messaging) configured with Exchange 2003, or does it support the Single Inbox feature on Exchange 2010 only?
Thanks

Thanks Anthony - I just found an updated doco that confirms that.

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Exchange 2013 DNS for internal and external domain

Hi All,
I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
We have an Active Directory domain myinternaldomain.net, and we have a public domain
mypublicdomain.com and we have setup email policy to have
mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
hardware LB is out of scope due to budget constrains.
We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
Thanks

Hi Sccmnb,
You can easily achieve this using split DNS.
Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
Reverse proxy server IP.
Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
SN= mail.mypublicdomain.com
SAN= autodiscover.mypublicdomain.com
You don't need to have the active directory domain name present in the certificate.
Additional to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
Some additional Info:
*Internal vs. External Namespaces
Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
*Managing Certificates in Exchange Server 2013 (Part 2)
*Nice step by step article
Designing a simple namespace for Exchange 2013
Regards,
Satyajit
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.

Exchange 2013 DAG with single site and 2 multi-role servers with error "MapiExceptionIllegalCrossServerConnection"

Hi,
I've got a lab with a domain controller and an Hyper-v with on it two multi-role exchange 2013 CU7 servers on W2K12 R2 OS, configured in DAG semplified (but the problem is the same also if I use the classical DAG configuration), a witness server, and a L7
load balancer for the exchange servers.
When I made the test to disable the OWA application pool where I've got the active mailbox database of the user, the balancer in correct manner redirect the session to the other exchange multi-role server, but the client in his OWA session is no more
able to send new mail with the error "Error your request can't be completed rigt now. Please try again later."
The only strange log that I see on the server in the MAPI client access directory where there is the following error message:
2015-01-21T08:00:45.132Z,956,1,/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt,,Microsoft.Exchange.RpcClientAccess.Monitoring.dll,15.0.0.0,Cached,,,,MapiHttp,Client=Microsoft.Exchange.RpcClientAccess.Monitoring,R:4ab7b6c8-54ee-4be3-aa9d-f8c856c4c47c:2,C:MAPIAAAAAOC4+7OCoZOjkqeKuoumlKSEtYO5ibyGs4bc/879z/vD9sX1zP28AwAAAAAAAA==|S:0-mGmHRQ==,OwnerLogon,0x6BB
(rpc::Exception),00:00:00.0310000,"Logon: Owner, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt in database last mounted on Exch2.lab.net",RpcEndPoint: [ServerTooBusyException]
Client is being backed off -> [ClientBackoffException] Mailbox was moved to a different mailbox server. A client needs to retry. -> [IllegalCrossServerConnectionException] Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt.
-> [MapiExceptionIllegalCrossServerConnection] Monitoring mailbox [] with application ID [Client=MSExchangeRPC] is not allowed to make cross-server calls from [Exch1.lab.net] to [Exch2.lab.net] [diag::AAAOAAAA/wAAAAAAAAAAAgAAAAA=],,,[email protected],
The CAS try to access the mailbox on the other server, but without success.
Someone have idea how to solve?
Thanks

Hi Hinte, sorry for the answer delay.
I've run the command you suggest to check the HealthMailbox status, but seems that all are fine:
[PS] C:\Windows\system32>get-Mailbox -Monitoring | ft name, servername
Name ServerName
HealthMailbox7021deb6ae104dadbf52feedfa7fa68b exch1
HealthMailboxb83c9040b32e4d1197f7f54f6709bb7f exch1
HealthMailboxb1c32037890b43fbb2af2efe7c36ba00 exch1
HealthMailbox8d174269b494458daf9ade5099e22845 exch1
HealthMailboxaa7d10f02d2d4cc588243b291ead3e3a exch1
HealthMailboxeb32c30a019f42968a7cbc49a6ac3e65 exch1
HealthMailboxc6ff1d36ba154c5db5411b44718edcbd exch1
HealthMailbox75dc7caa7e8c4a3b812a01b607536d48 exch1
HealthMailbox16c86e512f454e7890b80c180ce19c00 exch1
HealthMailboxc6e447f7dba24d9b913f1dfcabe9f927 exch1
HealthMailbox40fa5a3f2abc4accae6286cd98abc90a exch1
HealthMailbox2712b9544bad4e7b8b671be2cda8cfde exch2
HealthMailboxe2559124da20499386bf8103dcb21e9b exch2
HealthMailbox3264c6078dad45d4a78c56a3afe81df1 exch1
HealthMailboxacacc51eb8bc4717b295ddf0adccf77e exch2
HealthMailbox64c4dd8cddac4c4e8bb7314010e797b1 exch1
HealthMailbox4a92bfa14fdd47fbb27c19513f6d2beb exch2
HealthMailbox465d2a69de93430e84b4d699a88cb0c3 exch1
HealthMailbox97b578e57cd44204820fffa416b25633 exch2
HealthMailboxb411059771db4647bb775c665ec29440 exch1
HealthMailboxf981dde6f4134f839bf41eb0000434e4 exch2
HealthMailboxc33801c7c3b1474f8aa6065249bb4fca exch1
HealthMailbox2282128ed8d14937998212edd15adf20 exch2
HealthMailboxe3d12b756cf545239b38be4607904ae1 exch2
[PS] C:\Windows\system32>
Regarding the test sugested to diable instead the OWA App Pool only the OWA virtual directory, I've not found on IIS the possibility to stop the access to this virtual directory.
Also on exchnage Administration page there is no the possibility to switch off this virtual directory only (or I don't found where is this setting).
Regards

Outlook 2013 - Exchange 2013 - Prompts for username and password when EWS basic authentication is enabled

So we have an Exchange 2013 environment, and a CRM solution that requires basic authentication to EWS internally. Problem is, after a reboot of our Exchange server, all of our Outlook clients begin prompting for username and password (which nothing
works) which also starts locking users AD accounts out due to failed login attempts (somehow). If I disabled basic authentication on EWS, Outlook authenticates as normal using NTLM and there are no issues. Once Outlook has authenticated, I can
turn back on basic authentication, and Outlook will be fine until the next time the Exchange server is rebooted.
Any ideas?

Hi,
According to your description, I understand that Outlook client prompted for username and password when Exchange server restart and basic authentication is enabled for EWS.
If I misunderstand your concern, please do not hesitate to let me know.
It’s normal. This caused by the difference between basic authentication and NTML authentication:
Basic, with any version of Outlook prior to 2010, results in a pop up dialog asking for creds. Outlook 2010 makes the 'save this password' actually work, so in an Outlook 2010 or later world, Basic can mean no need to authenticate every time you open/reconnect,
but in all earlier versions, you will have to enter creds every time.
NTLM, when used by a client that is domain joined and logged in with cached creds, results in the client simply sending the cached in creds to the server, resulting in what looks like a pretty seamless single sign on experience. However, if you want to do pre-authentication
at something like TMG, and not let the traffic go all the way to CAS, you need to configure TMG for this.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Need help regarding the location of Exchange 2013 Logs for parsing

Hi, I am trying to create reports based on the logs that are created on my exchange server. I am using
exchange 2013. My problem is that I cannot handle every log, and instead want specific types of logs.
I need help finding the specific locations of the following types of logs (If they even exist), so that I can parse them and use them effectively:
Audit Logs (Mailbox logons, Mailbox permission changes, Mailbox property changes,
Exchange store changes)
Mail Report Logs (Mailbox size and growth, Mailbox storage growth, Enabled users, Expired and Soon-to-Expire Mailboxes)
Exchange Traffic Reports (Details on size and amount of messages sent and recieved, Internet traffic [to and from], Traffic between exchange users)
I understand this might sound like a huge undertaking, but any help that can be provided would be appreciated.
Again, I need information on the locations of these types of logs on the exchange server, so that I can parse them. Collecting them all and searching through them is not practical for my available resources.
Thanks,
Matt

Audit Logs (Mailbox logons, Mailbox permission
changes, Mailbox property changes, Exchange
store changes) ---- these are two type of logs, 1. mailbox audit logs and that is stored in each mailbox under dumpster
http://technet.microsoft.com/en-us/library/ff461930(v=exchg.150).aspx however you need to
enable
it for individual mailboxes... 2. admin audit log, this is stored into a system mailbox dumpster.... http://technet.microsoft.com/en-us/library/dd335052(v=exchg.141).aspx
Mail Report Logs (Mailbox size and growth, Mailbox
storage growth, Enabled users, Expired and Soon-to-Expire Mailboxes) ---- there isn't any specific log for this, you would need to create some time of script to collect this every day for you and store it somewhere... This is a good start... http://www.stevieg.org/2011/06/exchange-environment-report/
Exchange Traffic Reports (Details on size and
amount of messages sent and recieved, Internet traffic [to and from], Traffic between exchange users) ----- This you can get from message tracking log... http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx

We have a Exchange 2013 server and the Mailbox Database folder is filling up with .log files.

We are migrating from Exchange 2010 to Exchange 2013. We have installed the Exchange 2013 but it only has a couple of mailboxes on this server, all the mailboxes are still on the Exchange 2010 server.
I have run a Windows Backup of the Exchange 2013 but I am still seeing a ton a log files in the mailbox folder.
Also the database file is only about 1.1 GB but the backup is now 40 GB.
Is there something that can be done to truncate these logs and make the backup smaller?

Hi ,
1.Does the full backup completed successfully ?
2.what about the status for the below mentioned command ? Does the mailbox database headers updated with the latest time and date ?
Get-MailboxDatabase -Status | ft name,*full* -au
3.Just check the application event logs for the event id
2046 and that should state that the log truncation for the mailbox databases has been initiated or not.
4.Before initiating the backup just make the exchange writer is not on error.
vssadmin list writers
In case if it on error state ,please restart the Microsoft exchange replication service and check the exchange writers status again by using the above mentioned command.
Thanks & Regards S.Nithyanandham

CSCum80707 - Request to add Exchange 2013 support to TMSXE

Not being able to support commonly used, current rev platforms doesn't put Cisco in a favorable light.
There are more than a few folks in the forums asking and there are no replies from Cisco. Any time frame on a solution?
Thanks!

Hi,
As what Amit mentioned above, all DAG members should have the same operation system.
Please add a Mailbox server which is Exchange 2013 SP1 on the Windows Sever 2012 R2 to the existing DAG.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Outlook Clients for Exchange 2013 Prompt for Password

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

Hi,
Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
In addition, I recommend you refer to the following article:
Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
Thanks.
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality,
safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Niko Cheng
TechNet Community Support

Exchange 2013 OWA server accessing mailboxes on Exchange 2007

Hi All-
I just completed the installation of Exchange 2013, co-existing with Exchange 2007. I have 2013 CU1 and 2007 SP3 RU10. The issue I have is that I cannot access mailboxes existing in the 2007 mailbox servers through my 2013 OWA server. Is
there some advanced configuration that I need to do, on either 2007 or 2013? The documentation I have read seems to indicated that I should be able to use OWA 2013 to access 2007 mailbox.
TIA,
Chris

Just the HTTP 500 error through the website. I found this in the HTTPProxy logs:
2013-04-30T16:17:12.093Z,100f0d73-0d2c-4bee-aa7d-54ada2c4e050,15,0,620,16,,Owa,/owa,,FBA,True,Domain\username,,Sid~xxxxxx,Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0),10.1.200.21,servername,500,,ServerNotFound,GET,,,,,WindowsIdentity,,,,0,,,,2,0,,0,,0,,0,0,0,0,,-1,0,0,3,,,,2,,,OnBeginRequest=1;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
Unable to find proper HTTP service. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: Unable to find proper HTTP service.    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetBestBackEndServiceForVersion[ServiceType](TopologyWithSites
topology ClientAccessType clientAccessType Predicate`1 versionNumberCondition)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)
at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox BackEndServer
mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1 operationToTrack Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon
beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass2b.<OnCalculateTargetBackEndCompleted>b__2a()    --- End of inner exception stack trace ---;

Unity Connection 9.1.2 - MS Exchange 2013 support for Single Mailbox?

Similar Messages

Maybe you are looking for