ActiveSync 500 error and Exchange 2007/2013 coexistence

Hello,
We have Exchange 2007, and we've deployed Exchange 2013 and coexistence appears to be working. We have done a small pilot migration of 11 users, and I have 2 of those users that are not able to get iPhone/ActiveSync working. OWA and Outlook access
work without a problem. https://testconnectivity.microsoft.com/ is telling me "The test of the FolderSync command failed." and "Exchange
ActiveSync returned an HTTP 500 response (Internal Server Error)"
The error I'm receiving on the mailbox server event log is:
An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case,
Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization.
URL=
--- Exception start ---
Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
Exception message: A null value was received for the NTSD security descriptor of container CN=ExchangeActiveSyncDevices,CN=LASTNAME\, FIRSTNAME.,OU=XXX,OU=People,DC=DOMAIN,DC=local.
Most articles I've found with this issue say to confirm that "Inherit parent permissions" is check on the AD object, but that is already checked?
The funny thing is that most of our pilot users don't have this issue. It is only for some of them.
Any help is appreciated.

An update here, I was able to get the 2 pilot user's iPhone/ActiveSync access working by adding the following permissions by hand:
Add Exchange Servers, in Apply onto select
msExchActiveSyncDevices objects (note it's plural) and selecting
Full Control.
Once I did this, my problems went away.
So the big question is why aren't these permissions in place already? Isn't this something that the adprep/domain prep should have taken care of?
Thanks!

Similar Messages

Outlook client requirements and Exchange 2010/2013 coexistence

Good morning!
A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
Thanks in advance!

Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

HTTP 500 error when opening a legacy shared mailbox in OWA 2013 (Exchange 2007/2013 coexistence environment)

Hi,
Our Exchange 2013/2007 coexistence environment is set up and all is working apart from this:
Mailbox A has full permissions to Mailbox B. Mailbox A is migrated to Exchange 2013, but Mailbox B remains on Exchange 2007. If I login to Outlook Web App 2013 as Mailbox A and then "Open another mailbox..." and select Mailbox B, a new window opens
up saying "HTTP 500 Internal Server Error". The URL it is trying is :
https://webmail.ourdomain.com/owa/[email protected]/?offline=disabled
( I can open Mailbox A in Outlook 2010 and do "Open Other users's folder.." and Mailbox B opens up just fine. )
Our legacy CAS server's External and Internal URLs are set to :
https://legacy.ourdomain.com/owa
and the Exchange 2013 CAS server's External and Internal URLs are set to :
https://webmail.ourdomain.com/owa
We have FBA enabled on both the E2K7 and E2K13 OWA
In the IIS logs:
2015-03-02 16:36:50 <E2K13_IP> POST /owa/service.svc action=SubscribeToNotification&UA=0&ID=-25&AC=1&CorrelationID=c2899211-568d-4da4-a163-351a8621c9fd_142531419466924;&cafeReqId=7ffae082-a96f-42fd-85f8-bf23775ed5de; 443 ourdomain.com\MailboxA
<LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
https://webmail.ourdomain.com/owa/#path=/mail 200 0 0 109
2015-03-02 16:36:50 <E2K13_IP> GET /owa/ offline=disabled&CorrelationID=<empty>;&cafeReqId=7c8e137f-cdb7-4449-9cb8-f36f94539244; 443 ourdomain.com\MailboxA <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
- 500 0 0 265
In the OWA HTTP Proxy logs:
2015-03-02T16:36:50.096Z,7c8e137f-cdb7-4449-9cb8-f36f94539244,15,0,913,7,,Owa,webmail.ourdomain.com,/owa/,,FBA,True,ourdomain.com\MailboxA,ourdomain.com,[email protected],Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0),<LoadBalancer_IP>,<Exchange2013ServerName>,500,,ServerNotFound,GET,,,,,ExplicitLogon-SMTP-Header,,,,0,,,,40,9,,0,7;,7,,0,7,,0,46.8643,0,,,,,,,,,1,10,0,,10,,50,50,?offline=disabled,,BeginRequest=2015-03-02T16:36:50.049Z;CorrelationID=<empty>;ProxyState-Run=None;ServerLocatorRefresh=beebf732-0f99-47a0-9f36-d266573f1510;RefreshingCacheEntry=CacheEntry(BackEndServer
<Exchange2007ServerName>.ourdomain.com~1912832083|ResourceForest |LastRefreshTime 2015-03-02T16:01:29.3265514Z|IsSourceCachedData False);ProxyState-Complete=CalculateBackEnd;EndRequest=2015-03-02T16:36:50.096Z;I32:ADS.C[<DC_Name>]=1;F:ADS.AL[<DC_Name>]=6.6401;I32:ATE.C[<DC_Name>.ourdomain.com]=1;F:ATE.AL[<DC_Name>.ourdomain.com]=0,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
The server <Exchange2013ServerName>.ourdomain.com was not found in the topology. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: The server <Exchange2013ServerName>.ourdomain.com was not found in the topology.
at Microsoft.Exchange.Data.Storage.ServiceTopology.GetSite(String serverFullyQualifiedDomainName)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetServiceTopologyWithSites(String serverFqdn ServiceTopology
topology)    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__DisplayClass3b.<OnCalculateTargetBackEndCompleted>b__3a()
--- End of inner exception stack trace ---;
Hoping that somebody can help ?
Thanks

Hi Ansev,
Thank you for your question.
By my testing, user who was migrated to Exchange 2013 cannot access mailbox on Exchange 2007 with 500 error, although user account have “Full Access Permission” to mailbox on Exchange 2007.
I suggest we migrate account which has “Full Access Permission” for other user to Exchange 2013.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Lync 2010 and Exchange 2007/2013 Co-existence

Hi,
I do not work with Exchange, and am only familiar with how Lync 2010 actually interacts with the product. If today we are working with Exchange 2007, and in the future there are plans to migrate to Exchange 2013, I am assuming there will be some sort
of co-existence required for a period of time.
What I am wondering is if anyone has encountered (or is aware of) any issues that may arise as a result of having Lync 2010 deployed in an environment with both of the above versions of Exchange in parallel.
Would the differences essentially come down to where the user's mailbox was homed? In other words, would a Lync 2010 user receive the integration features that come with the particular version of Exchange they are homed on? Or would having both
versions of Exchange in one environment potentially impact Lync 2010 in some way?
Thanks so much in advance for any help you can provide, as I have had trouble finding answers so far.

sorry to reopen the thread...
Hi all,
Does anyone know of any update regarding the following link ??
http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/

Problem: Mixed Exchange 2007 / 2013 CAS Servers with wildcard certificates in Europe and non-wildcard Certficate in China

Hi,
we have following problem. We have a mixed multi-domain one-forest AD environment. We also have still a mixed exchange 2007 / 2013 environment. We also have different CAS Servers for 2007 SP3 (RU15) and 2013 (CU8) in europe and one 2007 SP3 (RU15) CAS Server
in China, because of bad connection to Europe. For the Migration to 2013 in Europe we installed a wildcard-certificate *.xyz.com and used the Set-OutlookProvider EXPR -CertPrincipalName msstd:*.xyz.com, so the wildcard certificate is accepted. Everything in
Europe works fine, inside and outside also between exchange 2007 and 2013 (both CAS Server 2013 and 2007 use the same wildcard certificate). But since the change of the Set-OutlookProvider EXPR we are facing problems with our CAS Server in China, because this
server has a different non-wildcard certificate and a different domain name (cas-server.xyz-china.com instead xyz.com). Now we have the problem that this Chinese CAS server the Outlook Anywhere does not work anymore and prompts always for the username. As
I see it is because of the EXPR change. Is it possible to set the the Outlook-Provider EXPR per Cas-Server ? (They also have their own Autodiscover on this front-end server). Because I see that the Outlook-Provider can only be stored forest-wide.
If not the other solution would be to register the chinese cas server in our xyz.com domain and use the same wildcard certificate on this system right ?
Any help would be appreciate….

Yes setting the EXPR value is most likely the cause of your issue. When you set this value you are telling Outlook to only accept connections from connections that have the cert with the subject name you specify here.
Unfortunately, based on my experience I believe this is an organization wide setting and cannot be configured on a CAS by CAS basis (If I'm wrong someone please keep me honest :)).
So the only option would you have is to change all the URLs to be on *.xyz.com domain. There's no need to change the domain the server actually resides on. The other option would be to purchase a UCC Cert with all the names you need and apply
to all your CAS servers and reset the EXPR value.
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

SBS 2008 and Exchange 2007 intermittent Email Issues

Hello
I am having an issue with my SBS 2008 Server and Exchange 2007. After setup, the mail seems to work great for about a week, then the mail just quits working. To get it working again, all I have to do is reboot the server and mail starts working
again. When looking in the event logs, all I come across is transport.exe errors. Any ideas on why it works for 5-10 days, then just quits working? Any help or insight would be much appreciated.
Thanks All

Larry
Here are some of the errors that i am getting:
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\NETWORK SERVICE; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: edgetransport.exe
Client ProcessId: 0
Client ApplicationId: Client=Transport
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\SYSTEM; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVERNAME/cn=Microsoft System
Attendant.
Error: -1069
Client Machine: SERVERNAME
Client Process: Microsoft.Exchange.ServiceHost.exe
Client ProcessId: 0
Client ApplicationId: Microsoft System Attendant Service Let
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account WIS\JLange; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: w3wp.exe
Client ProcessId: 0
Client ApplicationId: Client=ActiveSync;UserAgent=Apple-iPhone5C1/1002.329;Action=User=jlange&DeviceId=ApplF18KM7FHFH1C&DeviceType=iPhone&Cmd=Sync
These are a few errors that i get when the mail isn't working. When it stops of the server, the outlook clients show the exchange server disconnected, and active sync will not work either. I can still remote to the server, so i dont think its
an internet connectivity issue. Let me know if you have any other questions. Again, the mail seems to work for about 5-7 days, then i have to reboot the server to get the mail flowing again. Any help or direction would be appreciated.
Thanks for Looking

Deploying Windows Server 2012 and Exchange Server 2013

Hi All,
Our Clinet is planning to implement Exchange Server 2013 as an email solution. There is no Active Directory Domain exists in the environment. So, we have planned to configure a Windows Server 2012 R2 Standard as a Domain Controller and Exchange
Server 2013 Standard would be installed on another Windows Server 2012 R2 Standard.
The setup would be for 250 users. Please guide me about the Cost of OS + Exchnage and CAL for 250 Users.
Warm Regards,
Prosenjit Sen
Thanks & Regards, Prosenjit Sen.

Another option would be to consider signing up for Office 365 instead of setting up the hardware and software for such a small number of users. It will take a long time for the cost of the hardware, maintenance, and support to be less costly than Office
365, if it would ever be less expensive. There is a lot of maintenance required for Exchange, so unless your client already has someone experienced in configuring and maintaining Exchange, there is a lot of expense in bringing someone up to speed to
perform those functions capably.
Just a suggestion. I do not work for Microsoft and I have no financial incentive to propose an Office 365 environment. I just know that if I were running my own business, I would have to be convinced that my business required its own internal
mail system when there are so many fully functional and capable mail systems available via subscription.
. : | : . : | : . tim

Exchange 2013 Transport Rules and Exchange 2007 Decommissioning

Hello,
I recently migrated from Exchange 2010 to Exchange 2013, I do have a few traces of Exchange 2007 in the Active Directory that I would like to completely remove. The Exchange 2007 server failed earlier and wasn't decommissioned properly. I read a few articles
on how to completely remove it from AD, I am still concerned to make the changes in "ADSI Edit".
Here is the error message I receive when creating transport rules in Exchange 2013:
"You are about to create a rule in an organization where Hub Transport servers running Exchange Server 2007
exist. To ensure the rule is applied consistently across all Hub Transport servers in the organization, you must create an equivalent rule from the Exchange Management Console on an Exchange 2007 server."
I also noticed that the version of the rules remain Version: 14.0.0.0 for any new rules that I am creating in Exchange 2013.
I would really appreciate if someone can provide their views and the best practices to remove the traces of Exchange 2007 in AD.

Hi Sathish,
How about the result after using ADSI Edit ?
Best regards,
Niko Cheng
TechNet Community Support

Address list service failed to respond error on Exchange 2007 (after adding first 2013 server)

Hi,
We just installed an Exchange 2013 server within an Exchange 2007 environment.
The Exchange 2013 (CU6) server will be used to setup a hybrid connection with O365, and move mailboxes to O365.
After installing the Exchange 2013 server it isn't possible anymore to create/enable mailboxes on the Exchange 2007 server.
We end up with an error :
Mig1 TestAccount
Failed
Error:
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
Exchange Management Shell command attempted:
Enable-Mailbox -Identity 'domain.be/customer/TEMP/Mig1 TestAccount' -Alias 'mig1' -Database 'Exchange2007\SG01\DB02'
When executed via EMS we receive this error :
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error

Hi Lyncer
This error can be caused if the default Public Folder Database not being pointed to the exchange 2007 database which you are trying to create a new mailbox.
Also it can happen if System Attendant service is not running.
Troubleshooting steps:
1) Restart the System Attendant Service
2) Point the affected database to the default public folder
Follow the below steps to do that
Open EMC
Go to Organization Configuration > Mailbox.
Select the mailbox database that you want to change the default public folder database.
Right click the database and select properties
In <Mailbox Database Name> Properties, click the Client Settings tab.
Next to the Default public folder database box, click Browse.
In Select Public Folder Database, select the public folder database from the list of public folder databases, and then click OK.
Cheers!!!
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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Outlook 2013 and Exchange 2007 not always syncing read status of a message

Out users are experiencing this issue from time to time. Outlook 2013 is using Exchange mailbox as default storage (Exchange 2007 SP3). Sometimes it shows that Inbox has one or few unread messages (Inbox name is bolded and there is a number near it). But
a user can't find any unread messages in the inbox. If he logs to his mailbox via OWA, then he can find those unread messages. But they are marked as read in the Outlook. So it seems Outlook 2013 has issues syncing with Exchange 2007 as we have never experienced
such issues when using Outlook 2007 with the same server.
Any hints on how to make this thing go away, other than instructing users to log via OWA and mark unread messages as read?

Hi,
Switch to Exchange Online Mode, does the issue persist?
It seems to be a sync issue between Outlook and Exchange, make sure the Internet connection is good. Let me know if the issue persist after clicking
Send/Receive All Folders button.
Try to run Scanpst.exe to repair the local data file in case the data file has been corrupted:
http://support.microsoft.com/kb/272227
Regards,
Melon Chen
TechNet Community Support

HTTP 500 ERROR AFTER EXCHANGE 2013 SP1 INSTALL

Help after exchange 2013 sp1 new install unable to get to the ECP or OWA page with HTTP 500 error in IE the install went ok but not sure what can be causing the error any help would be appriciated.
EXCHANGE 2013--SP1 on WIN2K12--R2 Standard
TY
M4326

See the following:
http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
CK

Exchange 2013 and exchange 2007 mixed mode questions

I made my first attempt at migrating from 2007 to 2013 but ran into some problems. My 2013 CAS and MB servers are successfully installed along with their prerequisites (AD entries, external and internal DNS is active or ready to be, FW rules etc..). I'm
at this point here in the Microsoft plan..
http://technet.microsoft.com/en-US/exdeploy2013/PrintChecklist?state=2284-W-CQCkAgIAQACACEEAAQAAAA~~
"Perform the switch over"
My questions are about behavior.
1. When I have everything setup correctly and DNS and the SCP's changed, the Webmail OWA site for all users will be the 2013 login interface, and after logging in will my 2007 users then see the 2007 OWA interface on my old CAS?, or will they access their
2007 MB using the 2013 interface?
2. There is a "backend imap4" service on my 2013 servers. We will still have some 2007 mapi connected MB clients. Do I need these services started to hand off 2007 mapi requests to the 2007 portion of the environment?

Hi,
Yes.
Based on my knowledge, we should do some configurations.
More details in the following articles:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
Please also add the new URLs into certificates.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Search-Mailbox not attaching the infected emails in target folder and deleting the contents in exchange 2010 & 2013 coexistence

Dear All,
I have an issue with deleting circulated spam emails in my environment through search-mailbox
We have Exchange 2010 & 2013 CU5 environment
I followed the search and destroy document for exchange 2010
http://windowsitpro.com/exchange-server-2010/search-destroy-email-content-exchange-2010
Added the user to Discovery Management group
Created a new role group as below
New-RoleGroup "Mailbox Import-Export Management" -Roles "Mailbox Import Export"
Add-RoleGroupMember "Mailbox Import-Export Management" -Member Administrator
I ran the below commands
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "Administrator" -TargetFolder "Filter" -LogOnly -LogLevel Full
The above command gets completed successfully and sends the log report however im unable to see any attachments
Similarly the deletecontent also gets completed successfully and logs result. But it does not delete the infected emails
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "administrator" -TargetFolder "filter" -deletecontent -LogLevel Full
Any idea why it is not fetching the infected emails in zip file and why it is not deleting but it is able to log in the target folder
Any help much appreciated
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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Hi All
I managed to find the solution. Below command helped me in solving the issue
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -LogOnly -TargetMailbox administrator -TargetFolder filter -LogLevel Full
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -TargetMailbox administrator -TargetFolder filter -deletecontent -LogLevel Full
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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Lync2013 EWS URLs for Exchange 2007/2010 Coexistence

Hi
Last weekend we deployed and activated our new Exchange 2010 CAS. The 'old' Exchange 2007 CAS is still there, using the legacy URL method, since mailboxes are mostly still located on 2007 Mailbox servers.
In other words, clients connect to the Exchange web-services on the 2010 CAS, and depending on where their mailbox is located (2007 or 2010 Mailbox-server) they either stay with the 2010 CAS or get re-directed to the 2007 CAS (legacy.company.com)
Internal and External URL's are the same, for both the primary and the legacy URL's. All is well, no issues with Outlook clients or OWA, EWS, Activesync.
Enter Lync 2013.
Since the change this weekend, we're getting Outlook/Exchange Integration errors. Checking the Lync Configuration Information (CTRL-Click system tray icon), I can see the EWS Internal/External URL's being used by the client. These URL's point to the 2010 CAS.
So why the error ?
Does the 2010 CAS re-direct Lync clients to the legacy URL, just like it does with OWA/Outlook clients ?
Does it even have to, to supply EWS data for mailboxes on 2007 servers ?
Can I change the EWS URL's, and have them point to the legacy URL, but only for Lync clients ? (and change it back later)
Already checked a mailbox on Exchange 2010, it's Lync user does not get the integration error. So the problem is definitely related to mailboxes on 2007, that need the old CAS server during coexistence. Also, before the CAS 2007 server worked fine, providing
EWS to Lync clients.
Eventually, the plan is to move the mailboxes from 2007 to 2010, but this error puts pressure on that plan. It will take at least 2 or 3 weeks, during which time clients continue to get the error until they are moved.
I'm kinda stuck here.

Lync uses DNS to find autodiscover to obtain EWS URL.
Which server did the DNS record Autodiscover point to?
You can run the command Get-AutodiscoverVirtualDirectory to get the EWS internal URL and external URL on the server the Autodiscover pointing to.
2010 CAS can’t redirect Lync client to the legacy URL.
Lisa Zheng
TechNet Community Support

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

ActiveSync 500 error and Exchange 2007/2013 coexistence

Similar Messages

Maybe you are looking for