This article describes the improvements and issues that are fixed in the Azure File Sync Agent v14.1 release that is dated December 2021. Additionally, this article contains installation instructions for this release.
Improvements and issues that are fixed
Tiered files deleted on Windows Server 2022 are not detected by cloud tiering filter driver
This issue occurs because the DeleteFile API on Windows Server 2022 uses the FILE_DISPOSITION_INFORMATION_EX class to delete files. The v14.1 release adds support for detecting tiered files deleted using the FILE_DISPOSITION_INFORMATION_EX class.
Note: This issue can also impact Windows 2016 and Windows Server 2019 if a tiered file is deleted using the FILE_DISPOSITION_INFORMATION_EX class.
More information about the Azure File Sync Agent v14.1 release
-
This release is available for Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022 installations.
-
A restart is required for servers that have an existing Azure File Sync agent installation if the agent version is less than version 12.0.
-
The agent version for this release is 14.1.0.0.
How to obtain and install the Azure File Sync Agent
The Azure File Sync agent is available from Microsoft Update, Microsoft Update Catalog, and Microsoft Download Center.
Notes
-
If the Azure File Sync agent is not currently installed on a server, use the agent installation package on the Microsoft Download Center. The agent installation package on Microsoft Update and Microsoft Update Catalog is intended for agent upgrades only.
-
To update existing agent installations, run AfsUpdater.exe (located in the agent installation directory) or download and install the update from Microsoft Update or Microsoft Update Catalog.
Microsoft Update
To obtain and install from Microsoft Update, follow these steps on a server that has Azure File Sync agent installed:
Server 2016 and Server 2019
-
Click Start, and then click Settings.
-
In Settings, click Update & security.
-
In the Windows Update window, click Check online for updates from Microsoft Update.
-
Verify the Azure File Sync agent update is listed and then click Install now.
Server 2012 R2
-
Click Start, and then click Control Panel.
-
In Control Panel, double-click Windows Update.
-
In the Windows Update window, click Check for updates.
-
Click Important updates are available.
-
Verify the Azure File Sync agent update is selected, and then click Install.
Microsoft Update Catalog
Go to the following website to manually download this update from the Microsoft Update Catalog:
Azure File Sync Agent v14.1 release: December 2021 (KB5001873)
To manually install the update package, run the following command from an elevated command prompt:
msiexec.exe /p packagename.msp REINSTALLMODE=OMUS REINSTALL=StorageSyncAgent,StorageSyncAgentAzureFileSync,StorageSyncAgentGuardFilter,StorageSyncAgentUpdater /qb /l*v KB5001873.log
For example, to install the Azure File Sync agent update for Server 2016, run the following command:
msiexec.exe /p StorageSyncAgent_WS2016_KB5001873.msp REINSTALLMODE=OMUS REINSTALL=StorageSyncAgent,StorageSyncAgentAzureFileSync,StorageSyncAgentGuardFilter,StorageSyncAgentUpdater /qb /l*v KB5001873.log
Microsoft Download Center
Go to the Microsoft Download Center to manually download the agent installation package for new agent installations.
How to perform a silent installation for a new agent installation
To perform a silent installation for a new agent installation that uses the default settings, run the following command at an elevated command prompt:
msiexec /i packagename.msi /qb /l*v AFSv14Installation.log
For example, to install the Azure File Sync agent for Windows Server 2016, run the following command:
msiexec /i StorageSyncAgent_WS2016.msi /qb /l*v AFSv14Installation.log
Notes
-
Use the /qb switch to display restart prompts (if required), agent update, and server registration screens. To suppress the screens and automatically restart the server (if required), use the /qn switch.
-
To perform a silent installation with custom settings, follow the steps documented in KB4459986.
