Okay, let's get this party started.
This is going to be a stout series of demos because
we've got quite a bit of work to do.
We're going to start with Storage Migration Service,
and you're looking at the desktop.
Actually, if I do a run and do a winver,
it's actually a Windows Server 2019 machine.
And I've specifically done that, so if I open up again,
run win2019 as the host name. I've done that to show a use case of
Storage Migration Service of taking the file shares,
I have two here binaries and scripts,
and we're going to move these to my mem3 virtual server,
which is running Windows Server 2022.
Let's say that we want to decommission this box, all right?
So the front end we're going to use is Windows Admin Center,
and to show how I got to this particular screen,
let's go to All connections,
and I've got my Windows 2019 box set up as a WAC Gateway.
And then if I come down under my tools, I have Files & file sharing.
And then we can enumerate the file shares specifically by moving to that tab
where we can inspect if we want to binaries and scripts,
which are our two file shares, okay?
That's all well and good.
Now as far as storage migration goes, let's go to Storage Migration Service.
You have to remember that the extensibility of Windows Admin
Center happens through the extensions UI.
So if you don't see Storage Migration Service,
we'll want to come over to Settings here in the upper right,
and we'll want to go over to Extensions.
And you can search the extensions gallery,
bring that in as an installed extension.
Let me do a search here for storage mig, and there it is.
And you might have noticed, let me get rid of this filter,
that the WAC interface,
one of its hallmarks is the ability to have updates for these extensions.
So it's a much more contemporary 21st‑century administrative surface,
although unfortunately,
I see that the capabilities in here generally aren't matching
what's in the either Powershell interface natively or using a
Microsoft Management Console.
Anyway, get off your soapbox, Tim.
Let's just go back to our server, and let's go back to Storage Migration Service,
and let's do this thing.
Storage Migration Service, all right, so here we go,
migrate servers and file shares to Azure or Windows Server 2022
without requiring apps or users to change anything.
Nice.
Let's click Install,
and I am going to specify credentials that I know
are good for both of my machines.
I'll use these credentials for all connections and click Continue.
Yes, I'll save Edge.
I'll wait here,
and you don't have to wait with me for WAC in conjunction with my
local win2019 server to set up the service for us.
Here we are.
This is useful to read, although we can suppress ever seeing it again.
We're going to create a job and do an inventory that gathers the
file shares and configuration of our source,
we're then going to do a copy, and then optionally,
we can cut over where the new server actually takes over the identity of the
old so that apps or users don't have to change anything.
Let's click Close here.
So, here we have our overview, it's giving us a running inventory.
Now, of course, it's all 0's because we haven't done anything.
Let's come down and go to New job, and I'm going to call this win2019‑,
well, it doesn't like the dash, so I'll just leave that alone there.
The source device can either be Windows Server,
in or out of a failover cluster, Linux servers,
or a NetApp array.
I'm going to do Windows.
Let's click OK.
Now some points I want to call out on this prerequisite.
Again, you can reach all the way back to Windows Server 2003.
You can migrate in and out of clusters.
Some best practices here.
Not supported, this is important.
Domain migrations or cutover of domain controllers,
so we're talking about member servers only,
okay?
Let's click Next.
On the enter credential step,
it looks like a dun goofed by specifying a user principal name.
This makes sense because if you're cutting over or
planning to migrate from a really old server,
maybe the UPN support isn't quite as good,
so I'll do the old school NetBIOS domain name,
you know, not the DNS, but the NetBIOS domain name backslash username.
Now am I going to include administrative shares?
No, and I'm not going to migrate from a failover cluster either,
so let's click Next.
All right, so we're going to use this machine obviously as our orchestrator.
I guess I should have said that before.
The Orchestrator server is simply the machine that you
run the Storage Migration Service on,
and it looks like WAC is using my win2019 box as an orchestrator,
which is totally fine.
Looks like there's no dependencies.
Now I would need the Storage Migration Service installed if it weren't already,
and that's what would happen now.
So let's click Next, and let's do an inventory scan.
Now, again,
if we were on a separate machine acting as the orchestrator,
that would be contributing the network, the CPU,
the memory.
I'm going to do that on win2019 itself,
and I'm going to add in that particular device.
We can do an Active Directory search here for win2019.
Let me click Search.
Here is our machine, let's bring that in.
We'll hit Validate.
Let's validate that machine.
Looks like the server passed validation, let's click the link here.
This is just letting us know metadata.
Okay, warning on CPU, that's fine, it's a relatively low‑powered VM, so that's good to know.