Merge remote-tracking branch 'upstream/main' into AB#8605-TOC-update-for-Backup-and-Storage

Author: v-tappelgate

support/azure/virtual-machines/windows/windows-vm-wureset-tool.md

@@ -9,13 +9,13 @@ ms.date: 11/18/2025
 ms.custom: sap:Cannot create a VM, H1Hack27Feb2017
 ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 ---
-# Azure Virtual Machine (VM) Windows servicing stack reset tool
+# Azure Virtual Machine (VM) Windows Update Reset Tool
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
 ## Overview
 
-This article covers steps to run a PowerShell script that resets the Windows servicing stack for a VM running in Azure. Running the tool can fix most problems that prevent Windows Updates from installing successfully. 
+This article covers steps to run a PowerShell script that resets the Windows Update servicing stack for a VM running in Azure. Running the tool can fix most problems that prevent Windows Updates from installing successfully. 
 
 > [!NOTE]
 > This article is intended for use with support agents and IT professionals. If you're a home user and looking for more information about fixing Windows update errors, see [Fix Windows Update errors](https://support.microsoft.com/help/10164).
@@ -31,7 +31,7 @@ This article covers steps to run a PowerShell script that resets the Windows ser
 - Restarts services.
 - Generates a summary of actions performed.
 
-For more information, see [Resetting Windows Update servicing stack script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_WUA_Update_Reset?).
+For more information, see [Azure VM Windows WUA Update Reset Tool](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_WUA_Update_Reset?).
 
 
 :::image type="content" source="media/windows-vm-wureset-tool/windows-vm-wureset-tool.png" alt-text="Azure portal view Run Command example." lightbox="media/windows-vm-wureset-tool/windows-vm-wureset-tool.png":::   
@@ -50,12 +50,12 @@ For more information, see [Run scripts in your Windows VM by using action run co
 
 ## Recommended workflow
 
-1. Run `Windows_Update_Reset` to reset the servicing stack.
+1. Run `Windows_Update_Reset` to reset the Windows Update servicing stack.
 2. Try to install the Windows Update that previously failed.
 
 ## Additional resources
 
-- [Resetting Window Update servicing stack script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Update_Reset).
+- [Azure VM Windows WUA Update Reset Tool](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Update_Reset).
 
 
 [!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]

support/includes/azure/virtual-machines-runcmd-wu-tools.md

@@ -4,8 +4,8 @@
 >Trying to diagnose and resolve Windows Update or Windows OS upgrade issues for your Azure VM? Try one of the following tools:
 >
 >* [Azure VM Windows Update Error Detection Tool](../../azure/virtual-machines/windows/windows-vm-ipu-tool.md) to diagnose specific Windows Update errors.
->* [Azure VM Windows Servicing Stack Reset Tool](../../azure/virtual-machines/windows/windows-vm-wureset-tool.md) to reset the Windows servicing stack.
->* [Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool](../../azure/virtual-machines/windows/windows-vm-osupgradeassessment-tool.md) to validate the OS upgrade path and any known issues.
+>* [Azure VM Windows Windows Update Reset Tool](../../azure/virtual-machines/windows/windows-vm-wureset-tool.md) to reset the Windows servicing stack.
+>* [Azure VM Windows OS Upgrade Assessment Tool](../../azure/virtual-machines/windows/windows-vm-osupgradeassessment-tool.md) to validate the OS upgrade path and any known issues.
 >
 >If you're experiencing performance problems with VMs, run these tools first before contacting support.
 

support/system-center/scom/use-ca-certificate-on-scx-agent.md

@@ -2,7 +2,7 @@
 title: Convert self-signed SCX certificates to CA certificates
 description: Introduces how to convert a self-signed certificate on an SCX agent to a Certificate Authority (CA) signed certificate.
 ms.date: 04/15/2024
-ms.reviewer: alexkre, blakedrumm, edpaca, stparker, udmudiar, v-weizhu
+ms.reviewer: alexkre, blakedrumm, edpaca, stparker, udmudiar, v-weizhu, v-ryanberg
 ms.topic: how-to
 ms.custom: linux-related-content
 ---
@@ -76,65 +76,108 @@ On a CA server in your SCOM environment, follow these steps to create a certific
 
 ## Copy and edit the certificate on the Unix/Linux server
 
+Use one of the following methods to configure the certificate on the the Unix/Linux server:
+
+### Method 1: Configure certificate manually
+
 1. Copy the certificate to the Unix/Linux server for which the certificate was issued.
 1. Export the private key by using the following command:
 
     ```console
-    openssl pkcs12 -in <FileName>.pfx -nocerts -out key.pem
+    openssl pkcs12 -in <FileName>.pfx -nocerts -out /etc/opt/omi/ssl/omikey.pem -nodes -passin pass:"pfxpassword"
     ```
 
-    While exporting the private key from the certificate store, a new password has to be set for the new key file.
-
-    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-export-private-key.png" alt-text="Screenshot that shows the command to export the private key.":::
-
-    After the export is completed, you should see a *key.pem* file:
-
-    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-get-key-dot-pem-file.png" alt-text="Screenshot that shows the command to get the private key file.":::
+While exporting the private key from the certificate store, include the `-nodes` paramter (which stands for no Desktop Environments (DEs)). This instructs OpenSSL to output the private key in an unencrypted format. Otherwise a new password has to be set for the new key file. 
 
 1. Export the certificate by using the following command:
 
     ```console
-    openssl pkcs12 -in <FileName>.pfx -clcerts -nokeys -out omi.pem
+    openssl pkcs12 -in <FileName>.pfx -clcerts -nokeys -out /etc/opt/omi/ssl/omi-host-$(hostname).pem -passin pass:"pfxpassword"
     ```
 
-    While exporting the certificate from the certificate store, you have to enter the password for the *\<FileName>.pfx* file.
+1. Delete and create a new symbolic link:
 
-    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-export-certificate.png" alt-text="Screenshot that shows the command to export the certificate.":::
+    ```console
+    rm -f /etc/opt/omi/ssl/omi.pem
+    ln -s /etc/opt/omi/ssl/omi-host-$(hostname).pem /etc/opt/omi/ssl/omi.pem
+    ```
+   
+1. Set the correct permissions and ownership on the private key, certificate, and symbolic link:
 
-    After the export is completed, you should see an *omi.pem* file:
+    ```console
+    chmod 600 /etc/opt/omi/ssl/omikey.pem
+    chmod 640 /etc/opt/omi/ssl/omi-host-$(hostname).pem /etc/opt/omi/ssl/omi.pem
+    chown omi:omi /etc/opt/omi/ssl/omikey.pem
+    chown root:omi /etc/opt/omi/ssl/omi-host-$(hostname).pem /etc/opt/omi/ssl/omi.pem
+    ```
 
-    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-get-omi-dot-pem-file.png" alt-text="Screenshot that shows the command to get the certificate file.":::
+1. Restart the SCX agent by running the following command:
 
-1. Remove the password from the private key by using the following command:
+    ```console
+    scxadmin -restart
+    ```
+
+1. Make sure the Open Management Infrastructure (OMI) processes are running after restarting the agent:
 
     ```console
-    openssl rsa -in key.pem -out omikey.pem 
+    ps -ef | grep omi | grep -v grep
     ```
 
-    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-remove-password-from-private-key.png" alt-text="Screenshot that shows the command to remove password from the private key.":::
+    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-validate-omi-processes.png" alt-text="Screenshot that shows the command to validate omi processes running." lightbox="media/use-ca-certificate-on-scom-linux-agent/command-validate-omi-processes.png":::
 
-    This action is needed since the Linux agent doesn't know the password for the file.
+### Method 2: Configure certificate with bash script
 
-1. Move the *omikey.pem* file to the Open Management Infrastructure (OMI) directory by using the following command:
+1. Save the following bash script: `extract_scx_cert.sh`
 
     ```console
-    mv omikey.pem /etc/opt/omi/ssl/omikey.pem 
+    #!/bin/bash
+    
+    # Usage: sudo ./extract_scx_cert.sh /path/to/certificate.pfx <pfx_password>
+     
+    PFX_FILE="$1"
+    PFX_PASS="$2"
+    SSL_DIR="/etc/opt/omi/ssl"
+    KEY_FILE="$SSL_DIR/omikey.pem"
+    CERT_FILE="$SSL_DIR/omi-host-$(hostname).pem"
+    SYMLINK_FILE="$SSL_DIR/omi.pem"
+     
+    if [[ -z "$PFX_FILE" || -z "$PFX_PASS" ]]; then
+      echo "Usage: $0 /path/to/certificate.pfx <pfx_password>"
+      exit 1
+    fi
+     
+    echo "Extracting private key..."
+    openssl pkcs12 -in "$PFX_FILE" -nocerts -out "$KEY_FILE" -nodes -passin pass:"$PFX_PASS"
+     
+    echo "Extracting certificate..."
+    openssl pkcs12 -in "$PFX_FILE" -clcerts -nokeys -out "$CERT_FILE" -passin pass:"$PFX_PASS"
+     
+    echo "Creating symbolic link..."
+    rm -f "$SYMLINK_FILE"
+    ln -s "$CERT_FILE" "$SYMLINK_FILE"
+     
+    echo "Setting permissions..."
+    chmod 600 "$KEY_FILE"
+    chmod 640 "$CERT_FILE" "$SYMLINK_FILE"
+    chown root:omi "$CERT_FILE" "$SYMLINK_FILE"
+    chown omi:omi "$KEY_FILE"
+     
+    echo "Restarting omid service..."
+    systemctl restart omid
     ```
 
-1. Restart the SCX agent by using the following command:
+1. Change the script permissions to be run:
 
     ```console
-    scxadmin -restart
+    chmod +x /home/user/extract_scx_cert.sh
     ```
 
-1. Make sure the *omi* processes are running after restarting the agent:
+1. Run the following command to run the script with these two parameters: the path to the PFX file and the password for it.
 
     ```console
-    ps -ef | grep omi | grep -v grep
+    sudo ./extract_scx_cert.sh /path/to/certificate.pfx pfx_password
     ```
 
-    :::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-validate-omi-processes.png" alt-text="Screenshot that shows the command to validate omi processes running." lightbox="media/use-ca-certificate-on-scom-linux-agent/command-validate-omi-processes.png":::
-
 ## Validate that the certificate is signed by the CA
 
 1. Run the following command on the agent to verify that the certificate is signed by the CA:
@@ -159,6 +202,8 @@ On a CA server in your SCOM environment, follow these steps to create a certific
     notAfter=Jul 25 12:12:14 2033 GMT
     ```
 
+    > The path `/etc/opt/microsoft/scx/ssl` contains a symbolic link `scx.pem -> /etc/opt/omi/ssl/omi.pem` that's used by the SCX agent in order to use the OMI certificate created earlier.
+
 1. Run a network trace on one of the management servers/gateways in the UNIX/Linux resource pool.
 1. Run the following `WinRM` command against the agent and make sure you get the instance output:
 

support/windows-server/backup-and-storage/troubleshoot-performance-issues-storage-spaces-direct.md

@@ -0,0 +1,132 @@
+---
+title: Troubleshoot Performance Issues in Storage Spaces Direct
+description: Helps you identify and fix performance issues related to Storage Spaces Direct (S2D) in Windows Server environments.
+ms.date: 12/08/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, simonw, v-appelgatet
+ms.custom:
+- sap:backup, recovery, disk, and storage\Storage Spaces Direct (S2D)
+- pcy:WinComm Storage High Avail
+appliesto:
+  - ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+---
+# Troubleshoot performance issues in Storage Spaces Direct
+
+This article helps you identify and fix performance issues that are related to Storage Spaces Direct (S2D) in Windows Server environments.
+
+## Symptoms
+
+You experience one or more of the following performance issues:
+
+- When you access files that are stored in storage spaces, read and write speeds are slower than expected.
+- When you perform disk-intensive operations such as transferring large files, you experience delays or lags.
+- Task Manager shows high disk queue length or high disk usage.
+- Applications take longer than usual to load or respond.
+
+## Causes
+
+Several factors can cause degraded performance or bottlenecks for Storage Spaces. The following list includes the most common causes:
+
+- **Incorrect drive configuration**: Using mismatched or incompatible drives within a storage pool
+- **Incorrect storage space type**: Selecting the wrong resiliency option (such as parity instead of simple or mirror) for the workload
+- **Insufficient system resources**: Low memory or CPU availability
+- **Fragmentation**: Excessive fragmentation within the storage pool (slow data access)
+- **Firmware and driver issues**: Outdated or incompatible drive firmware and drivers
+- **Background tasks**: Resource-intensive background tasks, such as disk scrubbing or repair jobs
+
+## Resolution
+
+Follow the steps in this section to improve the performance of your storage space.
+
+Before you start to troubleshoot performance issues, consider measuring the system's current performance to establish a baseline. You can use tools such as Performance Monitor or Resource Monitor to collect metrics. You can also use third-party tools such as DiskSpd or CrystalDiskMark to run benchmark tests and gather detailed performance metrics.
+
+> [!IMPORTANT]  
+> Before you start changing your storage space configuration, make sure that you back up the storage space data and configuration settings.
+
+### Step 1: Collect performance metrics, events, and configuration information
+
+To help identify issues, collect the following data:
+
+- A detailed description of the storage space configuration, including the resiliency type and drive details. Use the following questions as guidelines:
+  - What type of storage space configuration is being used? For example, simple, mirror, or parity?
+  - What's the size of the storage pool, and how many drives are included?
+  - What are the current firmware and driver versions for the drives in the storage pool?
+  - Are all drives in the pool of the same type, capacity, and speed?
+  - Were any recent changes made to the system, such as software updates, hardware replacements, or new applications installed?
+  
+- Performance metrics, such as disk queue length and throughput. You can use tools such as Performance Monitor or Task Manager to collect this information. You can also review performance history information, as described in [Performance history for Storage Spaces Direct](/windows-server/storage/storage-spaces/performance-history).
+- Logs from the Event Viewer, specifically under the **System** and **Storage Spaces** categories. Include:
+  - Any error messages or warnings in the Event Viewer that are related to S2D, storage pools, or disk operations.
+  - Screenshots or photos of any error messages or alerts.
+
+- The output of the following Windows PowerShell commands:
+
+   ```powershell
+  Get-StoragePool | Get-PhysicalDisk | Select-Object DeviceID, MediaType, Size, HealthStatus
+  Get-VirtualDisk | Select-Object FriendlyName, ResiliencySettingName, OperationalStatus
+  Get-StoragePool | Get-StorageSubSystem | Select-Object FriendlyName, HealthStatus
+  ```
+
+### Step 2: Verify the Storage Space configuration
+
+1. Make sure that all the drives in the pool are of the same type (for example, all solid-state drives (SSDs) or all hard disk drives (HDDs)). Also make sure that the drives have similar performance characteristics.
+1. Verify that the storage space type (simple, mirror, or parity) is appropriate for the workload. For more information about storage space types in S2D, see [Deep Dive: Volumes in Storage Spaces Direct](https://techcommunity.microsoft.com/blog/filecab/deep-dive-volumes-in-storage-spaces-direct/425807).
+1. If you make any changes during this step, test the system's performance, and compare it to earlier measurements.
+
+### Step 3: Review the Server Manager and the event logs for potential issues
+
+1. In Server Manager (or by using Windows PowerShell) check the health and operational states of the storage pools and other S2D components. For more information, see [Troubleshoot Storage Spaces and Storage Spaces Direct health and operational states](/windows-server/storage/storage-spaces/storage-spaces-states).
+1. In Event Viewer, review the logs for Storage Spaces Direct warnings or errors.
+1. If you identify any issues (such as failing drives or subsystem errors), remediate them, as appropriate.
+1. If you make any changes during this step, test the system's performance, and compare it to earlier measurements.
+
+### Step 4: Make sure that the drivers and firmware for the drives are up to date
+
+1. Verify that all drives have the latest firmware installed.
+1. Update the storage controller and drive drivers to the most recent versions that the manufacturer supports.
+1. If you make any changes during this step, test the system's performance, and compare it to earlier measurements.
+
+### Step 5: Run storage maintenance tasks
+
+1. To optimize the storage pool, run the following cmdlet at a PowerShell command prompt:
+
+   ```powershell
+   Optimize-StoragePool -FriendlyName <StoragePoolName>
+   ```
+
+   > [!NOTE]  
+   > In this cmdlet, \<StoragePoolName> is the name of the storage pool. If you have to identify the storage pool name, run `Get-StoragePool`.
+
+1. If the storage pool uses HDD drives, manually defragment the drives.
+
+   > [!WARNING]  
+   > Don't perform this step if the storage pool uses SSD drives. Defragmentation can reduce the lifespan and performance of SSD drives.
+
+1. Test the system's performance, and compare it to earlier measurements.
+
+### Step 6: Identify resource usage issues
+
+1. Use monitoring tools such as Task Manager, Performance Monitor, or Resource Monitor to identify bottlenecks in CPU, memory, or disk usage. For more information about how to use these tools, see [Scenario guide: Troubleshoot performance problems in Windows](../performance/troubleshoot-performance-problems-in-windows.md).
+1. Close any unnecessary applications or processes that consume system resources.
+1. If you make any changes during this step, test the system's performance, and compare it to earlier measurements.
+
+### Step 7: Rebuild or re-create the storage space
+
+If you followed the previous steps, and the S2D performance didn't improve sufficiently, consider rebuilding the storage space. Follow these steps:
+
+1. Make sure that all backups are current and available.
+1. Delete the existing storage space.
+1. Re-create the storage space. Use optimal settings.
+1. Restore the data to the new storage space.
+
+## Preventing future performance issues
+
+To avoid future S2D performance issues, consider the following guidelines and best practices:
+
+- Make sure that a single storage pool uses drives that have similar performance, capacity, and media type. For more information about hardware requirements, see [Storage Spaces Direct hardware requirements in Windows Server](/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements).
+- Regularly update firmware and drivers to the latest manufacturer-recommended versions.
+- Monitor storage pool health by using the `Get-StoragePool` and `Get-PhysicalDisk` cmdlets.
+- To prevent data loss if a drive fails, schedule regular backups.
+- Unless you're implementing tiered storage, don't mix SSD and HDD drives in the same storage pool.

support/windows-server/toc.yml

@@ -778,6 +778,8 @@ items:
       href: ./backup-and-storage/extend-stand-alone-tiered-storage-spaces.md
     - name: Manage disks in standalone Storage Spaces
       href: ./backup-and-storage/manage-disks-standalone-storage-spaces.md
+    - name: Troubleshoot performance issues in Storage Spaces Direct
+      href: ./backup-and-storage/troubleshoot-performance-issues-storage-spaces-direct.md
   - name: System Restore or resetting your computer
     items:
     - name: How to restore a Windows 7 installation