Printer mapping based on client machine IP?

R.O.S.S.I

R.O.S.S.I

R.O.S.S.I

Soldato
Joined
16 Nov 2002
Posts
11,290
Location
The Moon
Hi all, just wondering if this is possible...

Basically I've got a remote desktop environment set up which users at 3 different sites connect to. At the moment when it comes to printing i've installed the 3 separate printers at each site direct onto the server so that they have access to them in their printers list.

I'm just wondering is there a way I can set it so that it only maps the printer associated with their site?

I'm thinking by IP as all 3 sites are on their own subnet. Would there be a way of telling the DC or whatever that if a client from this IP range logs in it should get this printer, etc? I'm assuming if it is possible it'll be via a group policy.

We've got some users who work across all 3 sites and they make mistakes sometimes due to not checking what is set as their default printer, so in an effort to make it simpler for them is there any way I can make it just map the correct printer?

I did have a quick look at location aware printing but i'm not sure if thats the correct thing!
 
You can do that with group policy preferences, its called item level targeting.

ntkZ7H4.jpg
 
Last edited:
ruffneck said:
You can do that with group policy preferences, its called item level targeting.

ntkZ7H4.jpg
Click to expand...

Cheers, will have a butchers and see if I can implement it. Would this method remove a printer and remap a new one aswell?

Say for example user logs in at site 1, gets site 1 printer mapped and set as default, then user goes to site 2 and site 1 printer gets removed and site 2 printer gets mapped instead - or will it keep all printers?

Thanks.
 
Hmmm I've tried that and have it just applied to one user at the moment to test but it doesn't seem to be playing ball.

A gpresult /r shows that the policy I've made is being applied to the test user but i'm not getting the printer mapping shown when they log on.
 
Ooops bit of a dumb moment, I hadn't installed the actual print drivers on our RDS server so it wouldn't map it! Installed them and looks to be working now!
 
Hi all, sorry to resurrect an old thread but I thought I'd got this sorted but it doesnt seem to want to map the correct printer....


I set it up so that the mappings were in the group policy for our 3 different sites and the 3 different printers we have. This worked fine when I tested it at our main site (it mapped the right printer), but when I went to the 2 other sites and logged on it wouldnt map the relevant printer it kept mapping the printer from the main site (even after deleting it and relogging)


Is there any problem with this sort of setup working on a thin client?

Just wondering if that is having anything to do with it - i.e the group policy is recognising the IP of the remote desktop server the thin client is loggin onto as the client, instead of the thin client's IP itself?! Which may explain why I am only getting the main site printer mapping across and not the other two when I go to those sites. (Not sure if I've made sense!)


Anyone any ideas?
 
Deathwish said:
You would need the IP of the client that is connecting to RDS, not the RDS servers IP.
Click to expand...

Sorry to quote myself, but you need the IP of the client. As the GPO you have created is being applied to the RDS server it will base the printer mappings on the IP of the RDS server, not the end user.

What clients are the remote users connecting from? You can make a script around some WMI, http://msdn.microsoft.com/en-us/library/aa383838.aspx
 
Deathwish said:
Sorry to quote myself, but you need the IP of the client. As the GPO you have created is being applied to the RDS server it will base the printer mappings on the IP of the RDS server, not the end user.

What clients are the remote users connecting from? You can make a script around some WMI, http://msdn.microsoft.com/en-us/library/aa383838.aspx
Click to expand...

Does it not recognise the Wyse terminals IP as the clients IP? I take it thats where im going wrong if so. Or have I completely missed something here?
 
Last edited:
A-ha! Think i've sussed it, turns out you need to specify it is a Remote Desktop Services session in the targetting editor - it then lets you specify a client IP address for the remote session.

Looks like its working now. Going to test a bit more but should be reet I hope!
 
Its mapping the correct printer for where they are based, but it isn't making it the default or removing any previously mapped printers!

At the moment I've got the printers installed directly onto the server, so all 3 printers are available to all 3 sites (which is no good). When I've sussed the printer mapping and it maps the correct printer depending on where you log on and removes the old ones, I'll just delete the ones installed to the server so that hopefully the user should have just one printer mapped (the one for their site)
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom