Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3

Dears,
i am working in Upgrading Exchange 2007 to Exchange 2013 CU7,, I came to know with CU7 we have new way for coexistence with legacy Public Folder
https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx
i did the steps exactly as it is in the article, but now users in Exchange 2013 always prompt for username /password when opening outlook and i found they still trying to connect to Exchange 2007 PF Server using HTTPS and failed..
BTW, Outlook anywhere is disabled in EX2007 and as per this article Q/A , it is no more needed
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
the issue now, still users getting prompted and cannot connect to PF in EX2007,,
your help is appreciated
thanks
Mufleh

I ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
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

Similar Messages

Exchange 2013 users cannot open public folders on exchange 2010

Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
client version is outlook 2013
outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
outlook any where external host name field is blank (we need to keep outlook any where disable for external)
outlook anywhere internal authentication is set to NTLM and Client require SSL to false
I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest

Hello,
Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
If the user has no permission to see the public folder, please check the permission.
=============================================================
1. Open ADSIEDIT.
2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
Administrative Group ->CN=Databases ->CN= PF Database.
3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 User cannot view public folders

Good morning,
User was able to view public folders, then lost connection to public folders. User cannot view public folders in OWA.
Verified proper permissions. No changes have been made to the user account in AD, exchange.

Did you do a fresh install of Exchange, meaning there was no version of Exchange installed previously? If not, have you moved Public Folders over to Exchange 2013 yet? If the answer to this question is no, then you will not be able to view Public
Folders in OWA until they are migrated over Exchange 2013.

Exchange 2013 user cannot mail 2010 user

Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.

Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin

Exchange 2013 - ECP shows wrong public folder permissions

Hi everybody,
I just migrated from Exchange 2007 to 2013 SP1 CU7 and we have an issue with the public folder permissions in ECP. ECP doest not show the correct permissions, here an example:
Get-PublicFolder "\Folder" | Get-PublicFolderClientPermission | ft
FolderName User AccessRights
Folder Default {Author}
Folder Anonymous {None}
Folder Administrator {Owner}
Thank you very much and best regards,
Sebastian

Hi,
Based on your description, the public folder permissions you get using command aren't the same with that you view from EAC.
Please check if you can change the wrong permissions to right in EAC.
If you have multiple public folder mailbox, please move affected public folders to another public folder mailbox and move back to check result.
And if you have multiple DCs, please make sure there is no replication issue between DCs or you can force DC replication and then to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange groupware connector cannot read public folder

Hi,
we're installing the Groupware Connector for Exchange (2003) on a Win2003 SP1 server. The installation is simple, but when starting the service, the following error occurs:
[26/Apr/2006:11:33:52 +0200] WARNING - - - - - "[WRN:1010] Invalid default target folder for contacts: [email protected] does not specify public folder
. Please verify 'replica.contacts.default-target' option in config.xml." Source: Common\GroupWare.cpp:199
I tried installing and starting the connector on both the exchange server and a seperate server, but in both a cases the message appears.
The public folder exists (called "contacts"), has an email address: [email protected] and we can sent emails to it and they arrive in the contacts folder. As far as I know we executed all the steps in the installation guide (permissions etc) but for some reason the connector cannot see the public folder.
Any ideas?
I've read the two notes: 908577 and 908571
Much obliged
Marcel Rabe

Hi,
Once again very sorry for such a delayed reponse ... i don't know how did i missed your response ... anyway
You can find version of Connector 2.1.053 after you install it on a system and right click on the connectorsvc.exe and go to the version tab, find the version of the GWC.
What ever versions you have mentioned i.e., 2.1.036 and 2.1.037 are versions of Install package of GWC (which is a common for both exchange gwc and lotus gwc ).
If you still have some problems with it then revert back to me via e-mail so that i won't miss your response.
regards,
Gokul
[email protected]

User cannot access shared folder on a single PC.

This one has got me thoroughly confused.
Over the weekend I'm moved a shared folder from an old file server to a new one. Move went well. Added share and security permissions. Changed user scripts. Check ever users system to insure they had the new share drive and wouldn't notice a thing. All worked well.
Except one user.
She cannot access the share at all. She can access other shares on the new file server. She can access the needed share on other systems. Other users who have access can access the share on her system.
Does anyone have anything I can do beside wiping her profile/system?
This topic first appeared in the Spiceworks Community

Today, 11:29 PM
I think it has something to do with WPA2/AES key renewals.

Access Public Folder in Exchange

Using CF8, I currently can access mailboxes and folders in my
exchange information store except for folders in the public store.
Does anyone know how to access information in the public folders
using CF8's exchange tags.
Trevor

Has anyone figured this out?
This would be an incredibly useful feature. Perhaps there is a way to do this by interacting directly with the Java?

Exchange 2013 user cann't access exchange 2013 public folder

Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
problem, thanks.
belows are information about outlook anywhere in our exchange.
exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
Identity                         : SHCAS01\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHCAS02\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : WXCAS01\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL04\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL05\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL06\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : DRPMAIL05\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : DRPMAIL06\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}

Hi,
I have found an article said that we need to set the external host name the same. See more details in the following link:
http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
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. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
The following configuration is set on each Exchange 2007 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Sent By
Silver

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

User cannot access redirected Documents folder, but can connect to share in Windows Explorer and access folder on server

I am in the final stages of a cross-forest migration. Users have Windows 7 workstations with redirected folders on a Windows Server 2012 box running in the old forest. User accounts were not migrated. The accounts in use have always
been in the "new" forest. One of our challenges was the large volume of data in redirected folders. I made sure users in the target forest had continued to have access to their redirected folders in the old forest and robocopied
the entire users share, copying the permissions with the files. By doing incremental robocopies, we can get a final copy done now in about six hours. The plan was simple: copy the files, do an incremental copy every night, on the night of the cutover
change the folder redirection policy Documents path from
\\oldserver\users\%USERNAME% to
\\newserver\users\%USERNAME%. The policy is configured to NOT copy user files from the existing folder to the new redirected folder. Everything was going well until I tested the policy change. After the folder redirection policy is updated
and applied, the user cannot access the private Documents folder. For example, user Chester Tester logs on as ctester. I open Windows Explorer and click the Documents shortcut. I see one subfolder, which is subfolder of Public Documents.
So I can look at Public Documents but when I click on the Documents folder (Under the Documents library link) I get an access denied error. Now for the kicker, if I open another Windows Explorer window and edit the address bar to
\\newserver\users\ctester, I can navigate the Documents folder tree and see my thousands of documents. What the ....?
I'm hoping this is something really simple to fix!
TIA

HI Vivian,
Thank you for your reply. Yes, the path in Group Policy Folder Redirection Root Path was updated to
\\NEWSERVER\users. I had planned to point this to the distributed file system, so the first used was actually
\\domain\dfs\users. To simplify things I have backed off to copying to just a normal share
\\newserver\users.
We are using BASIC folder redirection and we create a folder for each user under the root path.
We did not want the policy to move content, as we were seeing users requiring 15-20 minute logon times (or higher) after the policy is changed.
Grant the User exclusive right to Documents - Disabled
Move the contents of Documents to the new location - Disabled
Related folder settings
Video - Follow Documents
Music - Follow Documents
Pictures - Follow Documents
Now when I change the folder redirection from old server to new server I now have TWO My Documents folders in the user's redirection folder on the server. The redirected Documents points to an empty folder set. The copied folders with all user
data are there, but folder redirection refuses to recognize the original folder.
I am looking at the full view of the folder, nothing hidden, so I'm wondering how a folder can have two subfolders with the exact same name. For now, I just want the redirection to move from the old server to the new server properly. I deleted
the new My Documents folder, rebooted the user's workstation and tried again. The behavior repeats itself, i.e., a new My Documents folder is always created when the redirection policy is changed from the old server to the new server. The environment
has about 1500 users with approximately 1.3TB of data in the redirected Documents folders. OUCH!

Cannot Access EAC/ECP on exchange server 2013 after installation

Hi,
I can not Cannot Access EAC/ECP on exchange server 2013 after installation . Error 404.4 code 0x80070002
Help!
Thanks,

Hi Florin
Did you try accessing EAC by using below link
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
Please access EAC via Internal URL: https://<CASServerName>/ecp
Finally ensure that you have logged in as administrator as well as this might be problem as well
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

Windows Users Accessing Public Folder

I would like to know the way to allow Windows users to access only the Public folder on my mac.
When I try to access folders from Windows I go to My Network Places and click on the icon representing my Mac then I'm prompted for a password; as I have only my account on the Mac I have to put my user ID and password, thus allowing access to all my folders - not only Public.
I know that Mac users can access Public, but how to allow the Windows camp to do that?
17' PowerBook G4 Mac OS X (10.4.4)

SharePoints is a great tool to allow access to peripheral drives, volumes, and the like. But you shouldn't have to use it to access the Public folder via a PC as you can a Mac. That is a very big question on the boards that has yet to be answered.
Apple says it happens. If so, what's the secret to accessing the Public folder via a PC.
Any information will be greatly appreciated.

Exchange 2013 Mailbox Using 2010 Public Folders

Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while. Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company. Our environment consists of
8 Ex2010 servers and now the one Ex2013. I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine. How is that server discovered, and can we specify which one it uses? I understand the way 2013
public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

Cannot change public folder owner in adsiedit to the server_name$ where PF are stored

Hi,
I have migrated PF from Exch 2003 to the Exch 2010 SP2 RU6.
Some of PFs still have the old Exchange 2003 servername as the owner in Security-Advanced-Owner of ADSIEdit.
However when I try to change it to the Exch2010_server_name$ (the one where Public Folders are mounted - I cannot (without any reason). But I can change it to one of the CAS servers, strange isn't it?
I have already tried this using domain admin account and Exchange admin account (both are assigned to Public Folder Management).
Can you help me to set the correct server name (as it is set for new public folders), please?
BR Michal Ziemba

Hi Michal,
Based on my knowledge, we don't need to change the owner of public folder manually when we migrate public folder.
The issue may be related to AD replication. You can run Dcdiag on your domain controllers and make sure you're not having replication problems.
Here is a thread for your reference.
Public Folder Issues - Exchange 2010 after migration from 2003
http://social.technet.microsoft.com/Forums/exchange/en-US/fe0909c1-ee2e-448b-ad89-e8f4ff92b4a9/public-folder-issues-exchange-2010-after-migration-from-2003-insuffaccessrights?forum=exchange2010
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3

Similar Messages

Maybe you are looking for