Hi Wendy.

I'm still very much stuck.  I took a look at Peter's suggestion, but it didn't work for me.  I've been on NTLM since first installing Exchange 2013, so Sren's information was already in place.

I've had to slow down our implementation of 2013 due to other projects, and since I'm not yet seeing a solid resolution I am delaying our implementation.  I hope that this is something that can be fixed outside of CU2 as I'd really rather not wait another few months to migrate all of our users.  That's of course assuming that CU2 contains a fix for this coexistence problem and is delayed like CU1 was.

Alan

In additional to set NTLM (With set-outlookanywhere or GUI) on Legacy (exchange 2007/2010 client access) servers you need to remove negotiate from rpc virtual directory in IIS.

One day troubleshooting:) Hope it`s will be helpful.

I've succesfully had Outlook 2007 working with migrated mailbox on an E2K13 server and Public Folders on an E2K7 server. 

After all the setting up the single thing that fixed everything was rebooting the entire exchange environment.

I wish I new which services to simply restart but I couldn't find the right combo.  But after bouncing each box in the envirnment stuff started working.

Steps:

Make sure all keys have all proper DNS names.
Set authentication in OutlookAnywhere to NTLM for the 2013 servers.
Disable OutlookAnywhere on 2007 server then renable and set to NTLM if it hasn't already been setup like that.
If it doesn't work then reboot everything.

Thanks for the thoughts, David.  We've had a few full reboots since installing Exchange 2013, but we're still stuck.  I've been at NTLM on all servers since running through all of the published Microsoft documents but no luck.  Something behind the scenes is certainly broken and I'm hoping that it gets addresses in CU2.  We may just cutover in July and then clean up from there.  Everything else seems to be working great, so that's probably the best way to just eliminate EX2007 from the picture.

Alan

Does stuff work through OWA?

Maybe try recreating the Outlook account to see if it's something up with Outlook.

It does not.  I've re-built the Outlook profile both on my main machine and done fresh installs on other machines.  If I natively create a user in Exchange 2013 they have no trouble accessing EX2007 folders.  It's only users who were migrated from EX2007 (every existing employee that we want to move) that can't access the folders.  There are other threads that have emerged that note the same issue: migrated users don't work but native users do.

Same domain?  Meaning do you have subdomains?

Check the SRV records for autodiscover.  I'm betting they are still pointing at the old E2K7 server.  Modify those and if that doesn't make sure there's an record in DNS for autodiscover pointing to the new E2K13 box. 

We're a single-domain company.  All of our Autodiscover records (i.e. autodiscover.contoso.com) do point to the new server, though we don't use the SRV method of locating it.

This doesn't help:

http://support.microsoft.com/kb/2839517

I'm at a point right now where I've migrated public folders and now Outlook clients can't connect to the Public Folders on the E2K13 side.  Ugg.

Those are the kinds of roadblocks that seem to keep showing up in migration scenarios.  Granted, I can't fully blame them since they run EX2013 natively for Office 365, but it's really more like a late-stage beta right now as opposed to "fully supported" by CU1.

I'm hoping to avoid the issue you're having because we use the same name for both internal and external communications.  Or at least, that's what I've configured...

Alan

Yeah I'm doing a lab right now.  I'm at the final stages and the freakin client connections always seem to be the worst part.

First it was compatability between 2K13 MB and 2K7 PF but now I'm all 2K13 and the MB works but PF doesn't and only through the Outlook client.  OWA works fine so I guess I'm stuck waiting for a patch.

I discovered I'd fat fingered my E2K13 OutlookAnywhere settings for the External URL.  Once I fixed that all was resolved.

Hey Mikhail,

i dropt negotiate from legacy cas-servers from the /RPC in iis. like in your screenshot.

now public folders work for the 2013 users, but the legacy users connected trough anywhere getting a password popup and cannot connect to pub folders :/

is there anything more to do?

best wishes

dennis

• Proposed as answer by StephenTJ Wednesday, September 04, 2013 7:34 PM
• Unproposed as answer by StephenTJ Wednesday, September 04, 2013 7:34 PM

We are having the same issue.

Internally It works.  Set the protocol to NTLM on 2013 & 2007 outlook anywhere.

Externally outlook anywhere DOES NOT work properly.  Unable to expand the public folder which still resides on 2007.

I have had this issue on 2 different environments where 2007 & 2013 are in coexistence.  Suggestion by Mikhail did not work.

Please any one... Help!!

Never mind.  I figured it out myself....

test exchange connectivity website pointed me to the right solution which is "rpc over http proxy" component + NTLM.  Unlike exchange 2007/2010 coexistence, the 2007 outlook anywhere also needed to be enabled.

Many of these are mentioned nowhere in Microsoft's exchange 2013/2007 coexistence guide (If you can even call it a guide...)

There are actually multiple issue that can cause this.  What should be set to get PF working with OA enabled on both 2013 and 2007 is BASIC, NTLM on Exch 2007 servers (IIS Authentication) and Basic on External Client Authentication.  On Exch 2013 NTLM for everything.

Now the above only get is working so internal/external users on Exch 2007 or 2013 can access PF on Exch 2007.

Now once the on-prem is working we need to get O365 PF "Remote" to work using the endpoint 2013.  This is the difficulty bit and differs depending on if you have a 2010 or 2013 endpoint.

2010 seems to reliable and has always worked for the deployments I have done.  The issue is with Exch 2013 and this I have never got to work, but am spending all my time on this until I have answer.

I'll try and keep this post updated.

If anyone has an issue with 2010 then let me know.

I've been fighting this same issue for 8 hours straight.  Oddly enough, disabling Outlook Anywhere on the 2007 server made everything start working for me.  On the 2013 side, Outlook Anywhere is set for NTLM, both inside and out.

Hi everyone.

I disappeared from this thread as things tend to get extremely busy at colleges in the summer, and none of the further posts were resolving my issue.  I tried NTLM, no NTLM, basic, no basic, on, off, and everything inbetween.  I could not make it work.

As a recap, my issue was that users who were migrated to EX13 from EX07 could not access public folders nor shared ("Full Access") mailboxes on the EX07 server.  All of my URLs were fine, all of my authentication was fine, and all mail was flowing fine.  Users who were natively created in EX13 did not experience this issue, as alluded to in some earlier posts.

I'm happy to report that, for us at least, EX13 CU2 has completely resolved this issue.  I am able to access public folders again, as well as shared mailboxes, that are stored on the EX07 server.  Hopefully as you are able to deploy CU2 (make sure to get the re-released version!) you will have the same results.  I'm moving more people onto EX13 tonight to prepare for a main migration.

If CU2 happens to be the fix for you, please mark this response as the answer so that we can validate the fix.

Good luck!

Alan

• Edited by CofI-Alan Thursday, August 01, 2013 1:17 AM Grammar fixes.

Hey Mikhail,

i dropt negotiate from legacy cas-servers from the /RPC in iis. like in your screenshot.

now public folders work for the 2013 users, but the legacy users connected trough anywhere getting a password popup and cannot connect to pub folders :/

is there anything more to do?

best wishes

dennis

I had the same behavior when testing client connections from 2013 to 2010 for users on 2010 and for connection to 2013 for users on 2013 (they were connecting to the default public folder database on 2010 and failing).

In my investigation I found that the outlook client was configured to use NTLM for outlook anywhere and Negotiate for logon network security. Removing negotiate from the 2010 servers resulted in the same behavior you described, 2013 working but 2010 not.

My solution was to add negotiate back as a provider on all my /RPC directories (2010 and 2013) but put it 2nd in the list after NTLM. This resolved all my connection issues with all my clients regardless of mailbox location (2010 or 2013). I believe setting the logon network security in Outlook to NTLM would probably have also resolved the issue.

I had the same problem. exchange 2013 cu2v2 and exchange 2007 sp3 ur11.

user has outlook 2007/2010 and his mailbox is on exchange 2013. when browsing the public folders: "Cannot expand the folder... and so on"

sometimes i was able to see a promt for credentials what gave me a clue.

It worked in my case after changing the outlook anywhere configuration especially for exchange 2007:

Get-OutlookAnywhere | Set-OutlookAnywhere -ExternalClientAuthenticationMethod NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalClientAuthenticationMethod NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -IISAuthenticationMethods NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalClientRequireSSL $False

outlook anywhere was already enabled on exchange 2007 as well

then restart iis on both and public folders worked fine

so i can say, yes, outlook connected to exchange 2013 can use legacy public folders on exchange 2007.

whats not working is to access legacy public folders throught Webapp on Exchange 2013. I think this is related to that sentence youve allready posted: 

Exchange 2013 no longer supports public folder databases. Therefore, theres no coexistence with legacy public folders. As a result, Exchange 2013 is unable to read from the hierarchy stored in a public folder database on Exchange 2010 or Exchange 2007 servers.

 

regards

• Proposed as answer by Dean Drolet Sunday, November 24, 2013 3:01 AM

I had the same problem. exchange 2013 cu2v2 and exchange 2007 sp3 ur11.

user has outlook 2007/2010 and his mailbox is on exchange 2013. when browsing the public folders: "Cannot expand the folder... and so on"

sometimes i was able to see a promt for credentials what gave me a clue.

It worked in my case after changing the outlook anywhere configuration especially for exchange 2007:

Get-OutlookAnywhere | Set-OutlookAnywhere -ExternalClientAuthenticationMethod NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalClientAuthenticationMethod NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -IISAuthenticationMethods NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalClientRequireSSL $False

outlook anywhere was already enabled on exchange 2007 as well

then restart iis on both and public folders worked fine

so i can say, yes, outlook connected to exchange 2013 can use legacy public folders on exchange 2007.

whats not working is to access legacy public folders throught Webapp on Exchange 2013. I think this is related to that sentence youve allready posted: 

Exchange 2013 no longer supports public folder databases. Therefore, theres no coexistence with legacy public folders. As a result, Exchange 2013 is unable to read from the hierarchy stored in a public folder database on Exchange 2010 or Exchange 2007 servers.

 

regards

This was a partial fix for me. This seems to have resolved the Outlook always asking for password issue, but it still hasn't resolved my 2013 users' inability to access the public folders that are still on my 2010 server. We currently have two Exchange servers - 1 is 2010 sp3 and 1 is 2013 cu2. Most users are still on 2010. I have migrated myself and my junior admin. When we try to open public folders, we get the already mentioned errors. Any updates at all on this?

*EDIT* - I take this back. It solved nothing for me. What a mess this is.

• Edited by Rich Gallo Friday, November 15, 2013 5:14 PM

@Rich Gallo - Can you start a new post for your issue and I'll try and help.  Put the link in here so I can track.

I had the same problem. exchange 2013 cu2v2 and exchange 2007 sp3 ur11.

user has outlook 2007/2010 and his mailbox is on exchange 2013. when browsing the public folders: "Cannot expand the folder... and so on"

sometimes i was able to see a promt for credentials what gave me a clue.

It worked in my case after changing the outlook anywhere configuration especially for exchange 2007:

Get-OutlookAnywhere | Set-OutlookAnywhere -ExternalClientAuthenticationMethod NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalClientAuthenticationMethod NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -IISAuthenticationMethods NTLM
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalClientRequireSSL $False

outlook anywhere was already enabled on exchange 2007 as well

then restart iis on both and public folders worked fine

so i can say, yes, outlook connected to exchange 2013 can use legacy public folders on exchange 2007.

whats not working is to access legacy public folders throught Webapp on Exchange 2013. I think this is related to that sentence youve allready posted: 

Exchange 2013 no longer supports public folder databases. Therefore, theres no coexistence with legacy public folders. As a result, Exchange 2013 is unable to read from the hierarchy stored in a public folder database on Exchange 2010 or Exchange 2007 servers.

 

regards

This worked perfectly for me!  Thank you very much for the proper answer.  I was doing a 2007 to 2013 migration for a client and this thread was the one that helped to solve all the issues experienced like everyone above.

use Exchange deployment assistant  guild, there is commands need to be executed to change outlook anywhere settings on Exchange 2007 CAS Servers.

$Exchange2013HostName = "mail.contoso.com"
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $True} | ForEach {Set-OutlookAnywhere "$_\RPC (Default Web Site)" -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $Exchange2013HostName -IISAuthenticationMethods NTLM, Basic}
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $Exchange2013HostName -IISAuthenticationMethods NTLM, Basic

http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-FQCEAgAAQACACAEAAQAAAA~~

it's believe this will fix  your public folder issues.

• Proposed as answer by Indunil Sunday, May 11, 2014 8:24 AM

Well Done....its working for me.. Thanks.

Regards,

Shahir

Hi All,

This is an old case, but the issue(s) still loom.....

In my case, the issue was related to an invalid value in the "msExchHomePublicMDB" attribute (in adsiedit) of the Exch 2013 mailbox databases. Per MS Support, they do not know why it happens, but it happens on occasion. One of my three mailbox databases wad 'broken'. The symptom we experienced was that although the Public Folder was visible in the Outlook tree (left pane), it could not be expanded so the PF folders and content was not visible. In Outlook the following error was displayed when access was attempted: "Cannot expand the folder. The attempt to log on to Microsoft has failed." and then, "Cannot display the folder. Microsoft Office Outlook cannot access the specified folder location. Could not open the item try again."

I hope this info helps

1) Using --> ADSIEdit > Configuration >CN=Services > CN=Microsoft Exchange > CN=your ORG name > CN=Administrative Groups > CN=Exchange Administrative Group > CN=Databases
2) Navigate to the legacy Public Folder database, go into properties and copy the value of the "distinguishedName" attibute.
3) Navigate to the Exchange 2013 Mailbox database, go into properties and paste the legacy Public Folder database's value of the "distinguishedName" attribute (that was just copied) and paste it into the value field of "msExchHomePublicMDB" attribute of the Exchange 2013 mailbox database.
4) Update each Exchange 2013 mailbox database accordingly
5) Allow/Force AD replication and test (Note: even after forcing replciation, I needed to wait a solid 15 minutes before the change took effect).
6) If the Outlook connection status is checked all the connections to the Exchange 2013 mailbox will be HTTPS, but the connection to the legacy public folder will be TCP/IP. This is normal because the connection is to a legacy server.

I just want to state, i had the same problems as everyone else we were on Exchange 2013 SP1, we experienced the following:

Exchange 2007 mailboxes kept getting password prompts because of Public Folders, can witness through connection status window) we also had Exchange 2013 mailboxes (new users) who couldn't access PUblic folders on 2007 they would get the same password prompt.

In our legacy environment we had Outlook Anywhere disabled, I had NTLM set on the authentication as stressed so much in this thread but the key was to having the OUtlookAnywhere service setup on Legacy ALSO as NTLM. Once this happened, EVERYTHING started working correctly and no longer received password prompts.

So the saying that Public Folders aren't support is bogus and I really wish Microsoft would UPDATE THERE DOCUMENTATION! as nothings been updated as of today and it took me 7 days to finally get this figured out. THanks Alan for keeping at it and all the users who try to make this community a helpful place. I think MS reps should take note to stop marking stupid comments as answers when they know good and well they are NOT.