-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logon scripts on ARCBoxClient machine fail! #2845
Comments
Can you share your parameters please, without including any secrets? |
sure...
I used the default parameters
the tenant is "CONTOSO" ..... see the Subscription
[cid:cd045e55-6e55-449d-ab43-61845f962c5b]
[cid:e6ada8e9-944c-4e5f-a05c-2e8e8178359a]
[cid:3218812e-2949-491c-b02e-395d6e96c25b]
let me know if you have any questions or concerns
Daniele
…________________________________
Da: Dale Kirby ***@***.***>
Inviato: venerdì 15 novembre 2024 02:34
A: microsoft/azure_arc ***@***.***>
Cc: DanieleM69 ***@***.***>; Author ***@***.***>
Oggetto: Re: [microsoft/azure_arc] Logon scripts on ARCBoxClient machine fail! (Issue #2845)
Can you share your parameters please, without including any secrets?
—
Reply to this email directly, view it on GitHub<#2845 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMDPIXNO7R74JESFKBBSR432AVFRZAVCNFSM6AAAAABRUMB2XWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXG43TEOBQGE>.
You are receiving this because you authored the thread.
|
Same here. As a workaround I manually renamed the ArcBox-SQL to contoso-SQL in the folder This was only necessary for ArcBox-SQL.
|
@yveskerwyn @DanieleM69 Did you specify the Would be great if one of you could share all parameters specified for the deployment, then we can try to re-produce the issue. |
@yveskerwyn @DanieleM69 Any updates from your end? |
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: