PF migration 2007 - 2013 FailedOther

A Public folder migration 2007 -> 2013 is failing with the status detail: FailedOther
Error message: There are multiple primary SMTP addresses. Please ensure there is only one primary address for address type.
I can see the Identity as a guid, but can’t seem to identify what public folder is causing the error. Is there a way to see GUID to PF Names mapping?
Thanks

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

Similar Messages

Private marked Tasks in Public Folder after Migration 2007 - 2013 hidden

After the Migration of Public Folders from 2007 to 2013 some private marked tasks are hidden.
I see the item with mfcmapi but outlook doesnt show it. I think there is a problem with permission to see private marked items. But there is it possible to set this?
For example Public Delegation in Public Folder Mailbox?
Thanks fpr help

Hello,
At present, I'm afraid there is no way to set public delegation on public folder mailbox.
My environment is coexistence of exchange 2007 and exchange 2013. I check my environment, there is no way to set delegation for public folder in outlook or Exchange server.
Besides, we can't set permission on public folder in outlook.
Cara Chen
TechNet Community Support

SharePoint migration 2007 to 2013

We have SharePoint 2007 installed. We plan to migrate it to 2013. Please suggest upgrade path & tools

there are two stratgies for this migration.
1st is in house, mean migrate the content Database to 2010 and from 2010 to Migrate to 2013.
Resources:
file:///C:/Users/WSARWAR/Downloads/Migrating%20from%20SharePoint%202007%20to%20SharePoint%202013.pdf
http://sharepointpromag.com/blog/migrating-sharepoint-2007-sharepoint-2013-part-1
http://sharepointpromag.com/blog/migrating-sharepoint-2007-sharepoint-2013-part-2
2nd) you can use 3rd party tools for the migration, its depend upon the amount of data etc. there are many good tools for this i.e Metalogix, Dell Software, ShareGate, AvePoint.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Problem: Mixed Exchange 2007 / 2013 CAS Servers with wildcard certificates in Europe and non-wildcard Certficate in China

Hi,
we have following problem. We have a mixed multi-domain one-forest AD environment. We also have still a mixed exchange 2007 / 2013 environment. We also have different CAS Servers for 2007 SP3 (RU15) and 2013 (CU8) in europe and one 2007 SP3 (RU15) CAS Server
in China, because of bad connection to Europe. For the Migration to 2013 in Europe we installed a wildcard-certificate *.xyz.com and used the Set-OutlookProvider EXPR -CertPrincipalName msstd:*.xyz.com, so the wildcard certificate is accepted. Everything in
Europe works fine, inside and outside also between exchange 2007 and 2013 (both CAS Server 2013 and 2007 use the same wildcard certificate). But since the change of the Set-OutlookProvider EXPR we are facing problems with our CAS Server in China, because this
server has a different non-wildcard certificate and a different domain name (cas-server.xyz-china.com instead xyz.com). Now we have the problem that this Chinese CAS server the Outlook Anywhere does not work anymore and prompts always for the username. As
I see it is because of the EXPR change. Is it possible to set the the Outlook-Provider EXPR per Cas-Server ? (They also have their own Autodiscover on this front-end server). Because I see that the Outlook-Provider can only be stored forest-wide.
If not the other solution would be to register the chinese cas server in our xyz.com domain and use the same wildcard certificate on this system right ?
Any help would be appreciate….

Yes setting the EXPR value is most likely the cause of your issue. When you set this value you are telling Outlook to only accept connections from connections that have the cert with the subject name you specify here.
Unfortunately, based on my experience I believe this is an organization wide setting and cannot be configured on a CAS by CAS basis (If I'm wrong someone please keep me honest :)).
So the only option would you have is to change all the URLs to be on *.xyz.com domain. There's no need to change the domain the server actually resides on. The other option would be to purchase a UCC Cert with all the names you need and apply
to all your CAS servers and reset the EXPR value.
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

Is there a way to clean up the Timesheet tables in MS Project 2007 before I migrate to 2013?

Hi All
I'm attempting to migrate an instance of project server 2007 over to 2013. The problem is that it failes on the convertto process when combining the 4 2010 databases into a single 2013 database.
Reading through the logs it appears to be an issues with an invalid Foreign Key in the MSP_TimesheetProjects table.
On investigation I find that the 2007 Timesheet tables in the Reporting database have a number of invalid entries. We don't use the timesheeting system in that particular instance so there should not be any entries at all. There are however a
couple to projects in the TimesheetProjects table, as well as a few tasks and timesheet lines, even though there don't appear to be any timesheets. I have run a delete on all timesheets in the system, and have rebuild the Reporting database by restoreing
custom fields, but I can't seem to shift them.
If anyone has any ideas, I'd appreciate the help.
John

Hi John,
What I'd suggest would be to refresh the 2007 reporting DB. See the procedure below:
Logon to Project Web Access with Administrator credentials
Select Administrative Backup from the Database Administration secton on the Server
SettingsPage in Project Web Access
In the Items for Backup section of the Backup page,
select the checkbox for Enterprise Custom Fields and then click the Backup button and click the OK button
when prompted by the system
Select Administrative Restore from the Database Administration secton on the Server Settings Page in Project Web Access
Choose Enterprise Custom Fields from the Choose Item selector on the Restore page
Click the Restore button and then click the OK button
when prompted by the system
See reference
here.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Exchange Server 2007/2013 migration with ActiveSync users

Hi all
ongoing migration from 2007 to 2013 and have just one bugging questionmark...
ActiveSync users are currently connecting to as.company.com (exchange 2007 CAS, single site internet facing deployment).
do I need legacy hostname?
as per http://technet.microsoft.com/en-us/library/dn130105%28v=exchg.150%29.aspx I do need because it states:
All client connections will be redirected, including Exchange ActiveSync, Outlook Web App, POP3, and IMAP4.
as per http://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/OUC-B313 - slide #23, I do not need because 2013MBX will proxy to 2007 CAS.
I've found numerous "proxy connection" infos rather than "redirect connection" but I'm thinking that they are all referenced by that same slide :)
thnx in advance!

You can force "proxy connection" for ActiveSync by setting the AS URL to "null". Actually, this approach is recommended by some people to avoid redirection issues for iPhones.
Setting the AS URL to "legacy.company.com" (as recommended in MS docs) will result in redirection.

Issue removing Exchange 2007 after migration to 2013

After migrating relatively successfully from Exchange 2007 to 2013, I am in the process of trying to decommission and uninstall 2007 from the servers. Through this process I have been following a guide found
here. Our old 2007 servers have been off for over two weeks and it seems like a good time to remove them and reclaim some space. I removed the old OAB and Mailbox DB, however when I attempted to remove the Public Folders so I could take the PF DB out the
following error appeared.
Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'.
I know that there are Public Folders existing as I can see them when I run Get-PublicFolderStatistics:
I've been back and forth across the forums and web and haven't been able to find a solution to this. Ultimately we never have and are not interested in using public folders but they were originally configured when we had a contractor move us from 2003 >
2007 several years ago. What I would like is to remove all traces of this garbage and just be able to uninstall/delete the old servers and move on with life.
Any help is greatly appreciated. Thank you in advance.
Jon Howard

Hi,
Have you tried to use Exfolders tool to remove PF?
More details about exfolders tool refer to the following article:
http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
Thanks.
Niko Cheng
TechNet Community Support

Exchange Migration 2007 2010 to Exchange 2013

Let me lay it all out. We are running an Exchange 2007 environment with 2-CAS, 2-HT's and 2-MBX's clustered. We started a migration to Exchange 2010 and after starting the migration it was decided that we would instead got to Exchange 2013. In Exchange 2010
we have 3-CAS, 2-HT's and 2-MBX's. We have moved our external connections over to Exchange 2010 and only have test mailboxes on 2010 and that's where we stopped.
We installed Exchange 2013 3-CAS, 2-MBX's. We are testing out 2013 installation. We can access 2013 Web App with the 2013 test accounts. I can access 2013 test mailbox with outlook 2010 by configuring outlook for rpc/https. I am not getting free/busy
form 2007 or 2013 when logged into my 2013 test mailbox. My virtual directories are configured as the following:
Exchange 2007 - mail2007.domain.com\
Exchange 2010 - mail.domain.com\
Exchange 2013 - mail2013.domain.com\

Hello,
Please check internalurl of the Exchange 2007 and 2010 EWS virtual, you can use:
Get-WebservicesVirtualDirectory | select internalurl
If they are not set to their own FQDN, please change it back and restart the IIS services.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migration from 2007-2013 - Installation of 2010 server?

We have Exchange 2007 installed currently (SP3, latest UR). I installed Exchange 2013 in preparation for migration, started working on configuration. After doing some digging, we realized we don't have any licensing for 2013 (miscommunication). The obvious
solution is to purchase licensing for 2013, but the cost is an issue.
First questions: we do have licensing for 2010. Is there any way we can install Exchange 2010? Everything I'm reading says no, but would like confirmation. 2010 was never installed in the environment.
Second question: If I cannot install 2010, can I install a second 2007 server after 2013 has been installed (newer OS)? Safely uninstall 2013?
Thanks!

Hi Wlentz,
Thank you for your question.
1. First question: We install Exchange 2010 in organization without no problem.
We can refer to the following link to install Exchange 2010:
http://technet.microsoft.com/en-us/library/bb124558(v=exchg.141)
The following link is the coexistence of Exchange 2007 and Exchange 2010:
http://technet.microsoft.com/en-us/magazine/jj542449.aspx
2. Second question: we can safely uninstall Exchange 2013. we can install another Exchange 2007 after we uninstall Exchange 2013.
We can refer to the following link to install Exchange 2007:
http://technet.microsoft.com/en-us/library/bb124558(v=exchg.80).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Migrating to 2013 from 2007 with Outlook Anywhere disabled

Hello
I'm in the middle of a migration from 2007 With Outlook anywhere disabled.
After I installed 2013 I added the external url to both inside and outside url's on CliantAccess, o-anywhere url and Virtual catalogs.
When I configured the External Access domain on the 2013 it also added this on the external url's on the 2007 server. On the 2007 server i manuelly changed the external url's to the Legacy name which is mail.domain.com. The New server is webmail.domain.com
both internally and externally. The servers real name is xxmail.domain.internal
After this, when I configure an Outlook Client With a user on the old server With autodiscover it configures it With Outlook anywhere, not mapi, but With the external name of the New server, webmail.domain.com under http Proxy settings. When I then
moved this user to the New server it stopped working in Outlook.
Is the best approch to enable Outlook anywhere on the 2007 server before migrating the users or can I og from mapi/rpc to rpc over http in 2013 without Outlook problems?
Regards

Hi,
Firstly, I’d like to explain, all users in Exchange 2013 use Outlook Anywhere. The information of Exchange proxy settings tab is automatically updated by Autodiscover.
I recommend you the following troubleshooting:
1. Check the Autodiscover configuration on both Exchange 2007 and Exchange 2013 servers:
Get-clientaccessserver |fl autodiscoverserviceinternaluri
2. Check if there is any DNS entry about the legacy name points to Exchange 2007 IP address.
3. Check if you can logon OWA with both Exchange 2007 and Exchange 2013 server.
Best regards,
Angela Shi
TechNet Community Support

SharePoint 2007 – 2013 migration List view webpart still shows 2010 look and feel even after visual upgrade run successfully in 2013.

I migrated one site collection from 2007 to 2013 environment. I did Visual upgrade on both 2010 & 2013 successfully. We have a strange issue with Listviewwebpart with group by functionality still shows 2010 look and feel.
If I manually edit that webpart and click ok the Listviewwebpart UI is showing the 2013 Look and feel. However I can’t manually update all the webparts because there are nearly
1500 subsites. I tried using console to update webpart but still not lucky
Following is 2010 look and feel in sp 2013 site:
expected look and feel should be as follows in sp 2013
Thanks, Ram Ch

Hi ramch011 ,
For your issue, you can force through an upgrade to the new user interface by using Windows PowerShell:
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
At the Windows PowerShell command prompt, type the following command:
$webapp = Get-SPWebApplication http://sitename
foreach ($s in $webapp.sites)
{$s.VisualUpgradeWebs() }
For more information, see Get-SPWebApplication
Reference:
http://technet.microsoft.com/en-us/library/ff607998.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Outlook Authentication prompt after migrating from 2007/2013

I have a very simple environment. 3 new Exchange 2013 servers in a DAG behind a load balancer. Most users are still on Exchange 2007 environment. Autodiscover has been configured for load balanced name. There is no External Outlook
Anywhere connectivity. I have NOT enabled Outlook Anywhere in the 2007 environment. I have a simple Lync 2013 environment. 1 Server in a standard pool with no external connectivity. I have integration with OWA 2013 and Lync working.
All versions of Outlook are at least on the patch level required for Exchange 2013.
My issue is random password prompts in Outlook for some (not all) users with mailboxes on Exchange 2013. This password prompt appears to be coming from the load balanced Outlook anywhere name. I have had a few reports of users on Exchange 2007
getting an error stating they cannot open default set of folders. If I have them exit Lync 2013 client and open Outlook again it works fine. They can then open Lync without issue. Closing and opening Outlook will no longer reproduce the issue.
It seems like Lync is causing an issue here somewhere, but I have no idea where.
Lync BPA completes without any warning or errors. All test cmdlets complete without any errors.
2013 Outlook Anywhere settings:
Name                               : Rpc (Default Web Site)
ExternalHostname                   :
InternalHostname                   : mail.company.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
Get-AutodiscoverVirtualDirectory|select *auth*
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication : False
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : True
DigestAuthentication          : False
WindowsAuthentication         : True
OAuthAuthentication           : True
AdfsAuthentication            : False
brian smith

I just could not let this go last night. The issue was occurring when I moved a mailbox to 2013.
2 scenarios
#1. Users mailbox moved from 2007 to 2013. Profile has a secondary mailbox that is still on 2007. When entering Outlook they are prompted for
a password into the internally resolvable load balanced name (mail.company.com). If I remove this secondary 2007 mailbox they work fine, UNTIL they try to access anything on 2007 (calendar, Public Folder, another mailbox, etc). When they do attempt they
are prompted for a password.
I have seemingly fixed this error by adding the external URL back to AutoDiscover on 2013 based on
http://support.microsoft.com/kb/2839517<u5:p></u5:p>. Even though we have no intentions of using Outlook Anywhere externally.
During this troubleshooting I also changed InternalClientsRequireSsl from false to true. Now I have clients reporting errors in their event log “A fatal error occurred while
creating an SSL client credential. The internal error state is 10013." I do not think changing this to require SSL, but I’m almost scared to change it because this issue
is seemingly resolved.
#2 mailbox that is only accessed as a shared mailbox Mailbox is moved from 2007 to 2013. Users attaching to the mailbox are still on 2007. This works perfectly fine for some. However others receive a password prompt each time they open Outlook.
If the 2013 mailbox is removed from their outlook profile they receive no prompt. If I manually remove the mailbox from their profile and add it back the prompts go away. I have not been tracking client versions, but these last 4 are running 12.0.6691.5000.
I also noticed in checking the connection status all 2007 references are using [Nego] for authentication and mail.company.com is using NTLM. Is this normal? This is the same in my test environment, but I can’t replicate this issue in my test environment
either.
I’m very stumped.
2013 Outlook anywhere config:
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
SSLOffloading                      : True
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
2007 Outlook anywhere config:
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
SSLOffloading                      : True
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
brian smith

HTTP 500 error when opening a legacy shared mailbox in OWA 2013 (Exchange 2007/2013 coexistence environment)

Hi,
Our Exchange 2013/2007 coexistence environment is set up and all is working apart from this:
Mailbox A has full permissions to Mailbox B. Mailbox A is migrated to Exchange 2013, but Mailbox B remains on Exchange 2007. If I login to Outlook Web App 2013 as Mailbox A and then "Open another mailbox..." and select Mailbox B, a new window opens
up saying "HTTP 500 Internal Server Error". The URL it is trying is :
https://webmail.ourdomain.com/owa/[email protected]/?offline=disabled
( I can open Mailbox A in Outlook 2010 and do "Open Other users's folder.." and Mailbox B opens up just fine. )
Our legacy CAS server's External and Internal URLs are set to :
https://legacy.ourdomain.com/owa
and the Exchange 2013 CAS server's External and Internal URLs are set to :
https://webmail.ourdomain.com/owa
We have FBA enabled on both the E2K7 and E2K13 OWA
In the IIS logs:
2015-03-02 16:36:50 <E2K13_IP> POST /owa/service.svc action=SubscribeToNotification&UA=0&ID=-25&AC=1&CorrelationID=c2899211-568d-4da4-a163-351a8621c9fd_142531419466924;&cafeReqId=7ffae082-a96f-42fd-85f8-bf23775ed5de; 443 ourdomain.com\MailboxA
<LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
https://webmail.ourdomain.com/owa/#path=/mail 200 0 0 109
2015-03-02 16:36:50 <E2K13_IP> GET /owa/ offline=disabled&CorrelationID=<empty>;&cafeReqId=7c8e137f-cdb7-4449-9cb8-f36f94539244; 443 ourdomain.com\MailboxA <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
- 500 0 0 265
In the OWA HTTP Proxy logs:
2015-03-02T16:36:50.096Z,7c8e137f-cdb7-4449-9cb8-f36f94539244,15,0,913,7,,Owa,webmail.ourdomain.com,/owa/,,FBA,True,ourdomain.com\MailboxA,ourdomain.com,[email protected],Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0),<LoadBalancer_IP>,<Exchange2013ServerName>,500,,ServerNotFound,GET,,,,,ExplicitLogon-SMTP-Header,,,,0,,,,40,9,,0,7;,7,,0,7,,0,46.8643,0,,,,,,,,,1,10,0,,10,,50,50,?offline=disabled,,BeginRequest=2015-03-02T16:36:50.049Z;CorrelationID=<empty>;ProxyState-Run=None;ServerLocatorRefresh=beebf732-0f99-47a0-9f36-d266573f1510;RefreshingCacheEntry=CacheEntry(BackEndServer
<Exchange2007ServerName>.ourdomain.com~1912832083|ResourceForest |LastRefreshTime 2015-03-02T16:01:29.3265514Z|IsSourceCachedData False);ProxyState-Complete=CalculateBackEnd;EndRequest=2015-03-02T16:36:50.096Z;I32:ADS.C[<DC_Name>]=1;F:ADS.AL[<DC_Name>]=6.6401;I32:ATE.C[<DC_Name>.ourdomain.com]=1;F:ATE.AL[<DC_Name>.ourdomain.com]=0,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
The server <Exchange2013ServerName>.ourdomain.com was not found in the topology. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: The server <Exchange2013ServerName>.ourdomain.com was not found in the topology.
at Microsoft.Exchange.Data.Storage.ServiceTopology.GetSite(String serverFullyQualifiedDomainName)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetServiceTopologyWithSites(String serverFqdn ServiceTopology
topology)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer
mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1
operationToTrack Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass3b.<OnCalculateTargetBackEndCompleted>b__3a()
--- End of inner exception stack trace ---;
Hoping that somebody can help ?
Thanks

Hi Ansev,
Thank you for your question.
By my testing, user who was migrated to Exchange 2013 cannot access mailbox on Exchange 2007 with 500 error, although user account have “Full Access Permission” to mailbox on Exchange 2007.
I suggest we migrate account which has “Full Access Permission” for other user to Exchange 2013.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Free/busy information in 2007/2013 coexisitance

I'm in the process of migrating from a single server 2007 exchange environment to a multi server 2013 environment. I'm at the point where I want to move a small group of users to the 2013 serves to do some testing. The only issue holding that back
is anyone on the 2007 server cannot view free/busy information of a user on the 2013 servers. This does work when a 2013 tries to lookup a 2007 users free/busy information.
Anyone have any idea why that would be?

Hi,
Please check your Exchange 2007 Web service in CAS configurations. We need to set it with legacy.contoso.com. Just like:
Set-WebServicesVirtualDirectory –Identity “Exch07\EWS (Default Web Site)” -InternalUrl https://legacy.contoso.com/ews/exchange.asmx –ExternalUrl
https://legacy.contoso.com/EWS/Exchange.asmx
For more information about migrate from Exchange 2007 to Exchange 2013, please refer to:
Step-by-Step Exchange 2007 to 2013 Migration
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Thanks,
Winnie Liang
TechNet Community Support

Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes

Hey all,
So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
AD, etc. But I'm wondering if someone can break it down for me.
http://1drv.ms/1lWjLqG
The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
Original Design
The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
Migration/Hybrid Design
Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
Migration from Exchange 2007 to Exchange 2013
I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
The latest Service Packs and CUs are installed in both.
What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
SpecialBank that users are actively using.
I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
if I need to in order to make the migration transparent to users.
Can anyone help?

Hi ,
From you description i came to know contoso is the resource forest and special bank is the account forest .
You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
Regards
S.Nithyanandham
Thanks S.Nithyanandham

PF migration 2007 - 2013 FailedOther

Similar Messages

Maybe you are looking for