Public folders access

hello;
I have a group of users that is unable to access a contact list in the Public folder of outlook However, I do have some users that are able to access the contacts list form the Public folder. The following is a short detail of the problem I having any advice
would be a great help. Again thanks for your help with this matter.
(The client's in the (Education Department) is unable to add the education/contact list to the outlook address book. The department uses the contact list to perform their daily functions. This list should be first in the address book when they are trying
to send e-mails. They use this list to send e-mails to several different locations inside and outside of the company. The function that is used to add the contact list to address book within (Outlook) is not available).

It is hard to guess where is the problem. I would address Outlook forum and if there is Exchange server, then the Exchange forum is a good target.
http://social.technet.microsoft.com/Forums/en-US/home?forum=outlook
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
It seems to be misplaced topic.
HTH
Milos

Similar Messages

Public Folders not accessible as Guest

Having a problem connecting to Public folders as Guest on certain Mavericks iMacs [10.9.2] over the company LAN.
The network has no problems, no IP conflicts. There are other 10.9.2 Macs that can have their Public Folders accessed. There is no discernable difference between the computers, some are older that have been upgraded to Mav, others are new and came with Mav installed.
I've created different user accounts on the problem Macs and the result is the same. Changed the IP addresses, nothing.
I can connect to these Macs with admin user credentials and access the Public Folders that way, but it's kind of contradictory. This for me points away from the network and to the Macs themselves. Any ideas would be helpful.
Regards.

Thanks again Sterling, is there anyone near you who is familiar with Kerberos? Here is some Console details from the computer I am trying to access as guest:
14/04/2014 18:07:47.823 digest-service[320]: digest-request: od failed with 2 proto=ntlmv2
14/04/2014 18:07:47.823 digest-service[320]: digest-request: user=\GUEST
14/04/2014 18:07:47.824 digest-service[320]: digest-request: kdc failed with 36150275 proto=unknown
14/04/2014 18:07:47.824 digest-service[320]: digest-request guest: ok user=DAVE-MORRISSEY\GUEST proto=ntlmv2 flags: NEG_KEYEX, ENC_128, NEG_VERSION, NEG_TARGET_INFO, NEG_NTLM2, NEG_NTLM, NEG_TARGET, NEG_UNICODE
14/04/2014 18:07:54.454 digest-service[320]: digest-request: uid=0
14/04/2014 18:07:54.454 digest-service[320]: digest-request: init request
14/04/2014 18:07:54.456 digest-service[320]: digest-request: init return domain: DAVE-MORRISSEY server: DAVE-MORRISSEY indomain was: <NULL>
14/04/2014 18:08:02.468 kdc[93]: Got a canonicalize request for a LKDC realm from local-ipc
14/04/2014 18:08:02.468 kdc[93]: LKDC referral to the real LKDC realm name
14/04/2014 18:08:02.469 kdc[93]: AS-REQ davemorrissey@LKDC:SHA1.4FD5C7E5DC3FDB1A8E6B55B1AD6DF4B577C2CCE9 from local-ipc for krbtgt/LKDC:SHA1.4FD5C7E5DC3FDB1A8E6B55B1AD6DF4B577C2CCE9@LKDC:SHA1.4FD5C7E5DC3 FDB1A8E6B55B1AD6DF4B577C2CCE9
There are many Apple Discussions dating back to OS Tiger about LKDC and SMB issues, none that I read refer to guest logins, but they are centred around authentication.
When I guest access my own Mac [Mav upgrade] from the above machine [Mav out of the box] it is successful and there are no Console entries.

Cross-forest access to public folders Exchange 2013-2007

Dear.
We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
Thanks for the support.
Regards.
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Hi Stephen,<o:p></o:p>
<o:p> </o:p>
Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client permission
to see if we can access the
public folders.<o:p></o:p>
<o:p> </o:p>
If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
<o:p></o:p>
Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
Link:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
<o:p> </o:p>
So for public folder migration,
the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
<o:p></o:p>
Regards, Eric Zou

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

User Access to Public Folders Disappearing (Outlook 2013)

I have one particular user who is losing access to public folders in Outlook 2013. I have found that going to
File > Account Settings > Account Settings > Email [TAB] > Repair... and then following through that dialog temporarily restores public folder access after restarting Outlook. However, once Outlook is restarted
for 30-60 seconds, the public folders disappear again. This is only happening for this one user. They receive their public folder permissions via group membership. Other group members report no such issue. I had another user with identical permissions
log into the same workstation and they again had no issue.
What could be causing this? This is a particularly bothersome problem since this user happens to be the office scheduler and the calendar they schedule on is public (which, thanks to reduced functionality in Exchange 2013, is no longer accessible in OWA).
Tech specs: Exchange 2013 CU5 accessed from Outlook 2013 running on Windows 8.1 Update. Outlook did not log any events during the time when public folders were dropped, nor are there any network connectivity issues being logged.
Any ideas for resolving this?

Hi,
Please check the connection status for Outlook.
Press the CTRL key and right-click the Outlook icon in the notification area, then select Connection Status.
Please run the command get-mailbox administrator | fl defaul* to check the default public folder mailbox for this affected user.
Do you have mail-enabled public folders? If you have mail-enabled public folders, you can check if this user can view public folders in OWA.
If possible, please re-add the public folder permissions for this user to check result.
Best regards,
Belinda Ma
TechNet Community Support

Can't Access Public Folders Within Outlook, But Can Through Web Access

Hi all,
I have an Exchange 2010 Server (V14.02.0387.000) with clients using Outlook 2007-2013. Until recently all users could access all public folders without issue. However, since moving the location of the public and private mailboxes on the server (to new drives
with more space and defragging etc), a number of users are unable to access the public folders, getting error "Cannot expand the folder. the attempt to log on to Microsoft Exchange has failed". However, when they log in through Outlook Web Access,
they can view the public folders without issue.
I've tried restarting all the Exchange services, as well as multiple reboots of the server.
Many thanks in advance.
Bob

I'm going to start with some general advice. Don't bother running ESEUTIL anymore to reduce database sizes. If you find you need to do that, simply create a new database, move all the mailboxes to it, and then delete the old database.
If you created a new public folder database, did you change the mailbox databases to point to it using Set-MailboxDatabase -PublicFolderDatabase?
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Accessing public folders in the local network

I work with 8 other mac users and we all share files using our Public folders via local network. This is how we typically would access each other's Public folder: open a Finder window, choose Network, then choose the name of the mac that we want to connect to. Then, connect as "Guest". We are all on OS X Tiger.
Recently, one of us upgraded to the OS X Snow Leopard, and we couldn't access her Public folder since the switch. We believe she is on the network, because she has been printing to the network printer and can connect to all of our Public folders. I tried to follow this instruction from Apple Support page to set up file-sharing on her iMac (with Snow Leopard):
http://docs.info.apple.com/article.html?path=Mac/10.6/en/17131.html
I hit a snag at #4 (bullet #2), because I couldn't find "network users" to add to the users list. When the rest of us try to connect to her computer, this is the message that we got:
The alias "Stacey's computer (3)" could not be opened, because the original item cannot be found."
Can someone help me with this problem? I have browsed the Discussions and Forums and didn't see anything that was helpful. Thanks!

HI,
The Snow Leopard user... have her repair disk permissions and see if that helps...
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and restart your Mac.
Carolyn

Access refused in public folders when user is in a Group

Hi,
We have a Exchange 2003 server and an Exchange 2010 server
The Public folders are on the 2003.
Since 2 or 3 days, there is a access issue in juste ONE public folder: SOME users cannot access to the folder anymore if there are in a group (it asks for a login and a password -> if the user enters them, it doesn't work)
BUT the issue is just for some users not all and there are in the SAME group.
The issue is the same with both distribution or security group (and universal).
Please Help

Hi,
From your description, I recommend you follow the steps below for troubleshooting:
1. Please run the Get-PublicFolderAdministrativePermission -Identity "xxx" -User "xxx" cmdlet to check these users' permissions for the public folder.
2. If they don't have the related permissions, please use the Add-PublicFolderClientPermission -Identity "xxx" -AccessRights xxx -User xxx cmdlet to add the permissions for them.
For more information, here are some articles for your reference.
View Public Folder Administrative Permission Settings
http://technet.microsoft.com/en-us/library/aa998587(v=exchg.141).aspx
Add Permissions for Client Users to Access Public Folder Content
http://technet.microsoft.com/en-us/library/aa998834(v=exchg.141).aspx
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

MAPI_E_FAILONEPROVIDER == 0x8004011D when accessing public folders using mfcmapi

I seem to be getting this error when selecting the public folder in mfcmapi. I'm using the Feb 2014 release of mfcmapi.
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function CallOpenMsgStore( lpMAPISession, (ULONG_PTR)m_hWnd, lpEntryID, ulFlags, (LPMDB*)lppMAPIProp)
File MainDlg.cpp
Line 437
I can access the private mailbox without issue using mfcmapi, but the public folders I'm not able to. This problem is causing my backup software not to do document level backups. So I need to resolve this issue.
Also, if I create another user and give them the same access as administrator, the new user cannot access both the private mailbox nor the public mailbox when using mfcmapi so it must be a rights issue, but I can't find where it is!
Any idea's would be appreciated.
Thanks

Hi,
Please try to use MFCMapi tool as Administrator.
1. Can you access the public folder on both Outlook and OWA?
If can't access the PF on both Outlook and OWA, it seems there is something wrong on the Public Folder database side.
2. It also maybe the permission issue. Found a similar thread for your reference:
"MAPI_E_FAILONEPROVIDER (0x8004011D)" error message when you access an Exchange Server 2010 mailbox by using a MAPI application
http://social.technet.microsoft.com/Forums/exchange/en-US/3a2e9489-6137-42fb-95d1-bebcfe2ea138/mapiefailoneprovider-0x8004011d-error-message-when-you-access-an-exchange-server-2010-mailbox?forum=exchange2010
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

OK - How do you access Public Folders?

So I have my RTM environment build, and I have my public folder mailbox setup and folders created.
I've granted my test user access via EAC. However when I go in via OWA or Outlook 2013, I do not see them anywhere.
Is there some magic to getting access to these? I tried also going to open another mailbox but I was under the assumption they would show up just like they did in previous versions? At least it did from some of the screenshots I've seen.

Hello,
I suggest you run the “get-publicfolderclientpermission”
to check the test user permissions for a public folder.
Get-PublicFolderClientPermission
Here are two articles for your reference
Exchange 2013 Preview - Public Folders
(Part 1)
Exchange 2013 Preview - Public Folders
(Part 2)
Cara Chen
TechNet Community Support

Client-side GW integr.: access other folder than "inbox" and public folders

Hello,
in our current project the call center employees should work only with the CRM web UI. MS outlook client should run in background, however, they want to access the necessary data out of the CRM UI.
Thus, it would be possible to access other folders than the "inbox". In CRM UI, one is able to transfer e-mails from the MS outlook inbox to CRM including the creation of an activity. However, you can only access the inbox folder, not any other folder, like a subfolder of the inbox folder. Now in the call center mails are routed automatically into subfolders due to dispatching of incoming requests.
Second thing would be to access MS outlook public folders out of the CRM web UI since some kind of knowledge base things are stored there company-wide.
Many thanks for your help & kind regards
Wolfgang

Not answerted actually, but no further inputs received.

User Access to Public folders durring migration

I built a test environment in preparation for a migration I am doing. I have a 2007 and 2013 set up.
After I moved the test users from the 2007 exchange server to the 2013 server, they can no longer open the public folders still in the 2007 environment. The error is "the server mailbox cannot be opened because this address book entry is not
a mail user.".
The Public Folders will eventually be migrated, but I want to ensure users will still have access to them as they are migrated. What step am I missing?

Hi IT2B,
Is there any update after referring to these links?
Best regards,
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]
Niko Cheng
TechNet Community Support
Won't be able to work on until tomorrow. I'll post my results.

Is it possible to access the Public Folders in Exchange 2013 during a migration from Exchange 2007 to verify the files are there?

This is a migration from Exchange 2007 to Exchange 2013. We're in the middle of migrating the Public Folders. Is it possible to configure a database to point to the Exchange 2013 public folders so I can verify the data before the final cut?
If so what are the steps to do that? Thanks in advance.

To my knowledge no. It's an all or nothing thing with public folders.
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

Accounts made in o365 can't access legacy public folders - Migrated through 2010/2013 Hybrid can access

We've added two 2013 hybrid servers to our existing 2010 environment. Added the CAS role to all 2010 mailbox servers per ( https://technet.microsoft.com/en-us/library/dn249373%28v=exchg.150%29.aspx ) and currently have public folders (located on our
2010 mailbox servers) working in Outlook client for users whose mailboxes have been migrated from on-prem 2010 to o365. The problem is when we create a new user in o365, that user CAN see that we have public folders via Outlook client, but when we expand
the public folder list a credential window pops up and will not accept any set of credentials (even those of working hybrid migrated accounts).
We are following this method when creating new o365 accounts:
1) Make a user in AD
2) Dirsync the user
3) License the user for exchange
4) Run on on-prem mailbox server via Exchange Management Shell: Enable-RemoteMailbox "[email protected]" -RemoteRoutingAddress "[email protected]"
5) In o365 Remote Exchange Powershell run: Get-Mailbox -identity "[email protected]" |fl Identity,ExchangeGUID
6) Copy ExchangeGUID
7) Back on on-prem mailbox server via Exchange Management Shell: Set-RemoteMailbox "[email protected]" -ExchangeGUID <paste GUID here>
8) Dirsync the user again
I've compared two Remote User Mailboxes, ones that were migrated via Hybrid, and ones that were created in o365 and the settings look identical outside of the attribute "RemoteRecipientType" is set to Migrated vs ProvisionMailbox. I'm not
sure what else the difference in these accounts could possibly be that would be causing this credential failure.
Any thoughts would be appreciated.

Hi,
Please do the following steps to create an Exchange Online mailbox in your Hybrid environment:
Method 1: Create a remote mailbox for an existing user.
If you already have created a user in Active Directory, and the user has already been synced to online with license, we can give that user a mailbox in Exchange Online by using the Exchange Management Shell cmdlet Enable-RemoteMailbox on
your on-premise Exchange server:
Get-User “User1” | Enable-RemoteMailbox
Then the mailbox is enabled with an Exchange Online mailbox. We can check the mailbox by running the following command in On-premise Exchange server:
Get-RemoteMailbox “Test1” | FL *address*
Method 2: Directly create a new remote mailbox.
1. Create the remote mailbox in On-premise Exchange server by running:
$Credentials = Get-Credential
New-RemoteMailbox -Name "Test2" -Password $Credentials.Password -UserPrincipalName
[email protected]
2. Launch dirsync and assign a license to the newly created user with Office 365 account.
Then Test2 can sign in, using his on premises credentials, and open his online mailbox.
For more information about the remote mailbox, please refer to:
http://blogs.technet.com/b/ilvancri/archive/2011/08/24/exchange-online-exchange-on-premises-shared-namespace-how-about-mail-routing.aspx
Regards,
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]
Winnie Liang
TechNet Community Support

Migrating from Exchange 2007 to Exchange 2013 Public Folders coexistence

Hi all, I'm migrating from Exchange 2007 SP3 to Exchange 2013 SP1.
I have an Exchange 2007 server (Client Access, Hub Transport and Mailbox Server) in Site A, mailboxes and Publics Folders
In another Site in Site B, I have already installed (Client Access and Mailbox Server) Exchange 2013 server.
I am migrating test users, the fact is that users who migrated to Exchange Server 2013 Public folders do not see.
How I can make the migrated users from viewing the Exchange 2007 Public Folders duration coexistence?
Is there a "how to" to migrate Public Folders from Exchange 2007 to Exchange 2013?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Public folders access

Similar Messages

Maybe you are looking for