You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The problem is related to ArcBox for IT Pro scenario.
Describe the issue or the bug
The Logon scripts unable to complete because the environment parameters (Tenant, resource group etc.) non correctly passed to the PowerShell scripts!
To Reproduce
The deployment was executed using the ARM Template across multiple regions ("East US, France Central") and produced same results. It was also tested on different subscriptions: Microsoft on Internal and External Tenant.
The PowerShell Logon scripts unable to complete the expected scenario:
SQL Server VM is only the VM deployed on Hyper-V Server
No Other VW are deployed
No Onboarding of Arc Enabled Server
the last action is deploying SQL Server VM
Expected behavior
Environment summary
Have you looked at the Troubleshooting and Logs section?
No relevant Troubleshooting I can find
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Hi DanieleM69! 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?
The problem is related to ArcBox for IT Pro scenario.
Describe the issue or the bug
The Logon scripts unable to complete because the environment parameters (Tenant, resource group etc.) non correctly passed to the PowerShell scripts!
To Reproduce
The deployment was executed using the ARM Template across multiple regions ("East US, France Central") and produced same results. It was also tested on different subscriptions: Microsoft on Internal and External Tenant.
The PowerShell Logon scripts unable to complete the expected scenario:
Expected behavior
Environment summary
Have you looked at the Troubleshooting and Logs section?
No relevant Troubleshooting I can find
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: