E71 Imap4 Exchange Public Folder Issue

Hi All,
I am trying to find a way to easily access a Public Folder on my E71.
We share Support e-mails via an Exchage Public Folder.
Mail for Exchange only accesses the Inbox which is disappointing for what is supposed to be a Corporate Application.
E-mail access via IMAP4 correctly shows all Folders/SubFolders EXCEPT none under "Public Folders/". I have checked that these are accessible via Windows Mail so I know that it should work.
Does anyone know why I can't see the folders under Public Folders or have a suggestion for accessing Public Folders on the E71 (preferably without recourse to 3rd Party Software). For a "Road Warrior" phone it does seem a glaring omission in functionality.
Thanks in advance,
Adam

Hi,
Please check the replica for "SCHEDULE+ FREE BUSY", right click the folder and then select Properties. In the Replication tab, please confirm there is a replica. If there is no replica, add one public folder database as a replica for the folder.
After that, please restart the Microsoft Exchange Mailbox Assistants service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Exchange Online (O365) and Exchange 2013 On-Premise, Public Folder issues?

Hello,
I have recently migrated from Exchange 2010 to Exchange 2013 on premise (decommissioned the old server) and migrated my public folders to the new mailbox architecture found in Exchange 2013.
We are also hybrid setup with Office 365 and Exchange Online (AD FS and Password Sync). For our on-premise Exchange we use Split DNS.
What I am trying to do now is give my Exchange Online users the ability to see our on-premise public folder infrastructure however I am not having any luck in getting this to work.
On premise I have the "PublicFolderMaster" mailbox which is the Primary Public Folder Mailbox, and PublicFolderMailbox1 which is the secondary mailbox (where all the public folder data is).
How do I configure my Exchange Online to allow the users to see on-premise public folders? I tried..
Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PublicFolderMaster,PublicFolderMailbox1
In my O365 user's Outlook I see Public Folders, but when I try to expand it I get an error saying unavailable...
What am I doing wrong?

Or must I follow all these steps in addition to the last step above?
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx

Mail Enabled Public Folder Issues after migration online

Hi
We have recently migrated our Legacy (Exchange 2010) Public Folder Infrastructure to Exchange Online - we have a hybrid setup, SSO and DirSync.
We initially had an issue where some of our mail enabled public folders had lost their link with the associated MailPublicFolder objects and as such could not receive email.
We resolved this issue ourselves however we are now experiencing a different issue which i believe should be easily resolvable however this isn't the case at the minute.
The issue is that when a user emails a Mail Enabled Public folder Exchange online is attempting to relay the email back to our onPrem servers. This is occuring for the bulk of our Mail Enabled Public Folders - we have ~1200 of these. The only
folders that are working as expected are those that had the initial issue above and for which we had to remove and re mail enable these folders. We also had to recreate any secondary smtp address for these folders. This accounts for 88 of our total
MEPFs.
I have checked the attributes on the MailPublicFolder objects for those that are not working and those that are functioning as expected. The only difference in these that I can see is that the MEPFs with the issue have a value set in the ExternalEmailAddressAttribute.
I have tried to programatically set this value to $Null however i receive the following error:
The external e-mail address $null is not an SMTP e-mail address.
I have also tried the following : set-mailpublicfolder -Identity "MEPF"-ExternalEmailAddress "<not set>"
with the same resultAttempting to use the following syntax -externalemailaddress @{remove=$oldAddress} returns the following error:
Cannot process argument transformation on parameter 'ExternalEmailAddress'.Cannot convert the "System.Collections.Hashtable" value of type"System.Collections.Hashtable" to type "Microsoft.Exchange.Data.ProxyAddress".
At present the only fix that I have for this is to take a copy of the email addresses for an affected public folder, Mail disable it, wait for the object to be cleared, re-enable the public folder as a mail public folder and then re-add the email addresses.
This is ok on an adhoc basis but not for the ~1200 folders that are affected. Especially when from what i can see it should be relatively straightforward to resolve this with a simple PowerShell script.
I do have a case open with MS for this but I am hoping that somebody here can help also.
Thanks
Joe

Ok so i fixed it myself.
The thinking here is that the ExternalEmailAddress was set using the Primary SMTP address while the Public Folders were on premises.
In order to get the required information we ran a script to export all the MailPublicFolder objects which had a value in the ExternalEmailAddress attribute. We exported the Name, ExternalEmailAddress and GUID
We then ran a second script to export the Identity, MailRecipientGuid from Get-PublicFolder -recurse.
The MailRecipientGUID is what ties the Mail Enabled Public folder to the MailPublicFolder object.
Using Excel I then matched the two up and created a csv file with the Identity Attribute from the get-PublicFolder command and the ExternalEmailAddress Attribute from Get-MailPublicFolder.
The following script then used this csv file to first Mail Disable the Public Folder, then Mail Enable the Public Folder.
Once these steps have been completed the final stage is to add the SMTP address back in to the Public folder.
To do this it is necessary to retrieve the new MailRecipientGUID and use it to return the MailPublicFolder for the Set-MailPublicFolder command.
I was happy to use this script after i tested with a small subset of the data. It is provided as is with no guarantee that it will be suitable for you to use and any use of this script is at your own risk.
Script to Automatically fix brokenn Public Folder Objects
Created By: Joe McGrath
Created On: 18/02/2014
$Path = "C:\PublicFolders.csv"
import-csv -Path $Path | ForEach-Object `
Disable-MailPublicFolder -identity $_.Identity -Confirm:$False
Write-Host "Broken Public Folders Now Mail Disabled"
Write-Host "Waiting for commands to be fully processed online - the script will continue in 5 minutes"
Start-Sleep 300
Write-Host "Re MailEnabling Public Folders"
import-csv -Path $Path | ForEach-Object `
Enable-MailPublicFolder -identity $_.Identity
Write-host "Broken Public Folders now enabled"
Write-Host "Now waiting to allow online service to catch up - script will continute in 5 minutes"
Start-Sleep 300
Write-Host "Updating email addresses for broken public folders"
import-csv -Path $Path | ForEach-Object `
$NewPF = get-publicfolder -identity $_.Identity
Write-Host $NewPF.Identity
Write-host $newPF.MailRecipientGuid
$EmailAddresses = $_.AdditionalEMailAddresses
$NewMailPF = get-MailPublicFolder -resultsize unlimited | Where-Object {$_.Guid -eq $NewPF.MailRecipientGuid}
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$FALSE
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddresses $EmailAddresses -EmailAddressPolicyEnabled:$FALSE
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$TRUE
$EmailAddresses = ""
Write-Host "Completed!"

Error when moving Exchange Public Folder Tree Hierarchy

Hello,
I am during the transition from Exchange 2003 to 2007.
At the end of migrating Exchange 2003 to Exchange 2007 I have moved all the mailboxes, Public and System Folders have been replicated and moved, Mailbox Store and Public Store had been removed, Routing Connectors removed ...
I then created new Public Folder Container in Exchange Administrative Group (FYDIBOHF23SPDLT) and I attempted to drag and drop the Public Folder Tree Hierarchy from old Administrative Group to Exchange Administrative Group using ESM 2003.
During this I got the following error:
Access Denied.
Facility: LDAP Provider
ID no: 8007005
Exchange System Manager
Every public and system folders works fine (replicated to Exchange 2007), but the Public Folder Hierarchy is still on Exchange 2003.
Anyone has any idea how to continue decommission of Exchange 2003?
Regards,
Jacek

As I wrote before, when I tried to drag and drop the Public Folder Tree Hierarchy, I used account which had delegated Exchange Full Administrator role in Exchange 2003 and was also member of Enterprise Admins / Domain Admins in AD and Exchange Organization
Administrators in Exchange 2007. According to Sembee suggestion, it is more than needed ...
I think about manual deleting Public Folder Tree Hierarchy object from old Administrative Group (using ADSIEdit) and then recreating the new one in Exchange Administrative Group - using the following steps:
http://blog.bruteforcetech.com/archives/766
But I'm not sure if System Folders will be accessible then. There are many Outlook 2003 in organization, so "old" OAB access is necessary ...
I can take report of permissions for the problematic Public Folder Tree Hierarchy object using dsacls.exe, if needed (there are many ACEs in DACL on them). I can also check Effective Permission for user I used for moving.
But in both cases, I don't have any reference. I mean correct permission set for such object or necessary permission set for user used for moving.
Regards,
Jacek
MCT, MCITP, MCTS, MCSE+M, MCSA+M

Exchange Public Folder Migration - Public Folder Mailbox "LockedforMigration"

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

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

Search in exchange public folder

Hi all. I have sharepoint 2013 and exchange 2010. After configuring search and crawling public folders all works fine, but some links were broken. after googling and reading logs i found that some links was double encoded and given bed request. Looks like
"+" encoded to "%2" and after "%2" to "%252". I add some filters in iis like UrlScan, but it didn't work. Firewall turned off. I will very thankful for any ideas to fix it.

Thanks for answer.
I checked all twice. No results.
It's my html:
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
<head>
<title>Common Item Body</title>

</head>
<body>
<div id="Item_CommonItem_Body">

<div id="_#= $htmlEncode(id + Srch.U.Ids.body) =#_" class="ms-srch-item-body" onclick="_#= showHoverPanelCallback =#_">

<div class="ms-srch-item-icon">
<img id="_#= $htmlEncode(id + Srch.U.Ids.icon) =#_" onload="this.style.display='inline'" src="_#= $urlHtmlEncode(ctx.CurrentItem.csr_Icon) =#_" />
</div>

<div id="_#= $htmlEncode(id + Srch.U.Ids.title) =#_" class="ms-srch-item-title">
<h3 class="ms-srch-ellipsis">
_#= titleHtml =#_
</h3>
</div>

<div id="_#= $htmlEncode(id + Srch.U.Ids.summary) =#_" class="ms-srch-item-summary">_#= Srch.U.processHHXML(ctx.CurrentItem.HitHighlightedSummary) =#_</div>

<div id="_#= $htmlEncode(id + Srch.U.Ids.path) =#_" tabindex="0" class="ms-srch-item-path" title="_#= $htmlEncode(ctx.CurrentItem.Path) =#_" onblur="Srch.U.restorePath(this, '_#= $scriptEncode(truncatedUrl) =#_', '_#= $scriptEncode(ctx.CurrentItem.Path) =#_')" onclick="Srch.U.selectPath('_#= $scriptEncode(ctx.CurrentItem.Path) =#_', this)" onkeydown="Srch.U.setPath(event, this, '_#= $scriptEncode(ctx.CurrentItem.Path) =#_', '_#= $scriptEncode(truncatedUrl) =#_')" >
_#= truncatedUrl =#_
</div>
</div>

<div id="_#= $htmlEncode(id + Srch.U.Ids.preview) =#_" class="ms-srch-item-previewContainer">
_#= previewHtml =#_
</div>

</div>
</body>
</html>

Exchange 2010 Public folder database size grown upto 1.22TB

I have situation to discuss , have three exchange public folder server with 2010Ent edt. One of Pub folder dtabase has been reached 1.22TB . Problem is that we cant increase more storage as its reached over limit. We are unable to do backup as its need to
split in multiple chunk . I cant do offline defrag as if now casue of LUNs limit.
Do someone has such sitaution faced and have any recommendation is this ? I can do create a new PF database. More over I am looking some short of solution to split whole database in two part hosted by two PUB server and each database just do content replication
with each hosting own database on each server.Will really appriciate for any good suggestion. I am open for all other possibilities.
Saty

I have executed whole project to move from 2010 to 20103. Public folder was a big pain. It was 3 copy of 1.32 TB. Plan started from implementation of Archiving tool for exchange.
1- First level pulled all detail reports for PF name,size last access time ,update time ,type9 mail enable or normal.
2- Pull the report and calculate the free white space with all calculation of individual server wise, and get the actual data size ,
3- Target to one PF server holding passive copy of public folders (Not Master copy)
4- Target the public folder keeping 0KB size and create script to delete in non recurs mode so only folders which has size 0 will be delete and rest all be left just like that .
5- later target the folder size keeping huge data and foliter it out with root folder and check out the permission and reach out people if the really need the data .Get the sign off and delete it through recurs script.
If you not put recurs delete it will never allow to delete whole folder in one way.
6- Target folder which data are important and move them to shared mailbox . Using soem restore tool which can export pst of those folder and import into mailbox. Set the permission accordingly. And set Enterprise erchiving policy for that shared.Same above
two exercise need to apply for all public folders.
7- Target those folders which are in use and try to convince and move them to shared mailbox with unlimited mailbox size with EV archiving.
8- And at the end move replica of target server to master copy.
9- Once replica move is complete you can plan to delete the PF data edb file. It wont allow to delete directly as you have to go through ADSIEDIT method only.
10- while same exercise need to do for all other passive copy.
11- Create a fresh edb and now you can move pf replica content to new edb which will help to move actual data with very limited whitespace.
12- And this way whole PF will be in actual size and all junk and unwanted files/data/emails/meetings etc will be removed.
13- There will be one common issue of form created through outlook so you need to import them carefully using default system folder.

Exchange 2013 Public Folder Migration Problem

Hi All,
Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
I have followed the guide for public folder migration here
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders. Administrators can create them
fine from the ECP - just not from outlook.
It also appears some users cannot see some folders that they have permissions to.
Can anyone assist with some ideas to resolve ?
Thanks.

Question?
Are you able to create the Folder in OWA?
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
   LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
My Bad, that's what I was trying to say.
Testing the same thing in the LAB, should have some update tomorrow morning.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Syncronizing a Exchange 2007 Public folder to SP 2010 Caledar

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

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

Cannot change public folder owner in adsiedit to the server_name$ where PF are stored

Hi,
I have migrated PF from Exch 2003 to the Exch 2010 SP2 RU6.
Some of PFs still have the old Exchange 2003 servername as the owner in Security-Advanced-Owner of ADSIEdit.
However when I try to change it to the Exch2010_server_name$ (the one where Public Folders are mounted - I cannot (without any reason). But I can change it to one of the CAS servers, strange isn't it?
I have already tried this using domain admin account and Exchange admin account (both are assigned to Public Folder Management).
Can you help me to set the correct server name (as it is set for new public folders), please?
BR Michal Ziemba

Hi Michal,
Based on my knowledge, we don't need to change the owner of public folder manually when we migrate public folder.
The issue may be related to AD replication. You can run Dcdiag on your domain controllers and make sure you're not having replication problems.
Here is a thread for your reference.
Public Folder Issues - Exchange 2010 after migration from 2003
http://social.technet.microsoft.com/Forums/exchange/en-US/fe0909c1-ee2e-448b-ad89-e8f4ff92b4a9/public-folder-issues-exchange-2010-after-migration-from-2003-insuffaccessrights?forum=exchange2010
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Read MS Exchange "Public Folders"

Hi
I need to read a MS exchange public folder
The structure looks like this in out look
'Public Folders'
--- 'All Public Folders'
--------- 'Development'
--------------- 'Unsubscribe'
I have tried the code below I can see the 'Public Folders' but it returns nothing in the list. I also can't get to the 'Unsubscribe' folder either. Does any one have some code for me to look at that goes multi folders down and reads the emails in the sub folder
Your help would be greatly appreciated
Thanks
Properties props = new Properties();
Session session = Session.getDefaultInstance(props, null);
Store store = session.getStore("imap");
store.connect("server", "user", "password");
Folder publicFolder = store.getFolder("Public Folders/");
Folder[] folders = publicFolder.list();
for (int i=0; i < folders.length; i++) {
System.out.println(folders[i].getName());
}

A few suggestions...
Try the name without the trailing slash ("/"). It shouldn't make a difference,
but it might.
Try the folderlist.java demo program. It will list everything your server knows
about, starting with the "default folder".
Try using the Store.getSharedNamespaces() method and recurse from there
using the list method.

Exchange 2003 to 2010 Public folder Migration issue

I have successfully replicated our Exchange 2003 public folders to our exchange 2010 public folders using the addreplica script in exchange 2010 PS. I have moved all mailboxes to use the public folders on Exchange 2010. A couple of days ago I ran the
"moveallreplicas.ps1", and the command successfully ran and has removed all replica pointers in the exchange 2010 PF database pointing to the exchange 2003 database. In Exchange 2003 ESM, I still have the replication to all the PF databases, and
the 2k3 has not been removed, nor has the public folder instances folder count changed at all. In searching through the logs I am getting this error on the exchange 2003 event viewer for applications about every minute or less.
This is an SMTP protocol log for virtual server ID 1, connection #58254. The client at "xxx.xxx.xxx.xxx" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first ". The full command
sent was "xexch50 1076 2". This will probably cause the connection to fail.
The client IP indicated in the error is a Exchange 2010 server with the HUB/CAS roles loaded onto it. I am not sure if this is related or not.
I see some people have ran the move all replicas from the Exchange 2003 ESM, should I do that now? Is this even something to worry about since all my mailboxes are using the PF on 2010?
Thanks for any assistance!

I have looked at KB http://support.microsoft.com/?id=843106 and
it did not resolve the issue on the Exchange 2003 server or 2010.
Last night I put in the fix for the Event ID 36885, method three of this article http://support.microsoft.com/kb/933430/en-us,
and the errors on both servers seemed to go away, but then have started back up this morning after about seven hours of no errors. I thought the registry entry would fix the issue, and it appears it did, but not sure why it would come back like this. I may
try restarting the servers tonight, but kind of confused how this could still be an issue with the registry entry in place.

Exchange 2010 Public folder permission issue

When i select the public folder and click the permission tab to set the permission, below error message will be pop up. This error message only happen in few sub public folder, another folder without this problem. There are two replica
in different mail store server.
Microsoft Corporation
Microsoft® Windows® Operating System
6.1.7600.16385
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.ConstraintException: Column 'Identity' is constrained to be unique. Value 'gcr.geg.local/Managed OU/Galaxy Corporate/HR&A/Esther
Chan (Corp HR&A)' is already present.
   at System.Data.UniqueConstraint.CheckConstraint(DataRow row, DataRowAction action)
   at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
   at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Int32 position, Boolean fireEvent, Exception& deferredException)
   at System.Data.DataTable.InsertRow(DataRow row, Int64 proposedID, Int32 pos, Boolean fireEvent)
   at System.Data.DataRowCollection.Add(DataRow row)
   at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.AddEntry(DataTable table, ADObjectId identity, String name, MultiValuedProperty`1 accessRights)
   at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.GenerateClientPermissionDataSource(Object clientPermission)
   at lambda_method(ExecutionScope , String )
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateLambdaExpression(ColumnExpression expression, Type dataType, DataRow dataRow, DataRow inputRow)
   at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateCore(DataRow dataRow, DataRow inputRow, IList`1 query)
   at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.FillColumnsBasedOnLambdaExpression(String changedColumn)
   at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.UpdateTable(DataRow row, String targetConfigObject, Boolean isOnReading)
   at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandler.OnReadData(CommandInteractionHandler interactionHandler, String pageName)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.Read(CommandInteractionHandler interactionHandler, String pageName)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataContext.ReadData(CommandInteractionHandler interactionHandler, String pageName)
   at Microsoft.Exchange.Management.SystemManager.WinForms.ExchangePage.<OnSetActive>b__0(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.ActiveDS, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.TroubleshootingTool.Shared, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.RightsManagementServices.Core, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Common.IL, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Sqm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management.SnapIn.Esm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Microsoft.Exchange.Management.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35

Hi,
This issue appears to be related to
data access from their ASp.Net application.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft
Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
FIX: "Exception has been thrown by the target of an invocation"
error message
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.

Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations

I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months. I have followed every link I can find on how to do the migration properly. It will stay in a queued state for hours until the MRS is
restarted. It will then start copying messages. After reaching 28% I get RelinquishedWlmStall as Status Detail. Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)
Status : InProgress
FailureTimestamp :
IsValid : True
ValidationMessage :
OrganizationId :
RequestGuid : ff4af794-f31e-4334-959f-7d6c4ccbe310
RequestQueue : PublicFolders
ExchangeGuid : b12c1f83-c4ae-46bb-a26a-0422d90800e4
Identity : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
DiagnosticInfo :
Report
4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
10.
4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
folders total.
4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
manually by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
can be linked manually by running Enable-MailPublicFolder cmdlet after the
migration completes.
4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
can be linked manually by running Enable-MailPublicFolder cmdlet after the
migration completes.
4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
'96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
'82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
manually by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
complete: 15.
4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
processed.
4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
items loaded. Total size: 149 MB (156,253,810 bytes).
4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
(7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.
ItemsTransferred : 3660
PercentComplete : 25
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.
It never tries to restart. Can anyone please help? The server checks for health all come back ok. I will be more than glad to include further information.

Hi,
Basic on the error message, I notice that public folder migrate slow and display that “Relinquishing job because of large delays due to unfavorable server health or budget limitations” .
If I misunderstand your concern, please do not hesitate to let me know.
Since it is just slow and not failing, please do not stop the batch, it might connect to another server for sync.
Meanwhile, please refer to below link so that get details about Exchange Online migration performance and best practices:
https://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
If the issue persists, please collect the relevant migration report for further troubleshooting.
Thanks
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]
Allen Wang
TechNet Community Support

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

E71 Imap4 Exchange Public Folder Issue

Similar Messages

Maybe you are looking for