Merge pull request #283917 from khdownie/kendownie080724

remove login screenshot and cleanup

Author: Jill Grant

articles/storage/file-sync/file-sync-server-registration.md

@@ -3,29 +3,31 @@ title: Manage registered servers with Azure File Sync
 description: Learn how to register and unregister a Windows Server with an Azure File Sync Storage Sync Service.
 author: khdownie
 ms.service: azure-file-storage
-ms.custom:
 ms.topic: how-to
-ms.date: 10/04/2023
+ms.date: 08/07/2024
 ms.author: kendownie
 ---
 
 # Manage registered servers with Azure File Sync
+
 Azure File Sync allows you to centralize your organization's file shares in Azure Files without giving up the flexibility, performance, and compatibility of an on-premises file server. It does this by transforming your Windows Servers into a quick cache of your Azure file share. You can use any protocol available on Windows Server to access your data locally (including SMB, NFS, and FTPS) and you can have as many caches as you need across the world.
 
 The following article illustrates how to register and manage a server with a Storage Sync Service. See [How to deploy Azure File Sync](file-sync-deployment-guide.md) for information on how to deploy Azure File Sync end-to-end.
 
 ## Register/unregister a server with Storage Sync Service
-Registering a server with Azure File Sync establishes a trust relationship between Windows Server and Azure. This relationship can then be used to create *server endpoints* on the server, which represent specific folders that should be synced with an Azure file share (also known as a *cloud endpoint*). 
+
+Registering a server with Azure File Sync establishes a trust relationship between Windows Server and Azure. This relationship can then be used to create *server endpoints* on the server, which represent specific folders that should be synced with an Azure file share (also known as a *cloud endpoint*).
 
 ### Prerequisites
+
 To register a server with a Storage Sync Service, you must first prepare your server with the necessary prerequisites:
 
 * Your server must be running a supported version of Windows Server. For more information, see [Azure File Sync system requirements and interoperability](file-sync-planning.md#windows-file-server-considerations).
-* Ensure that a Storage Sync Service has been deployed. For more information on how to deploy a Storage Sync Service, see [How to deploy Azure File Sync](file-sync-deployment-guide.md).
+* Ensure that you've deployed a Storage Sync Service. For more information on how to deploy a Storage Sync Service, see [How to deploy Azure File Sync](file-sync-deployment-guide.md).
 * Ensure that the server is connected to the internet and that Azure is accessible.
 * Disable the IE Enhanced Security Configuration for administrators with the Server Manager UI.
 
-    ![Server Manager UI with the IE Enhanced Security Configuration highlighted](media/storage-sync-files-server-registration/server-manager-ie-config.png)
+    ![Server Manager UI with the IE Enhanced Security Configuration highlighted.](media/storage-sync-files-server-registration/server-manager-ie-config.png)
 
 * Ensure that the Azure PowerShell module is installed on your server. If your server is a member of a Failover Cluster, every node in the cluster will require the Az module. More details on how to install the Az module can be found on the [Install and configure Azure PowerShell](/powershell/azure/install-azure-powershell).
 
@@ -41,7 +43,7 @@ To register a server with a Storage Sync Service, you must first prepare your se
         * Show the proxy:   netsh winhttp show proxy
         * Set the proxy:    netsh winhttp set proxy 127.0.0.1:8888
         * Reset the proxy:  netsh winhttp reset proxy
-        * if this is setup after the agent is installed, then restart our sync agent:
+        * If this is set up after the agent is installed, then restart our sync agent:
             net stop filesyncsvc
 
 ```xml
@@ -54,55 +56,61 @@ To register a server with a Storage Sync Service, you must first prepare your se
 ```    
 
 ### Register a server with Storage Sync Service
+
 Before a server can be used as a *server endpoint* in an Azure File Sync *sync group*, it must be registered with a *Storage Sync Service*. A server can only be registered with one Storage Sync Service at a time.
 
 #### Install the Azure File Sync agent
+
 1. [Download the Azure File Sync agent](https://go.microsoft.com/fwlink/?linkid=858257).
+
 2. Start the Azure File Sync agent installer.
 
-    ![The first pane of the Azure File Sync agent installer](media/storage-sync-files-server-registration/install-afs-agent-1.png)
+    ![The first pane of the Azure File Sync agent installer.](media/storage-sync-files-server-registration/install-afs-agent-1.png)
 
-3. Be sure to enable updates to the Azure File Sync agent using Microsoft Update. It is important because critical security fixes and feature enhancements to the server package are shipped via Microsoft Update.
+3. Be sure to enable updates to the Azure File Sync agent using Microsoft Update. It's important because critical security fixes and feature enhancements to the server package are shipped via Microsoft Update.
 
-    ![Ensure Microsoft Update is enabled in the Microsoft Update pane of the Azure File Sync agent installer](media/storage-sync-files-server-registration/install-afs-agent-2.png)
+    ![Ensure Microsoft Update is enabled in the Microsoft Update pane of the Azure File Sync agent installer.](media/storage-sync-files-server-registration/install-afs-agent-2.png)
 
 4. If the server has not been previously registered, the server registration UI will pop up immediately after completing the installation.
 
 > [!IMPORTANT]  
-> If the server is a member of a Failover Cluster, the Azure File Sync agent needs to be installed on every node in the cluster.
+> If the server is a member of a Failover Cluster, the Azure File Sync agent must be installed on every node in the cluster.
 
 #### Register the server using the server registration UI
-1. If the server registration UI did not start immediately after completing the installation of the Azure File Sync agent, it can be started manually by executing `C:\Program Files\Azure\StorageSyncAgent\ServerRegistration.exe`.
-2. Click *Sign-in* to access your Azure subscription. 
 
-    ![Opening dialog of the server registration UI](media/storage-sync-files-server-registration/server-registration-ui-1.png)
+1. If the server registration UI didn't start immediately after completing the installation of the Azure File Sync agent, start it manually by executing `C:\Program Files\Azure\StorageSyncAgent\ServerRegistration.exe`.
 
-3. Pick the correct subscription, resource group, and Storage Sync Service from the dialog.
+2. Select *Sign-in* to access your Azure subscription.
 
-    ![Storage Sync Service information](media/storage-sync-files-server-registration/server-registration-ui-2.png)
+    ![Opening dialog of the server registration UI.](media/storage-sync-files-server-registration/server-registration-ui-1.png)
 
-4. In preview, one more sign-in is required to complete the process. 
+3. Pick the correct subscription, resource group, and Storage Sync Service from the dialog.
 
-    ![Sign in dialog](media/storage-sync-files-server-registration/server-registration-ui-3.png)
+    ![Storage Sync Service information.](media/storage-sync-files-server-registration/server-registration-ui-2.png)
+
+4. You might be prompted to sign into Azure again to complete the process.
 
 > [!IMPORTANT]  
 > If the server is a member of a Failover Cluster, each server needs to run the Server Registration. When you view the registered servers in the Azure Portal, Azure File Sync automatically recognizes each node as a member of the same Failover Cluster, and groups them together appropriately.
 
 #### Register the server with PowerShell
-You can also perform server registration via PowerShell. 
+
+You can also perform server registration via PowerShell.
 
 ```powershell
 Register-AzStorageSyncServer -ResourceGroupName "<your-resource-group-name>" -StorageSyncServiceName "<your-storage-sync-service-name>"
 ```
 
 ### Unregister the server with Storage Sync Service
+
 There are several steps that are required to unregister a server with a Storage Sync Service. Let's take a look at how to properly unregister a server.
 
 > [!WARNING]  
-> Do not attempt to troubleshoot issues with sync, cloud tiering, or any other aspect of Azure File Sync by unregistering and registering a server, or removing and recreating the server endpoints unless explicitly instructed to by a Microsoft engineer. Unregistering a server and removing server endpoints is a destructive operation, and tiered files on the volumes with server endpoints will not be "reconnected" to their locations on the Azure file share after the registered server and server endpoints are recreated, which will result in sync errors. Also note, tiered files that exist outside of a server endpoint namespace may be permanently lost. Tiered files may exist within server endpoints even if cloud tiering was never enabled.
+> Don't attempt to troubleshoot issues with sync, cloud tiering, or any other aspect of Azure File Sync by unregistering and registering a server, or removing and recreating the server endpoints unless explicitly instructed to by a Microsoft engineer. Unregistering a server and removing server endpoints is a destructive operation, and tiered files on the volumes with server endpoints will not be "reconnected" to their locations on the Azure file share after the registered server and server endpoints are recreated, which will result in sync errors. Tiered files that exist outside of a server endpoint namespace might be permanently lost. Tiered files might exist within server endpoints even if cloud tiering was never enabled.
 
 #### (Optional) Recall all tiered data
-If you would like files that are currently tiered to be available after removing Azure File Sync (i.e. this is a production, not a test, environment), recall all files on each volume containing server endpoints. Disable cloud tiering for all server endpoints, and then run the following PowerShell cmdlet:
+
+If you want files that are currently tiered to be available after removing Azure File Sync (i.e. this is a production, not a test, environment), recall all files on each volume containing server endpoints. Disable cloud tiering for all server endpoints, and then run the following PowerShell cmdlet:
 
 ```powershell
 Import-Module "C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"
@@ -113,14 +121,15 @@ Invoke-StorageSyncFileRecall -Path <a-volume-with-server-endpoints-on-it>
 > If the local volume hosting the server endpoint does not have enough free space to recall all the tiered data, the `Invoke-StorageSyncFileRecall` cmdlet will fail.  
 
 #### Remove the server from all sync groups
+
 Before unregistering the server on the Storage Sync Service, you must remove all server endpoints on that server. You can do this via the Azure portal:
 
 1. Navigate to the Storage Sync Service where your server is registered.
-2. Remove all server endpoints for this server in each sync group in the Storage Sync Service. This can be accomplished by right-clicking the relevant server endpoint in the sync group pane.
+2. Remove all server endpoints for this server in each sync group in the Storage Sync Service. Do this by right-clicking the relevant server endpoint in the sync group pane.
 
    :::image type="content" source="media/storage-sync-files-server-registration/sync-group-server-endpoint-remove.png" alt-text="Screenshot showing how to remove a server endpoint from a sync group.":::
 
-This can also be accomplished with a simple PowerShell script:
+You can also do this with a simple PowerShell script:
 
 ```powershell
 Connect-AzAccount
@@ -137,6 +146,7 @@ Get-AzStorageSyncGroup -ResourceGroupName $resourceGroup -StorageSyncServiceName
 ```
 
 #### Unregister the server
+
 Now that all data has been recalled and the server has been removed from all sync groups, you can unregister the server. 
 
 1. In the Azure portal, navigate to the Storage Sync Service and select **Sync** > **Registered servers**.
@@ -145,6 +155,7 @@ Now that all data has been recalled and the server has been removed from all syn
    :::image type="content" source="media/storage-sync-files-server-registration/unregister-server.png" alt-text="Screenshot showing how to unregister a server.":::
 
 #### Unregister the server with PowerShell
+
 You can also unregister the server via PowerShell by using the `Unregister-AzStorageSyncServer` cmdlet.
 
 > [!WARNING]  
@@ -155,28 +166,31 @@ $RegisteredServer = Get-AzStorageSyncServer -ResourceGroupName "<your-resource-g
 Unregister-AzStorageSyncServer -Force -ResourceGroupName "<your-resource-group-name>" -StorageSyncServiceName "<your-storage-sync-service-name>" -ServerId $RegisteredServer.ServerId
 ```
 
-## Ensuring Azure File Sync is a good neighbor in your datacenter 
-Because Azure File Sync will rarely be the only service running in your datacenter, you might want to limit the network and storage usage of Azure File Sync.
+## Ensuring Azure File Sync is a good neighbor in your data center
+
+Because Azure File Sync will rarely be the only service running in your data center, you might want to limit the network and storage usage of Azure File Sync.
 
 > [!IMPORTANT]  
 > Setting limits too low will impact the performance of Azure File Sync synchronization and recall.
 
 ### Set Azure File Sync network limits
+
 You can throttle the network utilization of Azure File Sync by using the `StorageSyncNetworkLimit` cmdlets.
 
 > [!NOTE]  
-> Network limits does not apply to the following scenarios:
+> Network limits don't apply to the following scenarios:
 > - When a tiered file is accessed.
 > - Sync metadata that is exchanged between the registered server and Storage Sync Service.
 >  
-> Because this network traffic is not throttled, Azure File Sync may exceed the network limit configured. Our recommendation is to monitor the network traffic and adjust the limit to account for the network traffic that is not throttled. 
+> Because this network traffic isn't throttled, Azure File Sync might exceed the network limit configured. We recommend monitoring the network traffic and adjusting the limit to account for the network traffic that isn't throttled.
 
-For example, you can create a new throttle limit to ensure that Azure File Sync does not use more than 10 Mbps between 9 am and 5 pm (17:00h) during the work week: 
+For example, you can create a new throttle limit to ensure that Azure File Sync doesn't use more than 10 Mbps between 9 am and 5 pm (17:00h) during the work week:
 
 ```powershell
 Import-Module "C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"
 New-StorageSyncNetworkLimit -Day Monday, Tuesday, Wednesday, Thursday, Friday -StartHour 9 -EndHour 17 -LimitKbps 10000
 ```
+
 > [!NOTE]  
 > To apply the network limit for 24 hours, use 0 for the `-StartHour` and `-EndHour` parameters.
 
@@ -192,10 +206,12 @@ To remove network limits, use `Remove-StorageSyncNetworkLimit`. For example, the
 Get-StorageSyncNetworkLimit | ForEach-Object { Remove-StorageSyncNetworkLimit -Id $_.Id } # assumes StorageSync.Management.ServerCmdlets.dll is imported
 ```
 
-### Use Windows Server storage QoS 
-When Azure File Sync is hosted in a virtual machine running on a Windows Server virtualization host, you can use Storage QoS (storage quality of service) to regulate storage IO consumption. You can set the Storage QoS policy either as a maximum (or limit, such as how `StorageSyncNetworkLimit` is enforced in the previous example) or as a minimum (or reservation). Setting a minimum instead of a maximum allows Azure File Sync to burst to use available storage bandwidth if other workloads are not using it. For more information, see [Storage Quality of Service](/windows-server/storage/storage-qos/storage-qos-overview).
+### Use Windows Server storage QoS
+
+When Azure File Sync is hosted in a virtual machine running on a Windows Server virtualization host, you can use Storage QoS (storage quality of service) to regulate storage IO consumption. You can set the Storage QoS policy either as a maximum (or limit, such as how `StorageSyncNetworkLimit` is enforced in the previous example) or as a minimum (or reservation). Setting a minimum instead of a maximum allows Azure File Sync to burst to use available storage bandwidth if other workloads aren't using it. For more information, see [Storage Quality of Service](/windows-server/storage/storage-qos/storage-qos-overview).
 
 ## See also
+
 - [Planning for an Azure File Sync deployment](file-sync-planning.md)
 - [Deploy Azure File Sync](file-sync-deployment-guide.md)
 - [Monitor Azure File Sync](file-sync-monitoring.md)