cancel
Showing results for 
Search instead for 
Did you mean: 

Local printer Lock with Printing Assistant Landscape (PAL)

Former Member
0 Kudos

Hello,

We are thinking about implementing PAL on SAP Systems. We have a small issue that i want to ask if someone has the same problem.

Is there a way to lock a printer only for one system ? For example the Printer A is them locked on Q system and in P system is unlocked.

One more question How should i deal with Virtual printers ?

Thanks

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Jorge -

We are faced with same issues.  What did you decide?  Did you just "lock" printer via security?  I'd love to use PAL, but we do lock all printers in Dev and Quality so nothing will print by accident (which it has before).  I'm concerned about pushing this to security since they already have bandwidth issues supporting our environment.

Florian
Active Contributor
0 Kudos

Hello Dawn,

this User last logged in Feb 27, 2013 as you can see in his profile. Might be you never get an answer.

Anyhow, why not push it to the security. Billy shows all options and you just have to decide. I mean, push it to the security team out of your bandwidth issues seems to be smart, but I don't think you will save a lot of your bandwidth.. The central configuration is not chanced that often...

On the other hand of course there is just one instance in one system, a very easy to support thing.

IT's really hard to give here a good decision without knowing the whole landscape and all your requirements.

~Florian

bxiv
Active Contributor
0 Kudos

You could use PAL for Dev and QA and leave Prod outside of PAL, to ensure you have consistency in Dev/QA at least.  Or you could setup a new group in PAL and have only Production in the group, this would still allow you to lock printers in Dev and QA but you are still looking at the same amount (if not more) work doing it in this fashion.

Former Member
0 Kudos

Yes, we do have a large landscape to administer. We have approx 10 production instances so we then have 20 Dev/QA systems.  We have approx 1200 printers we manage around the world.  The majority of printing really only comes from 3 of the production landscapes. We are forever having issues with inconsistencies between DEV/QA and production. PAL really looks promising to address those issues. I'll be reaching out to our security team to get their take on security.

We also have an option that we could just not setup the AIX print queue for DEV/QA that way those systems couldn't print unless needed by a special project. We would then just manually setup a print queue in AIX. Thank you for all the feedback! We really need to get handle on this administration nightmare we currently have for our printing environment.

bxiv
Active Contributor
0 Kudos

If you want the same printer name in all systems then, no you can not currently lock a printer for one system and not the others.  If the name is important, but you can put a suffix of qa or prd on the end, then you could lock on a per system basis.

Other thoughts, if the name needs to remain the same in all systems but you need to prevent printing:

  • Have SAP security prevent access to the printers, and only allow testing to occur if someone needs to print.
  • Go to your host file and put in 127.0.0.1 with the host name of that printer/print server....however this option is only going to work if you have SPAD setup to use DNS vs IP address.
  • Configure the firewall on the system to prevent traffic being sent to a destination IP address.

As for virtual printers, I'm not sure what this is in reference to PAL?