Merge pull request #3423 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/windowsserverdocs (branch main)

Author: Taojunshen

WindowsServerDocs/administration/windows-server-update-services/manage/managing-wsus-client-computers-and-wsus-computer-groups.md

@@ -12,26 +12,27 @@ ms.date: 10/16/2017
 
 >Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
 
-The computers node is central access point in the WSUS administrative console for managing WSUS client computers and devices. Under this node you can find the different groups you have set up (plus the default group, Unassigned computers).
+The Computers node is the central access point in the WSUS administrative console for managing WSUS client computers and devices. Under this node you can find the different groups you have set up (plus the default group, Unassigned computers).
 
 ## Managing Client computers
-Selecting one of the computer groups in the **computers** node under **Options** causes the computers in that group to be displayed in the details pane. If a computer is assigned to multiple groups, it will appear in the listings of both groups. If you select a computer in the list, you can see its properties, which include general details about the computer and the status of updates for it, such as the installation or detection status of an update for a particular computer. You can filter the list of computers under a given computer group by status. The default shows only computers for which updates are needed or which have had installation failures; however, you can filter the display by any status. Click **Refresh** after changing the status filter.
+
+Selecting one of the computer groups in the **Computers** node causes the computers in that group to be displayed in the details pane. If a computer is assigned to multiple groups, it will appear in the listings of all groups. If you select a computer in the list, you can see its properties, which include general details about the computer and the status of updates for it. You can filter the list of computers under a given computer group by status. The default shows only computers for which updates are needed or which have had installation failures; however, you can filter the display by any status. Click **Refresh** after changing the status filter.
 
 You can also manage computer groups on the computers page, which includes creating the groups and assigning computers to them. For more information about managing computer groups, see Managing computer Groups in the next section of this guide, and section [1.5. Plan WSUS computer groups](../plan/plan-your-wsus-deployment.md#15-plan-wsus-computer-groups) in Step 1: Prepare for Your WSUS Deployment of the WSUS deployment guide.
 
 > [!NOTE]
 > You must first configure client computers to contact the WSUS server before you can manage them from that server. Until you perform this task, your WSUS server will not recognize your client computers and they will not be displayed in the list on the computers page. For more information about setting up client computers, see [1.5. Plan WSUS computer groups](../plan/plan-your-wsus-deployment.md#15-plan-wsus-computer-groups) of Step 1: Prepare for Your WSUS Deployment, and Step 3: Configure WSUS, in the WSUS deployment guide.
 
 ## Controlling when WSUS client computers install updates
-There are two methods to control when WSUS client computers install updates:
 
--   Approval with deadlines: Deadlines strictly enforce when an update is installed
-
--   WSUS Group Policies: Group Policies control when the Windows Update Agent scans and installs updates
+There are two methods to control when WSUS client computers install updates:
+- Approval with deadlines: Deadlines strictly enforce when an update is installed
+- WSUS Group Policies: Group Policies control when the Windows Update Agent scans and installs updates
 
-    for more information, see: [Step 5: Configure Group Policy Settings for Automatic Updates](../deploy/4-configure-group-policy-settings-for-automatic-updates.md), in the WSUS Deployment Guide.
+    For more information, see [Step 5: Configure Group Policy Settings for Automatic Updates](../deploy/4-configure-group-policy-settings-for-automatic-updates.md), in the WSUS Deployment Guide.
 
 ## Managing computer Groups
+
 WSUS allows you to target updates to groups of client computers, so you can ensure that specific computers always get the right updates at the most convenient times. For example, if all the computers in one department (such as the Accounting team) have a specific configuration, you can set up a group for that team, decide which updates their computers need and what time they should be installed, and then use WSUS reports to evaluate the updates for the team.
 
 Computers are always assigned to the **All computers** group, and remain assigned to the **Unassigned computers** group until you assign them to another group. Computers can belong to more than one group.
@@ -40,9 +41,7 @@ Computer groups can be set up in hierarchies (for example, the Payroll group and
 
 Because computers can be assigned to multiple groups, it is possible for a single update to be approved more than once for the same computer. However, the update will be deployed only once, and any conflicts will be resolved by the WSUS server. To continue with the example above, if computerA is assigned to both the Payroll and the Accounts Payable groups, and Update1 is approved for both groups, it will be deployed only once.
 
-You can assign computers to computer groups by using one of two methods, server-side targeting or client-side targeting. With server-side targeting, you manually move one or more client computers to one computer group at a time. With client-side targeting, you use Group Policy or edit the registry settings on client computers to enable those computers to automatically add themselves into the previously created computer groups. This process can be scripted and deployed to many computers at once. You must specify the targeting method you will use on the WSUS server by selecting one of the two options on the **computers** section of the **Options** page.
+You can assign computers to computer groups by using one of two methods, server-side targeting or client-side targeting. With server-side targeting, you manually move one or more client computers to one computer group at a time. With client-side targeting, you use Group Policy or edit the registry settings on client computers to enable those computers to automatically add themselves into the previously created computer groups. This process can be scripted and deployed to many computers at once. You must specify the targeting method you will use on the WSUS server by selecting one of the two options on the **Computers** section of the **Options** page.
 
 > [!NOTE]
 > If a WSUS server is running in replica mode, computer groups cannot be created on that server. All the computer groups needed for clients of the replica server must be created on the WSUS server that is the root of the WSUS server hierarchy. For more information about replica mode, see [Running WSUS Replica mode](running-wsus-replica-mode.md) and for more information about server-side and client-side targeting, see section [1.5. Plan WSUS computer groups](../plan/plan-your-wsus-deployment.md#15-plan-wsus-computer-groups) of Step 1: Prepare for Your WSUS Deployment in the WSUS deployment guide.
-
-

WindowsServerDocs/administration/windows-server-update-services/manage/setting-up-update-synchronizations.md

@@ -8,6 +8,7 @@ author: JasonGerend
 manager: mtillman
 ms.date: 10/16/2017
 ---
+
 # Setting up Update Synchronizations
 
 >Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
@@ -19,12 +20,14 @@ The first time a WSUS server downloads updates may take a long time. If you are
 You can copy content from one WSUS server's content directory to another. The location of the content directory is specified when you run the WSUS post installation procedure. You can use the wsusutil.exe tool to export update metadata from one WSUS server to a file. You can then import that file into other WSUS servers.
 
 ## Setting up Update Synchronizations
+
 The **Options** page is the central access point in the WSUS Administration Console for customizing how your WSUS server synchronizes updates. You can specify which updates are synchronized automatically, where your server gets updates, connection settings, and the synchronization schedule. You can also use the Configuration Wizard from the **Options** page to configure or reconfigure your WSUS server at any time.
 
 ### Synchronizing Update by Product and Classification
-A WSUS server downloads updates based on the products or product families (for example, Windows, or Windows Server 2008, Datacenter edition) and classifications (for example, critical updates or security updates) that you specify. at the first synchronization, the WSUS server downloads all of the updates available in the categories that you have specified. In subsequent synchronizations, your WSUS server downloads only the newest updates (or changes to the updates already available on your WSUS server) for the categories you have specified.
 
-You can specify update products and classifications on the **Options** page under **Products and Classifications**. Products are listed in a hierarchy, grouped by product family. If you select Windows, you automatically select every product that falls under that product hierarchy. By selecting the parent check box you select all items under it, as well as all future versions. selecting the child check boxes will not select the parent check boxes. The default setting for products is all Windows products, and the default setting for classifications is critical and security updates.
+A WSUS server downloads updates based on the products or product families (for example, Windows, or Windows Server 2008, Datacenter edition) and classifications (for example, critical updates or security updates) that you specify. At the first synchronization, the WSUS server downloads all of the updates available in the categories that you have specified. In subsequent synchronizations, your WSUS server downloads only the newest updates (or changes to the updates already available on your WSUS server) for the categories you have specified.
+
+You can specify update products and classifications on the **Options** page under **Products and Classifications**. Products are listed in a hierarchy, grouped by product family. If you select Windows, you automatically select every product that falls under that product hierarchy. By selecting the parent check box you select all items under it, as well as all future versions. Selecting the child check boxes will not select the parent check boxes. The default setting for products is all Windows products, and the default setting for classifications is critical and security updates.
 
 If a WSUS server is running in replica mode, you will not be able to perform this task. For more information about replica mode, see [Running WSUS Replica mode](running-wsus-replica-mode.md), and [Step 1: Prepare for Your WSUS Deployment](../plan/plan-your-wsus-deployment.md).
 
@@ -41,15 +44,18 @@ If a WSUS server is running in replica mode, you will not be able to perform thi
 > [!NOTE]
 > You can remove products or classifications in the same way. Your WSUS server will stop synchronizing new updates for the products you have cleared. However, updates that were synchronized for those products before you cleared them will remain on your WSUS server and will be listed as available.
 >
-> To remove those products,  Decline the update, as documented in [Updates Operations](updates-operations.md), and then use the [The Server cleanup Wizard](the-server-cleanup-wizard.md) to remove them.
+> To remove those products, Decline the update, as documented in [Updates Operations](updates-operations.md), and then use the [Server cleanup Wizard](the-server-cleanup-wizard.md) to remove them.
 
 ### Synchronizing Updates by Language
+
 Your WSUS server downloads updates based on the languages that you specify. You can synchronize updates in all of the languages in which they are available, or you can specify a subset of languages. If you have a hierarchy of WSUS servers, and you need to download updates in different languages, make sure that you have specified all the necessary languages on the upstream server. On a downstream server you can specify a subset of the languages you specified on the upstream server.
 
 ### Synchronizing Updates from the Microsoft Update Catalog
-for details about synchronizing updates from the Microsoft Update Catalog site, see: [WSUS and the Catalog Site](wsus-and-the-catalog-site.md).
+
+For details about synchronizing updates from the Microsoft Update Catalog site, see: [WSUS and the Catalog Site](wsus-and-the-catalog-site.md).
 
 ## Configuring Proxy Server Settings
+
 You can configure your WSUS server to use a proxy server during synchronization with an upstream server or Microsoft Update. This setting will apply only when your WSUS server runs synchronizations. By default your WSUS server will try to connect directly to the upstream server or Microsoft Update.
 
 #### To specify a proxy server for synchronization
@@ -71,6 +77,7 @@ You can configure your WSUS server to use a proxy server during synchronization
     > Because WSUS initiates all of its network traffic, there is no need to configure Windows Firewall on a WSUS server connected directly to Microsoft update.
 
 ## Configuring the Update Source
+
 The update source is the location from which your WSUS server gets its updates and update metadata. You can specify that the update source should be either Microsoft Update or another WSUS server (the WSUS server that acts as the update source is the upstream server, and your server is the downstream server).
 
 Options for customizing how your WSUS server synchronizes with the update source include the following:
@@ -80,6 +87,7 @@ Options for customizing how your WSUS server synchronizes with the update source
 -   You can use Secure Socket Layers (SSL) to secure synchronization of update information between WSUS servers. For more information about using SSL, see section 3.5. Secure WSUS with the Secure Sockets Layer Protocol of [Step 3: Configure WSUS](../deploy/2-configure-wsus.md) in the WSUS deployment guide.
 
 ## Synchronizing Manually or Automatically
+
 You can either synchronize your WSUS server manually or specify a time for it to synchronize automatically.
 
 #### To manually synchronize the WSUS server
@@ -96,7 +104,7 @@ You can either synchronize your WSUS server manually or specify a time for it to
 
 3.  For **First synchronization**, select the time you want synchronization to start each day.
 
-4.  for **Synchronizations per day**, select the number of synchronizations you want to do each day. For example, if you want four synchronizations a day starting at 3:00 A.M., then synchronizations will occur at 3:00 A.M., 9:00 A.M., 3:00 P.M., and 9:00 P.M. each day. (Note that a  random time offset will be added to the scheduled synchronization time in order to space out the server connections to Microsoft Update.)
+4.  For **Synchronizations per day**, select the number of synchronizations you want to do each day. For example, if you want four synchronizations a day starting at 3:00 A.M., then synchronizations will occur at 3:00 A.M., 9:00 A.M., 3:00 P.M., and 9:00 P.M. each day. (Note that a  random time offset will be added to the scheduled synchronization time in order to space out the server connections to Microsoft Update.)
 
 5.  Click **OK**.
 

WindowsServerDocs/networking/technologies/pktmon/pktmon-wac-extension.md

@@ -20,7 +20,7 @@ Packet Monitor (Pktmon) is an in-box, cross-component network diagnostics tool f
 Windows Admin Center is a locally-deployed, browser-based management tool that lets you manage your Windows Servers with no Azure or cloud dependency. Windows Admin Center gives you full control over all aspects of your server infrastructure and is particularly useful for managing servers on private networks that are not connected to the Internet. Windows Admin Center is the modern evolution of "in-box" management tools, like Server Manager and MMC.
 
 ## Before you start
-- To use the tool, the target server needs to be running Windows Server 2019 version 1903 (19H1) and above.
+- To use the tool, the target server needs to be running Windows Server 2019, version 1903 or later.
 - [Install Windows Admin Center](../../../manage/windows-admin-center/deploy/install.md).
 - Add a server to Windows Admin Center:
   1. Click **+ Add** under **All Connections**.

WindowsServerDocs/remote/multipoint-services/Introducing-MultiPoint-services.md

@@ -9,7 +9,7 @@ manager: scottman
 ms.author: evas
 ---
 # Introducing MultiPoint Services
-MultiPoint Services role in Windows Server 2016 allows multiple users, each with their own independent and familiar Windows experience, to simultaneously share one computer.There are several ways users can access their sessions. One way is by remoting into the server using the [remote desktop apps](../remote-desktop-services/clients/remote-desktop-clients.md) with any device. Another way is through physical stations that stations attached to the MultiPoint server:
+MultiPoint Services role in Windows Server 2016 allows multiple users, each with their own independent and familiar Windows experience, to simultaneously share one computer.There are several ways users can access their sessions. One way is by remoting into the server using the [remote desktop apps](../remote-desktop-services/clients/remote-desktop-clients.md) with any device. Another way is through physical stations attached to the MultiPoint server:
 
 -   Directly to video ports on the computer
 
@@ -33,4 +33,4 @@ This document addresses the following factors to consider when you are planning
 
 -   [Storing Files with MultiPoint Services](Storing-Files-with-MultiPoint-services.md): Where will user files be stored, and how will they be accessed?
 
--   [Predeployment Checklist](Predeployment-Checklist.md)
+-   [Predeployment Checklist](Predeployment-Checklist.md)

WindowsServerDocs/storage/file-server/Troubleshoot/slow-file-transfer.md

@@ -85,4 +85,4 @@ We recommend that you make sure that the Office and SMB binaries are up-to-date,
    NET START SERVER
    ```
 
-To avoid this issue, you can also replicate the file to a local file server. For more information, see [aving Office documents to a network server is slow when using EFS](/office/troubleshoot/office/saving-file-to-network-server-slow).
+To avoid this issue, you can also replicate the file to a local file server. For more information, see [saving Office documents to a network server is slow when using EFS](/office/troubleshoot/office/saving-file-to-network-server-slow).

WindowsServerDocs/storage/storage-migration-service/migrate-data.md

@@ -73,7 +73,7 @@ In this step you transfer data after specifying where to put it on the destinati
     Here's a video showing how to use Storage Migration Service to migrate to Azure VMs.
     > [!VIDEO https://www.youtube-nocookie.com/embed/k8Z9LuVL0xQ]
 
-3. Map the source volumes to destination volumes, clear the **Include** checkbox for any shares you don't want to transfer (including any administrative shares located in the Windows system folder) and ensuring that the Azure Files Sync checkbox is set for any volumes or shares that are cloud tiering with Azure File Sync, and then select **Next**.
+3. Map the source volumes to destination volumes, clear the **Include** checkbox for any shares you don't want to transfer (including any administrative shares located in the Windows system folder) and ensuring that the Azure File Sync checkbox is set for any volumes or shares that are cloud tiering with Azure File Sync, and then select **Next**.
 
     > [!NOTE]
     > When migrating NetApp CIFS servers, source volumes don't show drive letters. You can map these volumes to any destination volumes, and you can map multiple NetApp CIFS volumes to the same destination volume. New root folder paths are created to avoid any folder overwrites or collisions, and then shares are created at the correct level. The **Shares** detail pane shows the folder structure you're about to create.