mari0bros

If you made a separate follow me queue using an existing device from your type 3 queue, you may need to adjust the settings for the release on the Devices section of Papercut to include both virtual queues. I also set "jobs will be directed to" setting to "This device (multiple queues to support different operating systems)" (step 3 of https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/device-mf-copier-integration-release-multiple-operating-systems.html). Once I was done testing, I reverted the settings back to a single virtual queue for those devices, changed the virtual queue driver to the Kyocera v4 (after clearing all pending print jobs from the queue), then changed the individual printers to the v4 driver (all driver changes from printmanagement.msc on the server). I've had a couple laptops so far that did not "update" the information from the print server and still were trying to use the v3 driver, but most automatically picked up the change. To avoid this issue, you may want to rename the find me queue if you push it by GPO (removing the old one from the policy and adding the new one, which would force the clients to query the server about the "new" queue and use the right driver). If users manually add/remove the printer, deleting and re-adding the printer fixes any that didn't update. Also, regarding Papercut Print Deploy, I have not used that (just GPO deployed printers and AD-published printers for Windows, and Mobility Print for Chrome/iOS), but the Known issues section of their help site (PD-1112 under https://www.papercut.com/support/known-issues/#mf ) mentions the windows update causes the admin prompts when using Print Deploy (unless you set the registry key to the insecure setting), so that does not appear to be a working alternative (They suggest Mobility print at the bottom).

I read a little while ago that Server.app 5.3 only supports TLS 1.2 (from https://apple.stackexchange.com/questions/280143/tlsv1-alert-protocol-version-when-connecting-via-ssl-to-os-x-server ). According to https://en.wikipedia.org/wiki/Transport_Layer_Security#Libraries , OSX 10.9 (and iOS 5.0) is the first to support TLS 1.1/1.2 (instead of just 1.0). You could try editing the Apache config files mentioned in the StackOverflow link to re-enable TLS 1.0, but that will lower the security of the server for all clients. (I do not have any OSX 10.8/iOS 4 clients so can't verify this works). Another option may be setting up a separate server just for these older macs.

Take a look at what extensions are installed/force-installed in Chrome and try disabling them. You can also go to "Content Scripts" on the Sources tab in Chrome's developer tools to see specific extensions modifying the page. I think I remember about a month ago a student had issues creating Kahoots and it was caused by an extension from Impero.

I don't have 1607, but I had seen something similar in 1507 last year. I had Chrome, Firefox, and IE available and Chrome set as default through powershell xml import/export. If Firefox updated itself under another user account, Windows thought it was "new" and displayed a prompt to choose a browser whenever opening a link or typing one in the run dialog. I fixed it by setting the GPO Computer Configuration > Policies > Administrative Templates > Windows Components > File Explorer > Do not show the 'new application installed' notification to Enabled, and I have not seen that dialog since then. Note: I don't set file associations by GPO so users can change e.g. their default browser from Chrome to Firefox if they want to.