Creating and removing printers via GP

Hi,

We currently deploy printers via GP and it works very well. We have a printer that we only want deployed to a particular security group. We use item level targeting and it works well. I've just noticed that it doesn't take the printer away once the user logs out, and it gives other (standard) users the ability to print to 'That' printer.

Can anyone help me with what the configuration needs to be so that the printer doesn't hang around after the privileged user has logged off?

Thanks
Talds_AloudsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

aroddickCommented:
Hey,

We have a Printer Preference item that 'deletes' the printer if they are in the wrong AD-Site (item level targetting) so that users on the VPN or in a remote site office don't see their Head Office printers. Works really well.

You could set a Delete Printer Preference item and item level target "the user is NOT a member of the security group" so that as a user logs on, it checks and blows away the "privileged" printer.

To change the item level targetting rule from IS to IS NOT, right click the rule and go to Rule Options - you can then change the AND/OR as well as the IS/IS NOT for the rule. Does that make sense?

Good luck.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Talds_AloudsAuthor Commented:
I'll try that.

What I did try is making a copy of the printer in GP then setting it to delete for everyone, then higher in the queue it creates the printer again.
0
aroddickCommented:
Yeah you have to be aware of the processing order of each item otherwise it may end up behaving strangely and it will do your head in!

See attached screenshot of our OR and IS NOT rule if it helps at all..
Capture.JPG
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Talds_AloudsAuthor Commented:
Thanks. So should I simple create a 'copy' of the update printer GP entry and convert it to delete and apply the IS NOT rule?
0
aroddickCommented:
Yeah that would be easiest I think, either way should be a pretty quick process. Order the items so that the Delete processes last.
0
Talds_AloudsAuthor Commented:
Fantastic! Works perfect
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Printers and Scanners

From novice to tech pro — start learning today.