You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| V16.2 Release - [KB5023052](https://support.microsoft.com/topic/azure-file-sync-agent-v16-2-release-february-2024-security-only-update-8247bf99-8f51-4eb6-b378-b86b6d1d45b8)| 16.2.0.0 | February 13, 2024 | Supported - Security Update - Agent version will expire on July 29, 2024|
@@ -67,6 +68,82 @@ Perform one of the following options for your Windows Server 2012 R2 servers pri
67
68
>[!NOTE]
68
69
>Azure File Sync agent v17.2 is the last agent release currently planned for Windows Server 2012 R2. To continue to receive product improvements and bug fixes, upgrade your servers to Windows Server 2016 or later.
69
70
71
+
## Version 18.0.0.0 (Flighting)
72
+
73
+
The following release notes are for Azure File Sync version 18.0.0.0 (released May 8, 2024). This release contains improvements for the Azure File Sync service and agent.
74
+
75
+
### Improvements and issues that are fixed
76
+
77
+
- Faster server provisioning and improved disaster recovery for Azure File Sync server endpoints.
78
+
- We're reducing the time it takes for the new server endpoint to be ready to use. When a new server endpoint is provisioned, it could take hours and sometime days for the server to be ready to use. With our latest improvements, we've substantially shortened this duration for a more efficient setup process.
79
+
- The improvement applies to the following scenarios, when the server endpoint location is empty (no files or directories):
80
+
- Creating the first server endpoint of new sync topology after data is copied to the Azure File Share.
81
+
- Adding a new empty server endpoint to an existing sync topology.
82
+
- How to get started: Sign up for the public preview [here](https://forms.office.com/r/gCLr1PDZKL).
83
+
- Sync performance improvements
84
+
- Sync upload performance has improved, and performance numbers will be posted when they are available. This improvement will mainly benefit file share migrations (initial upload) and high churn events on the server in which a large number of files need to be uploaded, for example ACL changes.
85
+
- Miscellaneous reliability and telemetry improvements for cloud tiering and sync
86
+
87
+
### Evaluation Tool
88
+
89
+
Before deploying Azure File Sync, you should evaluate whether it's compatible with your system using the Azure File Sync evaluation tool. This tool is an Azure PowerShell cmdlet that checks for potential issues with your file system and dataset, such as unsupported OS version. For installation and usage instructions, see [Evaluation Tool](file-sync-planning.md#evaluation-cmdlet) section in the planning guide.
90
+
91
+
### Agent installation and server configuration
92
+
93
+
For more information on how to install and configure the Azure File Sync agent with Windows Server, see [Planning for an Azure File Sync deployment](file-sync-planning.md) and [How to deploy Azure File Sync](file-sync-deployment-guide.md).
94
+
95
+
- The agent installation package must be installed with elevated (admin) permissions.
96
+
- The agent isn't supported on Nano Server deployment option.
97
+
- The agent is supported only on Windows Server 2019, Windows Server 2016 and Windows Server 2022.
98
+
- The agent installation package is for a specific operating system version. If a server with an Azure File Sync agent installed is upgraded to a newer operating system version, the existing agent must be uninstalled. Restart the server and then install the agent for the new server operating system (Windows Server 2016, Windows Server 2019, or Windows Server 2022).
99
+
- The agent requires at least 2 GiB of memory. If the server is running in a virtual machine with dynamic memory enabled, the VM should be configured with a minimum 2048 MiB of memory. See [Recommended system resources](file-sync-planning.md#recommended-system-resources) for more information.
100
+
- The Storage Sync Agent (FileSyncSvc) service doesn't support server endpoints located on a volume that has the system volume information (SVI) directory compressed. This configuration will lead to unexpected results.
101
+
- All supported Azure File Sync agent versions use TLS 1.2 by default and TLS 1.0 and 1.1 are not supported. Starting with v18 agent version TLS 1.3 will be supported for Windows Server 2022.
102
+
103
+
### Interoperability
104
+
105
+
- Antivirus, backup, and other applications that access tiered files can cause undesirable recall unless they respect the offline attribute and skip reading the content of those files. For more information, see [Troubleshoot Azure File Sync](/troubleshoot/azure/azure-storage/file-sync-troubleshoot?toc=/azure/storage/file-sync/toc.json).
106
+
- File Server Resource Manager (FSRM) file screens can cause endless sync failures when files are blocked because of the file screen.
107
+
- Running sysprep on a server that has the Azure File Sync agent installed isn't supported and can lead to unexpected results. The Azure File Sync agent should be installed after deploying the server image and completing sysprep mini-setup.
108
+
109
+
### Sync limitations
110
+
111
+
The following items don't sync, but the rest of the system continues to operate normally:
112
+
113
+
- Azure File Sync v17 agent and later supports all characters that are supported by the [NTFS file system](/windows/win32/fileio/naming-a-file) except invalid surrogate pairs. See [Troubleshooting guide](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#handling-unsupported-characters) for more information.
114
+
- Paths that are longer than 2,048 characters.
115
+
- The system access control list (SACL) portion of a security descriptor that's used for auditing.
116
+
- Extended attributes.
117
+
- Alternate data streams.
118
+
- Reparse points.
119
+
- Hard links.
120
+
- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
121
+
- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data.
122
+
123
+
> [!NOTE]
124
+
> Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
125
+
126
+
### Server endpoint
127
+
128
+
- A server endpoint can be created only on an NTFS volume. ReFS, FAT, FAT32, and other file systems aren't currently supported by Azure File Sync.
129
+
- Cloud tiering isn't supported on the system volume. To create a server endpoint on the system volume, disable cloud tiering when creating the server endpoint.
130
+
- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
131
+
- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
132
+
- Don't store an OS or application paging file within a server endpoint location.
133
+
134
+
### Cloud endpoint
135
+
136
+
- Azure File Sync supports making changes to the Azure file share directly. However, any changes made on the Azure file share first need to be discovered by an Azure File Sync change detection job. A change detection job is initiated for a cloud endpoint once every 24 hours. To immediately sync files that are changed in the Azure file share, use the [Invoke-AzStorageSyncChangeDetection](/powershell/module/az.storagesync/invoke-azstoragesyncchangedetection) PowerShell cmdlet to manually initiate the detection of changes in the Azure file share.
137
+
- The storage sync service and/or storage account can be moved to a different resource group, subscription, or Microsoft Entra (formerly Azure AD) tenant. After moving the storage sync service or storage account, you need to give the Microsoft.StorageSync application access to the storage account (see [Ensure Azure File Sync has access to the storage account](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#troubleshoot-rbac)).
138
+
139
+
> [!NOTE]
140
+
> When creating the cloud endpoint, the storage sync service and storage account must be in the same Microsoft Entra tenant. After you create the cloud endpoint, you can move the storage sync service and storage account to different Microsoft Entra tenants.
141
+
142
+
### Cloud tiering
143
+
144
+
- If a tiered file is copied to another location by using Robocopy, the resulting file isn't tiered. The offline attribute might be set because Robocopy incorrectly includes that attribute in copy operations.
145
+
- When copying files using Robocopy, use the /MIR option to preserve file timestamps. This will ensure older files are tiered sooner than recently accessed files.
146
+
70
147
## Version 17.2.0.0
71
148
72
149
The following release notes are for Azure File Sync version 17.2.0.0 (released February 28, 2024). This release contains improvements for the Azure File Sync service and agent.
Copy file name to clipboardExpand all lines: articles/storage/file-sync/file-sync-server-endpoint-create.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Understand the options during server endpoint creation and how to b
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: how-to
7
-
ms.date: 02/05/2024
7
+
ms.date: 05/08/2024
8
8
ms.author: kendownie
9
9
---
10
10
@@ -102,6 +102,27 @@ How files appear on the server after initial download finishes depends on your u
102
102
***Cloud tiering is enabled** </br> New and changed files from other server endpoints will appear as tiered files on this server endpoint. These changes will only come down as full files if you opted for [proactive recall](file-sync-cloud-tiering-overview.md#proactive-recalling) of changes in the Azure file share by other server endpoints.
103
103
***Cloud tiering is disabled** </br> New and changed files from other server endpoints will appear as full files on this server endpoint. They won't appear as tiered files first and then recalled. Tiered files with cloud tiering off are a fast disaster recovery feature and appear only during initial provisioning.
104
104
105
+
### Provisioning steps
106
+
107
+
When a new server endpoint is created using the portal or PowerShell, the server endpoint isn't ready to be used immediately. Depending on how much data is present on the corresponding file share in the cloud, it might take few minutes to hours for the server endpoint to be functional and ready to use.
108
+
109
+
In the past, if you wanted to check the status of the server endpoint provisioning status and whether the server is ready for users to access data, you had to log in to the server endpoint and see if all the data had been downloaded. With provisioning steps, you can understand whether a server endpoint is ready to use or not and if the sync is fully functional directly from the Azure portal, in the server endpoint overview blade.
110
+
111
+
For supported scenarios, the **Provisioning steps** tab provides information on what's happening on the server endpoint, including when the server endpoint is ready for user access.
112
+
113
+
#### Supported scenarios
114
+
115
+
Currently, provisioning steps are only displayed when the new server endpoint being added has no data on the server path selected for the server endpoint. In other scenarios, the provisioning steps tab isn't available.
116
+
117
+
#### Provisioning status
118
+
119
+
Here are the different statuses that are displayed when server endpoint provisioning is in progress and what they mean:
120
+
* In progress: SEP isn't ready for user access.
121
+
* Ready (sync not functional): Users can access data, but changes won't sync to cloud file share.
122
+
* Ready (sync functional): Users can access data and changes will be synced to the cloud share making the endpoint fully functional.
123
+
* Failed: Provisioning failed because of an error.
124
+
125
+
The provisioning steps tab is only visible in the Azure portal for supported scenarios. It won't be available or visible for unsupported scenarios.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments