Okay.
Now I want to demo creating a print mapping using GP preferences printers and I've created a GPO called
Printer Mapping Policy, so I'm going to go ahead and edit that GPO.
And I'm going to Golan under user configuration preferences, control panel settings, printers, and
I'm going to go ahead and create a new shared printer and I'll leave the action it update.
And I'm going to go ahead and.
Do a share path of this particular server that I'm on backslash, backslash 2012 or 2-001/ and then
I've got this share name.
This is a print server.
That's shared out this particular printer here, and I'm going to go ahead and set it at default.
So that on the client when this gets processed.
This particular printer will be set to default.
And I'm going to go ahead and say, okay.
So now I've got this printer shared out.
And I'm going to link it to let me go ahead and.
Oops.
I accidentally controlled and created a second one here, so I'll go ahead and delete that.
I'm going to go ahead and link this GPO up to the sales OYU to the sales users oyu.
And now I've got that printer there.
Now I'm going to go back to my Windows client.
And I'm going to go ahead and do a GP update on this client.
And I'm going to target the user since this is a user policy that's being processed.
And I'll let that complete.
Okay.
So now that's run to completion.
Let me go under devices and printers and see what I've got here.
And now you've noticed that I've got that shared printer connected as a printer connection.
It's set to default.
So it made that connection for me when I ran update.
Now again, notice that.
Unlike GP preferences drive mappings, I did not need to log off, log back on for that print or mapping
to take effect.
In fact, the GP update was sufficient or it could have.
I could have waited for a background refresh.
That happens every 90 minutes, plus that 30 minute random interval.
And that would have been sufficient.
But you know, in any case, that was a simple process of sharing out that printer on my server.
Using GP preferences to create that printer object.
And then processing that printer object as the client.
And I was able to to successfully get that printer.
So that kind of underscores how easy it can be to use the printer mapping policies or the printer mapping
preferences to create printer connections for clients.
So what I'll mention is that even though I didn't use it, I could have created an item level target
that controlled who mapped this printer based on one of these criteria.
So just like I did with preferences, drive mappings and using a security group.
I could have also controlled who would be able to map this printer based on any number of these criteria.
And one area where this might come in handy is with the IP address range filter.
And you can imagine a scenario where certain printers physically, Mike, reside on certain floors of
a building and those floors might be served by a particular IP address range.
So what this would allow you to do is essentially create an item level target that ensured that only
printers that are physically close to the particular user's subnet.
Would get maps.
So I might have, for example, a bunch of addresses in this range that represent a printer on the first
floor of the headquarters building.
And anyone that's within the subnet on their computer would get this printer mapped.
So there's some interesting scenarios you can use item level targeting for.
To make the kind of positioning or the connecting of printers more proximate to the user and where they
actually sit physically, which has always been a challenge with printing.