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

Similar Messages

Exchange 2010 - visibility of items in Public Folders

Hello all,
I already posted this question to the German Exchange 2010 forum, but have not gotten an answer yet. So I hope to be more lucky in the English forum.
Environment: Exchange 2010 SP3 RU4, 2 replicas for Public Folders, Outlook 2007 cache Mode
Problem:
Some of our users have a phenomenon when working with mail enabled Public Folders:
User has the focus set to Public Folder A, an email is sent there (and correctly delivered) but remains invisible to the user. When he changes the focus to point to his inbox or to Public Folder B and directly changes back to folder A he can see the email.
Other users can see the email directly on delivery without leaving the folder first.
When an affected user adds Public Folder A to his Public Folder Favorites he can see that an email is delivered from the change in numbers of unread mails (number in brackets behind folder name).
I already checked the Exchange server to see if there is a replication related problem (though the default Public Folder DB is the same for all mailbox databases). Even after a successful replication an effected user does not see the email unless he leaves
the folder and re-opens it.
As the problem does not affect all users having permissions to this folder I picked one affected user and tried to remedy the issue as follows:
- deleted the existing Outlook profile and re-created it => without success
- deleted the user profile and re-created it => without success
We use Outlook Cache Mode (set by policy, so the user cannot deactivate it) but there is no Public Folder data downloaded.
When I create a new mail enabled Public Folder to test the scenario with an affected user everything works without problems, he can see an email on delivery.
As far as I know this problem occurs with only two folders (and for both folders only a few users are affected - different users for each folder) I do not know what else to do. Can someone please give me a hint where to look at? Thanks in advance.
Kind regards,
Klaus

The user is caching the public folder. When he changes the focus and goes back, it tells Outlook to update. In my experience, I've seen that Outlook only gets the update notices for the primary mailbox, so cached shared mailboxes are generally
rarely updated. We have stopped caching shared mailboxes for this reason and others. Think of the following scenario:
Ten different users perform actions on items in a shared mailbox
When they first get the message, they move it to a subfolder in the mailbox (so it won't be there for other users)
Since users are working in Cached mode, they will see an out-of-date image of the mailbox - they will move the item in their copy of the mailbox, but that won't be reflected in the other mailboxes until their copy updates to the server, then the server updates
the other copies. Talk about being lagged ...

Finalising the migration of Exchange 2003 public folders over to an Exchange 2010 environment

After migrating all the user mailboxes, I set up replicas of the Public Folders which I have been running for several weeks.
Once everything had been replicated, using System Manager on the Exchange 2003 server, I removed the source replica server from the list (aka the Exchange 2003 server).
Is this step sufficient to move the replicas over?
Under the First Storage Group -->Public Folder Store do I need to run the
Move All Replicas command? Will this generate a lot of traffic given that I have ran replication for a number of weeks?
I saw somewhere some Exchange 2010 a similar Powershell command .\MoveAllReplicas.psl as well.
I have updated the offline address book, carried out the Address List Conversion and Recipient Polices.
If everything is in order, I am going to run the uninstall on the 2003 server.

After verifying that all the public folders are been replicated, I carried out the following:-
On the Exchange 2003 server under System Mangager > First Storage Group, I issued the command Move All Replicas over the weekend.
When I came back in today I could see the contents of the Public Folders
are now empty.
However, the Public Folder Instances still appears to have content. Is this normal?
On the Exchange 2010 server I have since issued the MoveAllReplicas.ps1 script to see if this will make any difference.
In addition when browsing the Default Public Folders via EMC, if I attempt to Update Content on any of the Public Folders I get the following error:
Cannot start replication against public folder....
MapiExceptionNoReplicaAvailable: StartContentReplication failed.

Migrating 2003 to 2010 - public folders - stuck in SmtpRelayToTiRg queue?

I'm in the process of migrating Exchange 2003 over to 2010. Both systems are DCs (2010 running on server 2012). The routing group connectors (which I believe this queue relates to) are in place. All the user mailboxes and mail flow has been migrated over
to 2010 already, users have been happily emailing internally and externally as normal for a few days now, and I wish to shut 2003 down. I've just moved over the OAB and followed instructions for moving public folder replicas which I found here : http://exchangeserverpro.com/migrate-public-folders-from-exchange-2003-to-exchange-server-2010/
The process began successfully about 12 hours ago, and after a while I noticed some of the PF instances from 2003 appearing over on 2010. But it hasn't progressed in a long time, with only a few of the instances having appeared on 2010, and none of them
have disappeared from 2003. Then I noticed a queue suddenly building up on 2010, under "SmtpRelayToTiRg". There's over 100 messages in there, and they're all apparently destined for 2003 but are unable to be delivered. This queue was definitely not
there before I began the PF "move all replicas" process. So I've got the process apparently stuck, and a queue building up. What can I do to fix this? Thanks in advance :)

Hi Statick,
Few days ago even I faced the same problem when I migrated from 2003 to 2010.Long queue got built in my test mailboxes and all mails stuck and were not getting delivered. When I was
trying to resolve the issue, I found that server was not able to deliver because it was not able to route correctly. This problem "SmtpRelayToTiRg queue"
generally arises in public folders while moving all replicas.
So in order to fix this problem, I just added IP address of new Exchange server 2010 and complete queue vanished in few minutes.
I hope this will work for you.

Exchange Online, Outlook 2013 - Copying large emails to public folders takes a long time

We are using Office 365 and when copying a large email (with attachment) to a public folder in exchange online, the copy takes a long time. Outlook does not let you do anything until it's finished coping. This is different to other folder
behavior in outlook where the sync with EO would happen in the background. Is there a way round this? It's really frustrating to copy a load of emails to a public folder.
Thanks.

Hi,
I recommend you ask in office 365 forum, there are more experts to help you:
http://community.office365.com/en-us/f/default.aspx
Thanks.
Niko Cheng
TechNet Community Support

Public folders recover deleted items

1) do public folder databases have a "recover deleted items" option, as standard mailboxes do? i.e. if a user inappropriately deletes an item from public folders, can it be recovered easily, or would it need to be recovered from a backup?
2) how can you get a report of which users can add files to the public folder databases, and which users can delete files/folders in the public folders..

Hi,
For the first question, yes, user can restore the folder by using "Recover deleted items" within Outlook so long as the item is not over the age of the retention period. If the user is unable to do this for some reason, ExFolders can also be used to recover
public folder items.
For the second question, you can use the
Get-PublicFolderClientPermission cmdlet to retrieve the user permissions for a public folder. For more information about public folder permissions, please refer to
Understanding Public Folder Permissions.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Public folders in Mixed Exchange environment

We are running
- Exchange 2007 - a LOT of users and a LOT of PF
- Exchange 2010 ( currently very limited )
- Exchange 2013 - about 2000 users
The Exch 2010 environment was pretty much stood up and had 30 pilot accounts on it before we decided to go to Exch 2013 instead/ These account have since been migrated to Exch 2013, so it is currently VERY LIMITED use.
We have a large number of Public Folders in Exch 2007. We do not plan on using the Exch 2013 model of shared mailboxes, but are looking to create the Public Folders in the Exch 2010 environment so we can close down Exch 2007.
The bulk of my users are still on 2007, but I have a couple thousand already moved to 2013. All users can access the Public Folders on Exch 2007.
We have not created any Public Folders in Exch 2010 yet. Practically all the posts I read state to enable replication for the 2007 folders to get them to 2010, but what about NEW folders. If I create a new folder on Exch 2010, without configuring replication
to 2007, will the Exch 2007 and Exch 2013 users be able to access it?
Tom

For Exchange 2010 or Ex2007 you will need to setup the replication but for Exchange 2013 it is different.
what is your plan,, do you want to keep them on 2013 or 2010 or you want keep the mix environment?
If I create a new folder on Exch 2010, without configuring replication to 2007, will the Exch 2007 and Exch 2013 users be able to access it? Yes you can still access them. You will need to setup the database for the default public folders.
Where Technology Meets Talent

Outlook 2010: show subfolders in Favorites for a folder in Public Folders

I have a folder in Public Folders / All Public folders that I would like to see in my mail items favorites. I right clicked on it, clicked "Add to Favorites" and selected the options to show subfolders (i.e. "Add subfolders of this folder").
It then shows in the Public Folders / Favorites and shows subfolders there. But, when I right click on the item in Public Folders / Favorites to add it to the mail item Favorites (Show in Favorites), there is no option to include subfolders and the subfolders
do not show in the mail items Favorites. Any ideas?
Thank you.
Jerry

Hi,
Tested and I can confirm this is not possible in current versions. However, if you want to switch to folder list quickly when you are in Favorite folders, press CTRL+6 for workaround. Thanks.
Tony Chen
TechNet Community Support

Mail-enabled Public Folders not showing as enabled in PFMC or EMS

Good morning
I have some PF's that are mail enabled, but running the Get-PublicFolder cmdlet shows "mailenabled" attribute as False. Also, in the PF Management Console, the folder shows as not mail enabled (with an option to enable it).
I found this thread that seems to be related:
http://social.technet.microsoft.com/Forums/exchange/en-US/918aad03-c96f-4023-89cc-ec2c66e51b93/mailenabled-public-folders-not-showing-as-mailenabled?forum=exchangesvrgenerallegacy
I'd like to do some testing, but recreating this issue with a test PF is actually really hard.
Does anyone know a way to force that "mailenabled" attribute to False after mail-enabling a PF? I can't find any ADSI attribute that is obvious. I changed MsExchRecipientTypeDetails to <not set> but that didn't do it...
**UPDATE** I just found out that msExchMailboxGuid is missing from that object. Does anyone have any kind of suggestion for how I can find the Guid of the mailbox that is no longer associated with this PF?
**UPDATE 2** I have found other PF's that are missing this attribute, but they are not displaying any symptoms. They are showing as mail enabled in the EMS and PFMC. So I guess this isn't a required attribute.
Could anyone explain the purpose of this attribute for mail-enabled public folders? I just assumed it was required.
Thanks!

Hi,
Do you migrate these mail-enabled public folders from previous Exchange server to Exchange 2010?
Please check if you can see the SMTP address for mail-enabled public folders via Properties of Public folders.
Please check if they show in the Microsoft Exchange System Objects in ADUC.
Besides, I recommend you mail disable the public folder and then mail enable it again to check the result in the Public Folder Management Console.
For a mail-enabled recipient, a minimum set of attributes is required to make all Exchange components work properly. For example, a mail-enabled entry (a user, contact, group, or public folder) has to have at least these attributes: mailNickname, legacyExchangeDN,
and displayName. Without the mailNickname attribute, an object is not considered mail-enabled.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

SBS2003- SBS2011 migration - public folders still replicating...

Doing a SBS2003 to SBS2011 migration using the MS method. All is going well so far except the public folder replication is taking forever. I've done all the tricks like increasing the replication priority and limits but it's still going (I think,
anyways, it's hard to tell sometimes). The public folder instances still shows several pages of folders although about two thirds of the folders have moved so at least it's working (I hope). A few questions regarding my situation:
1) Is it OK to execute the "Move all replicas" command in SBS2003 ESE again? Or should I goto the SBS2011 and try the MoveAllReplicas.ps1 exchange powershell command?
2) Can I move onto the next steps of moving the OWA and moving the actual mailboxes? It would save me time if I could just continue and get back to this later.
3) Any other tips on how to compare the two public folder stores and be sure they all got transferred?
Thanks.
-- Al

The replication takes time if you have a lot of public folders. Good you have it working though, since you said most of the folders have moved over.
1) Yes, it is safe, go ahead. The powershell command in destination doesn't work with the legacy source server as I recall.
2) Yes, you can move mailboxes and public folders at the same time. Go ahead and proceed and let the PF's replicate in the background
3) The folders are transferred properly when they disappear from the SBS2003 ESM PF instances. To see the status of the migrated folders in the target server, get a script from here:
http://blog.mikewalker.me/2013/05/exchange-2010-public-folder-replication.html. But the move needs to be initiated and controlled from the source ESM.
Additional tips:
- if you think the replication has stalled, you can debug it by enabling logging on the Default SMTP Connector in the target server. If you see replication related messages in the logs, the replication should be working.
- check that the target message size limits (in SMTP connector and in database) are not preventing the replication if you have large items in your PF database
- sometimes the values in the source server PF replication settings are blank. Set default values + always run if that is the case
- sometimes it helps with some folders that won't move, if you go to destination server EMC and mail disable them.
- redoing "move all replicas" and a reboot of the source helps occasionally too

Issue with migration of Public folders from Exchange 2010 to Exchange Online.

We are trying to migratie the Public folders structure of one of our clients and are running in an error during migration.
We are following the steps provided by
https://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
But after creating the New-PublicFolderMigrationRequest the migration request fails (within 15 minutes) with TooManyBadItemsPermanentException. The following errors are reported.
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Denbosch""
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Eindhoven""
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Enschede""
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Groningen""
23-1-2015 20:59:17 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Hoofddorp""
23-1-2015 20:59:45 [AM2PR02MB0370] Fatal error TooManyBadItemsPermanentException has occurred.
","30-12-2114 20:55:36","New"
With the report logs, we gathered the following information (for every folder that is "corupted")
Timestamp         : 23-1-2015 20:59:17
FailureType       : MapiExceptionPermanentImportFailure
FailureCode       : -2147467259
MapiLowLevelError : 0
FailureSide       : Source
FailureSideInt    : 1
ExceptionTypes    : {Exchange, Mapi, DataProviderPermanent, MapiImportFailure}
ExceptionTypesInt : {1, 30, 102, 43}
Message           : MapiExceptionPermanentImportFailure: Data import failed --> Save on the folder partially succeeded.
                     Result = PartiallySucceeded, Property: [0x3fc90102] , PropertyErrorCode: AccessDenied, PropertyErr
                    orDescription: .. Error code = PartialCompletion (0x00040680)
MessageData       :
DataContext       : --------
                    Operation: ISourceFolder.CopyTo
                    Operation: ISourceFolder.CopyTo
                    OperationSide: Source
                    Outlook Anywhere Public Folders (/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT
                    )/cn=Recipients/cn=sysadmin)
                    PropTags: [count:23, 0x360f000d(ContainerContents); 0x3610000d(FolderAssociatedContents); 0x360e000
                    d(ContainerHierarchy); 0x61af0102; 0xe080003(MessageSize); 0xe230003(InternetArticleNumber); 0xff40
                    003(Access); 0x360a000b(SubFolders); 0x36170003(AssocContentCount); 0x65e00102(SourceKey); 0x65e101
                    02(ParentSourceKey); 0x65e20102(ChangeKey); 0xe270102(NTSD); 0xf000102(FreeBusyNTSD); 0x3fe00102; 0
                    x3fe0000d(AclTable); 0x3ffe0102; 0x3fe1000d(RulesTable); 0x3fe10102; 0x66980102(ReplicaList); 0x663
                    b0102(AddressBookEntryId); 0x671d0102(PfProxy); 0x671f000b(PfProxyRequired)]
                    Folder: 'Public Root/IPM_SUBTREE/werkbevestigingen', entryId [len=46, data=000000001A44739
                    0AA6611CD9BC800AA002FC45A0300E588060DE94CBC42AA16C57D7D69B8D400000093A2A60000], parentId [len=46, d
                    ata=000000001A447390AA6611CD9BC800AA002FC45A0300E588060DE94CBC42AA16C57D7D69B8D40000000000010000]
DataContextData   :
StackTrace        :    at Microsoft.Mapi.MapiExceptionHelper.ThrowImportFailureException(String message, Exception inne
                    r)
                       at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesF
                    lags copyPropertiesFlags, Boolean useCopyProps)
                       at Microsoft.Exchange.MailboxReplicationService.MapiSourceFolder.Microsoft.Exchange.MailboxRepli
                    cationService.ISourceFolder.CopyTo(IFxProxy destFolderProxy, CopyPropertiesFlags flags, PropTag[] e
                    xcludeTags)
                       at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.<>c__DisplayClass2.<Microsof
                    t.Exchange.MailboxReplicationService.ISourceFolder.CopyTo>b__0()
                       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(Action operation)
                       at Microsoft.Exchange.MailboxReplicationService.ExecutionContextWrapper.Execute(Action operation
                    , Boolean measure)
                       at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.Microsoft.Exchange.MailboxRe
                    plicationService.ISourceFolder.CopyTo(IFxProxy destFolder, CopyPropertiesFlags flags, PropTag[] exc
                    ludeTags)
                       at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.<>c__DisplayClass12.<CopyFolde
                    rProperties>b__d()
                       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.ProcessKnownExceptionsWithoutTracing
                    (Action actionDelegate, FailureDelegate processFailure)
InnerException    : RopExecutionException: Save on the folder partially succeeded. Result = PartiallySucceeded, Propert
                    y: [0x3fc90102] , PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. Error code = Partia
                    lCompletion (0x00040680)
UnknownElements   :
UnknownAttributes :
Does someone has a tip for further troubleshooting this issue?

Hi,
There are a lot of corrupted items. You can try raising the baditemlimit to 999 to workaround this issue
Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -baditemlimit 100
To resumed the PublicFolderMigrationRequest
Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Simon Wu
TechNet Community Support

Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

Exchange 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName                         : EXCHANGE2007SVR
SSLOffloading                      : False
ExternalHostname                   : legacy.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             :
EXCHANGE2007SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/31/2013 4:08:04 PM
WhenCreated                        : 7/18/2008 10:56:46 AM
WhenChangedUTC                     : 12/31/2013 9:08:04 PM
WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ServerName                         :
EXCHANGE2013SVR
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/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                             : EXCHANGE2013SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 1/7/2014 11:29:05 AM
WhenCreated                        : 12/31/2013 1:17:42 PM
WhenChangedUTC                     : 1/7/2014 4:29:05 PM
WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Exchange 2010 - Exchange 2013 permanent coexsistence to avoid migration of Public Folders

Hi Guys,
I was hoping to get some opinions/ advices regarding the case explained below.
The company I work for has a medium-sized Exchange 2010 infrastructure that consists of several geographically dispersed 2-node DAGs and corresponding CASArrays. It hosts about 1000 mailboxes in total and large public folder database that is replicated on
every mailbox server in the environment. All users are using Outlook 2010/2013.
There is a business drive to perform migration to Exchange 2013. However, migration of the Public Folders is not feasible because of the lack of multimaster replication, the complicated migration process and several other limitations in Ex2013 PFs.
To work around this issue while still performing the migration I am considering the following scenario:
Deploy Exchange 2013 servers in the organization
Migrate all mailboxes to Exchange 2013 servers
Don't ever start migration of Public Folders (leave one Exchange 2010 mailbox server in every location for hosting the Public Folder database)
Keep the coexistence permanently (with mailboxes on 2013 and public folders on 2010)
What do you think of this setup? Do you see any issues with such long-term coexistence?
Thanks.

Hi,
You can leave the public folders on Exchange 2010 if you can’t migrate them to Exchange 2013. Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can’t access public folders on Exchange 2013.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

2010 - 2013 Migration of Public Folders blank spaces in Public Folder names

So I found the problem that I was running into with this thread:
http://social.technet.microsoft.com/Forums/en-US/466106c8-33a4-4474-83eb-2f6451e0d4eb/2010-2013-public-folder-migration-failed-property-expression-isnt-valid?forum=exchangesvrdeploy , however the question I have is a bulk solution for this problem.
The customer I am working with has just shy of 200GB of Public Folder items with many, well organized public folders that they have been using for many years. I am trying to finish up their migration to 2013 and the solution of ADSI Edit removing blank spaces
is not going to be a good option, it would add days to the migration and many hours of labor.
What I am looking for is to see if there is a way to remove these spaces in a bulk or automated fashion. It may be asking a lot but it will save MUCH time and effort. If there is anyone that has any ideas I would love to hear them.
Thanks,
Joe

I ended up opening a support case with MS to resolve this issue. The issue took us through a few different things, on our Get-PublicFolders we had to add the -ResultSize Unlimited flag. He had a modified script that enumerated all of the special characters
and performed a replace like the script in the prior link had performed.
From there we also had another issue with trailing blank characters. For that we had a three step process.
1. Get the list of Public Folders that were Mail Enabled
2. Disable Mail for all Public Folders
3. Enable Mail flow to the above Public Folders that had mail flow going to them.
Finally I was able to get the public folders to migrate.

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

Migrate Large Items in Public Folders - OnPremise

Similar Messages

Maybe you are looking for