Note: For ease of issues and pull requests management and tracking, we kindly ask you to provide a meaningful and concise title to this issue and answer all questions to the best of your ability.
Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
After completing the Deployment: Bicep deployment via Azure CLI step and connecting to Agora-Client-VM, the Logon scripts is showing errors while installing Azure IoT operations. These errors appear multiple times as the logon scripts tried to install Azure IoT operations again and again. After a while the logon script's window disappears without completing the installation of Azure IoT operations.
Note: I have used Standard_D32s_v3 as vmSize instead of Standard_D32s_v5 due to capacity availability issue for the region and subscription.
Hi nabeelmsft! Thank you for opening this issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on the Arc Jumpstart.
Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
https://arcjumpstart.com/azure_jumpstart_ag/contoso_motors/deployment
Describe the issue or the bug
After completing the Deployment: Bicep deployment via Azure CLI step and connecting to Agora-Client-VM, the Logon scripts is showing errors while installing Azure IoT operations. These errors appear multiple times as the logon scripts tried to install Azure IoT operations again and again. After a while the logon script's window disappears without completing the installation of Azure IoT operations. Note: I have used Standard_D32s_v3 as vmSize instead of Standard_D32s_v5 due to capacity availability issue for the region and subscription.
To Reproduce
Expected behavior
The above-mentioned errors should not show, and logon scripts should complete successfully. Environment summary
Dependencies:
Have you looked at the Troubleshooting and Logs section?
Screenshots
Additional context
Standard_D32s_v3 as vmSize instead of Standard_D32s_v5 due to capacity availability