PF Migration, Multiple Databases (Exchange 2010 to Exchange 2013)
Hey All
We have 3x Public Folder Databases in our exchange environment, I have successfully migrated one of the public folder databases over and see all of your content.
My question is this:
Do I need to run the migration process for each database? or if I run it for one database will that migrate all Public Folder data over to 2013?
Thanks,
Robert
Robert
Hi Robert,
The key point here is to collect and migrate all public folders from PF databases. In most cases several PF databases just have replicas of the same Public Folders, so no need for processing each database specifically.
Enumerate all Public Folders you have in previous Exchange version, compare the list to the Public Folders you have migrated to Exchange 2013 using the most up to date source. If both lists match each other - you have migrated all necessary public folders
and you don't need to process other PF databases.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru
Similar Messages
-
Migrate mailboxes from Exchange 2013 to Exchange 2010
Hello,
We have a merger and would like to know if it is possible to migrate mailboxes from Exchange 2013 to Exchange 2010 in a cross-forest scenario.
Or should we first upgrade destination Exchange 2010 to 2013?
PeterisHi Peteris,
Based on my tests, we can move mailboxes from Exchange Server 2013 to Exchange server 2010. You can use the Prepare-MoveRequest.ps1 script in the EMS to prepare mailboxes for cross forest moves.
For more information about it, here is a helpful article for your reference.
Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Mailbox migration between two Exchange 2013 servers is horribly slow
Hi,
when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
are next to each one, same VLAN, same switch. Just migrating between databases.
When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
I have also checked MsExchangeMailboxReplication.exe.config on both servers:
MaxActiveMovesPerSourceMDB="20"
MaxActiveMovesPerTargetMDB="20"
MaxActiveMovesPerSourceServer="100"
MaxActiveMovesPerTargetServer="100"
MaxTotalRequestsPerMRS="100"
Do you have any idea where to look why only 1 mailbox is migrating at once?
ThanksHello,
For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
the AllowLargeItems parameter.
Here are some articles for your reference.
New-MigrationBatch
http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
Exchange 2013 Local Mailbox Moves
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support -
How to migrate Zimbra to Exchange 2013?
Dear All,
Last year, we migrated Exchange 2010 to Zimbra and found it was difficult to handle.
So we want to move back to Exchange 2013. Exchange 2013 and Zimbra may co-exist in our organization.
We will deploy two Exchange Server,CAS+Mailbox.
We are considering if put Exchange as the smarthost.
Anyone has idea?
Besides, is there any wonderful migration tool?
Xiu
Hey, I am backHi ElenaNorge,
According to your description, I understand you want to migrate from Zimbra to Exchange 2013 and deploy co-existence environment.
If I misunderstand your concern, please do not hesitate to let me know.
I notice that you haven’t uninstall Exchange architecture from your environment, can you power on the previous Exchange 2010?
I find an article about your question, for your reference:
https://social.technet.microsoft.com/Forums/en-US/b85d4c49-2918-4dc3-80b7-87820f4e5ffa/zimbra-8-to-exchange-2013-migration-suggestions?forum=exchangesvrdeploy
“exporting all data from Zimbra and importing them into new Exchange 2013 is the best way to performing such this migration”
Besides, this may be related to Zimbra. Please contact the product provider so that you can get more professional suggestions.
Best Regards,
Allen Wang -
ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!
Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
As you can see from the error above ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
virtual folders?!
What I’m missing here?! Please help.Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
To check whether inheritance is disabled on the user:
1.Open Active Directory Users and Computers.
2.On the menu at the top of the console, click View > Advanced Features.
3.Locate and right-click the mailbox account in the console, and then click Properties.
4.Click the Security tab.
5.Click Advanced.
6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
Ref:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
Also check the Virtual directory authentication
Microsoft-Server-ActiveSync
•Basic authentication
•SSL required
•Requires 128-bit encryption
Ref:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
Check the IIS log if you are able to find any error message on it
Exchange Queries -
Duplicate Contacts when migrating mailboxes to exchange 2013 SP1 CU7
Hello,
We started to notice that when we move a user from our legacy exchange 2007 to exchange 2013, the contact list appears twice for users. I heard CU6 was suppose to fix this issue but we went ahead and downloaded the latest version and we are still seeing
this. Can anyone provide guidance on how to stop this for the remaining migrations?
ThanksHi Joey,
I'm back : )
According to your description, I know that the contact list appears twice for users after moving users from Exchange 2007 to Exchange 2013.
I notice that you want to install CU6 to fix this issue, based on my knowledge, CU6 can cause an known issue when you are using Exchange 2007 and 2013 coexistence and query mailbox move request via EMS. However is known issue has fixed in CU7, I suggest
install CU7 for testing.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support -
Migrate clients from Exchange 2013 to a different Exchange 2013
Hi,
We are planning to migrate an Exchange 2013 instance to a centralized one. The question is how to deal with the Outlook OST mail files left over from the old instance and were wondering what best practices in this regard there may be.
Thanks in advance for any advice you can provide.Hi,
Do you mean you want to migrate mailbox from one Exchange server to another Exchange server? If it is, we can directly move the whole mailbox to another mailbox server instead of Exporting/Importing a mailbox to PST file.
If you want to migrate a large number of user mailboxes, we can
specify a CSV file when you use the Exchange admin center (EAC) or the New-MigrationBatch cmdlet in the Exchange Management Shell to create a migration batch.
Here are some detailed information about mailbox moves in Exchange 2013:
http://technet.microsoft.com/en-us/library/dn170437(v=exchg.150).aspx
Move Mailbox in Exchange Server 2013
http://msexchangeteam.in/move-mailbox-in-exchange-server-2013/
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.
Thanks,
Winnie Liang
TechNet Community Support -
Unable to migrate Cross Forest Exchange 2013 to Exchange 2013
I am unable to migrate mailboxes from an on prem (same physical virtual host) to an on prem (same physical virtual host) cross forest.
MRSProxy is enabled on both the target and the source.. and a migration endpoint is enabled on the source. I can succesefuly prepare-moverequest on the target, but when I perform
PS] D:\Exchange\Scripts>New-MoveRequest -Identity [email protected] -Remote -TargetDatabase "DomainCorp" -RemoteGlobalCatalog
ads-ad-01.domain.local -RemoteCredential $RemoteCredentials -TargetDeliveryDomain "domaincorp.local" -Remote
HostName ads-exch-01domain.local
The call to 'https://ads-exch-01.domain.local/EWS/mrsproxy.svc' failed. Error details: Could not establish trust
relationship for the SSL/TLS secure channel with authority 'ads-exch-01.domain.local'. --> The underlying connection
was closed: Could not establish trust relationship for the SSL/TLS secure channel. --> The remote certificate is
invalid according to the validation procedure..
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : [Server=ADS-EXCHCORP-01,RequestId=3f49d075-8110-48fd-8157-9b4d87921252,TimeStamp=5/1/201
5 4:00:11 PM] [FailureCategory=Cmdlet-RemoteTransientException] EA6D7B2B,Microsoft.Exchange.Management.RecipientTa
sks.NewMoveRequest
+ PSComputerName : ads-exchcorp-01.domaincorp.local
If I change remote hostname to exch.domain.com I get a different error message.
[PS] D:\Exchange\Scripts>New-MoveRequest -Identity [email protected] -Remote -TargetDatabase "domainCorp" -RemoteGlobalCatalog ads-ad-01.domain.local -RemoteCredential $RemoteCredentials -TargetDeliveryDomain
"domaincorp.local" -Remote
HostName exch.domain.com
The call to 'https://exch.domain.com/EWS/mrsproxy.svc' timed out. Error details: The request channel timed out
attempting to send after 00:00:07.9643241. Increase the timeout value passed to the call to Request or increase the
SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. -->
The HTTP request to 'https://exch.domain.com/EWS/mrsproxy.svc' has exceeded the allotted timeout of
00:00:07.9640000. The time allotted to this operation may have been a portion of a longer timeout. --> The operation
has timed out
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : [Server=ADS-EXCHCORP-01,RequestId=f5807f2d-c8d5-4fb3-86b3-a831cae92626,TimeStamp=5/1/201
5 4:01:10 PM] [FailureCategory=Cmdlet-RemoteTransientException] F2700578,Microsoft.Exchange.Management.RecipientTa
sks.NewMoveRequest
+ PSComputerName : ads-exchcorp-01.domaincorp.local
I feel like I have been hitting my head on the desk for about a week now.
We Also should note that we exported the Wildcard cert from the source server and imported it into the target server.Hello
if open imported wildcard cert from mmc on source computer it show the cert is ok? not missing root cert?
sorry my english -
SmallSearchInputBox not seen in the Migrated site from SP 2010 to SP 2013
We did the content database attach migration and didnt use any tool.
We reworked on the Master Page by taking the seattle.master page and put the custom placeholders.
The design came out well, but the SmallsearchInputbox is not seen in the "View All Site Content" and the Home Page.
Please help to fix this. Thanks in advance
Veena RHi Veena,
What did you mean by “We reworked on the Master Page by taking the seattle.master page and put the custom placeholders”?
Did you set the seattle.master page as the default master page for the migrated site?
If yes, I recommend to set the master page to be v4.master and then do visual upgrade for the migrated sites.
After that, add the custom placeholders to the seattle.master page and then check the results.
If I misunderstood, please feel free to correct me.
Thanks,
Victoria
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]
Victoria Xia
TechNet Community Support -
Migrating Autotext from Word 2010 to Word 2013 on a Network
I am trying to share my autotext (created in Word 2010) with my employees who are now working on Word 2013. They have smart boxes and are working through the server. I have tried every "fix" that I've read and nothing seems to be working. HELP
! We use autotext a GREAT deal.
rjHi
Do you have a backup file of Word 2010 Normal.dotm?
If so, replace the current Normal.dotm with the backup file.
Hope this helps. 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. -
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 -
Exchange 2010 dag migration to exchange 2013 help
If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
A B -------------- C D
Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
A1 ----------- C1
B ------------- D
Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
A1 B1 ----------- C1 D1
Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
Anand_NHi,
When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
Migrating an Exchange 2010 DAG to Exchange 2013
http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
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.
Best regards,
Belinda
Belinda Ma
TechNet Community Support -
Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8
I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error. Is this even possible? I cannot find any documentation on this scenario yet.
VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequestHi Steve,
I'm a little confused what you are saying. Here is my understanding:
When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
If I have misunderstood your concern, please let me know.
For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
2007.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Exchange 2013 Mailbox Using 2010 Public Folders
Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while. Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company. Our environment consists of
8 Ex2010 servers and now the one Ex2013. I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine. How is that server discovered, and can we specify which one it uses? I understand the way 2013
public folders are moving but is there a downside to leaving our configuration this way for a long period of time?Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
between two exchange server. It ensures about the data security and email contents during the completion of entire migration process. -
Exchange 2010 OWA usage in Exchange 2013
Hi,
I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
Before Migration we want below things to keep in mind...
1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
2. Can i use my Existing Exchange certificate to get the above goal done ?
3. What will be the steps and pre-requsite to achieve the Goal ?
An Early reply would be appreciated !!
AmitHi Amit
First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
Configure external DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
Ensure that you are having a seperate name for CAS array from external ews url
Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
Authentication for OUtlook Anywhere should be - NTLM
for OWA exchange 2010 - FBA and windows
Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users
You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
Apply a new certificate with all the required site names included in Exchange 2013 CAS.
Whats more you can refer my blog as well
http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
Cheers :)
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com
Maybe you are looking for
-
If you have forgotten your security question how can you change them?
Have not had to use this option so I really have forgot all about setting this up till the other day.. But when this come up that I did have to use I found out I forgot what I had use.. Stupid me.. Any way I did get my password rest and thought chang
-
Hyperlinks in PDF, WORD, PPT not working in Safari on iPad
We have an intranet we are serving up for use on the iPad. The links to other documents in PDF, WORD, PPT work on my pc and laptop but not in the iPad. I have looked to see of there is a setting but the only thing I found was to allow pop ups which o
-
EBS BAI2 file - Transaction 475, check clearing - extra character appending
Hello experts, We are using Algorithm 13 for processing checks which are processed using the transactin 475 on the incoming bank file. In the BAI2 file format, the check numer is contained in record 16 in the following format- 16,475,58740,0,91809147
-
IPod Classic music artwork Displayed on TV????
Is there a way to display my iPod Classic music artwork to my TV like my Zune does?
-
HT201442 Received "This device isn't eligible for the requested build" error
I followed instructions on apple support site, but in my hosts file, I don't have a line indicating gs.apple.com, which the instructions suggest adding a '# ' in front of, what should I do?