1
00:00:01,040 --> 00:00:04,720
In this demonstration, I'm going to show you how to migrate print queues,

2
00:00:04,720 --> 00:00:08,290
then we'll look at Windows Server Migration Tools in the context of

3
00:00:08,290 --> 00:00:11,390
migrating dynamic host configuration protocol,

4
00:00:11,390 --> 00:00:14,440
or DHCP, from one server to another.

5
00:00:14,440 --> 00:00:18,370
Now speaking of which, the source server is what I'm logged onto right now.

6
00:00:18,370 --> 00:00:22,400
This is a Windows Server 2019 box named,

7
00:00:22,400 --> 00:00:27,840
funnily enough, win2019old, I believe, is the host name,

8
00:00:27,840 --> 00:00:29,730
as embarrassing as that is.

9
00:00:29,730 --> 00:00:31,300
And I also have another machine.

10
00:00:31,300 --> 00:00:34,340
Let me actually bring up Visual Studio Code here.

11
00:00:34,340 --> 00:00:37,000
I have another machine running Windows Server 2022,

12
00:00:37,000 --> 00:00:41,710
a domain member server named mem1.timw.info,

13
00:00:41,710 --> 00:00:43,850
and actually, let's run some PowerShell here.

14
00:00:43,850 --> 00:00:47,770
I'm going to create a variable that stores a PowerShell

15
00:00:47,770 --> 00:00:50,140
remoting session to that target server,

16
00:00:50,140 --> 00:00:52,850
and then we're going to conveniently enter a remoting

17
00:00:52,850 --> 00:00:56,640
session on that box using the stored Session.

18
00:00:56,640 --> 00:00:59,920
I then want to run Get‑WindowsFeature to see what's

19
00:00:59,920 --> 00:01:01,680
installed here just to make sure.

20
00:01:01,680 --> 00:01:04,840
So it looks like Hyper‑V is already installed,

21
00:01:04,840 --> 00:01:10,280
IIS is already installed, but the Print Server component is not,

22
00:01:10,280 --> 00:01:14,010
so let's take care of that right now with Install‑WindowsFeature.

23
00:01:14,010 --> 00:01:17,040
The name is print‑server.

24
00:01:17,040 --> 00:01:19,400
I'm going to include the Management Tools,

25
00:01:19,400 --> 00:01:22,670
I don't think we'll need to restart, but just in case,

26
00:01:22,670 --> 00:01:24,440
I'll hit Restart.

27
00:01:24,440 --> 00:01:24,850
Hopefully,

28
00:01:24,850 --> 00:01:28,880
it makes sense that we're going to need not only the relevant features

29
00:01:28,880 --> 00:01:31,570
installed on the source and destination machines,

30
00:01:31,570 --> 00:01:35,800
we're also going to need the Windows Server Migration Tools as well.

31
00:01:35,800 --> 00:01:39,040
So while we're waiting for that installation to complete,

32
00:01:39,040 --> 00:01:40,940
let me add in one more call here.

33
00:01:40,940 --> 00:01:45,890
Let's do an Invoke‑Command where the computer names are

34
00:01:45,890 --> 00:01:54,840
mem1.timw.info and win2019old.timw.info,

35
00:01:54,840 --> 00:01:57,880
and the ScriptBlock in question here, we're going to do again,

36
00:01:57,880 --> 00:02:03,440
Get‑WindowsFeature, and the name of the feature is migration.

37
00:02:03,440 --> 00:02:05,170
Let's try that after.

38
00:02:05,170 --> 00:02:07,700
Okay, so success true, restart, null.

39
00:02:07,700 --> 00:02:11,290
Let's do an exit to close that remote session,

40
00:02:11,290 --> 00:02:16,060
and now let me do my Invoke‑Command here just to report.

41
00:02:16,060 --> 00:02:22,750
So it looks like the win2019old has the migration tools installed,

42
00:02:22,750 --> 00:02:24,790
they're not installed on mem1.

43
00:02:24,790 --> 00:02:25,260
Nuts.

44
00:02:25,260 --> 00:02:27,470
Well, I should have stayed in my session there.

45
00:02:27,470 --> 00:02:31,640
Let's enter the session again and let's do one more.

46
00:02:31,640 --> 00:02:36,260
I'm using the up arrow to invoke command history.

47
00:02:36,260 --> 00:02:40,320
So edit this command, and we'll send that.

48
00:02:40,320 --> 00:02:42,880
And again, I'm showing this to you for the two reasons,

49
00:02:42,880 --> 00:02:45,740
one for your career development, number two,

50
00:02:45,740 --> 00:02:49,730
help you gain additional comfortability working from a command

51
00:02:49,730 --> 00:02:52,440
shell environment for your exam success,

52
00:02:52,440 --> 00:02:54,410
especially, I don't know if I told you this,

53
00:02:54,410 --> 00:02:58,390
but Microsoft Worldwide Learning is beginning to reintroduce

54
00:02:58,390 --> 00:03:01,430
performance‑based testing labs on their exams,

55
00:03:01,430 --> 00:03:05,750
and these are mini labs where you're actually doing work,

56
00:03:05,750 --> 00:03:09,740
and you can do that work either with PowerShell or Azure

57
00:03:09,740 --> 00:03:11,640
CLI or in the Azure portal.

58
00:03:11,640 --> 00:03:13,580
So it's just something to keep in mind.

59
00:03:13,580 --> 00:03:14,750
Alright, good deal.

60
00:03:14,750 --> 00:03:16,580
Well that's enough of that stuff.

61
00:03:16,580 --> 00:03:19,520
Now let's get into print server migration,

62
00:03:19,520 --> 00:03:23,290
and I mentioned I wanted to do this using the graphical tools,

63
00:03:23,290 --> 00:03:26,580
then we'll use the Windows Server Management Tools because again,

64
00:03:26,580 --> 00:03:28,740
I just want doing a survey here.

65
00:03:28,740 --> 00:03:32,940
We don't have time or scope to do a demo of every workload,

66
00:03:32,940 --> 00:03:34,490
and I also want to, again,

67
00:03:34,490 --> 00:03:37,610
show some of the graphical possibilities versus the

68
00:03:37,610 --> 00:03:40,930
WSMT possibility using PowerShell.

69
00:03:40,930 --> 00:03:43,290
So here, I'm on my local server,

70
00:03:43,290 --> 00:03:48,350
and I've got this machine win29old setup with some shared printers,

71
00:03:48,350 --> 00:03:51,150
particularly, I have two TCP/IP printers,

72
00:03:51,150 --> 00:03:55,240
one called netprint1 and one called netprint2.

73
00:03:55,240 --> 00:03:58,770
And I want to bring these machines over to a new server,

74
00:03:58,770 --> 00:04:00,370
and when we do it graphically,

75
00:04:00,370 --> 00:04:03,010
you're not allowed to pick and choose on the export,

76
00:04:03,010 --> 00:04:05,240
it's going to export everything.

77
00:04:05,240 --> 00:04:09,330
So let's right‑click the Print Management console node and go

78
00:04:09,330 --> 00:04:12,640
to Migrate Printers from the shortcut menu,

79
00:04:12,640 --> 00:04:16,290
and notice there is export and import as our two options.

80
00:04:16,290 --> 00:04:22,280
So let's do a Next, This print server, Next, Next.

81
00:04:22,280 --> 00:04:24,240
Where are we going to store?

82
00:04:24,240 --> 00:04:27,100
Why don't we put this on the root of drive C.

83
00:04:27,100 --> 00:04:36,740
I'll create a folder called printers, and I'll call this win2019.

84
00:04:36,740 --> 00:04:37,640
Alright.

85
00:04:37,640 --> 00:04:42,450
Now the name of the file is win2019.printerExport.

86
00:04:42,450 --> 00:04:45,340
It's a long extension for a file, isn't it?

87
00:04:45,340 --> 00:04:47,110
It's actually a binary format.

88
00:04:47,110 --> 00:04:49,070
I tried to open it in VS Code.

89
00:04:49,070 --> 00:04:51,800
You're not going to get very far with that, trust me.

90
00:04:51,800 --> 00:04:56,640
It's a binary format file so we can't peek inside of it, unfortunately.

91
00:04:56,640 --> 00:04:57,950
Alright, so no errors.

92
00:04:57,950 --> 00:04:59,710
Everything is good with that.

93
00:04:59,710 --> 00:05:01,700
To do the import, let me see here.

94
00:05:01,700 --> 00:05:03,820
We should be able to do everything from here.

95
00:05:03,820 --> 00:05:08,330
Let me open up an empty MMC console, and let's do a File,

96
00:05:08,330 --> 00:05:10,640
Add/Remove snap‑in,

97
00:05:10,640 --> 00:05:17,840
and let's bring in the Print Management console on a remote server mem1.

98
00:05:17,840 --> 00:05:24,400
Actually, I'll put the full DNS name, mem1.mw.info, click Finish.

99
00:05:24,400 --> 00:05:26,340
Okay.

100
00:05:26,340 --> 00:05:27,850
Alright, so far so good.

101
00:05:27,850 --> 00:05:29,240
Now let's do the same thing.

102
00:05:29,240 --> 00:05:33,040
Right‑click the node, Manage Printers from the shortcut menu.

103
00:05:33,040 --> 00:05:36,640
This time, we'll import printer queues from a file,

104
00:05:36,640 --> 00:05:39,830
and I'm going to path out here using universal naming

105
00:05:39,830 --> 00:05:42,940
convention syntax to win2019old\c$,

106
00:05:42,940 --> 00:05:48,470
which is the administrative share at the root of the volume \printers\,

107
00:05:48,470 --> 00:05:51,300
and then I actually forgot the name of the printer so I'm going

108
00:05:51,300 --> 00:05:54,740
to cheat a little bit and open up Explorer.

109
00:05:54,740 --> 00:05:57,840
Let me just grab this file name in total,

110
00:05:57,840 --> 00:06:01,340
copy that, paste that in here, click Next.

111
00:06:01,340 --> 00:06:04,110
Alright, so I'm going to bring in just the print queues,

112
00:06:04,110 --> 00:06:06,240
as well as the associated drivers.

113
00:06:06,240 --> 00:06:09,740
Now that's a great convenience and that's really what we're talking

114
00:06:09,740 --> 00:06:13,710
about here with these migration wizards giving you as a hybrid cloud

115
00:06:13,710 --> 00:06:15,720
administrator much more convenience,

116
00:06:15,720 --> 00:06:21,310
not having to hunt down and redownload and reinstall all those printer drivers,

117
00:06:21,310 --> 00:06:21,640
you know?

118
00:06:21,640 --> 00:06:23,940
Who's got time for that?

119
00:06:23,940 --> 00:06:28,360
We're going to install the print server, not on this one, but on the network.

120
00:06:28,360 --> 00:06:32,140
That's going to be \\mem1.

121
00:06:32,140 --> 00:06:37,140
We're going to keep existing printers or overwrite existing printers.

122
00:06:37,140 --> 00:06:40,990
We're going to list the printers that were previously listed in the directory.

123
00:06:40,990 --> 00:06:43,490
I'm going to list all of these printers in Active

124
00:06:43,490 --> 00:06:46,440
Directory to make them easier to find.

125
00:06:46,440 --> 00:06:55,000
We'll click Next, and it looks like there was some errors, but we can conveniently open Event Viewer using this button.