May 20 2020 06:52 AM - edited May 20 2020 07:43 AM
Not sure if I am doing something wrong or this needs some fix.
It's a quite simple scenario, here we go -
Can someone confirm if there is something wrong with deployment steps or could it be a potential bug or an expected behavior (that will be surprising).
FYI - all my deployments are in the Southeast Asia region and metadata is being stored in West US region.
May 21 2020 04:30 AM
Solution@bhushangawale all right, seems I have found the issue. It was because of the fact that the image itself was containing the wvd agent and agent boot-loader installed on it and hence. Had to re-create the image without these agents and issue was resolved. a big thanks to Dean Cefola for the tip!
May 21 2020 04:30 AM
Solution@bhushangawale all right, seems I have found the issue. It was because of the fact that the image itself was containing the wvd agent and agent boot-loader installed on it and hence. Had to re-create the image without these agents and issue was resolved. a big thanks to Dean Cefola for the tip!