_techie_ Posted April 26, 2021 Posted April 26, 2021 Hi. We recently did an in place update through our print support vendor, to PC v20. It was reported recently that students weren't getting notifications from PC for hold release queue jobs. We are running the following: Server 2016 Print Server Win10 LTSC 2019 Clients Zero Papercut client deployment from PCClient share. I can replicate this and originally put this down to me blocking the notification area for students. However re-enabling still shows no notifications for PC. If I send a manual notification from PC admin console, that doesn't make any difference either. Running as a domain admin with no user GPOs applying allows some notifications to work, but I don't get the papercut logo, or the actual message, just a pc-toast notify notification to show in the notification area. Sending a manual notification from PC admin results in the same pc toast notification with no message. Doing the same on a workstation with no Computer GPOs applying results in the same. The The solution ATM is to run the local cache version but trying to deploy this using the same gpo method (system...logon...run these programs at login) caused logon to slow to around 2, 2.5 mins from a normal 20 seconds. How are people deploying the local cache version? Any suggestions welcome, bit odd this one. Cheers Mark
_techie_ Posted April 28, 2021 Author Posted April 28, 2021 For anyones reference, I sorted this by using the following: --disable-toast-notifications on the login script, whilst removing --disable-balloon-tips This allowed basic pop ups in the systray area, without needing access to the notifications pane. Cheers Mark 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now