Now what took me a long,
long time was to discover that the scan command is hidden
depending on your resolution actually.
See, I select this and validate runs your initial prereq check,
but I'm like why are there no shares showing up down here?
Well, you know what it is?
Select the server, and hidden here, Start scan.
That took way too long for me to figure out, it really did.
After the scan, which didn't take long in my case,
I have my scripts and binaries folders listed down below,
and we can see some metadata in terms of how we're sharing them,
what the size is, succeeded failed, file enumeration,
and if we click one,
it just gives us all the specific meta that we would want to know,
and actually let me show you this,
if I go and take a look at say the binaries shared folder,
I just want to go over to security,
I just want you to see that I have some non‑default DACL,
or discretionary access control list, entries here and these could be local or,
in my case, they're domain groups.
I've got an automation team, and we would presumably,
I think you'd agree, want that to migrate along with the file share and its data.
If we plan on actually cutting over the server,
we have to be apprised as far as IP addressing as you can see,
as well as the volume structure and layout on that machine.
Good.
So there is our enumeration here.
We've got three shares, this MTA.
What's this MTA one?
MTATempStore.
Yeah, well that one, unfortunately, is skipped.
We don't need that.
I just want my user share.
So let's click Next, enter credentials for the destination device.
Again it brings in the default I had before,
so I'm going to need to modify this into old school format here.
Let's click Next.
The destination is going to be my mem1 server.
So let me do Use an existing server, and then we're going to browse for that.
But what I want you to see here just as a possibility is that we could
create a new Azure VM to migrate directly into Azure.
Don't transfer files.
Well, no, we don't want that.
So you can either go directly into Azure,
there is a nice shortcut path for that, or if you're going to stay local,
use an existing mem1.
Let's browse, mem1, search, there is the server,
let's bring that in, Scan,
and let's make sure that that Windows Server 2022 member server has what it
takes as it were to receive the file share data from our source.
Nuts!
You know something, I don't even think that mem1 is online.
Let me click Browse again.
I actually want Windows Server, it's actually mem3.
Whoops.
So let's resolve mem3, and let's add that in and let's do a scan there.
Okay, so here we can see that mem3 just has a single system volume.
We definitely have enough space 165 MB.
Notice that we've got compatibility with Azure File Sync,
which we'll do later in this demo.
I'm going to stay local here, in this case.
Select the shares to transfer.
I'm going to deselect that MTA.
I just want to include binaries and scripts here.
Okay, looking good so far.
Let's click Next.
Here we're asked to adjust our meta, metadata.
Basically,
we can have the storage migration service do a checksum to make sure that
the copied files are exactly the same as the source.
That's a good idea in practice.
We can set a maximum job duration.
In terms of local users and groups, those will be replicated.
How do you want to handle name collisions,
and then we've got retry and delay logic as well.
So let's click Next.
Alright, so another related Windows service,
Storage Migration Service is the engine that you're
going to need on your orchestrator.
The destination machine is going to need the storage
migration service proxy and that's just what happened here
on the Install required features step.
Let's click Next.
Let's validate our Windows 2019 source machine.
Got a warning on that.
What was that?
Well, the CPU I'm fine with, as long as I don't get any errors,
I think I'm fine.
Okay.
Review our settings.
Okay, we can proceed here.
It looks like we're ready to go.
So we've got 23 files to go from Windows 2019 over to mem3.
Let's go ahead and start the transfer.
Alright, it appears to have succeeded,
but I have to say this is a bit inscrutable that
the progress is 99.99% complete.
Now we can come down further here in the report,
actually up on top and look at transfer detail,
source, processed, files, okay, we're good,
SMB details, there is our two boulders that were completely migrated.
So far, so good.
And now we have a very important question about cutting over to the new server.
How do we want to handle this in terms of credentials?
I spent some time reformatting my cred so I'm certainly going to
use those stored credentials on this page,
so let's click Next.
Now on the left, we have our source network adapter and,
it's as any good server should be, statically assigned,
or at least, a DHCP reservation.
I'm going to cut over that information to the destination because,
again, the idea is that we don't want to disrupt connectivity here.
Subnet, I believe, means subnet mask, that's pretty unfortunately named,
and then my gateway is going to be in my environment 10.1.10.1.
Now we're going to want to rename the source computer to avoid a conflict.
We can do either random or we can choose a name.
I'm going to do 2019old.
Is that within the NetBIOS 15‑character limit?
Yes, it is.
Our destination network adapter on my server is this one here via Ethernet.
Okay, looking good.
Let's click Next.
Configuring the mapping.
Alright.
What is our cut over timeout, and what are our Active Directory credentials?
Source credentials will be used if not provided.
That's fine.
So let me click Next.
Again, we want to do a validation here.
While we're waiting, the original name of the source server is Win2019,
the new host name will be win2019old.
Now this is important.
Remember,
that we're subsuming or taking over the original server
name and it's a bit unfortunate because my mem3timw.info
is a Windows server 2022 box, and it's going to be known from now on as win2019,
which again, it's unfortunate.
So make sure you're not hardcoding anything like a
version in your server host name.
That's fine, in this example, though.
So let's start the cut over here by clicking Next,
and then selecting our row, Start cutover.
There we go.
Storage migration will create a temporary account here
and then delete that temporary account.
It's going to need to reboot the machines as well. So we'll let that happen.