Problems moving public folders for 2k3 to 2k7 migration

Hello,
i'm having problems with moving the public folder from the 2k3 to 2k7, following the steps i've found on mig docs and googling for this issue and i cant seem to solve it, letme detail:
There are only 3 user created public folders, all with contacts, they weight less than a MB combined.
So first thing, iin E2k3 ESM i right click the public folder store and select "move all replicas", it works succesfully.
if i expand the pf store and check replicas i see a ton of system folders with 2 replicas.
i also check every user folder, change the replication to always and urgent and resend changes/synch content from 2k3 to 2k7
Now according to migration documents the "pf instances" should empty by itself after some time....
well it's been a day and in fact i see more items than before on the 2k3, if i expand the instances on the 2k7 i see 4/5 folders, none of the user ones!.
I also ran the moveallreplicas.ps1 script.
if i run Get-publicfolder -recurse |fl name,replicas i only get:
Name : IPM_SUBTREE
Replicas : {}the next step is apparantely to move the public folder "folder" itself from the 2k3 admin group to the 2k7, i can do that and it gives no error but i'm worried that if i decommision the 2k3 that it will all fail horribly.
¿whats going on, how can i move this thing for once?

Hi,
Make sure you have added the Exchange 2007 in the Replication tab list of all folders in Exchange Server 2003.
In Exchange 2003, please increase the logging level to Maximum on the diagnostic logging categories: Replication Incoming Messages and Replication Outgoing Messages.
Here is a related article which can help you for your reference.
How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/kb/842273/en-us
Another useful article:
Some Public Folder content is not replicating from Exchange 2003 to Exchange 2007
http://blogs.technet.com/b/dblanch/archive/2009/04/10/some-public-folder-content-is-not-replicating-from-exchange-2003-to-exchange-2007.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2003 - 2010. Moving public folders one at a time

Hi all,
I'm in the process of decomisioning our old Exchange 2003 server (long overdue after what has been a relativly smooth and trouble free transition to 2010). As the first step in the decomisioning process, I'm looking to move the public folders from the 2003
box to the 2010 box. From my understanding there are a couple of ways to achieve this (please correct me if I'm wrong). The first is to add the Exchange 2010 server as a new replication partner, allow for replication of the PFs to occur, and then remove the
2003 partner from the replication partnership. The other option is to use MoveAllReplicas.ps1.
I opted for the first option, but the problem I have is that the initial replication process started to generate a very large number of transaction logs on the Exchange 2010 server, to the point I was slightly conccerned I was going to run out of space on
the volume (our server is backed up nightly at which point the transaction logs are normally flushed).Whilst I know I could potentially increase the size of the volume or turn on cicular logging for the duration of the migration (neither of which is appealing
as it will involve down time), I was wondering if there was a way to move a smaller set of Public folders one at a time with a powershell command, or is it an all or nothing operation? My other option may be to replicate a small subset of folders everyday,
but that just a little painful as there are a large number of child folders with in the structure. Any other suggestions welcome!
Many thanks,
Rob

Hi,
If your Public Folder Database is large, you can use tool like Exfolders or ESM to add replica folder by folder.
A related article for your reference.
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
And it is recommended to replicate public folders off business hours.
Best regards,
Belinda Ma
TechNet Community Support

Moved Public Folders - 4 System Folders wont Remove

I have moved Public Folders from one Exchange 2007 Server to another Exchange 2007 Server using the ./movereplicas script. All Folders have replicated ok, but on the old server which I want to decomission I am unable to remove the public
folder DB because it says not all folders have replicated.
If I run Get-publicfolderstatistics on both servers I am left with 4 system folders on the old server. These seem to have replicated across to the new server ok - the item count is higher on the new server.
I have tried running the script again, but these 4 folders never get removed. The folders are OAB, Store Events which have an item count of 0 on both serversthese two are higher on the new Public Folder DB.
Hope someone can advise
Thanks
Dave

Hi,
If they're system folders you don't need, like those other than SCHEDULE+ FREE BUSY, OFFLINE ADDRESS BOOK and EFORMS REGISTRY (if you use Organizational Forms), then you can delete them.
Based on the description, it looks like the four system folders have replicas on another Exchange 2007 server, you can just delete these system folders.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Downsize Public Folders for Migration to Office 365

To migrate public folders, I have been following this link: http://technet.microsoft.com/en-us/library/jj983799%28v=exchg.150%29.aspx
However, this customer's public folders are exceeding well over 50GB. There are contacts and a calendar. I am looking for assistance/advice on downsizing public folders for migrating to Office 365.
Exchange 2007
Server: Windows Server 2008 Standard

Hi,
To reduce the public folder's size prior to the migration, you can try to delete the old content or split it into multiple smaller public folders.
Here is a related article for your reference.
Public Folders and Exchange Online
http://blogs.technet.com/b/exchange/archive/2013/05/02/public-folders-and-exchange-online.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Public folders for users to identify spam

It looks like it should work, but ...
I have SL server providing IMAP mailboxes for users, and that all works fine. As it is now, for a user to notify SpamAssassin that it didn't classify a message properly, they have to actively redirect the message to the junkmail or notjunkmail account. This is a PITA and a) they can't be bothered and b) the email address to which they're to redirect or forward the improperly classified message is subject to errors.
What I'd like is a pair of public mailboxes that they can just drag misclassified messages to, so I set up a public namespace containing two mailboxes, JunkMail and NotJunkMail. They're visible to all the users I want them to be and the permissions seem right. The plan is to whip up a launchd job to digest the contents of these mailboxes in the middle of the night, much like the stock sa-learn job.
The problem is that when I try to drag a sample email message from my inbox to the JunkMail foler, I get an error that says <bold>Blah blah blah</bold> The IMAP command "UID COPY" (to Public.JunkMail) failed for the mailbox "wherever I drag from" with server error: Character not allowed in mailbox name '.'.
I've tried changing the 'separator' in the namespaces to bot '/' and '.', with no discernible difference in behavior or message. I've set all of the mail logging levels to DEBUG to no avail. I've made the public mail boxes world-writable. Nothing seems to help, or even change the client-side behavior.
If someone more knowledgeable about dovecot and its IMAP configuration can point me in the right direction, I'd appreciate it greatly.
Thanks,
- Ted

This is a followup to let people know how I got it to work.
My supposition is that when dovecot evaluates whether a user can write into a folder it does not do a full group membership expansion to determine the user's rights, so making the folders in question writable by the shared 'mailusers' group (that all human mail users are members of) was not adequate.
Instead, I had to add ACLs to the target folders granting explicit rights to each individual user. My nightly spam-training script uses the approach of stopping the mail server, moving any folders that might contain trainable messages aside, replacing those folders with empty versions of themselves, then restarting the mail server.
I had been using a more elaborate approach that evaluated whether there was anything to process before stopping the mail server, but with the ACL approach that also meant comparing the current group membership with what users had been set on the folders' ACLs. After I had written the script to do that, I decided the slight increase in efficiency wasn't worth the added complexity - bouncing my mail server in the middle of the night isn't even marginally problematic for my users, but YMMV. Instead, by just replacing the folders each night with their ACLs generated from the current group membership, membership changes are incorporated within 24 hours, which is good enough for me.
Anyway, this Bash snippet shows the crux of what I'm doing now:
readonly    SP='[:space:]'
readonly    UserList="$(dscl '/LDAPv3/127.0.0.1' \
    '-read' "/Groups/$UserGroup" 'Member' | sed -En \
    "s!^[$SP]*Member[$SP]*:[$SP]*(.+)[$SP]*\$!\\1!p")"
readonly    ServerStatus="$(serveradmin status mail \
    | sed -En 's!^[^"]*"([^"]+)".*$!\1!p' \
    | tr '[:upper:]' '[:lower:]')"
[[ "$ServerStatus" != 'running' ]] \
    || serveradmin stop mail > /dev/null
for d in "$PublicSpamPath" "$PublicHamPath"
do
    [[ ! -d "$d" ]] || mv "$d" "$d.$ScanSuffix"
    mkdir -m 2755 "$d"
    chgrp "$UserGroup" "$d"
    for n in $UserList
    do
        chmod +ai "$n allow $UserAcls" "$d"
    done
    mkdir -m 2755 "$d/cur" "$d/new" "$d/tmp"
    chgrp "$UserGroup" "$d/cur" "$d/new" "$d/tmp"
done
[[ "$ServerStatus" != 'running' ]] \
    || serveradmin start mail > /dev/null
If this helps, you're welcome.

Problems with Public Folders in Exchange 2010

Last month I upgraded my servers from 2000 to 2010. The route I took for exchange was 2000 -> 2003 -> 2010. Everything went fairly smooth and I have had no real problems until this week. (I have uninstalled the older exchange servers.) I have been
trying to clean out some of the remnants that have been left over from the older servers (for whatever reason the uninstall did not remove the information on the new server). I used ASDI edit to remove some old information that was pointing to the old exchange
server (First Administration Group I think it was called).
After that I upgraded to SP1 and Rollup 1. The Public folder database no longer appears under Organization Configuration, Mailbox. I am not sure if it was there after my deletion or not, so I am unsure if the problem is caused by my deletions or the upgrade.
I followed the instructions found here, http://technet.microsoft.com/en-us/library/bb727370%28EXCHG.80,printer%29.aspx . The CN=Public folders was found in CN=Folder Hierarchies. However
msExchOwningPFTree is greyed out, so I cannot update it. I have tried to delete it and remake it, same thing.
I also get the following events which I am assuming is caused by the Public Folders database not being mounted:
Log Name:      Application
Source:        MSExchangeRepl
Date:          10/28/2010 11:03:51 AM
Event ID:      3154
Task Category: Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sachdc00001.sunshineacres.local
Description:
Active Manager failed to mount database Public Folder Database 1678798462 on server sachdc00001.sunshineacres.local. Error: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error.
Error: A transient error occurred during a database operation. Error: MapiExceptionADPropertyError: Unable to mount database. (hr=0x80004005, ec=2418)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="49156">3154</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-10-28T18:03:51.000000000Z" />
    <EventRecordID>42074</EventRecordID>
    <Channel>Application</Channel>
    <Computer>sachdc00001.sunshineacres.local</Computer>
    <Security />
</System>
<EventData>
    <Data>Public Folder Database 1678798462</Data>
    <Data>sachdc00001.sunshineacres.local</Data>
    <Data>An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionADPropertyError:
Unable to mount database. (hr=0x80004005, ec=2418)
</Data>
</EventData>
</Event>
Log Name:      Application
Source:        ExchangeStoreDB
Date:          10/28/2010 11:03:51 AM
Event ID:      231
Task Category: Database recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sachdc00001.sunshineacres.local
Description:
At '10/28/2010 11:03:51 AM', the copy of database 'Public Folder Database 1678798462' on this server encountered an error during the mount operation. For more information, consult the Event log on the server for "ExchangeStoreDb" or "MSExchangeRepl"
events. The mount operation will be tried again automatically.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="ExchangeStoreDB" />
    <EventID Qualifiers="49156">231</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-10-28T18:03:51.000000000Z" />
    <EventRecordID>42073</EventRecordID>
    <Channel>Application</Channel>
    <Computer>sachdc00001.sunshineacres.local</Computer>
    <Security />
</System>
<EventData>
    <Data>Public Folder Database 1678798462</Data>
    <Data>0855badd-62f3-421f-9175-86cf26891c8a</Data>
    <Data>Store</Data>
    <Data>GenericMountFailure</Data>
    <Data>
    </Data>
    <Data>Store</Data>
    <Data>There is only one copy of this mailbox database (Public Folder Database 1678798462). Automatic recovery is not available.</Data>
    <Data>10/28/2010 11:03:51 AM</Data>
</EventData>
</Event>
Log Name:      Application
Source:        MSExchangeIS
Date:          10/28/2010 11:03:51 AM
Event ID:      9519
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sachdc00001.sunshineacres.local
Description:
While starting database 0855badd-62f3-421f-9175-86cf26891c8a, the following error occurred: 0x972.
Look up of DB Info failed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeIS" />
    <EventID Qualifiers="49158">9519</EventID>
    <Level>2</Level>
    <Task>6</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-10-28T18:03:51.000000000Z" />
    <EventRecordID>42072</EventRecordID>
    <Channel>Application</Channel>
    <Computer>sachdc00001.sunshineacres.local</Computer>
    <Security />
</System>
<EventData>
    <Data>0x972</Data>
    <Data>0855badd-62f3-421f-9175-86cf26891c8a</Data>
    <Data>Look up of DB Info failed</Data>
    <Binary>5B444941475F4354585D00002E000000FF8C170000000000000220000000496340107209000068284010720900003DE900104000060E3DD1401072090000</Binary>
</EventData>
</Event>
Also, the CN=InformationSore is empty. Is this normal?
Now I am assuming I deleted something that I shouldn't have.

Tried that, I get the following when I go to the Public Folder Management Console:
Cannot complete the operation because there isn't an available public folder database on server
And even if I did that how does that help me retrieve my missing information?

Moving public folders from exchange 2003 to exchange 2010 error while moving replicas

Dear All,
i am in the process of migrating from Microsoft Exchange 2003 to Exchange 2010,
i am done with moving all the mailboxes 300 mailbox almost with a 1.5 TB DB with no issues
when i tried all the processes, procedures, instructions and forums to move the public folder or
to use move all replicas from Exchange 2003 to Exchange 2010 i always get errors , now when i try
to open PF Management console from the exchange 2010 server i get it but it is disconnected
then i can choose to coneect to the new server name EXCHANGE2010 with no issues
when i try to expand the default folder and system folder i get the following error.
OAB is set on the new server as default.
when i try to add replica using power shell i get this error:
WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an inst
of an object.
Object reference not set to an instance of an object.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
following error when trying to expand PF on EXCHANGE 2010
Microsoft Corporation
Microsoft® Windows® Operating System
6.0.6000.16386
Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''.
Microsoft.Exchange.Configuration.MonadDataProvider.CommandExecutionException: Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''. ---> System.NullReferenceException: Object
reference not set to an instance of an object.
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.GetMapiPublicFolderDatabasesIdentities(ADSystemConfigurationSession configurationSession, ADObjectId serverId, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ValidateServerContainsPFDatabase(Server server, ADSystemConfigurationSession scSession, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ResolvePublicFolderServerAndUserLegacyDNs(ADSystemConfigurationSession scSession, ServerIdParameter serverIdParameter, String& serverLegacyDN, String& userLegacyDN, Fqdn& serverFQDN,
TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.GetMapiObjectTask`2.CreateSession()
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalStateReset()
at Microsoft.Exchange.Management.MapiTasks.GetPublicFolder.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Close()
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Dispose(Boolean disposing)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.Fill(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.OnDoRefreshWork(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.RefreshableComponent.worker_DoWork(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
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.0.631.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.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, 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.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.Common, 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.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.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, 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.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UmDiagnostics.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Collaboration, Version=3.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Media, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=1.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.HelpProvider, Version=14.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
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Microsoft.Exchange.Data.Directory.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.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
i will be thankful for any assistant.
PF DB is arounf 90 GB with alot of public folders and sub-folders. around 60 mail PF and too many subfolders.

First and the most important thing you need to do is, upgrade exchange 2010 to SP2 and RU5.
Exchange 2010 RTM support is long gone.
http://www.microsoft.com/en-us/download/details.aspx?id=36768
http://www.microsoft.com/en-us/download/details.aspx?id=41480
Your exchange 2010 is still in stogeage ;)
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://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.

Enable legacy public folders for Exchange 2013 prior to migration?

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

I know they've made alot of changes recently in how legacy public folders are handled in Exchange 2013 (mostly CU7), but I haven't had to do anything more than just setting the proper public folder database on the Exchange 2013 databases.
That being said, looking over the article you are not doing any moves, and it looks eerily similar to this blog post:
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
So I don't think this would hurt Public Folder access for your users in your legacy environment.
Did you deploy CU7? If so, then do what both articles say. If not try using Set-MailboxDatabase -Identity <2013 db name> -PublicFolderDatabase <PF DB NAME>
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Public Folders after 2007 to 2010 Migration

I am unable to move public Folders from 2007 to 2010. Will not replicate nor can I create or use any new Public Folders on the 2010 server. Every other part of the migration has been completed and the system is working well.
Is there anything that I might be missing in order to move Public Folders to 2010?

Hi,
Please check the msExchHomePublicMDB value in ADSI Edit:
1. In Adsiedit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
2. Right-click the listed database > Properties.
3. Make sure the msExchHomePublicMDB value is pointed to the Public Folder database in Exchange 2010 instead of Exchange 2007.
Additionally, please use the ReplaceReplicaOnPFRecursive.ps1 script to move all the replicas of a public folder subtree from one server to another server. For more information about Public Folder migration from Exchange 2007 to Exchange 2010, please refer
to:
https://technet.microsoft.com/en-us/library/bb331970(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

CSS problem using different folders for different files

So I am trying to organize my files into different sections
so that updating will be easier in the future. However right now,
when I create a file in a new folder, my drop downs quit working on
the files inside the folder and some of my css (mainly the css in
my IE conditional statements). My drop downs do work if I put a
copy of the css that controls the drop downs into that folder. The
thing is, if I ever want to update the css, I want to update it in
only one spot rather than in ever folder that I had to copy it
into. How do I get my folder files to work from the css files that
I created inside my local root folder?

I managed to slove this by creating symbolic link to the new location on filesystem.
I was hoping there was some more elegant solution for moving backup sets.
Thanks,
-- dragisa
Ok I understood you. You have to restore your backup
sets in the same location where RMAN backuped them
because that information is stored in the catalog.
In fact, if you remove the backup sets from the disk
, they get "Expired Status" and if you restore them
to disk the status is going to be "Available". Test
it!!!
To carry out this you have to use crosscheck
command.
Joel Pérez

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

Permissions problem: Public folders/Shared Calendars across domains with Linked accounts

I have a linked mailbox that is accessed by an account in a trusted domain. The account can access e-mail, send e-mail, free-busy search, etc, just fine. However, there seems to be a permissions issue with the public folders and shared calendars.
When trying to access the public folders for which permissions have been assigned to the linked account from the trusted domain account, I get an error, or just can't see the folders. The only way I can view public folders is by setting default permissions
on the folder to 'Read'.
I've found some other threads that reference this problem, and a blog that no longer exists as the solution:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrclientslegacy/thread/5fdf4cd7-3543-4b5d-94cc-317446ddaa46
If anyone has any ideas or the solution that was shown in the above referenced blog, I'd be very grateful!
-shane

Hi,Shane,
I believe you can try James' suggestion in the link
http://social.technet.microsoft.com/Forums/en-US/exchangesvrclientslegacy/thread/6c88569d-e693-46f4-a8fa-e1f9e5b6234e/ to get it solved.
Per the
Detecting and Correcting msExchMasterAccountSid Issues it says,
Active Directory does not enforce simultaneous performance of all these tasks, nor does it enforce removal of the Associated External Account or
msExchMasterAccountSid if an Active Directory account is re-enabled.
Regards,
Sharon
Sharon Shen
TechNet Community Support
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.

Announcing Office 365 compliance toolset for public folders

Announcing compliance toolset for public foldersWe are pleased to announce that the Office 365 archiving and eDiscovery toolset is being extended to include public folders. Customers can now place public folder content on hold to preserve it for legal or regulatory requirements. They can perform eDiscovery functions on public folder data, including search, preview and export. Entire public folders or specific content (based on keywords) can be preserved immutably. They can delete aged items out of public folders. And all administrative activities on public folders are fully audited. Throughout all these operations, users can continue to interact with public folder data without any change in their experienceTo perform an eDiscovery search on public folders, you simply specify “public folders” as the source. If you choose to put public...
This topic first appeared in the Spiceworks Community

Hi,
Please see the step 1 in the following article:
Configure Legacy On-Premises Public Folders for a Hybrid Deployment
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx
Thanks,
Simon Wu
TechNet Community Support

Exchange 2003 to Exchange 2010 Public Folders

Hi Gurus, I’m in the process of moving public folders from Exch03 to Exch2010 and I have some clarifications before I proceed with this task. As I have understood the replication process between public folders working in a multi-master environment, I still
need some deep understanding. Okay, the task is to ensure that we don’t lose any PF when I remove the last Exch03 where there’s a lot of PF residing. From my understanding, these PFs found at Exch03 are only replicas from Exch2010. From testing I can verify
that the Outlook clients are looking at Exch2010. The way I tested this is by creating a test PF from Outlook and it did reflected on Exch2010 PF. Looking Exch03 for a couple of days, the test PF never reflected there so I'm just just assuming that there's
no replication happening between Exch2010 and Exch2010.
Please verify on this. Does it mean that Exch2010 is not replicating to Exch03?
If yes, if I remove the PFs from Exch2003 without moving the replicas first to Exch2010, like plainly removing them for decommission, will that delete/remove the PFs on Exch2010?
I have a feeling that it don’t because the PFs I’m creating/deleting at Exch03 are all replicas and I don't see any of the PFs that I deleted at Exch03 to also get deleted at Exch2010. More likely the PFs I'm creating at Exch2010 are not replication across
to Exch03 and therefore removing these PFs at Exch03 should not affect the PFs at Exch2010.
Please confirm on this before I proceed.
Note that I've already taken copy of these Exchange servers because these are all VMs.
Thanks....

Hi,
When you add Exchange 2010 to the replica list on Exchange 2003 server, it will replicate the Exchange 2003 Public Folder hierarchy and content to Exchange 2010, not from Exchange 2010 to Exchange 2003.
You can remove public folders on Exchange 2003 without affecting the public folders which have been replicated to Exchange 2010.
Before you decide to remove Exchange 2003 server, I recommend you put the Exchange 2003 server offline temporarily to check if Exchange 2010 works well.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrate Large Items in Public Folders - OnPremise

Hi,
we are currently in the progress of migrating more and more customers to Exchange 2013. Now there is a limit for large Items within public folders. We do know that we have large items and it is OK to wait for the replication to be done but how can we also
migrate those large items?
For instance within the public folder Migration-Request log we find:
15.06.2014 22:28:37 [EXCHANGE] A large item was encountered: Item (IPM.Note) Subject:"MESSAGESUBJECT",
Size: 22.69 MB (23,795,978 bytes), Folder:"PF Folder Name"
Now I'm aware of the switch -LargeItemLimit but with that we will loose those large items. I haven't found any switch to enable the move of those large items - anyone an idea to also get those items moved to modern public folders?
Thanks!
Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

Hi Peter,<o:p></o:p>
<o:p> </o:p>
As I know, if we have too many large items
within the Public Folders being migrated, the migration may fail with error
message like “TooManyLargeItemsPermanentException”. If the large
items can be copies without any issue, please just wait for the replication, I
believe the replication will not take too much time(always be copied within
10-15 minutes).<o:p></o:p>
<o:p> </o:p>
If we have too many large items that can’t
be migrated, please try to set the migrated request attribute “LargeItemLimit”
to 0(0 means it will not lost any large items). If issue persists, since it
can’t replicate so much large items, we need to specify the “BadItemLimit”,
“AcceptLargeDataLoss” “LargeItemLimit" attributes. So please first export
the public folders that have large items to PST file(login Outlook with an
account with access to all the public folders and export the public folders),
then start a new migration request with the “BadItemLimit”, “AcceptLargeDataLoss”
“LargeItemLimit" attributes, it will skip the large items. After that, we
can export the PST file with contains the large item back to the public
folders.<o:p></o:p>
Regards, Eric Zou

Problems moving public folders for 2k3 to 2k7 migration

Similar Messages

Maybe you are looking for