1 00:00:00,840 --> 00:00:04,350 Configure Azure File Sync. Well, if you're coming from the 2 00:00:04,350 --> 00:00:06,310 previous module, and I hope you are, 3 00:00:06,310 --> 00:00:11,200 you know what a server endpoint is. A server endpoint is going to be one or more 4 00:00:11,200 --> 00:00:14,920 physical or virtual file servers in your local environment. 5 00:00:14,920 --> 00:00:18,400 And when you join or register a server to your 6 00:00:18,400 --> 00:00:20,570 storage service and join a sync group, 7 00:00:20,570 --> 00:00:24,770 you provide a local path to the file share. No Universal Naming 8 00:00:24,770 --> 00:00:28,720 Convention paths nor are Network Attached Storage devices 9 00:00:28,720 --> 00:00:31,920 supported. It needs to be a local internal path. 10 00:00:31,920 --> 00:00:35,390 I had mentioned that you can sync individual file 11 00:00:35,390 --> 00:00:37,410 shares, which is the preferred way to go. 12 00:00:37,410 --> 00:00:42,660 You can add volumes to your sync group, but that doesn't support the 13 00:00:42,660 --> 00:00:47,830 tiering, so you wouldn't get the benefit of heatmap that AFS has as one 14 00:00:47,830 --> 00:00:50,290 of its native features. Within its sync group, 15 00:00:50,290 --> 00:00:53,130 you're limited to one registered server per endpoint. 16 00:00:53,130 --> 00:00:56,340 So in all likelihood, although you may very well have just 17 00:00:56,340 --> 00:00:58,440 one storage service in your environment, 18 00:00:58,440 --> 00:01:03,200 you're likely in a common scenario to have a registered server with multiple 19 00:01:03,200 --> 00:01:06,850 file shares, each share syncing to a separate sync group. 20 00:01:06,850 --> 00:01:09,720 And lastly, there is a PowerShell module. 21 00:01:09,720 --> 00:01:13,110 The nouns start with storage sync that allow you to 22 00:01:13,110 --> 00:01:15,360 configure and customize the service. 23 00:01:15,360 --> 00:01:18,340 One PowerShell cmdlet you may want to be aware of is 24 00:01:18,340 --> 00:01:22,830 New‑StorageSyncNetworkLimit. This helps your AFS implementation 25 00:01:22,830 --> 00:01:25,550 be a better citizen in your local data centers. 26 00:01:25,550 --> 00:01:33,000 In other words, you can throttle the amount of bandwidth that AFS uses on a given registered server.