My assessment gets stuck.

[Victorteamti]

My App Service assessment stops at this part. Both the firewall team and our Acronis team have assured that there is no blockage. What could it be?

[krolson]

Hi - thanks for posting this issue!

Have you checked that outbound connections are allowed for the specific required endpoints, like readinessapi.trafficmanager.net (https://github.com/Azure/App-Service-Migration-Assistant/wiki/How-the-Assistant-Works#outbound-connections)?

I'm not that familiar with Acronis, however if there is some process on the machine preventing things like creating temporary files or network access that could also be an issue for this step. (A temporary file is made as part of assessment, and an outbound call to do the assessment is made: https://github.com/Azure/App-Service-Migration-Assistant/wiki/How-the-Assistant-Works#what-information-is-sent-for-assessments )

There are a couple potential things to try if we can't figure out why this step won't move on, including:

1. Giving a try using the slightly newer version of the tool (what the link at top of the tool will direct you to (https://appmigration.microsoft.com/api/download/windowspreview/AppServiceMigrationAssistant.msi). While I can't think of a related change off the top of my head that would fix the behavior you're seeing, this is often a first step just in case.
2. Manually get the assessment result using the cmdline with the migration tool (must be using the newer Preview version - local "AssessReadiness" command not present in 1.0.6 build)

• do the steps in https://github.com/Azure/App-Service-Migration-Assistant/wiki/How-the-Assistant-Works#what-information-is-sent-for-assessments to create the assessment file locally
• run command to generate assessment results json:
  iisConfigAssistant.exe AssessReadiness [pathToAnonAssessmentInfoFile] > [pathToSaveResultsFile]
  example:
  iisConfigAssistant.exe AssessReadiness C:\TEMP\AnonAssessmentInfo.json > c:\TEMP\AssessmentResults.json

3. Use the PowerShell scripts to get assessment check information instead (can even do the whole server at once rather than just one site, and doesn't require a call-out to an internet API so avoids any potential network layer complications. More info: https://github.com/Azure/App-Service-Migration-Assistant/wiki/PowerShell-Scripts

[Victorteamti]

I will try to follow the steps above. I had already read your recommendation. I apologize for not responding earlier; I've been caught up in the daily rush these days. I will try your recommendation, and once done, I will leave my feedback. I hope you're having a great day.

[Victorteamti]

If I perform the migration using scripts and PowerShell, will my site be fully migrated? I’d like to know what happens to the original site on the on-premises server. Will it remain intact? I want to migrate a replica while keeping the original site running on the on-premises server without any changes.
Because I know that using the Migration Assistant would do this, but would it work the same way with PowerShell? Have a great Friday, Krolson, and thank you in advance for your support and patience

[krolson]

Yes, the migration performed using the PowerShell scripts is very similar to how it would be done with the Migration Assistant GUI - in that the original site running on-prem on IIS will not be affected - a copy of the site content will be created (a .zip file) which is then pushed to a newly-created App Service site without changing any of the on-prem site settings/operations. The PS scripts are more likely to work for the migration step as well, as they avoid using Basic Authentication for that .zip publishing step (and basic authentication may be disabled).

Both the PowerShell scripts and the Migration Assistant GUI will not change anything about a local running IIS site.

[Victorteamti]

OK, I will test it on Saturday. Thank you for your response and patience. Have a great weekend. If you have any additional documentation on the step-by-step process for the PowerShell method, please send it to me. I am following your previous recommendations mentioned on GitHub.

…

________________________________ From: krolson ***@***.***> Sent: Friday, January 17, 2025 12:26 To: Azure/App-Service-Migration-Assistant ***@***.***> Cc: Victor Danin - Team Ti Soluções em Tecnologia ***@***.***>; Author ***@***.***> Subject: Re: [Azure/App-Service-Migration-Assistant] My assessment gets stuck. (Issue #98) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Yes, the migration performed using the PowerShell scripts is very similar to how it would be done with the Migration Assistant GUI - in that the original site running on-prem on IIS will not be affected - a copy of the site content will be created (a .zip file) which is then pushed to a newly-created App Service site without changing any of the on-prem site settings/operations. The PS scripts are more likely to work for the migration step as well, as they avoid using Basic Authentication for that .zip publishing step (and basic authentication may be disabled). Both the PowerShell scripts and the Migration Assistant GUI will not change anything about a local running IIS site. — Reply to this email directly, view it on GitHub<#98 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOMBML5KMLJLJ4NJPH6XQ3D2LEOJLAVCNFSM6AAAAABU7DXM3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJYGYYDMNJZGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>