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

Similar Messages

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Unable to Open Public folders from Windows XP after the upgrade of CU4 to Cu7

We still have few machines running windows Xp, who cannot access Public folders after the upgrade to the latest CU7. Is there any fix for it other than moving them to Windows 7?

Hi DNair,
Hope you are already upto date. But still just putting it through to cross check.
Outlook Versions Supported by Exchange 2013
The following Outlook client versions are fully supported by Exchange server 2013. Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013.All
of the Outlook versions listed below have been thoroughly tested by the Exchange Product group:
Outlook 2013
Outlook 2010 SP1 with November 2012 Cumulative Update ( available from
http://support.microsoft.com/kb/2687623 )
Outlook 2007 SP3 with November 2012 Cumulative Update ( available from
http://support.microsoft.com/kb/2687404 )
Entourage 2008 for Mac, Web Services Edition
Outlook for Mac 2011
Outlook clients earlier than Outlook 2007 are not supported.
Find and Manage
Outlook Updates here.
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

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

Unable to access public ip from branch vpn (Cisco ASA 5510 Firewall)

                   Hi,
As per the above diagram
in Head office - able to access public ips
In Branch office - unable to access public ips only accessing head office servers and internet is shared from head office.
please see the below configuration in Branch office router:
access-list 1 permit any
access-list 100 remark ****** Link to Firewall-HO1 ******
access-list 100 permit ip 10.21.211.0 0.0.0.255 172.16.35.0 0.0.0.255
access-list 100 permit ip 10.21.211.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 100 permit ip 10.21.211.0 0.0.0.255 10.11.0.0 0.0.255.255
access-list 100 permit ip 10.21.211.0 0.0.0.255 10.12.0.0 0.0.255.255
access-list 100 permit ip 10.21.111.0 0.0.0.255 172.16.35.0 0.0.0.255
access-list 100 permit ip 10.21.111.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 100 permit ip 10.21.111.0 0.0.0.255 10.11.0.0 0.0.255.255
access-list 100 permit ip 10.21.111.0 0.0.0.255 10.12.0.0 0.0.255.255
access-list 100 permit ip 10.21.10.0 0.0.0.255 172.16.35.0 0.0.0.255
access-list 100 permit ip 10.21.10.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 100 permit ip 10.21.10.0 0.0.0.255 10.11.0.0 0.0.255.255
access-list 100 permit ip 10.21.10.0 0.0.0.255 10.12.0.0 0.0.255.255
access-list 100 permit ip 10.21.211.0 0.0.0.255 host 78.93.190.226
access-list 100 permit ip 10.21.111.0 0.0.0.255 host 78.93.190.226
access-list 100 permit ip any any
access-list 101 deny   ip 10.21.211.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 101 deny   ip 10.21.211.0 0.0.0.255 10.11.0.0 0.0.255.255
access-list 101 deny   ip 10.21.211.0 0.0.0.255 10.12.0.0 0.0.255.255
access-list 101 deny   ip 10.21.211.0 0.0.0.255 172.0.0.0 0.255.255.255
access-list 101 deny   ip 10.21.111.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 101 deny   ip 10.21.111.0 0.0.0.255 10.11.0.0 0.0.255.255
access-list 101 deny   ip 10.21.111.0 0.0.0.255 10.12.0.0 0.0.255.255
access-list 101 deny   ip 10.21.111.0 0.0.0.255 172.0.0.0 0.255.255.255
access-list 101 deny   ip 10.21.10.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 101 deny   ip 10.21.10.0 0.0.0.255 10.11.0.0 0.0.255.255
access-list 101 deny   ip 10.21.10.0 0.0.0.255 10.12.0.0 0.0.255.255
access-list 101 deny   ip 10.21.10.0 0.0.0.255 172.0.0.0 0.255.255.255
access-list 101 permit ip host 10.21.211.51 any
access-list 101 permit tcp 10.21.211.0 0.0.0.255 host 66.147.240.160 eq pop3
access-list 101 permit tcp 10.21.211.0 0.0.0.255 host 66.147.240.160 eq smtp
access-list 101 permit tcp 10.21.211.0 0.0.0.255 host 78.93.56.10 eq pop3
access-list 101 permit tcp 10.21.211.0 0.0.0.255 host 78.93.56.10 eq smtp
access-list 102 permit ip 10.21.211.0 0.0.0.255 any
route-map nonat permit 10
match ip address 101
Thanks for your valuable time and cosiderations

any1 can help me ?

Unable to open Public Folders in Outlook or OWA (Exchange 2010)

Exchange 2010 Public folders can not be opened from Outlook or from OWA, in the ADIS I do not see Folder Hierarchies. Under the public folder Management Console,i get an error that states "You cant perform this operation because public folder
database isnt mounted. Please mount it and try afain, It wsas running the command ger-publicfolder -getchildren -identity "\"-server 'MBXserver'"

Run "Get-PublicFolderDatabase" and see what it says the status of the database is. This error implies that the database in offline. You will also want to find the status of your public folder copies.
Get-PublicFolder -Recurse | Ft
or
Get-PublicFolder -Recurse | Export-Csv PublicFolderStatus.csv -NoTypeInformation
The first will work if you are checking a small number of folders, but you'll want the latter if you have many of them.

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

Users could not open Public Folders in Outlook 2007 SP3.

Is anybody had this issue or probably know how to fix it?
We have Exchange 2013 server and users workstations with XP SP3 and Office 2007 SP3 installed. Exchange has users’ mailboxes and public folders. Public folders work OK until last week. Issue probably happened after latest CU update for Exchange 2013 installation.
Now users could not open Public Folders in their Outlook. The error is:
"Cannot expand the folder. Your profile is not configured. (/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected])"
And this "[email protected]" is public folder ContentMailboxGuid.
And this error message appears when user click on Public Folders \All Public Folders in Outlook. So company public folders do not even appear in All Public Folders folder. Users have Owner permissions for all Public Folders and Root Public folders.
Also one more error in Outlook about it:
“Cannot display the folder. Microsoft Office Outlook cannot access the specified folder location.”
One more issue is that previous Exchange 2007 server died (RAID died) so we had to delete it from AD and clean its records in ADSIEdit (CN=configuration,DC=.domainname,DC=.COM > CN=Services > CN=Microsoft Exchange > CN=Organization > CN= Administrative
Groups > CN=(Groupname) > CN=Servers >) and install new server with Exchange 2013, and import all users mailboxes from backup. Public folders were not migrated from the old server because of its death. We create new public folders in Exchange and
then manually import all folders from latest .pst backup using user Outlook.
And it work OK more than a month till last week.
Thanks,
Andrey

Hi Mavis,
Thank you for your answer.
I check permissions couple of times for both public folder and its root and both are granted for users as “Owner” and applied to public folder and its subfolders.
This server has 2 mailbox stores and both are currently mounted.
[PS] C:\Windows\system32>Get-MailboxDatabase -Status |fl name,mounted
Name    : Mailbox Database 2104233799
Mounted : True
Name    : MBDB1
Mounted : True
But when I check homeMDB property for Microsoft System Attendant in ADSIEdit I found that it is empty.
And it looks like System Attendant mailbox & service have been removed from Exchange 2013.
http://howexchangeworks.com/2013/05/cannot-open-microsoft-system-attendant-mailbox-error-during-exchange-2013-mailbox-move.html
and even from Exchange 2010.
http://blogs.msdn.com/b/dvespa/archive/2009/10/06/say-so-long-to-the-system-attendant-mailbox.aspx
Also I check arbitration mailboxes and all are looks to be in default database “Mailbox Database 2104233799” which is currently mounted.
[PS] C:\Windows\system32>Get-Mailbox -Arbitration |fl name,data*
Name     : FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
Database : Mailbox Database 2104233799
Name     : SystemMailbox{1f05a927-77cc-4f5d-b5ca-667ea4256ff9}
Database : Mailbox Database 2104233799
Name     : SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
Database : Mailbox Database 2104233799
Name     : SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
Database : Mailbox Database 2104233799
Name     : Migration.8f3e7716-2011-43e4-96b1-aba62d229136
Database : Mailbox Database 2104233799
Thanks,
Andrey

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

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

Exchange 2010 SP3 - RU3 RU4 Public Folders issues ( not refreshing ) when grouping by Categories for "(None)" Group

After installing Exchange 2010 SP3 RU3, I had an issue in Public Folders, once having group by categories in Outlook, the Group of "(None)" categories is not refreshing when changing flag... I also installed RU4 but nothing changed, any reason
Thx

Hi,
From your description, the group with none categories won’t fresh when changing flag in Category view. If I misunderstood, please point it out.
As you can in the View tab as below, there is Category as well as Flag: Start date or Due Date. It means that grouping per color categories is more or less different from that
grouping by flag.
Should you need more assistance, feel free to tell me.
Regards,
Rebecca Tu
TechNet Community Support

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Exchange 2007 servers reports mailbox size full, but mailbox shows empty in OWA or Outlook.

When the users log into their mailboxes in OWA or Outlook get this warning: "You have exceeded your limit quota and can not send or receive mail" but really they have the mailbox empty, there's nothing in calendar, folders or deleted items.
I ran this command Get-MailboxStatistics and the mailbox reports for example 500 MB.
I deleted the deleted items and I configured deleted items retention to 0 days to ensure that it wasn't the problem, but the servers still reporting the same mailbox size (500 MB).
This happen to some mailboxes, not all
Please help, what can I do?

1. How many Exchange 2007 servers do you have?
2. What service pack and rollups are installed on the Exchange 2007 server(s)?
3. If you have more than one server, are you using any form of replication: LCR, SCR, CCR... etc. ?
4. What 3rd party software is installed on the Exchange 2007 server(s)? For example, antivirus, archiving, etc.
5. Can you confirm that this happens in OWA as well? I see you mentioned OWA but I've just glanced at another problem with incorrect folder size being indicated in Outlook and it apparently had to do with the .OST file. Of course, if the problem occurs with
OWA as well, then the OST file would not come into play. Sorry to insist on that but I'm trying to rule some things out, if possible (like 3rd party apps, maybe something with replication, maybe a problem that was corrected in a service pack or rollup).
Please 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.

Cannot access DFS folders as domain admin when using Server 2012 R2

Hello,
recently we added a new domain controller running Windows Server 2012 R2 to our domain. All other domain controllers are running Server 2008 R2. A user now had a problem with his home folder. Therefore, I logged into the new domain controller as a domain
administrator and opened an Explorer. Next I entered "\\ourdomain.comp\accounts$\homes" into the address bar. To my suprise I could only see one folder (the one for the domain administrator account). If I do the same on a any of the Server 2008 R2
machines, I can see all user homes (as expected).
I temporarily disabled ABE for the home folder and now I can see all folders. But if I click on any of them, I get an access denied error stating that I have insufficient permissions to access this folder. It does not matter whether I open Explorer as administrator
or not. On Server 2008 R2 it works in either case. I don't get what's going wrong. No matter which machine I use, I always end up trying to access the same folder on the same machine. Therefore, the rights on this folder are always the same and I should be
able to access it. Do I need to configure something on the new DC? Is there anything related to this that has changed with Server 2012 R2?
Regards,
Oliver

Hi Oliver,
According to your description above, here are the symptoms you observed:
•Logon Server 2008 R2 DC as domain administrator, you can see all user home folders under
\\ourdomain.comp\accounts$\homes and access these folders.
•Logon Server 2012 R2 DC as domain administrator, you can only see the domain administrator home folder under
\\ourdomain.comp\accounts$\homes.
•Logon Server 2012 R2 DC as domain administrator and disable ABE, then you can see all user home folder under
\\ourdomain.comp\accounts$\homes but get an access denied error when you access others user home folder.
Is there any error message in event log on Server 2012 R2 DC when you access the shared folder? Try to disable UAC on the server to check if you can access the shared folder.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

Similar Messages

Maybe you are looking for