Problems during migration exchange 2010 to 2016

Dear Experts,

I used this site to prepare and do the exchange migration.
Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 1) - TechGenix

after step 4 : Updating Exchange 2010 Virtual Directory URLs : Enable-OutlookAnywhere -Server $Server -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $HTTPS_FQDN -IISAuthenticationMethods NTLM, Basic

If first receive an error that the RPC connection allready exists.

and after updating the DNS records from mail.

I am unable to get the Outlook clients connected to the new mailserver 2016. it constantly asks for credentials and is unable to start outlook.

I think this can also be because the first IT provider has called the exchange 2010 server “mail”.
after changing the A records Mail. the new 2016 server loses connection with 2010.

any tips? can i rename the old server without any problems? so i can easily change the A record?
jav_sevenofnineIT ConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

viktor grantExchange ServersCommented:
Hi,

You need to change all the virtual directories in order to match with the certificate.

If you recreated the Outlook profile, are you able to create the outlook profile?

Cheers
0
jav_sevenofnineIT ConsultantAuthor Commented:
Hi on the new server i configured all virtual directories. and on the old server i removed all virtual directories.
Which is the way to make a hybrid connection.
I think after i set the mail record (a) to the new server everything went wrong.
After opening the outlook clients a authentication box appeared and tried every combination. but without success.

Maybe i  rename the old server and change the A record after that?
0
Jason CrawfordTransport NinjaCommented:
Here's a PowerShell script I wrote that configures vDirs and Outlook Anywhere for you.  Just be sure the hostname you entered is covered in a 3rd party cert:

begin {
    $exchhost = Read-Host 'Enter the hostname'
    $server = Read-Host 'Enter the server name'
    $ErrorActionPreference = 'Stop'
}

process {
    try {
        Write-Host 'Setting OWAVirtualDirectory to: '"https://$exchhost/OWA"
        Get-OWAVirtualDirectory -Server $server | Set-OWAVirtualDirectory -ExternalURL "https://$exchhost/OWA" -InternalURL "https://$exchhost/OWA" -WarningAction silentlycontinue

        Write-Host 'Setting OABVirtualDirectory to: '"https://$exchhost/OAB"
        Get-OABVirtualDirectory -Server $server | Set-OABVirtualDirectory -ExternalURL "https://$exchhost/OAB" -InternalURL "https://$exchhost/OAB"

        Write-Host 'Setting WebServicesVirtualDirectory to: '"https://$exchhost/ews/exchange.asmx"
        Get-WebServicesVirtualDirectory -Server $server | Set-WebServicesVirtualDirectory -ExternalURL "https://$exchhost/ews/exchange.asmx" -InternalURL "https://$exchhost/ews/exchange.asmx"

        Write-Host 'Setting ActiveSyncVirtualDirectory to: '"https://$exchhost/Microsoft-Server-ActiveSync"
        Get-ActiveSyncVirtualDirectory -Server $server | Set-ActiveSyncVirtualDirectory -ExternalURL "https://$exchhost/Microsoft-Server-ActiveSync" -InternalURL "https://$exchhost/Microsoft-Server-ActiveSync"

        Write-Host 'Setting ECPVirtualDirectory to: '"https://$exchhost/ECP"
        Get-ECPVirtualDirectory -Server $server | Set-ECPVirtualDirectory -ExternalURL "https://$exchhost/ECP" -InternalURL "https://$exchhost/ECP" -WarningAction silentlycontinue

        Write-Host 'Configuring OutlookAnywhere...'
        Get-OutlookAnywhere -Server $server | Set-OutlookAnywhere -ExternalHostname $exchhost -InternalHostname $exchhost -ExternalClientAuthenticationMethod basic -ExternalClientsRequireSsl $true -InternalClientAuthenticationMethod ntlm -InternalClientsRequireSsl $true -IISAuthenticationMethods basic,ntlm -SSLOffloading $false

        Write-Host 'Configuring ClientAccessServer...'
        Get-ClientAccessServer $server | Set-ClientAccessServer -AutoDiscoverServiceInternalUri "https://$exchhost/Autodiscover/Autodiscover.xml"
    }
    catch {
        Write-Host 'An error occurred' -ForegroundColor Red
    }
}

Open in new window

0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

viktor grantExchange ServersCommented:
Hi,

At this moment the users are Exchange 2010?

If you migrate an user to Exchange 2016, the new user can connect?

Cheers
0
Jason CrawfordTransport NinjaCommented:
Please don't rename the old server.  Is this a production environment?  You need to research co-existence before proceeding any further or devise a plan to cut everything over during one maintenance window so you can avoid co-existence all together.
0
Jason CrawfordTransport NinjaCommented:
Or hire me and push the easy button :)
0
jav_sevenofnineIT ConsultantAuthor Commented:
Hi Jason,

Thanks for the script.
i allready set the virtual directories.
the old server is called mail.customer1.nl and the external url is also mail.customer1.nl. (3th party cert).
When i set t he A records from 192.168.0.14 to the new 192.168.0.15 the mailbox store shows offline on the new database.
Which is offcourse impossible.
So after that i created a hosts entry on the new exchange server to the old exchange server. i was able to see the datbase again.
But clients were unable to connect to the new exchange server.

@viktor
all users are in the exchange 2010 environment was we speak.
When i moved a user to 2016 it was unable to connect. but! was able to login on the webmail.
0
Jason CrawfordTransport NinjaCommented:
Ok do this.  Open up EMS and run this command:

Get-ExchangeServer

Do the results include both the source and target server(s)?  Did you run through the Exchange pre-requisites as published by Microsoft?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RoninCommented:
You should be using an official Microsoft Exchange Server Deployment Assistant.
All the required, correct steps will be outlined in the Wizard.
0
viktor grantExchange ServersCommented:
no more answers...issue seem to be solved
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.