|
2 | 2 | author: khdownie |
3 | 3 | ms.service: azure-file-storage |
4 | 4 | ms.topic: include |
5 | | -ms.date: 06/05/2024 |
| 5 | +ms.date: 01/07/2025 |
6 | 6 | ms.author: kendownie |
7 | 7 | --- |
8 | | -The Azure File Sync agent is updated on a regular basis to add new functionality and to address issues. We recommend updating the Azure File Sync agent as new versions are available. |
| 8 | +The Azure File Sync agent is updated regularly to add new functionality and to address issues. We recommend updating the Azure File Sync agent as new versions are available. |
9 | 9 |
|
10 | 10 | #### Major vs. minor agent versions |
11 | 11 |
|
12 | | -* Major agent versions often contain new features and have an increasing number as the first part of the version number. For example: 17.0.0.0 |
13 | | -* Minor agent versions are also called "patches" and are released more frequently than major versions. They often contain bug fixes and smaller improvements but no new features. For example: 17.2.0.0 |
| 12 | +* Major agent versions often contain new features and have an increasing number as the first part of the version number. For example: 18.0.0.0 |
| 13 | +* Minor agent versions are also called "patches" and are released more frequently than major versions. They often contain bug fixes and smaller improvements but no new features. For example: 18.2.0.0 |
14 | 14 |
|
15 | 15 | #### Upgrade paths |
16 | 16 |
|
17 | 17 | There are five approved and tested ways to install the Azure File Sync agent updates. |
18 | 18 |
|
19 | | -1. **Use Azure File Sync agent auto-upgrade feature to install agent updates.** |
20 | | - The Azure File Sync agent will auto-upgrade. You can select to install the latest agent version when available or update when the currently installed agent is near expiration. To learn more, see [Automatic agent lifecycle management](#automatic-agent-lifecycle-management). |
| 19 | +1. **Use Azure File Sync agent auto upgrade feature to install agent updates.** |
| 20 | + The Azure File Sync agent auto upgrades. You can select to install the latest agent version when available or update when the currently installed agent is near expiration. To learn more, see [Automatic agent lifecycle management](#automatic-agent-lifecycle-management). |
21 | 21 | 2. **Configure Microsoft Update to automatically download and install agent updates.** |
22 | 22 | We recommend installing every Azure File Sync update to ensure you have access to the latest fixes for the server agent. Microsoft Update makes this process seamless by automatically downloading and installing updates for you. |
23 | 23 | 3. **Use AfsUpdater.exe to download and install agent updates.** |
24 | 24 | The AfsUpdater.exe is located in the agent installation directory. Double-click the executable to download and install agent updates. Depending on the release version, you might need to restart the server. |
25 | 25 | 4. **Patch an existing Azure File Sync agent by using a Microsoft Update patch file, or a .msp executable. The latest Azure File Sync update package can be downloaded from the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Search.aspx?q=Azure%20File%20Sync).** |
26 | | - Running an .msp executable will upgrade your Azure File Sync installation with the same method used automatically by Microsoft Update. Applying a Microsoft Update patch will perform an in-place upgrade of an Azure File Sync installation. |
| 26 | + Running an .msp executable upgrades your Azure File Sync installation with the same method used automatically by Microsoft Update. Applying a Microsoft Update patch performs an in-place upgrade of an Azure File Sync installation. |
27 | 27 | 5. **Download the newest Azure File Sync agent installer from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?linkid=858257).** |
28 | | - To upgrade an existing Azure File Sync agent installation, uninstall the older version and then install the latest version from the downloaded installer. The server registration, sync groups, and any other settings are maintained by the Azure File Sync installer. |
| 28 | + To upgrade an existing Azure File Sync agent installation, uninstall the older version and then install the latest version from the downloaded installer. Agent settings (server registration, server endpoints, etc.) are maintained when the Azure File Sync agent is uninstalled. |
29 | 29 |
|
30 | 30 | > [!NOTE] |
31 | 31 | > The downgrade of Azure File Sync agent isn't supported. The new versions often include breaking changes when compared to the old versions, making the downgrade process unsupported. In case you encounter any problems with your current agent version, reach out to support or upgrade to the latest available release. |
32 | 32 |
|
33 | 33 | #### Automatic agent lifecycle management |
34 | 34 |
|
35 | | -The Azure File Sync agent will auto-upgrade. You can select either of two modes and specify a maintenance window in which the upgrade shall be attempted on the server. This feature is designed to help you with the agent lifecycle management by either providing a guardrail preventing your agent from expiration or allowing for a no-hassle, stay current setting. |
| 35 | +The Azure File Sync agent auto upgrades. You can select either of two modes and specify a maintenance window in which the upgrade shall be attempted on the server. This feature is designed to help you with the agent lifecycle management by either providing a guardrail preventing your agent from expiration or allowing for a no-hassle, stay current setting. |
36 | 36 |
|
37 | | -1. The **default setting** will attempt to prevent the agent from expiration. Within 21 days of the posted expiration date of an agent, the agent will attempt to self-upgrade. It will start an attempt to upgrade once a week within 21 days prior to expiration and in the selected maintenance window. **This option doesn't eliminate the need for taking regular Microsoft Update patches.** |
38 | | -2. Optionally, you can select that the agent will automatically upgrade itself as soon as a new agent version becomes available (currently not applicable to clustered servers). This update will occur during the selected maintenance window and allow your server to benefit from new features and improvements as soon as they become generally available. This is the recommended, worry-free setting that will provide major agent versions as well as regular update patches to your server. Every agent released is at GA quality. If you select this option, Microsoft will flight the newest agent version to you. Clustered servers are excluded. Once flighting is complete, the agent will also become available on Microsoft Update and [Microsoft Download Center](https://go.microsoft.com/fwlink/?linkid=858257). |
| 37 | +1. The **default setting** attempts to prevent the agent from expiration. Within 21 days of the posted expiration date of an agent, the agent attempts to self-upgrade. It starts an attempt to upgrade once a week within 21 days prior to expiration and in the selected maintenance window. **This option doesn't eliminate the need for taking regular Microsoft Update patches.** |
| 38 | +2. Optionally, you can select that the agent will automatically upgrade itself as soon as a new agent version becomes available (currently not applicable to clustered servers). This update occurs during the selected maintenance window and allows your server to benefit from new features and improvements as soon as they become generally available. This is the recommended, worry-free setting that provides major agent versions and regular update patches to your server. Every agent released is at GA quality. If you select this option, Microsoft will flight the newest agent version to you. Clustered servers are excluded. Once flighting is complete, the agent will also become available on Microsoft Update and [Microsoft Download Center](https://go.microsoft.com/fwlink/?linkid=858257). |
39 | 39 |
|
40 | | -##### Changing the auto-upgrade setting |
| 40 | +##### Changing the auto upgrade setting |
41 | 41 |
|
42 | 42 | The following instructions describe how to change the settings after you've completed the installer, if you need to make changes. |
43 | 43 |
|
@@ -68,10 +68,10 @@ Set-StorageSyncAgentAutoUpdatePolicy -PolicyMode InstallLatest -Day <day> -Hour |
68 | 68 |
|
69 | 69 | Azure File Sync is a cloud service which continuously introduces new features and improvements. This means that a specific Azure File Sync agent version can only be supported for a limited time. To facilitate your deployment, the following rules guarantee you have enough time and notification to accommodate agent updates/upgrades in your change management process: |
70 | 70 |
|
71 | | -- Major agent versions are supported for at least six months from the date of initial release. |
| 71 | +- Major agent versions are supported for at least 12 months from the date of initial release. |
72 | 72 | - We guarantee there is an overlap of at least three months between the support of major agent versions. |
73 | 73 | - Warnings are issued for registered servers using a soon-to-be expired agent at least three months prior to expiration. You can check if a registered server is using an older version of the agent under the registered servers section of a Storage Sync Service. |
74 | | -- The lifetime of a minor agent version is bound to the associated major version. For example, when agent version 17.0.0.0 is set to expire, agent versions 17.\*.\*.\* will all be set to expire together. |
| 74 | +- The lifetime of a minor agent version is bound to the associated major version. For example, when agent version 18.0.0.0 is set to expire, agent versions 18.\*.\*.\* will all expire together. |
75 | 75 |
|
76 | 76 | > [!NOTE] |
77 | | -> Installing an agent version with an expiration warning will display a warning but succeed. Attempting to install or connect with an expired agent version isn't supported and will be blocked. |
| 77 | +> Installing an agent version with an expiration warning displays a warning but will succeed. Attempting to install or connect with an expired agent version isn't supported and will be blocked. |
0 commit comments