Merge pull request #7604 from MicrosoftDocs/repo_sync_working_branch

Resolve syncing conflicts from repo_sync_working_branch to main

Author: robinharwood

WindowsServerDocs/administration/windows-commands/lodctr.md

@@ -4,7 +4,7 @@ description: Reference article for the lodctr command, which allows you to regis
 ms.topic: reference
 ms.author: roharwoo
 author: robinharwood
-ms.date: 10/16/2017
+ms.date: 10/22/2025
 ---
 
 # lodctr
@@ -33,6 +33,7 @@ lodctr <filename> [/s:<filename>] [/r:<filename>] [/t:<servicename>]
 #### Remarks
 
 - If the information that you supply contains spaces, use quotation marks around the text (for example, "file name 1").
+- An exit code of **0** indicates the command line syntax was correct. It doesn't mean the operation was successful. Check the output from the command for potential error messages.
 
 ### Examples
 

WindowsServerDocs/administration/windows-commands/ping.md

@@ -28,7 +28,7 @@ ping [/t] [/a] [/n <count>] [/l <size>] [/f] [/I <TTL>] [/v <TOS>] [/r <count>]
 
 | Parameter | Description |
 |:--:|---|
-| /t | Specifies ping continue sending echo Request messages to the destination until interrupted. To interrupt and display statistics, press CTRL+ENTER. To interrupt and quit this command, press CTRL+C. |
+| /t | Specifies ping continue sending echo Request messages to the destination until interrupted. To interrupt and display statistics, press CTRL+BREAK. To interrupt and quit this command, press CTRL+C. |
 | /a | Specifies reverse name resolution be performed on the destination IP address. If this operation is successful, ping displays the corresponding host name. |
 | /n `<count>` | Specifies the number of echo Request messages be sent. The default is 4. |
 | /l `<size>` | Specifies the length, in bytes, of the **Data** field in the echo Request messages. The default is 32. The maximum size is 65,500. |

WindowsServerDocs/administration/windows-commands/unlodctr.md

@@ -4,7 +4,7 @@ description: Reference article for the unlodctr command, which removes Performan
 ms.topic: reference
 ms.author: daknappe
 author: dknappettmsft
-ms.date: 10/16/2017
+ms.date: 10/22/2025
 ---
 
 # unlodctr
@@ -29,6 +29,10 @@ unlodctr <drivername>
 | `<drivername>` | Removes the **Performance counter name** settings and **Explain text** for driver or service `<drivername>` from the Windows Server registry. If your `<drivername>` includes spaces, you must use quotation marks around the text, for example "Driver name". |
 | /? | Displays help at the command prompt. |
 
+#### Remarks
+
+An exit code of **0** indicates the command line syntax was correct. It doesn't mean the operation was successful. Check the output from the command for potential error messages.
+
 ## Examples
 
 To remove the current **Performance counter names** and **Explain text** for the Simple Mail Transfer Protocol (SMTP) service, type:

WindowsServerDocs/identity/ad-cs/migrate-certification-authority.md

@@ -1,5 +1,5 @@
 ---
-title: Migrate the Certification Authority in Windows Server
+title: Migrate a Certification Authority in Windows Server
 description: Learn how to migrate your Certification Authority with step-by-step instructions and best practices.
 ms.topic: how-to
 ms.author: daknappe
@@ -8,7 +8,7 @@ ms.date: 04/22/2025
 #customer intent: As a system administrator, I want to migrate the Certification Authority so that I can ensure continuity of certificate services.
 ---
 
-# Migrate the Certification Authority
+# Migrate a Certification Authority
 
 Migrating a Certification Authority (CA) ensures the continuity of your organization's certificate services. This guide provides step-by-step instructions and best practices for successfully migrating a CA. It covers essential tasks such as backing up the CA database and private key, removing the CA role service from the source server, and restoring the CA on the destination server. Whether you're using the Certification Authority snap-in, Windows PowerShell, or command-line tools like Certutil, this guide offers detailed steps tailored to various migration scenarios. Follow these instructions to ensure a smooth and secure migration process.