|
^ How did you get into the dog pee industry
|
#
¿
Jul 23, 2020 02:27
|
|
|
|
| # ¿ Apr 2, 2023 08:59 |
|
|
We're moving towards a VPNless user environment, and have recently implemented a managed printer setup where the user prints to a virtual printer and then can release the job from any on-site printer. As such, when working from home, a user will have to wait until they're on-site to be able to send the jobs to the virtual printer because it will fail if Windows can't see the print server. Is there any known way where a user could send a print job in a way that within Windows the job remains in a holding pattern until the next time the print server is visible to Windows (when connected to the cooperate network on-site) and then spits out all the jobs to it?
|
|
#
¿
Nov 20, 2020 18:41
|
|
|
Peachfart posted:On a more useful note, Papercut is dirt cheap for a print management software suite and works well, I recommend it. Papercut the software is pretty great for what you pay for, and I love that I can manage color printing access through an AD security group, automap the Black and White queue out with a GPO, and automap/autounmap the color queue with a security group validated GPO. Papercut support however has been pretty terrible in my experience. We first have to go through our vendor, whose only expertise is the initial setup. Anything else tends to leave them clueless and waste a lot of time, and its up to them to decide if escalating directly to PC support is necessary. Even when we do manage to get there, our support experience with PC hasn't been fantastic.
|
|
#
¿
Mar 4, 2021 21:57
|
|
|
ShaneMacGowansTeeth posted:The "PrinterNightmare" print spooler exploit has reached the ears of the higher ups of my IT people so on Thursday evening, someone decided to push a group policy disabling the print spooler for every device on the whole company - every laptop, desktop, tablet, phone & server had their spooler disabled across the entire estate. I work for a very large aerospace company who make planes and also satellites so you might be able to gather who it might be. After four hours, we were able to force a roll back on the policy and restart the spooler but it would also be nice if the company would include the printer team in any changes that might affect the printer estate. After all three weeks ago, one of their network guys changed the DNS record for the print server off his own back without notifying anyone that he was doing so then went on holiday, and it, again, took us about four hours to work out what had got hosed up and how to unfuck it Did they apply to the GPO to the default domain policy/root of the domain by accident or did they really not confirm with the suits if losing the ability to print literally anywhere until a patch dropped was an acceptable loss of functionality?
|
|
#
¿
Jul 13, 2021 14:49
|
|