We're back from a reboot.
Actually,
you'll find that both the source and destination
machines will reboot several times,
and there's actually a lot going on under the hood with Storage
Migration Service in terms of the servers.
Because of the rename of both machines, they're going to need to unjoin,
rejoin the domain, there's temp accounts being created.
I would suggest you read the Microsoft Docs article,
How cutover works in Storage Migration Service,
to learn about those details.
But I've signed back into my old Windows Server 2019 machine.
And we can see in WAC, win2019old.timw.info.
I've gone back into Storage Migration Service,
and we now can see that we're showing that the job,
the cutover, has succeeded, and so we're all set to go,
and we can verify this by making a connection to our new server,
which is win2019.timw.info.
And as a matter of fact, here we are right now.
I'm on the machine formerly known as mem3.tim w.info, now known as win2019.
I can demonstrate that just by doing a hostname, win2019.
And if we do a winver,
I guess I could have done that from the PowerShell prompt as well,
this is a Windows Server 2022 box.
And lastly, if I do \\win 2019, we can see our file shares.
And if we go to the local file system, we've got our scripts and binaries.
And if we go and take a look at the access‑control list,
those have been successfully migrated.
Pretty clean, pretty useful.
I think you'd agree.
Without further ado, let's now shift to Azure File Sync.
And so the use case here is you've got one or more local file servers,
and you just have this mass of shared folders with or without DFS.
How can you provide cloud tiering?
How can you provide greater business continuity,
disaster recovery, high availability?
How can you easily do cloud backup?
So that's what we're going to set up.
I'm going to do this directly from this server.
We'll go up into Azure, and as I mentioned,
the first thing you'll want to do is create an
instance of a Storage Sync Service.
I've already created one.
Notice that they are in fact regional resources.
Ps‑storage‑sync, let's come in here,
and let's go ahead and register a server first of all.
We'll go to Registered servers and download the Azure File Sync
agent from the Microsoft Download Center.
Let me click Download.
And let's see here, notice that it supports not only Server 2022,
but there's an msi for 2019, 2016, and even 2012R2.
Remember that one of the use cases of Azure File Sync is to help you move
forward to decommission those old legacy file servers.
So I'm going to open this msi, and we'll just run through this installer.
Just a Next, Next, Finish kind of operation here.
I'll accept the terms of the License Agreement.
We'll install the Azure File Sync agent and the default directory.
No proxy in my environment.
I do, indeed, want to automatically update the agent with Windows Update,
so I'll select that and click Next.
All right, that's finished.
Let's click Finish,
and you'll find that the agent has just a minimal graphical
interface in addition to the service, the Windows service,
that runs in the background.
Let's click OK here and get signed in.
We're going to sign into not a sovereign cloud, but the public cloud.
I'm not a Cloud Solution Provider.
Let's sign in here.
Oh boy!
Looks like we've got a reliance on Internet Explorer.
I can't believe that.
So let me quickly take care of that by opening up Server Manager.
You know what I'm going to do.
And we'll go to Local Server, and we'll turn on that I,
we'll turn off, rather, the IE, Internet Explorer,
Enhanced Security Configuration.
Yikes!
Okay, let's try that again.
And it's not liking it, so let's close out of the agent and let's start it again.
Okay,
so we'll sign in with my Azure AD account that has
enough privileges to do this operation.
I use Azure MFA, or multi‑factor authentication,
so I'll want to take care of that.
Once you've handled authentication,
we need to map in and register with our Storage Sync Service.
So I'll select my Subscription from the list,
my Resource Group, and then ultimately the ps‑storage‑sync Storage Sync Service.
Let's click Register.
Handshake this in.
Again, there's no reliance on an ExpressRoute circuit or a site‑to‑site VPN. We're going over TCP 443.