Skip to content

Commit 809e777

Browse files
authored
Merge pull request #277192 from jeffpatt24/patch-9
Update storage-sync-files-agent-update-policy.md
2 parents 6359b66 + f4dda5c commit 809e777

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

includes/storage-sync-files-agent-update-policy.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
author: khdownie
33
ms.service: azure-file-storage
44
ms.topic: include
5-
ms.date: 02/13/2024
5+
ms.date: 06/04/2024
66
ms.author: kendownie
77
---
88
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.
99

1010
#### Major vs. minor agent versions
1111

12-
* Major agent versions often contain new features and have an increasing number as the first part of the version number. For example: 14.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: 14.1.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: 16.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: 16.2.0.0
1414

1515
#### Upgrade paths
1616

@@ -35,7 +35,7 @@ There are five approved and tested ways to install the Azure File Sync agent upd
3535
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.
3636

3737
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-
1. 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 Download Center](https://go.microsoft.com/fwlink/?linkid=858257) aka.ms/AFS/agent.
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).
3939

4040
##### Changing the auto-upgrade setting
4141

@@ -61,6 +61,8 @@ To change the current policy setting to the immediate update track, you can use:
6161
```powershell
6262
Set-StorageSyncAgentAutoUpdatePolicy -PolicyMode InstallLatest -Day <day> -Hour <hour>
6363
```
64+
> [!NOTE]
65+
> If flighting has already completed for the latest agent version and the agent auto update policy is set to InstallLatest, the agent will not auto-update until the next agent version is flighted. To update to an agent version that has completed flighting, use Microsoft Update or AfsUpdater.exe. To check if an agent version is currently flighting, check the [supported versions](/azure/storage/file-sync/file-sync-release-notes#supported-versions) section in the release notes.
6466
6567
#### Agent lifecycle and change management guarantees
6668

@@ -69,7 +71,7 @@ Azure File Sync is a cloud service which continuously introduces new features an
6971
- Major agent versions are supported for at least six months from the date of initial release.
7072
- We guarantee there is an overlap of at least three months between the support of major agent versions.
7173
- 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.
72-
- The lifetime of a minor agent version is bound to the associated major version. For example, when agent version 14.0.0.0 is set to expire, agent versions 14.\*.\*.\* 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 16.0.0.0 is set to expire, agent versions 16.\*.\*.\* will all be set to expire together.
7375

7476
> [!NOTE]
7577
> 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.

0 commit comments

Comments
 (0)