1 00:00:03,070 --> 00:00:03,610 Okay. 2 00:00:03,640 --> 00:00:09,820 Now I want to demo creating a print mapping using GP preferences printers and I've created a GPO called 3 00:00:09,820 --> 00:00:13,870 Printer Mapping Policy, so I'm going to go ahead and edit that GPO. 4 00:00:14,750 --> 00:00:20,630 And I'm going to Golan under user configuration preferences, control panel settings, printers, and 5 00:00:20,630 --> 00:00:24,740 I'm going to go ahead and create a new shared printer and I'll leave the action it update. 6 00:00:24,740 --> 00:00:26,450 And I'm going to go ahead and. 7 00:00:27,420 --> 00:00:35,040 Do a share path of this particular server that I'm on backslash, backslash 2012 or 2-001/ and then 8 00:00:35,040 --> 00:00:36,090 I've got this share name. 9 00:00:36,090 --> 00:00:37,260 This is a print server. 10 00:00:38,280 --> 00:00:43,520 That's shared out this particular printer here, and I'm going to go ahead and set it at default. 11 00:00:44,530 --> 00:00:47,440 So that on the client when this gets processed. 12 00:00:48,450 --> 00:00:51,510 This particular printer will be set to default. 13 00:00:52,460 --> 00:00:54,920 And I'm going to go ahead and say, okay. 14 00:00:55,890 --> 00:00:58,200 So now I've got this printer shared out. 15 00:00:59,140 --> 00:01:03,160 And I'm going to link it to let me go ahead and. 16 00:01:03,160 --> 00:01:03,730 Oops. 17 00:01:04,720 --> 00:01:09,970 I accidentally controlled and created a second one here, so I'll go ahead and delete that. 18 00:01:10,990 --> 00:01:16,660 I'm going to go ahead and link this GPO up to the sales OYU to the sales users oyu. 19 00:01:17,540 --> 00:01:19,640 And now I've got that printer there. 20 00:01:20,620 --> 00:01:23,350 Now I'm going to go back to my Windows client. 21 00:01:24,300 --> 00:01:28,170 And I'm going to go ahead and do a GP update on this client. 22 00:01:29,160 --> 00:01:34,170 And I'm going to target the user since this is a user policy that's being processed. 23 00:01:35,110 --> 00:01:36,700 And I'll let that complete. 24 00:01:37,680 --> 00:01:38,130 Okay. 25 00:01:38,130 --> 00:01:39,880 So now that's run to completion. 26 00:01:39,900 --> 00:01:43,530 Let me go under devices and printers and see what I've got here. 27 00:01:44,480 --> 00:01:49,060 And now you've noticed that I've got that shared printer connected as a printer connection. 28 00:01:49,130 --> 00:01:50,420 It's set to default. 29 00:01:51,440 --> 00:01:55,040 So it made that connection for me when I ran update. 30 00:01:56,030 --> 00:01:57,590 Now again, notice that. 31 00:01:58,560 --> 00:02:05,040 Unlike GP preferences drive mappings, I did not need to log off, log back on for that print or mapping 32 00:02:05,040 --> 00:02:05,940 to take effect. 33 00:02:06,900 --> 00:02:10,550 In fact, the GP update was sufficient or it could have. 34 00:02:10,560 --> 00:02:13,380 I could have waited for a background refresh. 35 00:02:13,410 --> 00:02:17,520 That happens every 90 minutes, plus that 30 minute random interval. 36 00:02:18,410 --> 00:02:20,450 And that would have been sufficient. 37 00:02:21,430 --> 00:02:27,370 But you know, in any case, that was a simple process of sharing out that printer on my server. 38 00:02:28,360 --> 00:02:31,960 Using GP preferences to create that printer object. 39 00:02:32,920 --> 00:02:36,580 And then processing that printer object as the client. 40 00:02:37,520 --> 00:02:40,850 And I was able to to successfully get that printer. 41 00:02:41,850 --> 00:02:47,400 So that kind of underscores how easy it can be to use the printer mapping policies or the printer mapping 42 00:02:47,400 --> 00:02:50,500 preferences to create printer connections for clients. 43 00:02:51,480 --> 00:02:57,060 So what I'll mention is that even though I didn't use it, I could have created an item level target 44 00:02:57,060 --> 00:03:00,870 that controlled who mapped this printer based on one of these criteria. 45 00:03:01,830 --> 00:03:07,050 So just like I did with preferences, drive mappings and using a security group. 46 00:03:08,040 --> 00:03:13,710 I could have also controlled who would be able to map this printer based on any number of these criteria. 47 00:03:14,660 --> 00:03:19,340 And one area where this might come in handy is with the IP address range filter. 48 00:03:20,340 --> 00:03:25,590 And you can imagine a scenario where certain printers physically, Mike, reside on certain floors of 49 00:03:25,590 --> 00:03:30,090 a building and those floors might be served by a particular IP address range. 50 00:03:31,080 --> 00:03:36,420 So what this would allow you to do is essentially create an item level target that ensured that only 51 00:03:36,420 --> 00:03:40,080 printers that are physically close to the particular user's subnet. 52 00:03:41,050 --> 00:03:41,920 Would get maps. 53 00:03:41,920 --> 00:03:47,770 So I might have, for example, a bunch of addresses in this range that represent a printer on the first 54 00:03:47,770 --> 00:03:49,600 floor of the headquarters building. 55 00:03:50,480 --> 00:03:55,070 And anyone that's within the subnet on their computer would get this printer mapped. 56 00:03:56,050 --> 00:04:00,490 So there's some interesting scenarios you can use item level targeting for. 57 00:04:01,450 --> 00:04:06,700 To make the kind of positioning or the connecting of printers more proximate to the user and where they 58 00:04:06,700 --> 00:04:10,780 actually sit physically, which has always been a challenge with printing.