Skip to content

Commit a40da41

Browse files
authored
Merge pull request #49990 from jeffpatt24/patch-21
Update storage-sync-files-planning.md
2 parents 0cdf87a + 30d088f commit a40da41

File tree

3 files changed

+19
-12
lines changed

3 files changed

+19
-12
lines changed

articles/storage/files/storage-sync-files-deployment-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ We strongly recommend that you read [Planning for an Azure Files deployment](sto
2020
- [Region availability](storage-sync-files-planning.md#region-availability) for Azure File Sync.
2121
- [Create a storage account](../common/storage-create-storage-account.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json) for a step-by-step description of how to create a storage account.
2222
- [Create a file share](storage-how-to-create-file-share.md) for a step-by-step description of how to create a file share.
23-
* At least one supported instance of Windows Server or Windows Server cluster to sync with Azure File Sync. For more information about supported versions of Windows Server, see [Interoperability with Windows Server](storage-sync-files-planning.md#azure-file-sync-interoperability).
23+
* At least one supported instance of Windows Server or Windows Server cluster to sync with Azure File Sync. For more information about supported versions of Windows Server, see [Interoperability with Windows Server](storage-sync-files-planning.md#azure-file-sync-system-requirements-and-interoperability).
2424
* Ensure PowerShell 5.1 is installed on your Windows Server. If you are using Windows Server 2012 R2, ensure that you are running at least PowerShell 5.1.\*. You can safely skip this check on Windows Server 2016 as PowerShell 5.1 is the default version out-of-box. On Windows Server 2012 R2, you can verify that you are running PowerShell 5.1.\* by looking at the value of the **PSVersion** property of the **$PSVersionTable** object:
2525

2626
```PowerShell

articles/storage/files/storage-sync-files-planning.md

Lines changed: 16 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -62,18 +62,25 @@ Cloud tiering is an optional feature of Azure File Sync in which infrequently us
6262
> [!Important]
6363
> Cloud tiering is not supported for server endpoints on the Windows system volumes.
6464
65-
## Azure File Sync interoperability
66-
This section covers Azure File Sync interoperability with Windows Server features and roles and third-party solutions.
65+
## Azure File Sync system requirements and interoperability
66+
This section covers Azure File Sync agent system requirements and interoperability with Windows Server features and roles and third-party solutions.
6767

68-
### Supported versions of Windows Server
69-
Currently, the supported versions of Windows Server by Azure File Sync are:
68+
### System Requirements
69+
- A server running Windows Server 2012 R2 or Windows Server 2016
7070

71-
| Version | Supported SKUs | Supported deployment options |
72-
|---------|----------------|------------------------------|
73-
| Windows Server 2016 | Datacenter and Standard | Full (server with a UI) |
74-
| Windows Server 2012 R2 | Datacenter and Standard | Full (server with a UI) |
71+
| Version | Supported SKUs | Supported deployment options |
72+
|---------|----------------|------------------------------|
73+
| Windows Server 2016 | Datacenter and Standard | Full (server with a UI) |
74+
| Windows Server 2012 R2 | Datacenter and Standard | Full (server with a UI) |
7575

76-
Future versions of Windows Server will be added as they are released. Earlier versions of Windows might be added based on user feedback.
76+
Future versions of Windows Server will be added as they are released. Earlier versions of Windows might be added based on user feedback.
77+
78+
- A server with a minimum of 2GB of memory
79+
80+
> [!Important]
81+
> If the server is running in a virtual machine with dynamic memory enabled, the VM should be configured with a minimum 2048MB of memory.
82+
83+
- A locally attached volume formatted with the NTFS file system
7784

7885
> [!Important]
7986
> We recommend keeping all servers that you use with Azure File Sync up to date with the latest updates from Windows Update.

articles/storage/files/storage-sync-files-server-registration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Registering a server with Azure File Sync establishes a trust relationship betwe
2121
### Prerequisites
2222
To register a server with a Storage Sync Service, you must first prepare your server with the necessary prerequisites:
2323

24-
* Your server must be running a supported version of Windows Server. For more information, see [Supported versions of Windows Server](storage-sync-files-planning.md#supported-versions-of-windows-server).
24+
* Your server must be running a supported version of Windows Server. For more information, see [Azure File Sync system requirements and interoperability](storage-sync-files-planning.md#azure-file-sync-system-requirements-and-interoperability).
2525
* Ensure that a Storage Sync Service has been deployed. For more information on how to deploy a Storage Sync Service, see [How to deploy Azure File Sync](storage-sync-files-deployment-guide.md).
2626
* Ensure that the server is connected to the internet and that Azure is accessible.
2727
* Disable the IE Enhanced Security Configuration for administrators with the Server Manager UI.
@@ -186,4 +186,4 @@ When Azure File Sync is hosted in a virtual machine running on a Windows Server
186186
## See also
187187
- [Planning for an Azure File Sync deployment](storage-sync-files-planning.md)
188188
- [Deploy Azure File Sync](storage-sync-files-deployment-guide.md)
189-
- [Troubleshoot Azure File Sync](storage-sync-files-troubleshoot.md)
189+
- [Troubleshoot Azure File Sync](storage-sync-files-troubleshoot.md)

0 commit comments

Comments
 (0)