Forum Discussion
cannot establish remote desktop to virtual win10 azure client due to "welcome screen"
Dear Kent,
thank you for your help. I tried to download the VHD, but without success.
I tried the powershell Save-AzureVHD commando, but this always wants me to set the default description. I try to do this with Select-AzureSubscription <mySubscription> but every <mySubscription> I try is not working - subscription not found. I tried subscription guid, name of the storage accounts, VM name, ...
Is there another way to download the VHD?
Regards,
Francisco
Dear Kent,
I managed to download the VHD using the \storage accounts\myMachineNamedisks123-Container\vhds\blob properties\... So waiting for 250GB download now ;-)
There is also an upload button in this view - I'm curious if I can overwrite the existing files.
Best regards,
Francisco
So i feel horrible forgetting to mention this, but Azure now support Nested VM's, meaning you can enable hyper-v on a 2016 VM, and the data doesnt have to leave the datacenter.
OK, that means I need a 2016 Windows Server with hyper-v and then I can "add" the virtual azure client as nested VM into 2016 windows server? Is this something I can do in azure - so let's setup an 2016 windows server in azure and there add the not-working vm? so I can remote login to the server and from the server I can start the nested vm and get through the welcom screen?
you still need to expose the vhd to the 2016 by upload or mapping the url, i would suggest uploading it to the recovery vm to insure perfomance. but yes that should be possible.
