Jump to content

Recommended Posts

Posted

We added secure print to our print management solution recently which meant giving all staff the ability to print to the secure print queue.

 

Problem is that menas now that they have multiple printers when they roam around that the default printer isn't always setting to the correct one, and everyone has different requirements which has left me scratching my head on how to solve this really.

 

Under GPP > Printers I've got a list from 1 - 47, every printer is in twice, first as a delete rule than as an update rule (I can't remember why they're in as update rather than create, I'm sure there must be a reason for that but maybe someone else can remember why?) Secure print was the last one added so that's down at 46 for delete and 47 for update. This means it's the last one in the list to processed as from the looks of things it process them from the top down rather than in a priority order like I'm used to with the policies themselves.

 

We've got people with local printers and people with other networked printers which aren't a part of secure print. These ideally need to be the default, leaving secure print as a secondary printer, whilst still making the secure print queue the default on PCs where no other printer exists.

 

I wonder if maybe i need to completely change the way my printers are deployed to get this working better rather than modifying a current system, unless someone can give me some good advise here?

Posted
We had this headache - and I think they were set to update rather than create because it speeded up the login - but in the end we went back to scripts. Seems a bit of a backwards step but it seems to work much better :)
Posted
Do you have just one policy to deploy all printers? Would it not be better to target printer deployment in multiple polcies at OU level. Locations that only have the secure print available will then only get the secure print policy and set to default?
Posted
Do you have just one policy to deploy all printers? Would it not be better to target printer deployment in multiple polcies at OU level. Locations that only have the secure print available will then only get the secure print policy and set to default?

 

All in one global policy yes, I previously had an implementation where it was multiple policies at OU level but it was more of a headache than it was worth. I ended up implementing the same thing in one policy that was easier to manage, this is the first real issue i've had with this method in 2 or so years.

 

On the other hand you've given me an idea.....if i just split the secure print into a separate policy and do some fancy jiggery pokery with the item level targetting i might be able to get secure print to apply first, then the main print policy to apply second and override any defaults set by the secure print policy.

Posted
All in one here with item level targeting. You can order in gpp as well

 

This is one of the things that's bugging me...the ordering.

 

I can't seem to move the order around beyond simply moving the one at the bottom up 1 or the one at the top down 1...that's all i seem to be able to do. What am I doing wrong here?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...