In this demonstration, I'm going to show you how to migrate print queues,
then we'll look at Windows Server Migration Tools in the context of
migrating dynamic host configuration protocol,
or DHCP, from one server to another.
Now speaking of which, the source server is what I'm logged onto right now.
This is a Windows Server 2019 box named,
funnily enough, win2019old, I believe, is the host name,
as embarrassing as that is.
And I also have another machine.
Let me actually bring up Visual Studio Code here.
I have another machine running Windows Server 2022,
a domain member server named mem1.timw.info,
and actually, let's run some PowerShell here.
I'm going to create a variable that stores a PowerShell
remoting session to that target server,
and then we're going to conveniently enter a remoting
session on that box using the stored Session.
I then want to run Get‑WindowsFeature to see what's
installed here just to make sure.
So it looks like Hyper‑V is already installed,
IIS is already installed, but the Print Server component is not,
so let's take care of that right now with Install‑WindowsFeature.
The name is print‑server.
I'm going to include the Management Tools,
I don't think we'll need to restart, but just in case,
I'll hit Restart.
Hopefully,
it makes sense that we're going to need not only the relevant features
installed on the source and destination machines,
we're also going to need the Windows Server Migration Tools as well.
So while we're waiting for that installation to complete,
let me add in one more call here.
Let's do an Invoke‑Command where the computer names are
mem1.timw.info and win2019old.timw.info,
and the ScriptBlock in question here, we're going to do again,
Get‑WindowsFeature, and the name of the feature is migration.
Let's try that after.
Okay, so success true, restart, null.
Let's do an exit to close that remote session,
and now let me do my Invoke‑Command here just to report.
So it looks like the win2019old has the migration tools installed,
they're not installed on mem1.
Nuts.
Well, I should have stayed in my session there.
Let's enter the session again and let's do one more.
I'm using the up arrow to invoke command history.
So edit this command, and we'll send that.
And again, I'm showing this to you for the two reasons,
one for your career development, number two,
help you gain additional comfortability working from a command
shell environment for your exam success,
especially, I don't know if I told you this,
but Microsoft Worldwide Learning is beginning to reintroduce
performance‑based testing labs on their exams,
and these are mini labs where you're actually doing work,
and you can do that work either with PowerShell or Azure
CLI or in the Azure portal.
So it's just something to keep in mind.
Alright, good deal.
Well that's enough of that stuff.
Now let's get into print server migration,
and I mentioned I wanted to do this using the graphical tools,
then we'll use the Windows Server Management Tools because again,
I just want doing a survey here.
We don't have time or scope to do a demo of every workload,
and I also want to, again,
show some of the graphical possibilities versus the
WSMT possibility using PowerShell.
So here, I'm on my local server,
and I've got this machine win29old setup with some shared printers,
particularly, I have two TCP/IP printers,
one called netprint1 and one called netprint2.
And I want to bring these machines over to a new server,
and when we do it graphically,
you're not allowed to pick and choose on the export,
it's going to export everything.
So let's right‑click the Print Management console node and go
to Migrate Printers from the shortcut menu,
and notice there is export and import as our two options.
So let's do a Next, This print server, Next, Next.
Where are we going to store?
Why don't we put this on the root of drive C.
I'll create a folder called printers, and I'll call this win2019.
Alright.
Now the name of the file is win2019.printerExport.
It's a long extension for a file, isn't it?
It's actually a binary format.
I tried to open it in VS Code.
You're not going to get very far with that, trust me.
It's a binary format file so we can't peek inside of it, unfortunately.
Alright, so no errors.
Everything is good with that.
To do the import, let me see here.
We should be able to do everything from here.
Let me open up an empty MMC console, and let's do a File,
Add/Remove snap‑in,
and let's bring in the Print Management console on a remote server mem1.
Actually, I'll put the full DNS name, mem1.mw.info, click Finish.
Okay.
Alright, so far so good.
Now let's do the same thing.
Right‑click the node, Manage Printers from the shortcut menu.
This time, we'll import printer queues from a file,
and I'm going to path out here using universal naming
convention syntax to win2019old\c$,
which is the administrative share at the root of the volume \printers\,
and then I actually forgot the name of the printer so I'm going
to cheat a little bit and open up Explorer.
Let me just grab this file name in total,
copy that, paste that in here, click Next.
Alright, so I'm going to bring in just the print queues,
as well as the associated drivers.
Now that's a great convenience and that's really what we're talking
about here with these migration wizards giving you as a hybrid cloud
administrator much more convenience,
not having to hunt down and redownload and reinstall all those printer drivers,
you know?
Who's got time for that?
We're going to install the print server, not on this one, but on the network.
That's going to be \\mem1.
We're going to keep existing printers or overwrite existing printers.
We're going to list the printers that were previously listed in the directory.
I'm going to list all of these printers in Active
Directory to make them easier to find.
We'll click Next, and it looks like there was some errors, but we can conveniently open Event Viewer using this button.