Migration questions from Exchange 2007 to Exchange 2013

Dear Forum Members,
I'd ask just two short questions, regarding a migration from Small Business Server 2008 (Exchange 2007) to 2013. We installed the two Exchange 2013 servers, configured a DAG and updated every single URL (OWA, ECP, AnyWhere, Autodiscover etc.) to be a mail.domain.com
record (DNS round robin, since no HW load balancer :( )
Thankfully, the mail flow between the Internet and the other Exchange 2007 users are still working. Now for those users I've already migrated, if I check outlook connections there are several connections for GUID based servers via the DNS Round Robin
name proxy (the AnyWhere address). But I saw that there are still just one connection (type: Exchange Public Folders) to the old 2007 server. Is it okay? I'm a bit afraid to uninstall it because of this.
And the other thing: Based on what I wrote, do you think I've done it good? Or could I miss any important things? You are much experienced than me in these migrations so I hope that I can get some confirmation/advice here :(
ps: Is it good if I set NTLM authentication for Outlook AnyWhere?
Thank you really much for your help,
Best Regards,
Chris

Hi Chris,
Agree with Hinte, the user will still connect to the exchange 2007 server if there is a public folder database in the old server.
If the old public folders are no longer in use, you can delete the public folder database and create a new one in the exchange 2013 server, you can also consider migrating public folders to Exchange 2013 .
The following articles for your reference:
Use serial migration to migrate public folders to Exchange 2013 from previous versions
Set up public folders in a new organization
Step-by-Step Exchange 2007 to 2013 Migration
>>Is it good if I set NTLM authentication for Outlook AnyWhere?
The Outlook Anywhere authentication method you choose will depend on a few factors in your environment,
I recommend you refer to the following thread to understand how to choose:
https://social.technet.microsoft.com/Forums/exchange/en-US/75f8d6c4-70f4-49e5-ac32-a49dd91b5520/outlook-anywhere-ntlm-for-internal-users-and-basic-for-external-users?forum=exchangesvrclients
Exchange 2013: Configuring Outlook anywhere
Best 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]
Niko Cheng
TechNet Community Support

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?
Peteris

Hi 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

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

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.NewMoveRequest

Hi 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

Cannot send mail from Exchange 2013 to Exchange 2007

I have an
Exchange 2007server with all roles in the same server (Version:
08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
(full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
few articles on the Internet.
Any suggestions?

These two sentences are in conflict : "I can also send
internal mail
from Exchange
2007 to
Exchange 2013. But
the problem is
that I am unable
to send from Exchange
2007 to
Exchange 2013. "
Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
Please 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. Thank you! Damir

Migrating user from Exchange 2010 to Exchange 2013 succeeds but OWA redirects to 2010

Hello everyone,
I am migrating users from exchange 2010 to 2013, Users migration works perfectly and completes without any issue but after the user migration finishes I try to login to OWA but user goes to OWA exchange 2010 not 2013 as if the mailbox has not been migrated.
I have checked the HomeMDB attribute and I can see the new database on 2013 is located there. how to solve this? I have retransfered the user back to 2010 and 2013 but it didn't work.
I would appreciate your help.
Thanks
Mohammed JH

Hi Amit
After 30 mins approximately we checked the inboxes that have been migrted (2) and we found out they are working.
İ wonder why there is this delay ? İ have already done migration before but it never took this much time. İ would appreciate your reply.
Thanks
Mohammed JH

Moving mailbox from exchange 2013 back to exchange 2007 ..

Hi Guys,
I recently configured configured co-existence between exchange 2007 and exchange 2013. I moved a pilot user from exchange 2007 to exchange 2013 and now the user has issues receiving mails.
I am trying to move the user back to 2007 pending the resolution of the issue. The move status says completed but the mailbox remains in the exchange 2013 environment.
I need to return the user to an exchange 2007 mailbox database ..any ideas on what I am missing.
Thanx guys ..
~Richard
..forever is just a minute away*

Hi Richard,
Please move your mailbox from Exchange 2013 to 2007 from the Exchange 2013 admin center (EAC) and the Exchange Management Shell instead of EMC in Exchange 2007.
Then check whether the issue persists. If possible, please provide more error logs for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Migrate Notes from Exchange server 2007 to office 365

Hi,
Anyone help me to how to migrate notes from exchange server 2007 to office 365 . My customer having notes on his existing exchange account . We would like to move notes to office 365 .
Please help me or guide me .
Thanks & Regards,
Vinoth

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365. That's hardly a trivial task. If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Upgrading from Exchange 2013 CU1 to CU2

1 : Upgrading from Exchange 2013 CU1 to CU2
================================================================
"Unable to remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1.
Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Service 'Tracing Service for Search in Exchange ' (SearchExchangeTracing) could not be stopped.
Verify that you have the correct permissions to stop system services.'."
================================================================

Hi,
According to the error message, it is highly likely caused by insufficient permission.
Please verify that your user account is member of Exchange administrators group and not limit by RBAC, than try again to see if this works.
If the issue continues, run the command below to uninstall the product:
msiexec.exe /X {code 4934d1ea-be46-48b1-8847-f1af20e892c1}
Msiexec (command-line options):
http://technet.microsoft.com/en-us/library/cc759262(v=ws.10).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Force downloading mysite HD photos from Exchange 2013

Hi Sharepoint Admins,
I want to force download all HD photos from Exchange 2013 into users mysite profiles. I already provisioned all user mysites by powershell. HD photos are also available, but every user has to open his own mysite by himself to trigger the picture download.
The goal is to download photos without having every user to logon on their site.
Is there any way to force this?
"SharePoint Server 2013 requests photos from Exchange 2013 automatically when a user performs an operation that causes a request for their own photo (for example, browsing to their own user profile page). That means that the user needs to have requested
his/her own photo, before other users will be able to see it."
Best Regards
Markus Kühn

Hi Markus,
I understand you would like to manually sync HD photo from Exchange 2013 to SharePoint 2013 mysite.
Since "SharePoint Server 2013 requests photos from Exchange 2013 automatically when a user performs an operation that causes a request for their own photo (for example, browsing to their own user profile page)", you need to browse all
sites in Mysite web application.
To do this, you may refer SharePoint warmup script and make the script to work for you MySite web application. Just run the warmup script, all mysites can be browsed once.
https://gallery.technet.microsoft.com/office/SharePoint-2007-2010-or-d1884b4b
https://spbestwarmup.codeplex.com/
Regards,
Rebecca Tu
TechNet Community Support
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]

Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server

Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server. The command works if you issue directly from the server exchange shell.
I open the remote power shell to the exchange server 2013.
Issue the following commands and getting the following error.
$mailbox = Get-Mailbox -Identity testuser$mailbox.EmailAddresses -= "eum:50004;phone-context=telExt5digits.lync5.com"Then getting the following error:Method invocation failed because [System.Collections.ArrayList] doesn't contain a method named 'op_Subtraction'.
At line:1 char:27
+ $mailbox.EmailAddresses -= <<<< "eum:50004;phone-context=telExt5digits.lync5.com"
+ CategoryInfo : InvalidOperation: (op_Subtraction:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFoundHelp!

Now for an answer - your remote session doesn't have the same object you have on the server itself. Notice it says this is an array list, not a ProxyAddressCollection. If you need to work around this, you'll need to massage the addresses another
way that the system will accept. I'd try the following:
$NewAddresses = $mailboxEmailAddresses | ? { $_ -notlike "eum:50004;phone-context=telExt5digits.lync5.com" }
See what you get in the $NewAddresses variable when you do this.

Loading MySites profile photos from Exchange 2013 to Sharepoint 2013

Hi
I've configured SharePoint 2013 to get it's profile photos from Exchange 2013 using the method in the link below BUT Is there way to force the initial sync other than requiring the user to load their profile in a browser?
http://blogs.technet.com/b/jenstr/archive/2012/08/17/using-exchange-2013-preview-high-resolution-photos-from-sharepoint-server-2013-preview.aspx
Thanks

As a workaround I have applied a client-side powershell load of the SharePoint thumbnail image. This triggers the sync just like loading in a browser does. I run it hidden on the user PC. I run it once a day for a while as for some reason
a load of the profile does not always trigger the sync and if it does not subsequent immediate sync's don't help - presumably due to the UserPhotoExpiration or
UserPhotoErrorExpiration settings.
Here's the code - enjoy....
# script to trigger Sharepoint to download the high res photo from Exchange
# sadly this must be done client side.
# have PC management software copy the files to the local PC then run......
# powershell.exe -ExecutionPolicy Unrestricted -noninteractive -File "%temp%\PhotoSync.ps1" >>"PhotoSync.log" 2>&1
# All output will end up in the log file
# the following syntax triggers the download (just find yours from your Sharepoint User profile photos)
#https://people.myco.com/User%20Photos/Profile%20Pictures/USERNAME_LThumb.jpg
$username = [Environment]::UserName
$userphoto = "https://people.myco.com/User%20Photos/Profile%20Pictures/" + $username + "_LThumb.jpg"
write-host "$username : $userphoto"
$web = New-Object system.Net.WebClient
$web.UseDefaultCredentials=$true
Try{
$result = $web.Downloadstring($userphoto)
Catch {
Write-Warning "$($error[0])"

Migrating Clients from SCCM 2007 to SCCM 2012 R2 via GPO

Hello.
I can do the migration of customers from SCCM 2007 to SCCM 2012 via GPO?
When I'm migrating customers from SCCM 2007 to SCCM 2012 I have to keep the boundaries of SCCM 2007 or just the SCCM 2012?
Atenciosamente Julio Araujo

For migrating the clients you can use any client deployment method that's available (see for planning your strategy: (http://technet.microsoft.com/en-us/library/gg712283.aspx).
During the client migration I would also start with migrating your boundaries. The most important thing is that you have no overlapping boundaries for site assignment when you are using auto assignment.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Migrating Clients from SCCM 2007 to SCCM 2012 R2 via SCCM 2007 PACKAGE

I can migrate sccm clients from sccm 2007 to sccm 2012 using sccm 2007 package with sccm 2012 client?
Thanks!
Atenciosamente Julio Araujo

Thanks for help me Peter and Torsten but this documentation says:
"You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client."
I Need migrate clients from sccm 2007 to sccm 2012 r2 and
I thought ofcreate a package in sccm 2007 with a sccm 2012 client.
Atenciosamente Julio Araujo

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them.
With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
Questions are, Is this the right way to migrate all the users to Exchange 2013?
Will it affect the operation of existing Exchange 2007 server?

Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
2013 for standardization.
Refer article for configuring URLs -
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Sarvesh Goel - Enterprise Messaging Administrator

Migration questions from Exchange 2007 to Exchange 2013

Similar Messages

Maybe you are looking for