Merge pull request #7541 from MicrosoftDocs/main

Auto push to live 2024-10-23 02:00:02

Author: Deland-Han

.openpublishing.redirection.json

@@ -12339,6 +12339,11 @@
       "source_path": "support/dynamics-365/sales/sorry-something-went-wrong-while-initializing-the-app-error.md",
       "redirect_url": "/troubleshoot/dynamics-365/sales/errors-when-opening-365-app-outlook",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "support/mem/configmgr/setup-migrate-backup-recovery/site-system-installation-account-used-for-db-connection.md",
+      "redirect_url": "/troubleshoot/mem/configmgr/welcome-configuration-manager",
+      "redirect_document_id": false
     }
   ]
 }

support/azure/azure-kubernetes/create-upgrade-delete/error-code-invalidparameter.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot the InvalidParameter error code
 description: Learn how to troubleshoot the InvalidParameter error when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 03/22/2022
+ms.date: 10/22/2024
 editor: v-jsitser
 ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis
 ms.service: azure-kubernetes-service

support/azure/azure-kubernetes/create-upgrade-delete/error-code-serviceprincipalvalidationclienterror.md

@@ -1,9 +1,8 @@
 ---
 title: Troubleshoot the ServicePrincipalValidationClientError error code
 description: Learn how to troubleshoot the ServicePrincipalValidationClientError error when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 03/22/2022
-editor: v-jsitser
-ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis
+ms.date: 10/23/2024
+ms.reviewer: rissing, chiragpa, erbookbi, momajed, v-leedennis, v-weizhu
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the ServicePrincipalValidationClientError error code so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -52,14 +51,28 @@ The secret that's provided for the highlighted service principal isn't valid.
 
 ## Solution 1: Reset the service principal secret
 
-Reset the secret that's used for the service principal by running the [az ad sp credential reset](/cli/azure/ad/sp/credential#az-ad-sp-credential-reset) command:
+To resolve this issue, reset the service principal secret by using one of the following methods:
+
+- Reset the service principal's credential by running the [az ad sp credential reset](/cli/azure/ad/sp/credential#az-ad-sp-credential-reset) command:
+
+  ```azurecli-interactive
+  az ad sp credential reset --name "01234567-89ab-cdef-0123-456789abcdef" --query password --output tsv
+  ```
+
+- Specify the expiration date by running the following command: 
+
+  ```azurecli-interactive
+  az ad sp credential reset --name <service-principal-name> --credential-description "New secret for AKS" --years 1
+  ```
+
+The preceding command resets the secret and displays it as output. Then, you can specify the new secret when you try to create the new cluster again.
+
+For failed operations in an existing cluster, ensure that you update your AKS cluster with the new secret:
 
 ```azurecli-interactive
-az ad sp credential reset --name "01234567-89ab-cdef-0123-456789abcdef" --query password --output tsv
+az aks update-credentials --resource-group <resource-group> --name <aks-cluster> --reset-service-principal --client-secret <new-client-secret>
 ```
 
-This command resets the secret, and displays it as output. Then, you can specify the new secret when you try again to create the new cluster.
-
 ## Solution 2: Create a new service principal
 
 You can create a new service principal and get the secret that's associated with it by running the [az ad sp create-for-rbac](/cli/azure/ad/sp#az-ad-sp-create-for-rbac) command:
@@ -81,6 +94,12 @@ The output of the command should resemble the following JSON string:
 
 Note the `appId` and `password` values that are generated. After you get these values, you can rerun the cluster creation command for the new service principal and secret.
 
+To update your AKS cluster with the new service principal's credential, run the following command:
+
+```azurecli-interactive
+az aks update-credentials --resource-group <resource-group> --name <aks-cluster> --service-principal <new-client-id> --client-secret <new-client-secret>
+```
+
 ## More information
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)

support/azure/virtual-machines/windows/debug-customscriptextension-runcommand-scripts.md

@@ -1,8 +1,8 @@
 ---
 title: Debug PowerShell scripts run by Custom Script Extension or Run Command
 description: Troubleshoot PowerShell script failures when you run them remotely on a virtual machine by using the Custom Script Extension or Run Command feature.
-ms.date: 03/15/2022
-ms.reviewer: clandis, v-leedennis
+ms.date: 10/23/2024
+ms.reviewer: clandis, kegregoi, v-leedennis, v-weizhu
 editor: v-jsitser
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Admin - Windows (Guest OS), devx-track-azurepowershell
@@ -121,76 +121,31 @@ wevtutil set-log "Microsoft-Windows-PowerShell/Operational" /ms:104857600
 
 ### Turn on process creation auditing
 
-Use the [auditpol set](/windows-server/administration/windows-commands/auditpol-set) command, [New-Item](/powershell/module/microsoft.powershell.management/new-item) cmdlet, and [New-ItemProperty](/powershell/module/microsoft.powershell.management/new-itemproperty) cmdlet to turn on process creation auditing:
+Use the following command to turn on process creation auditing:
 
-```powershell
-auditpol /set /category:"detailed tracking" /success:enable /subcategory:"Process Creation"
-
-$registryPath = @{
-    Path = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit'
-}
-New-Item @registryPath
-
-$forceDwordOne = @{
-    PropertyType = 'DWord'
-    Value = 1
-    Force = $True
-}
-New-ItemProperty @registryPath -Name 'ProcessCreationIncludeCmdLine_Enabled' @forceDwordOne
+```console
+reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit" /v "ProcessCreationIncludeCmdLine_Enabled" /t REG_DWORD /d 1 /f
 ```
 
 ### Turn on PowerShell transcription
 
-```powershell
-$registryPath = @{
-    Path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\Transcription'
-    Force = $True
-}
-New-Item @registryPath
-
-$dwordOne = @{
-    PropertyType = 'DWord'
-    Value = 1
-}
-New-ItemProperty @registryPath -Name 'EnableTranscripting' @dwordOne
-New-ItemProperty @registryPath -Name 'EnableInvocationHeader' @dwordOne
-New-ItemProperty @registryPath -Name 'OutputDirectory' -PropertyType 'String' -Value 'C:\Transcripts'
+```console
+reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\Transcription" /v "EnableTranscripting" /t REG_DWORD /d 1 /f
+reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\Transcription" /v "EnableInvocationHeader" /t REG_DWORD /d 1 /f
+reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\Transcription" /v "OutputDirectory" /t REG_SZ /d C:\Transcripts /f
 ```
 
 ### Turn on PowerShell module logging
 
-```powershell
-$moduleLoggingPath = @{
-    Path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging'
-}
-New-Item @moduleLoggingPath
-
-$forceDwordOne = @{
-    PropertyType = 'DWord'
-    Value = 1
-    Force = $True
-}
-New-ItemProperty @moduleLoggingPath -Name 'EnableModuleLogging' @forceDwordOne
-
-$moduleNamesPath = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames'
-New-Item -Path $moduleNamesPath
-New-ItemProperty -Path $moduleNamesPath -Name '*' -PropertyType String -Value '*'
+```console
+reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging" /v "EnableModuleLogging" /t REG_DWORD /d 1 /f
+reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames" /v "*" /t REG_SZ /d *
 ```
 
 ### Turn on PowerShell script block logging
 
-```powershell
-$registryPath = @{
-    Path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging'
-}
-New-Item @registryPath
-
-$forceDwordOne = @{
-    PropertyType = 'DWord'
-    Value = 1
-    Force = $True
-}
-New-ItemProperty @registryPath -Name 'EnableScriptBlockLogging' @forceDwordOne
+```console
+reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v "EnableScriptBlockLogging" /t REG_DWORD /d 1 /f
 ```
 
 ## Understand the output
@@ -294,65 +249,29 @@ To undo the changes that you made to enable the logging of PowerShell scripting
 
 1. Turn off process creation auditing:
 
-    ```powershell
-    auditpol /set /category:"detailed tracking" /success:disable /subcategory:"Process Creation"
-    $commandSettings = @{
-        Path = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit'
-        Name = 'ProcessCreationIncludeCmdLine_Enabled'
-        PropertyType = 'DWord'
-        Value = 0
-        Force = $True
-    }
-    New-ItemProperty @commandSettings
+    ```console
+    reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit" /v "ProcessCreationIncludeCmdLine_Enabled" /t REG_DWORD /d 0 /f
     ```
 
 1. Turn off transcription:
 
-    ```powershell
-    $registryPath = @{
-        Path = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription'
-    }
-    $forceDwordZero = @{
-        PropertyType = 'DWord'
-        Value = 0
-        Force = $True
-    }
-    New-ItemProperty @registryPath -Name 'EnableTranscripting' @forceDwordZero
-    New-ItemProperty @registryPath -Name 'EnableInvocationHeader' @forceDwordZero
-    Remove-ItemProperty @registryPath -Name 'OutputDirectory'
+    ```console
+    reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription" /v "EnableTranscripting" /t REG_DWORD /d 0 /f
+    reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription" /v "EnableInvocationHeader" /t REG_DWORD /d 0 /f
+    reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription" /v "OutputDirectory"
     ```
 
 1. Turn off module logging:
 
-    ```powershell
-    $moduleLoggingPath = @{
-        Path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging'
-    }
-    $forceDwordZero = @{
-        PropertyType = 'DWord'
-        Value = 0
-        Force = $True
-    }
-    New-ItemProperty @moduleLoggingPath -Name 'EnableModuleLogging' @forceDwordZero
-
-    $moduleNamesPath = @{
-        Path = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames'
-    }
-    Remove-ItemProperty @moduleNamesPath -Name '*'
+    ```console
+    reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging" /v "EnableModuleLogging" /t REG_DWORD /d 0 /f
+    reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames" /v "*"
     ```
 
 1. Turn off script block logging:
 
-    ```powershell
-    $registryPath = @{
-        Path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging'
-    }
-    $forceDwordZero = @{
-        PropertyType = 'DWord'
-        Value = 0
-        Force = $True
-    }
-    New-ItemProperty @registryPath -Name 'EnableScriptBlockLogging' @forceDwordZero
+    ```console
+    reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v "EnableScriptBlockLogging" /t REG_DWORD /d 0 /f
     ```
 
 1. Remove the transcription folder:

support/developer/webapps/iis/health-diagnostic-performance/http-403-14-forbidden-webpage.md

@@ -9,7 +9,7 @@ ms.custom: sap:Site Behavior and Performance\Runtime errors and exceptions, incl
 
 This article helps you resolve the "HTTP Error 403.14 - Forbidden - The web server is configured to not list the contents of this directory" error that occurs when you open an Internet Information Services (IIS) webpage.
 
-_Original product version:_   Internet Information Services
+_Original product version:_   Internet Information Services  
 _Original KB number:_   942062
 
 > [!NOTE]

support/docfx.json

@@ -217,7 +217,7 @@
         "power-platform/ai-builder/**/**.*": "ai-builder",
         "sql/**/*.md": "sql",
         "sql/analysis-services/**/*.md": "analysis-services",
-        "sql/azure-sql/**/*.md": "virtual-machines-sql",
+        "sql/azure-sql/**/*.md": "azure-vm-sql-server",
         "sql/reporting-services/**/*.md": "reporting-services",
         "developer/dotnet/**/*.md": "dotnet",
         "developer/visualstudio/**/*.md": "visual-studio-family",

support/mem/configmgr/setup-migrate-backup-recovery/site-system-installation-account-used-for-db-connection.md

@@ -335,8 +335,6 @@ items:
           href: setup-migrate-backup-recovery/failed-to-find-folder-or-file-error.md
         - name: Function sequence error in Smsdbmon.log
           href: setup-migrate-backup-recovery/function-sequence-error.md
-        - name: Site system installation account incorrectly used for database connection
-          href: setup-migrate-backup-recovery/site-system-installation-account-used-for-db-connection.md
         - name: SQL Server updates must be manually installed on secondary sites
           href: setup-migrate-backup-recovery/sql-cus-must-be-installed-on-secondary-sites.md
         - name: Support policies for manual database changes

support/mem/configmgr/toc.yml

@@ -136,6 +136,8 @@
       href: desktop-flows/console-not-show-desktop-flows.md
     - name: Power Automate service doesn't start automatically after restarting
       href: desktop-flows/windows-services-not-start-after-restart.md
+    - name: Registration fails with RegisterFlowMachine deactivated error
+      href: desktop-flows/verify-dataverse-process-registerflowmachine.md
     - name: SessionHasLoggedOff occurs during a desktop flow run connected with the cloud
       href: desktop-flows/session-has-logged-off-troubleshooting.md
     - name: 'Security update for "connect with sign-in" connections on AD domain-joined machines'

support/power-platform/power-automate/toc.yml

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot high-CPU-usage issues in SQL Server
 description: This article provides a procedure to help you fix high-CPU-usage issues on a server that is running SQL Server.
-ms.date: 01/25/2024
+ms.date: 10/23/2024
 ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage)
 ms.topic: troubleshooting
 ms.reviewer: jopilov, v-jayaramanp, v-sidong
@@ -34,24 +34,28 @@ Use one of the following tools to check whether the SQL Server process is actual
 
 - You can use the following PowerShell script to collect the counter data over a 60-second span:
 
-    ```powershell
-    $serverName = $env:COMPUTERNAME
-    $Counters = @(
-        ("\\$serverName" + "\Process(sqlservr*)\% User Time"), ("\\$serverName" + "\Process(sqlservr*)\% Privileged Time")
-    )
-    Get-Counter -Counter $Counters -MaxSamples 30 | ForEach {
-        $_.CounterSamples | ForEach {
-            [pscustomobject]@{
-                TimeStamp = $_.TimeStamp
-                Path = $_.Path
-                Value = ([Math]::Round($_.CookedValue, 3))
-            }
-            Start-Sleep -s 2
-        }
-    }
-    ```
-
-If `% User Time` is consistently greater than 90 percent (% User Time is the sum of processor time on each processor, its maximum value is 100% * (no of CPUs)), the SQL Server process is causing high CPU usage. However, if `% Privileged time` is consistently greater than 90 percent, your antivirus software, other drivers, or another OS component on the computer is contributing to high CPU usage. You should work with your system administrator to analyze the root cause of this behavior.
+  ```powershell
+  $serverName = $env:COMPUTERNAME
+  $Counters = @(
+      ("\\$serverName" + "\Process(sqlservr*)\% User Time"), ("\\$serverName" + "\Process(sqlservr*)\% Privileged Time")
+  )
+  Get-Counter -Counter $Counters -MaxSamples 30 | ForEach {
+      $_.CounterSamples | ForEach {
+          [pscustomobject]@{
+              TimeStamp = $_.TimeStamp
+              Path = $_.Path
+              Value = ([Math]::Round($_.CookedValue, 3))
+          }
+          Start-Sleep -s 2
+      }
+  }
+  ```
+
+  If `% User Time` is consistently greater than 90 percent (% User Time is the sum of processor time on each processor, its maximum value is 100% * (no of CPUs)), the SQL Server process is causing high CPU usage. However, if `% Privileged time` is consistently greater than 90 percent, your antivirus software, other drivers, or another OS component on the computer is contributing to high CPU usage. You should work with your system administrator to analyze the root cause of this behavior.
+
+- [Performance Dashboard](/sql/relational-databases/performance/performance-dashboard): In SQL Server Management Studio, right click **\<SQLServerInstance\>** and select **Reports** > **Standard Reports** > **Performance Dashboard**.
+
+  The dashboard will illustrate a graph titled **System CPU Utilization** with a bar chart. The darker color indicates the SQL Server engine CPU utilization, while the lighter color represents the overall operating system CPU utilization (see the legend on the graph for reference). Select the circular refresh button or <kbd>F5</kbd> to see updated utilization.
 
 ## Step 2: Identify queries contributing to CPU usage