1
00:00:01,040 --> 00:00:05,570
Migrate DFS to Azure File Sync. Let's consider that you're

2
00:00:05,570 --> 00:00:10,280
currently aggregating multiple file shares into a single DFS

3
00:00:10,280 --> 00:00:12,780
tree infrastructure. And going further,

4
00:00:12,780 --> 00:00:16,110
you've enabled DFS replication to have multiple

5
00:00:16,110 --> 00:00:18,490
servers in your on‑premises environment,

6
00:00:18,490 --> 00:00:21,040
maintaining copies of those shared folders.

7
00:00:21,040 --> 00:00:25,160
DFS has been around in Windows Server for many years as a way to make

8
00:00:25,160 --> 00:00:28,140
file shares more accessible across your organization.

9
00:00:28,140 --> 00:00:32,320
Now that we have AFS and you see how easy it is to install the agent on

10
00:00:32,320 --> 00:00:36,630
servers, register them into sync groups and get syncing, you might wonder how

11
00:00:36,630 --> 00:00:40,330
can we migrate DFSR to AFS? It's really straightforward.

12
00:00:40,330 --> 00:00:41,510
There's no magic to it.

13
00:00:41,510 --> 00:00:43,650
Of course, you're going to want to create a sync group.

14
00:00:43,650 --> 00:00:46,040
I would start with the root of the DFS tree,

15
00:00:46,040 --> 00:00:49,400
install the AFS agent on the primary DFS host,

16
00:00:49,400 --> 00:00:53,310
create a server endpoint. The big catch here is do not enable tiering.

17
00:00:53,310 --> 00:00:56,680
You don't want to have unexpected behavior between DFS,

18
00:00:56,680 --> 00:01:01,670
particularly DFS replication and AFS replication. Sync up the

19
00:01:01,670 --> 00:01:05,090
files, follow suit with your other DFS hosts, and once the

20
00:01:05,090 --> 00:01:07,640
entire file server army, as it were,

21
00:01:07,640 --> 00:01:11,440
has its file share synchronizing, now you would need to structure

22
00:01:11,440 --> 00:01:14,140
those sync groups in the cloud appropriately.

23
00:01:14,140 --> 00:01:16,860
At that point, you can retire DFS. Again,

24
00:01:16,860 --> 00:01:19,070
it's nothing that normal logic,

25
00:01:19,070 --> 00:01:25,000
it seems to me, wouldn't lead you to in terms of that migration, and that's good news, I think.