Merge pull request #41861 from jeffpatt24/patch-9

Update storage-files-release-notes.md

Author: v-shils

articles/storage/files/storage-files-release-notes.md

@@ -21,7 +21,9 @@ The following versions are supported for the Azure File Sync agent:
 
 | Milestone | Agent version number | Release date | Status |
 |----|----------------------|--------------|------------------|
-| March update rollup | 2.2.0.0 | March 12, 2018 | Supported (recommended version) |
+| Refresh 2 | 3.0.12.0 | May 22, 2018 | Supported (recommended version) |
+| April update rollup | 2.3.0.0 | May 8, 2018 | Supported |
+| March update rollup | 2.2.0.0 | March 12, 2018 | Supported |
 | February update rollup | 2.1.0.0 | February 28, 2018 | Supported |
 | Refresh 1 | 2.0.11.0 | February 8, 2018 | Supported |
 | January update rollup | 1.4.0.0 | January 8, 2018 | Supported until May 8, 2018<sup>1</sup> |
@@ -34,6 +36,58 @@ The following versions are supported for the Azure File Sync agent:
 ### Azure File Sync agent update policy
 [!INCLUDE [storage-sync-files-agent-update-policy](../../../includes/storage-sync-files-agent-update-policy.md)]
 
+## Agent version 3.0.12.0
+The following release notes are for version 3.0.12.0 of the Azure File Sync agent (released May 22, 2018).
+
+### Agent installation and server configuration
+For more information on how to install and configure the Azure File Sync agent with Windows Server, see [Planning for an Azure File Sync (preview) deployment](storage-sync-files-planning.md) and [How to deploy Azure File Sync (preview)](storage-sync-files-deployment-guide.md).
+
+- The agent installation package must be installed with elevated (admin) permissions.
+- The agent is not supported on Windows Server Core or Nano Server deployment options.
+- The agent is supported only on Windows Server 2016 and Windows Server 2012 R2.
+- The agent requires at least 2 GB of physical memory.
+- The Storage Sync Agent (FileSyncSvc) service does not support server endpoints located on a volume that has the system volume information (SVI) directory compressed. This configuration will lead to unexpected results.
+
+### Interoperability
+- 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 (preview)](storage-sync-files-troubleshoot.md).
+- Don't use File Server Resource Manager (FSRM) or other file screens. File screens can cause endless sync failures when files are blocked because of the file screen.
+- Running sysprep on a server which has the Azure File Sync agent installed is not supported and can lead to unexpected results. Agent installation and server registration should occur after deploying the server image and completing sysprep mini-setup.
+- Data deduplication and cloud tiering aren't supported on the same volume.
+
+### Sync limitations
+The following items don't sync, but the rest of the system continues to operate normally:
+- Paths that are longer than 2,048 characters.
+- The discretionary access control list (DACL) portion of a security descriptor if it's larger than 2 KB. (This issue applies only when you have more than about 40 access control entries (ACEs) on a single item.)
+- The system access control list (SACL) portion of a security descriptor that's used for auditing.
+- Extended attributes.
+- Alternate data streams.
+- Reparse points.
+- Hard links.
+- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
+- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data. 
+    
+    > [!Note]  
+    > Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
+ 
+### Server endpoints
+- 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.
+- Cloud tiering is not supported on the system volume. To create a server endpoint on the system volume, disable cloud tiering when creating the server endpoint.
+- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
+- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
+- Don't store an OS or application paging file that's within a server endpoint.
+- Tiered files will become unusable if the files are not recalled prior to deleting the server endpoint.
+ 
+### Cloud tiering
+- 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.
+- When you're viewing file properties from an SMB client, the offline attribute might appear to be set incorrectly due to SMB caching of file metadata.
+
+## Agent version 2.3.0.0
+The following release notes are for version 2.3.0.0 of the Azure File Sync agent released May 8, 2018. These notes are in addition to the release notes listed for version 2.0.11.0.
+
+This release includes the following fixes:
+- Agent updates may hang if the cloud tiering filter driver does not unload.
+- Sync performance may decrease when syncing lots of files.
+
 ## Agent version 2.2.0.0
 The following release notes are for version 2.2.0.0 of the Azure File Sync agent released March 12th, 2018.  These notes are in addition to the release notes listed for version 2.1.0.0 and 2.0.11.0