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

Similar Messages

Configure legacy public folders where user mailboxes are on Exchange 2013 servers

Hello all,
I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over. I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?). The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
on the 2013 server, using the mailbox name I had created, it says it cannot be found. Of course I checked and the mailbox exists, is configured properly, and so is the new database. The 2013 EAC also sees the mailbox with no issues.
Can someone tell me why I am getting this error?
Thanks,
Shaibal

Hi Mavis,
Thank you for your response. I am the full domain admin, and check and was part of both groups mentioned above. Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
-PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
Below is the error I get:
[PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
    + CategoryInfo          : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
    4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetOrganizationConfig
    + PSComputerName        : zor-exchange01.zubatkin.lan

Enable legacy public folders for Exchange 2013 prior to migration?

We're about ready to migrate to Exchange 2013 from 2010. We have a public folder database on 2010 that users can't see once migrated to 2013. If I run through the commands according to the technet article "Configure legacy public folders where user
mailboxes are on Exchange 2013 servers" (https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx), will users who's mailboxes are still on Exchange 2010 be able to see these public folders?

I know they've made alot of changes recently in how legacy public folders are handled in Exchange 2013 (mostly CU7), but I haven't had to do anything more than just setting the proper public folder database on the Exchange 2013 databases.
That being said, looking over the article you are not doing any moves, and it looks eerily similar to this blog post:
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
So I don't think this would hurt Public Folder access for your users in your legacy environment.
Did you deploy CU7? If so, then do what both articles say. If not try using Set-MailboxDatabase -Identity <2013 db name> -PublicFolderDatabase <PF DB NAME>
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

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

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

After upgrading to Mavericks i can't subscribe IMAP public folders separately in Mail.app

I can access all public folders but cannot choose anymore witch one to subscribe... Mail server is Debian 6.0.7 running Dovecot v1.2.15-7
Before (Mountain Lion):
After (Mavericks):

bump!
any answers to this problem?
it's a bit annoying as I am now subscribed to few hundred folders I don't want to be!
Mail v7.2
dovecot v2.1.7

Trying to activate a new iPad mini. Keep getting message that activation server can't be reached and to try through iTunes. I can't go back beyond the language choice screen to select iTunes. Two days of trying to activate. Help?

Trying to activate a new iPad mini. Keep getting message that activation server can't be reached and to try through iTunes. I can't go back beyond the language choice screen to select iTunes. Two days of trying to activate. Help?

Apple's download AND activation servers are being stressed today with all the downloads/activations. It might be best to wait and try later.

Unable to read data in Excel 2010/2013 from encrypted Access 2010/2013 database

A customer has an Access database (.accdb), which was encrypted/given a database password in Access 2013. It should be possible to read that data from Excel 2010/2013, but when clicking on Data-->From Access
and the correct path is put in and the correct database password has been entered, Excel just keeps prompting for the database password. This happens with both Excel 2010 and 2013.
The database password supplied is correct as evidenced by opening the database in Access 2013 using the same database password.
A colleague in a separate company has found that a separate .accdb file he has recently encrypted also has the same problem as above, yet a .accdb file encrypted ages ago
is readable from Excel.
How do I get Excel 2010/2013 to read the data from the encrypted .accdb file, please?

Since Access 2010 the encryption algorithm has changed:
Source
Follow the next steps to apply an encryption method that will allow you to (programmatically) connect to the database:
1. Decrypt the database
2. Change the encryption method:
   - In Access Options select 'Client Settings'
   - Scroll down to section 'Advanced'
   - 'Encryption Method': select option 'Use legacy encryption (..'
   - Click 'OK'
3. Encrypt the database
Hope this helps.
Emiel Nijhuis

Can no longer see messages in public folders in Outlook (2010) conversation view

(originally posted this under MS Community outlook discussion and it was suggested I post it here):
Hello:
I believe this may be related to a recent update, but previously I could see messages from public folders in my conversation view. Now, I am only able to see messages in private folders (including sent items).
I have the cached exchange mode on.
I loved the conversation view because I could move e-mails out of my inbox to public folders (on our company server) to keep my inbox under required size limits, but still have easy access to e-mails within the conversation string. That view in my
opinion was the best upgrade to Outlook when it first came out. Now it's virtually useless for me again.
If there's something i can change to get those messages re-appearing again I'd really love to know what I can do, it was really useful for me.
Thanks in advance to any who reply!

Hi,
Based on the descrtiption, I know that there is no emails exist in public folder when using conversation view in Outlook after installing update.
1. I suggest use OWA to check whether emails exist in public folder when using Conversation View. If it works well, it seems an issue on the Outlook client side.
2. Please check the connectivity between Outlook and Public Folder.
3. I suggest disable conversation view for test to verify whether emails appear in public folder. If the emails appear, it seems an issue on Outlook Conversation View.
4. I also suggest run Outlook under safe mode to avoid some AVs and add-ins. Try to re-create profile to refresh the caches.
Thanks
Mavis Huang
TechNet Community Support

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

Can't send email with lotus inotes through forefox server but can through yahoo - what do I need to do to correct this?

when accessing my teacher email through firefox I can receive and open email but can't send any (the teacher email uses IBM Lotus Inotes

I am running Lotus iNotes version 8.5.2 on Firefox version 6.02. I am not seeing any errors in a red bar. I click "send" and nothing happens.

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."

I can´t access my private folders.

Good morning.
I configured a file system repository manager.
In the KM Content, I can access the public folders but can´t my private folders.
I get the following error:
Item not found
/Homes_02/acastaneda
The item you are attempting to access is not available. Check that the name or link is correct. You might also check whether the associated repository is currently accessible.
other user can see his public and private folders.
How can I sover the problem?.
Best regards.

Hi Ticiano,
If this error is coming, then might be the name is not correct or that particular file is not stored in the correct path. I request you to check again for the name and the document path.
Also about the access for the users, you have to check whether that folders have your permissions or not.
For that you have to go to that particular folder in the KM content under Content Admin, and check the permissions of the folder under settings.
I hope your query will be resolved with this.
Regards.
Piyush
Pl reward points if this reply helps.

Cannot expand public folders in Outlook but can in OWA

Hi All,
I have a problem which I hope some one might be able to shed some light on. Firstly, the environment is Exchange 2010 (v 14.01.0438.000) and all clients use Outlook 2007. We have one user in the organisation who recently noticed that he cannot expand public
folders. He had been able to do so a couple of months back but could not pin point the time it stopped working. The error received reads :-
"Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed."
I thought that this might be a permissions issue but this particular user can access the public folders via OWA. Also, my AD account was a copy of this user's and I can access public folders without issue.
I have tried the following so far :-
Tried running Outlook in safe mode
Tried recreating the Outlook profile.
Tried creating a new Outlook profile on a different client PC.
Tried running Outlook in cached an online modes.
Ran Exchange BPA and found no issues.
Checked ADSIedit for old administrative groups left over from past migrations.
used the test-outlook connectivity cmdlet from powershell which ran it's tests successfully.
This user originally set up all the public folders and was still listed as the owner of all of them.
Tried creating a new public folder.
Checked for an Outlook update that had caused a similar issue.
All the above failed to progress the situation. I have come across posts online that sound very similar, one stated that a Microsoft tech had found a permission that wasn't correct but didn't list which permission and the other related to an update to Outlook
that had triggered it. I can confirm it's not the update and I have checked permissions in the public folder management utility in Exchange. Also, my AD account is a copy of his and I can access the folders without issue.
I have also considered what may have changed on the network recently. The only major change has been a new admin password but I cannot see how that would be relevant.
Any help would be hugely appreciated!
Thanks in advance!

Hello John: We are having the exact same issue. Thank you for the great description, it hits the nail on the head for an issue that is tough to explain. Did rebuilding the mailbox fix the problem? We thought a next step would be to create a new
AD profile for the user all together, although replacing the user herself would be easier for us. She obviously caused this problem and will most likely cause us more problems that might be worse if she keeps clicking and sliding on every thing that
is shiny to see what it does..
I can only surmise that CaRa ChEn has decided to "better understand customer views on social support experience" elsewhere. I think the only logic for the mailbox suggestion would be "grasping for straws" and it is the only thing you have not tried
so far. (Other than replacing the user). Pactera employees get points for being the first to reply to a question and the first to have a suggestion marked as helpful as well as the sheer quantity of replies to the forums that are made. High
value is placed on moving posts to different forums as well so I thought I would ask quick before the thread gets shoveled somewhere else.. If she needs help with the interview project she can find plenty of my thoughts here in the community.
Thanks again, and we will reply back if replacing the user (account) does NOT solve the problem, otherwise one can assume we are happy campers again our new employee and remember just because it is blinking does not mean you should click on it. :)
Best regards,
RickkEE

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

Similar Messages

Maybe you are looking for