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
Copy file name to clipboardExpand all lines: azure-local/known-issues.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,7 @@ The following table lists the known issues from previous releases:
94
94
| Update | When updating the Azure Local instance via the Azure Update Manager, the update progress and results may not be visible in the Azure portal.| To work around this issue, on each node, add the following registry key (no value needed):<br><br>`New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Services\HciCloudManagementSvc\Parameters" -force`</br><br> Then on one of the nodes, restart the Cloud Management cluster group. </br><br>`Stop-ClusterGroup "Cloud Management"`</br><br>`Start-ClusterGroup "Cloud Management"`</br><br> This won't fully remediate the issue as the progress details may still not be displayed for a duration of the update process. To get the latest update details, you can [Retrieve the update progress with PowerShell](./update/update-via-powershell-23h2.md#step-6-track-update-progress). |
95
95
| Update <!--26659432-->|In some cases, `SolutionUpdate` commands could fail if run after the `Send-DiagnosticData` command. | Make sure to close the PowerShell session used for `Send-DiagnosticData`. Open a new PowerShell session and use it for `SolutionUpdate` commands.|
96
96
| Security <!-- 56969147 -->| When fixing the compliance for the minimum password length rule, even after you've changed the minimum password length on the Azure Local host to 14, you continue to see it as non-compliant in Azure policy. | You can verify the length of the password using the `net accounts` cmdlet. In the output, find **Minimum password length** to see the value. |
97
+
| Azure Arc registration <!-- 32995193 -->| When registering a new machine with Azure Arc, registration fails during `ImageRecipeValidationTests` with the following error:<br>` "Responses": [ { "Name": "ImageRecipeValidation", "Status": "Failed", "Errors": [ { "ErrorMessage": "Diagnostics failed for the test category: ImageRecipeValidation.", "StackTrace": null, "ExceptionType": "DiagnosticsTestFailedException", "RecommendedActions": [ "Please contact Microsoft support." ] } ] } `| Complete these steps:<br>1. Open PowerShell as Administrator.<br>2. Run the following command:<br>`Get-ScheduledTask -TaskName ImageCustomizationScheduledTask`<br>3. If the state is `Ready`, do the following:<br>a. Run `Get-ScheduledTask -TaskName ImageCustomizationScheduledTask \| Start-ScheduledTask`<br>b. Wait for the task to reach the `Disabled` state. Rerun the `Get-ScheduledTask -TaskName ImageCustomizationScheduledTask` command as needed until the task state shows `Disabled`. |
97
98
98
99
## Known and expected behaviors
99
100
@@ -153,6 +154,7 @@ The following table lists the known issues in this release:
153
154
| Add server <br> Repair server <!--32483959-->| If running `Add-server` and `Repair-server` cmdlets with customized storage adapter IP configured in your Azure Local instance, the operation might fail with the error: <br> `Type 'ConfigureAzureStackHostStorageAdpaterIPAddressesInAddRepairNode' of Role 'HostNetwork' raised an exception: Connecting to remote server <MACHINE> failed with the following error message : Access is denied.`. | Contact Microsoft Support if you experience this issue. |
154
155
| Security management <!--57340784-->| The **Security defaults**, **Application control**, and **Data protections** pages show *Unknown* for all security settings. | This issue is only in the security compliance report. The states of the security settings are unaffected. Use PowerShell to verify the compliance status of the security settings. <br><br>For more information, see [Manage secure baseline via PowerShell cmdlets](./manage/manage-secure-baseline.md#powershell-cmdlet-properties)|
155
156
| Deployment <!--33008717-->| In this release and previous releases, registration fails with the following error when you try to register Azure Local machines with Azure Arc: <br>`AZCMAgent command failed with error: >> exitcode: 42. Additional Info: See https://aka.ms/arc/azcmerror`. | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/users/kagoyal/tsg-error42/TSG/ArcRegistration/TSG%20%7C%20Arc%20registration%20failing%20with%20error%2042.md). |
157
+
| Azure Arc registration <!-- 32995193 -->| When registering a new machine with Azure Arc, registration fails during `ImageRecipeValidationTests` with the following error:<br>` "Responses": [ { "Name": "ImageRecipeValidation", "Status": "Failed", "Errors": [ { "ErrorMessage": "Diagnostics failed for the test category: ImageRecipeValidation.", "StackTrace": null, "ExceptionType": "DiagnosticsTestFailedException", "RecommendedActions": [ "Please contact Microsoft support." ] } ] } `| Complete these steps:<br>1. Open PowerShell as Administrator.<br>2. Run the following command:<br>`Get-ScheduledTask -TaskName ImageCustomizationScheduledTask`<br>3. If the state is `Ready`, do the following:<br>a. Run `Get-ScheduledTask -TaskName ImageCustomizationScheduledTask \| Start-ScheduledTask`<br>b. Wait for the task to reach the `Disabled` state. Rerun the `Get-ScheduledTask -TaskName ImageCustomizationScheduledTask` command as needed until the task state shows `Disabled`. |
0 commit comments