Forum Discussion
MicrosoftMigration from Fall 2019 to Spring update 2020
PavithraT do you have an estimate for when the updated article with cmdlets will be provided? We have several Fall release WVDs with problems and need to get them updated to Spring release. Thank you!
- PavithraT
JesseVaught No ETA, yet. What is stopping the custoemr from setting up a new environment in Azure portal and migrate the VMs (if its personal) or create new VMs (if its pooled)?
PavithraT, thank you for your reply! We have a couple clients with the Fall 2019 Release and are having some problems with permissions and adding users to the hostpool. We have a support case open and the engineers are saying something is corrupted on the back end (because all our permissions are indeed correct on the front end). Because Fall 2019 will no longer be supported soon and because Spring 2020 is better, we want to migrate. Came across your article here, which states that it will be updated with powershell cmdlets to perform the migration.
I'm ok creating a new environment, but was hoping to migrate the WVDs themselves (well, one in particular) because of the user-specific settings on their own profiles (shortcuts, installed apps, various user-specific settings). If we provision a brand new WVD it will seem like a brand new computer to them. That is what I was hoping to avoid by migrating the WVD, if possible.- PavithraT
WVD classic (aka Fall 2019) will be supported for a while. No worries there.
VMs can be migrated from classic to ARM WVD - https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell#update-the-agent
I am not sure how many VMs they want migrated, but this could work.
PavithraT we are at risk of losing our existing personal desktops. also rejoining machines to the new host pool might need a redo of the agents
