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

Similar Messages

Outlook 2013 users getting "The Microsoft Exchange administrator has made a change that.....

Hi,
We are on Exchange 2013 SP1 and we are randomly seeing all Outlook 2013 clients getting "the Microsoft Exchange administrator has made a change..." forcing them to restart Outlook. Outlook 2010 clients are not affected so seems to be related to
Outlook anywhere.
Cant see anything in the event log but seeing some 500 errors in the IIS log.
any ideas on where to look?
Kristian

Hi,
I finally get to resolve my issue with this :
http://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
"Please check in ADSIEdit > Configuration >CN=Services > CN=Microsoft Exchange
> CN=your ORG name > CN=Administrative Groups > CN=Exchange Administrative Group > CN=Databases, please check the attribute “MSEXCHHomePublicMDB”
of your databases, if they are pointing towards the deleted Objects, please delete the entries."
Restart the server, restart computers and it should be OK. If not, you might try to create a public folder (http://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy)

Guest user cann't access report when using xdo_user_name

when i added xdo_user_name into the sql, the report could no be accessed by Guest user via URL.
Firstly, create a very simple report.
i have set Guest user could access Guest folder and create a report under this folder.
1.data model:
select 'a' XDO_USER_NAME,
'b' XDO_USER_ROLES
FROM DUAL
2.generate a RTF template.
3.view this report
4.get link of this report
5.log out and access this report via URL by Guest
6. access this report successfully.
Secondly, update the data model:
select :xdo_user_name XDO_USER_NAME,
:xdo_user_roles XDO_USER_ROLES
FROM DUAL
access this report via URL by Guest user again, get error message:
The report cannot be rendered because of an error, please contact the administrator.

These bind variables are bounded to the user logged in, and these are not available for guest, thats why you get these errors.
log an support ticket for this, Oracle support/team will help you on this, if they think its nice functionality.

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

Exchange 2010 - Exchange 2013 permanent coexsistence to avoid migration of Public Folders

Hi Guys,
I was hoping to get some opinions/ advices regarding the case explained below.
The company I work for has a medium-sized Exchange 2010 infrastructure that consists of several geographically dispersed 2-node DAGs and corresponding CASArrays. It hosts about 1000 mailboxes in total and large public folder database that is replicated on
every mailbox server in the environment. All users are using Outlook 2010/2013.
There is a business drive to perform migration to Exchange 2013. However, migration of the Public Folders is not feasible because of the lack of multimaster replication, the complicated migration process and several other limitations in Ex2013 PFs.
To work around this issue while still performing the migration I am considering the following scenario:
Deploy Exchange 2013 servers in the organization
Migrate all mailboxes to Exchange 2013 servers
Don't ever start migration of Public Folders (leave one Exchange 2010 mailbox server in every location for hosting the Public Folder database)
Keep the coexistence permanently (with mailboxes on 2013 and public folders on 2010)
What do you think of this setup? Do you see any issues with such long-term coexistence?
Thanks.

Hi,
You can leave the public folders on Exchange 2010 if you can’t migrate them to Exchange 2013. Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can’t access public folders on Exchange 2013.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2010 to Exchange 2013 Public Folder Problem

Dear Experts,
I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
1) Parent Domain in Site A (abc.com)
2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
Anyone help will be highly appreciated.
Thanks & Regards,
ZB

so you want users to access the PF in site B.
Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
run this for Exchanger 2013 DA
Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
Where Technology Meets Talent

MT Exchange 2013 and Public Folder Limits

So having some real trouble trying to digest this data from a multi-tenant perspective.
Total public folders in hierarchy
10,000
Although you can create more than 10,000 public folders, it isn’t supported. Create
a Public Folder
Sub-folders under the parent folder
10,000
Although you can create more than 10,000 sub-folders under a parent folder, it isn’t supported.FolderHierarchyChildrenCountReceiveQuota parameter on the Set-Mailbox cmdlet.
So if my hierarchy consists of root folders 0-9,A-Z. Then below those top levels I place tenant domain level folders. Then below that I actually have folders for tenant data. Which of the above category applies? Sub-folders under
the parent folder is somewhat misleading? Does that mean in my above scenario I would only have 36 "parent" folders then would be able to have a total of 10k subfolders under those parents?
Or does it effectively mean 10k folders, that is all. One parent folder and 9,999 sub-folders? Or some combination of the two?
I had very high expectations for the redesigned public folders with incorporation into the DAG, but this solution seems MUCH less scalable and flexible then the legacy design. Additionally the recommendation of 2k concurrent users per PF mailbox, with
a max number of PF mailboxes at 100 effectively sets an org limit of 200k total mailboxes.
I can't help but feel this is just another nail in the coffin of non O365 Exchange resellers.

Hi,
Based on my research, the public folder size can be up to 100GB in the hosted Exchange 2013 environment:
http://www.wisnet.com/blog/hosted-exchange-2013-is-available-now/
As long as the total number is beyond the limit, we can at most have 100 public folder mailboxes ,10k public folders, 10k subfolders under one public folder and 200 concurrent users for one public folder mailboxes.
For more information about the public folders in Exchange 2013, you can refer to the following articles:
Public folders
http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
FAQ: Public Folders
http://technet.microsoft.com/en-us/library/jj552408.aspx
Public folders in the new Office
http://blogs.technet.com/b/exchange/archive/2012/11/08/public-folders-in-the-new-office.aspx
Exchange 2013 Modern Public Folders
http://windowsitpro.com/blog/exchange-2013-modern-public-folders
Public Folder Hierarchy and PF Mailboxes for Hosted setup
http://social.technet.microsoft.com/Forums/exchange/en-US/e9062abe-f484-462b-bc5e-ebdcb0862760/public-folder-hierarchy-and-pf-mailboxes-for-hosted-setup
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.
If you have any question about Exchange server, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Public Folder in exchange server 2013

We are using an legacy application developed in Classic ASP. In this application we are rendering the message items in the public folder on the exchange server 2003.
Now we are going to migrate our exchange server 2003 to exchange server 2013.
Do exchange server 2013 have public folder? Is this migration have impact on the public folders usage.
Please let me know for any clarifications.

There will be no co-existence support for Exchange Server 2003. In your scenario, you will have to migrate twice, once from Exchange 2003 to Exchange 2007 or 2010, then again to Exchange 2013 or another option you have to proceed that by using any third-party
migration tool to accomplish this task in one go. When you preparing to migrate mailbox, you can have a look at
exchange server deployment assistant to see the current recommended steps for your configuration. A good resource for swing migration direct from exchange 2003 to 2013 can be explored at
here.
In the same way, You cannot migrate public folders directly from Exchange 2003. You will have to move all public folder databases and replicas to Exchange 2007 SP3 RU10 or later. No public folder replicas can remain on Exchange 2003.
I would like to refer on couple of links mentioned below. It will help you better to clarify the scenario further :
Understanding the public folder architecture
Public folder migration

Exchange Online users logging into OWA On Premises.

Greetings!
We are implementing hybrid Exchange Online with Exchange 2013, and we face the following situation:
When an Exchange Online user tries to access through OWA on-premises, a page appears with a link to the Exchange Online OWA.
Is it supposed to be this way?
Why the redirection is not automatic?
Seems so obvious that the redirect should be automatic that if it is to be this way (the user having to click the link), there must be some technical justification. Can anyone refer me some article about it? For to convince the top brass of the company here
that it has to be like that!
Thanks in advance !!!
Fabio Martins MCDST/MCSA Brasil!!!

Hi
As per the information and details provided by you, to solve the problem of Exchange online users logging into OWA on Premises, please follow these steps: -
The user will be able to use the
OWA URL points to the on-premises Exchange 2013 server. On the redirection page, you can choose to
save the new URL to his browser favorites and click on the URL.
When clicking on the URL, the user will be taken through the authentication process. For OWA, that means that you can try to access his mailbox in Exchange Online &
Exchange online will redirect the user to “login.microsogtonline.com”, where
you can enter UPN.
Once the UPN is entered and you switches to the password field, Office 365 will detect that the UPN domain is federation with an Office 365 tenant. This result in a redirect
to the on-premises federation endpoint (in this case sts.clouduser.dk) and depending on whether the user is domain joined and domain-connected or uses an external client, you will get
single sign-on (SSO) or be required to enter your UPN and password.
Because of the organizational relationship that was set up between Exchange Online and Exchange on-premises during the Exchange hybrid configuration lookups when booking
meetings, mail tips, etc. also work as expected from Exchange Online to Exchange on-premises and vice versa.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

After Public Folder Migration 2010 to 2013

Last week I used technet page to migrate our exchange 2010 public folders over to exchange 2013. I'm still new to exchange management so I'm trying to understand what to do next.
The migration move showed 100% complete and successful and now show up as a mailbox in the 2013 admin center. I thought to myself Great! I did it. So I attempted to decommission my 2010 exchange server.
I attempted to remove my public folder database in the 2010 EMC and it tells me the database still contains folder replicas.
I found a couple options as possible fixes, either to remove it in ADSI edit or delete the files in the folder. I just want to make sure doing so won't effect the 2013 public folders.
Or should I do this a different way? Thanks in advance.

I had the server shut down for about 10 minutes and tested and was able to access PF's normally. Would you suggest longer?
Also I did attempt to remove the public folders via that article already and got the following error. I'm connected as an Admin with the correct rights.
[PS] C:\program files\microsoft\exchange server\v14\scripts>.\MoveAllReplicas.ps1 -Server mx2010 -NewServer mx2013
No existing 'PublicFolder' matches the following Identity: '\'. Make sure that you specified the correct'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.
+ CategoryInfo
: NotSpecified: (0:Int32) [Get-PublicFolder], MapiTransientException
+ FullyQualifiedErrorId : 2FF5D899,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
+ PSComputerName        : mx2010.company.local
No existing 'PublicFolder' matches the following Identity: '\NON_IPM_SUBTREE'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.
+ CategoryInfo
: NotSpecified: (0:Int32) [Get-PublicFolder], MapiTransientException
+ FullyQualifiedErrorId : 304E9272,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
+ PSComputerName        : mx2010.company.local

Public Folder Migration - 2010 to 2013 - Downtime incurred at "Lockdown" Stage

Looking for some information from those who have completed a successful Public Folder migration from 2010 to 2013.
1. Size of 2010 Public Folder Store
2. Downtime incurred upon the "Lock down 2010 Public Folder" stage once all mailboxes moved to 2013 and ready to cut-over to 2013

I would like to refer you at this well explained technet library and check whether you follow all the required prerequisites for a successful public folder migration from Exchange 2010 to 2013 : http://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx
Also, please check this another article resource : http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html
Apart from above resources, you may also consider at this comprehensive application(http://www.exchangemigrationtool.com/) that can be a better alternative approach while migrating public folder database
between two exchange server.

Exchange Public Folder Migration - Public Folder Mailbox "LockedforMigration"

I've recently started a SBS2008 (Exchange 2007 - Latest SP3) migration to Exchange 2013CU6.
Most of the Migration has gone to plan however I've been following a few guides on the Public Folder migration and have seen more errors and time spent than what it is worth.
I've now decided to abandon the Public folder migration as there wasn't really anything of importance in the old 2007 Public Folders, and just setup a new Public Folder Mailbox and PF Folder on the 2013 environment, however... as I started with the migration
the 2013 Server is stuck in "LockedforMigration" mode and will not allow me to create a new Public Folder.
Is there anyway to forcibly 'unstuck/release' the "LockedforMigration = True value.
Or can I just start decommissioning the old 2007 Box and that will force the unlocking of Migration flag
By no means is this the only guide, but here is what I've been following if that will help
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Thanks Ian

Hi Ian,
According to the error message above, please make sure you are running the command as Administrator, and make sure the Administrator is a member of Organization Management Group and Server Management Group. Then try to run command to release "LockedforMigration
$True".
Since Public Folders on Exchange server 2013 can't be coexisted with legacy Public Folders within an Org, you should delete Public Folder Database from legacy Exchange server 2007 first, then create a new Public Folder Mailbox on Exchange server 2013.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Public Folder Exchange 2010

Good Day ,
I did migration from exchange 2003 to exchange 2010 for mailbox but not yet for public folder , in my situation i have just 3 folders in public folder , my idea is I creat new public folder in exchange 2010 and I copy in the path this three folders
and iI gave autorisation it's possible ?
Regards
e

You can take a look into below mentioned few good resources that clarifies your concern in depth. It will assist you to move public folders between two exchange server : http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
http://exchangeservermigration.blogspot.in/2013/06/how-to-perform-migration-in-exchange.html
http://www.petenetlive.com/KB/Article/0000426.htm

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.

Syncronizing a Exchange 2007 Public folder to SP 2010 Caledar

Greetings
I am running Share Point 2010 Enterprise and Exchange 2007. We have a large amount of Public Folders that we need to migrate to Share Point. I was wondering if there is a way to do this without having to buy any extra software. I have researched
some and all that I have read is that you can use a the Outlook sync button to link the calendar to Outlook which I am fine with. All our workstations are using Outlook 2010. But I have read that if you copy the appointments from one calendar to
this SP linked calendar all appointments will sync from that point on, which is incorrect. Moreover, when I select list view to copy the appointments over and then open appoints in calendar view none of the appointments show I am assuming
that this is a permissions issue. So I guess I am asking two questions here. 1) what is the best way to migrate Exchange Public Folders into SharePoint? And why are the appointments that I copy over from the public folder are not showing
up when I change the view back to calendar view in Outlook. I really appreciate you time for reading my post. Thanks in advance.

Hi,
According to your post, my understanding is that you wanted to migrate the exchange public folders to SharePoint 2010 calendar.
If you hava a small number public folders, you can migrate the public folders manully.
Here is an article which about migrate public folders to SharePoint manully(although it’s about SharePoint 2007, I think it’s helpful for you).
http://www.messageops.com/manually-migrating-public-folder-content-to-sharepoint-online
If you have a large number of Public Folders it would be recommended that you take a look at 3rd Party Migration Tools,
such as the Quest or AvePoint products:
http://www.quest.com/public-folder-migrator-for-sharepoint/
http://www.avepoint.com/exchange-public-folder-to-sharepoint-migration-docave/
More reference:
http://www.msexchange.org/articles-tutorials/exchange-server-2010/planning-architecture/using-sharepoint-provide-public-folder-functionality.html
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Exchange 2013 user cann't access exchange 2013 public folder

Similar Messages

Maybe you are looking for