Public Folder access on Exch 2007 from exch 2013 user

I have an issue with my test user that I migrated from 2007 to exch 2013 being able to access public folders that reside on the 2007 server. 2007 users accessing public folders on 2007 have no issues. I have it narrowed down to autodiscover. Please see the
below exerpt from autodiscover. The "<PublicFolderServer>ex2013.accessDOMAIN.net</PublicFolderServer>" section shows that autodiscover is giving the name of the exchange 2013 server as the publicfolderserver
instead of the exchange 2007 server. My question is how do I reflect the correct server "Exch2007" on this autodiscover output?
<Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <MicrosoftOnline>False</MicrosoftOnline>
      <Protocol>
        <Type>EXCH</Type>
        <Server>[email protected]</Server>
        <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
        <ServerVersion>73C0834F</ServerVersion>
        <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>ex2013.accessDOMAIN.net</PublicFolderServer>
        <AD>DC.domain.local</AD>
        <ASUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</ASUrl>
        <EwsUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</EwsUrl>
        <EmwsUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</EmwsUrl>
        <EcpUrl>https://ex2013.accessDOMAIN.net/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.local</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.local</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.local</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.local</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.local</EcpUrl-sms>
        <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=domain.local</EcpUrl-publish>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.local</EcpUrl-photo>
        <EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.local</EcpUrl-tm>
        <EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.local</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.local</EcpUrl-tmEditing>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.local</EcpUrl-extinstall>
        <OOFUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</OOFUrl>
        <UMUrl>https://ex2013.accessDOMAIN.net/EWS/UM2007Legacy.asmx</UMUrl>
        <ServerExclusiveConnect>off</ServerExclusiveConnect>
      </Protocol>

Thank you for your time. I verified that the build number on outlook is greater than SP1. This would indicate that the hotfix was applied as it was included in cumulative rollups.
The output from the geet-outlookanywhere command is found below. I have adjusted the auth to basic as that is where I would like it to be.
[PS] C:\Windows\system32>Get-Outlookanywhere | fl Identity,*auth*,*hostname,*ssl
Identity                           : Exch07\Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
ExternalHostname                   : legacymail.DOMAIN.net
InternalHostname                   : legacymail.DOMAIN.net
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
Identity                           : Exch13\Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
ExternalHostname                   : webmail.DOMAIN.net
InternalHostname                   : webmail.DOMAIN.net
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True

Similar Messages

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Outlook Public Folder access and permissions

How do I add an account to a public Folder and grant management permissions to that account?

Hi,
To add permissions for client users to access Public Folder content, we can use Exchange Management Shell to add it as what ManU PhiliP posted.
Alternatively, we can use the Public Folder Management Console to add public folder permissions for a client user. For detailed steps about this, please refer to the following official article:
https://technet.microsoft.com/en-us/library/aa998834(v=exchg.141).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

IDisk Public folder access

I'm attempting to give others browser access to my public folder. Everything works per the directions below except that the public folder password doesn't work. It's necessary to use my dot-Mac password to reach my public folder! Has anyone else seen this?
"Mac or Windows users who are not MobileMe members can access your iDisk by opening a web browser and entering: public.me.com/[YourMemberName], and if necessary, entering your Public folder password."

I have the exact problem mentioned above.
I have changed my System Preferences — MobileMe — iDisk — Your iDisk Public Folder — Password-protect your public folder PASSWORD to a NEW PASSWORD that is not my ACCOUNT PASSWORD and it won't take.
I have tried to access my public folder with the NEW PASSWORD but it only responds to my ACCOUNT PASSWORD.
I've reset it the password many times, restarted many times and have tried accessing the public folder through Safari and Firefox.
I'd prefer to have a separate password for my public folder.
Any suggestions?
Thanks.

Public folder access error 0x8004011D when 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

You really don't need to cross-post these, and you especially don't need to post these multiple times in the same forum.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Public folder calendar will not add to favorites or users default view in Outlook 2010

I have created a shared public calendar in the public folders of our exchange server set-up (priovided by a popular cloud supplier). It appears under public folders in Outlook 2010 but right-clicking add to favorites does nothing and I cant make the calendar
show up in the normal calendar view (alongside other calendars) for the people that need to share it. What am I doing wrong?

Hi ,
This folder was added to the “public favorites” folder and then added to your favorites menu and don’t shows up in the Navigation Pane under “Other Contacts”.
1.If so , please check the calendar folder you initially added to the public folder as being available .
2.Open the Outlook E-mail account –more setting—chose Download Public Folder Favorites.
3.Add the “Show in Favorites” button to your Quick Access Toolbar at the top of your Outlook by expanding the menu next to it, choosing Customize, and
finding the “Show in Favorites” item under all commands.
4.Switch to Folder View and click to open your Public Foder in your main Outlook window.
5.Switch to Mail View but don’t click any folders. You should see that your “Show in Favorites”button turns from grey to colored. Click it and it will
add the public foder to your Favorites list.
Wendy Liu

Exchange 2007 - Public Folder Access

Hello,
i have a little problem. I'm using my iPhone in my company like some other guys here. I want to synchronize the Exchange Public Folders through the iPhone. I already know thats not possible in a direct way. Does anyone know a good Tool to synchronize Folders in Exchange? I found some Tools, but only Add-Ins, no standalone applications which work without Outlook and completely alone. I'm searching for some kind of tool which runs in a process on a webserver.
MfG KeRn

I know this is an issue, Microsoft are so backwards in their way of thinking.....Most companies use public folders in one way or another.
I have a Kerio Mail Server it's identical to Exchange but better and more stable and costs a fraction of the price, they released a version of their software by accident that synced and supported public folders to my iPhone, they removed it in the next update, I have contacted them on this issue and they say that they are working on solving this problem and it is due to a bug in the syncing process. So I am waiting with anticipation for them to release it very soon, so up that Microsoft!!!!!! Get with the real world!!

Exchange 2013 Public Folder Accessability Issues

After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders. Issues range from a hung server requests to on-screen errors like this one:
“Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
Ideas?

Hi Niko,
Firstly, apologies for the delayed update...
We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation. While migrating from Exchange 2010
to Exchange 2013 we did follow the migration process.
Here is what our current settings from Get-OutlookAnywhere -Server %Server%
RunspaceId                         : e2e4f324…
ServerName
: %server%
SSLOffloading
: True
ExternalHostname
: <set>
InternalHostname                   : <set>
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods
: {Basic, Ntlm, Negotiate}
XropUrl
ExternalClientsRequireSsl
: True
InternalClientsRequireSsl
: True
MetabasePath
        : IIS://%server%/W3SVC/1/ROOT/Rpc
Path
: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags
ExtendedProtectionSPNList
AdminDisplayVersion
: Version 15.0 (Build 775.38)
Server                             : %server%
AdminDisplayName
ExchangeVersion
: 0.20 (15.0.0.0)
Name
: Rpc (Default Web Site)
DistinguishedName
: CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                    Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
Identity                           : %server%\Rpc (Default Web Site)
Guid
: 0bf08d0e…
ObjectCategory
: %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged
: 5/5/2014 3:08:31 PM
WhenCreated
: 2/20/2014 2:13:17 PM
WhenChangedUTC
: 5/5/2014 8:08:31 PM
WhenCreatedUTC
: 2/20/2014 8:13:17 PM
OrganizationId
OriginatingServer
: %server%
IsValid
: True
ObjectState
: Changed

"Exchange Server 2003" Public folder access within OWA

Hello,
I can connect to my exchange server 2003 (I know I have to upgrade) with OWA through an alias (webmail). After connecting in OWA, when I click a button in the navigation bar (contact, rules, ...), it's working OK except for public folders. When I click on
public folders button, IE open a new window with this URL https://<netbios server name>/public instead of https://webmail/public. I googled around and found a thread explaining how this problem can be address by modifying navbar.js. But in my situation
navbar.js and every other files located in ..\exchweb\control doesn't seem to be access anymore, they have been replaced by those here ..\exchweb\6.5.7651.60. There is no navbar.js in this folder but a vw_navbar.js. I can't find the code I have to modify like
in navbar.js to to address the problem.
Thanks for your help.
Chris

Hi Chris,
This symptom can be caused if we enabled any redirection on /Public virtual directory. You can check the /Public settings and configuration files to remove the redirection. We can also reset the reset the default virtual directories as the KB introduced:
http://support.microsoft.com/kb/883380
Best Regards,
Tracy

Help with public function (accessing to addchild object from other public function)

Hi, i have below piece of my code AS3 (Flash CS4). I would like to get access to addchild Movie Clip object (ZoltyWjazdMC) in function two() which i created by addchild command in public function one(). I know it`s basic question but i can`t find answer for it. Anybody would help me with that?
public function one():void
var ZoltyWjazdMC:MovieClip = new MovieClip();
this.addChild(ZoltyWjazdMC);
ZoltyWjazdMC.addChild(assets.ZoltyWjazd.loader);
this.setChildIndex(ZoltyWjazdMC,1);
ZoltyWjazdMC.alpha = 0;
ZoltyWjazdMC.visible = true;
assets.ZielonyWjazd.alpha = 1;
public function two():void
ZoltyWjazdMC.alpha = 1;
Do i need remove "this" and change it to "stage". Is it necessary?

Define your variable var ZoltyWjazdMC:MovieClip outside of function one(). Currently ZoltyWjazdMC is local to function one() so that function two() does not understand what it is!

Exch 2007 to Exch 2007 Cross forest migration

Hi all,
I am currently migrating all users from a root domain in one forest to a child domain in a second forest.
Source: Forest A\DomainA is server 2003 r2 with Exchange 2007 SP3
Target: Forest B\Domain B is server 2008 r2 with Exchange 2007 SP3
I am using ADMT to migrate the user accounts with SID history. Data has been replicated over with permissions in tact.
domain trusts have been put in palce and SID filtering has been disabled.
Order of migration thus far;
1. Migrate Sec Groups
2. Migrate Distribution lists - with target proxt address only (source will be added on the weekend of the cut over)
3. Migrate User Accounts. all exchange attributes are stripped out. Source/target user account's are left in current state (not disabled)
4. I then run this powershell command to migrate the user mailbox over;
Move-Mailbox -TargetDatabase TargetStore -Identity SourceUser -GlobalCatalog TargtDC -SourceForestGlobalCatalog SourceDC -NTAccountOU SourceOrgUnit -SourceForestCredential SourceCredential -TargetForestCredential TargetCredential -Confirm:$False
The mailbox is migrated over and it automatically connects to the corresponding user that was migrated previously. How is this connection made. The move-mailbox does not migrate the source user. I was under the impression that the mailbox would show in the
target as a linked mailbox and then I would have to disconnect and it reconnect it to the target account. it makes my life easier that it reconnects it but i wanted to know if im missing something. is this the correct way in which to migrate the mailboxes.
Thanks

Hello,
It’s expected. In AD account properties, there are a lot of attributes about Exchange, such as HomeMDB, HomeMTA…
When you use AMDT, these values will be changed to the target domain so that they matches.
Thanks,
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]
Simon Wu
TechNet Community Support

Public Folder Access

We have just implemented Exchange 2013 and when looking in OWA we cannot see any of the Public Folders.
Not sure why,, any ideas?
thx

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Access windows server 2003 from a local user machine (windows 7 pro)?

Is there a way to look up user accounts from a local machine running windows 7 pro without having to always go to the physical server itself?
The reason is the location of the server, a bit of an inconvenience.
It's a windows server 2003 btw.
Thank you,
Cris

Hi,
Thank you for posting in Windows Server Forum.
Good to hear that you go it working.
In respect to your another question, it seems that you want to have with smart card technique for password without entering manual credential. Please check following article for information.
Smart Card and Remote Desktop Services
http://technet.microsoft.com/en-us/library/ff404286(v=WS.10).aspx
Guidelines for enabling smart card logon with third-party certification authorities
http://support.microsoft.com/kb/281245
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Public Folder Database Removal

Hello,
I am working in a Exchange 2010/2013 co-existence environment.
All mailboxes have been moved to Exchange 2013.
Public folders remain on Exchange 2010 for the moment.
There are 4 Public folder databases, all identical in terms of replicas:
PFDB1 - MBX01
PFDB2- MBX02
PFDB3 - MBX03
PFDB4 - MBX04
Circumstances beyond my control may mean that I need to take the MBX03 and MBX04 servers out of the production environment before I have migrated the public folder hierarchy across to 2013.
What is the recommended method for removing the public folder databases on these two servers?
Previous experience tells me that removing a database containing any replicas will fail. How can this be mitigated while keeping the PF structure in tact on PFDB1 and PFDB2 and thus serving the client mailboxes?
Regards
Matt

Hi,
To remove a public folder databae, you can look at the following article.
Remove Public Folder Databases
http://technet.microsoft.com/en-gb/library/dd876883(v=exchg.141).aspx
Before you delete public folder database, please dismount public folder databases temporarily and make sure Exchange 2013 users can access public folders normally.
Best regards,
Belinda Ma
TechNet Community Support

How to get a list of public folder which haven't been accessed from last 90 days.

How do I get public folder list which are inactive from last 90 days in exchange 2010? Is there any script\shell command to get the same?

Hi,
We can use the Get-PublicFolderStatistics to retrieve last logon time about Public Folder with the following command.
Get-PublicFolder | Get-PublicFolderStatistics | where {$_.LastLogonTime -lt (get-date).addDays(-90)}
Note: Make sure you have been assigned proper permissions before you can run this cmdlet. To see what permissions you need, see the "Public folders" entry in the
Mailbox Permissions topic.
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]
Lynn-Li
TechNet Community Support

Public Folder access on Exch 2007 from exch 2013 user

Similar Messages

Maybe you are looking for