Weird Private print issue

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Jaycat718
    Technician

    50+ Posts
    • Oct 2013
    • 70

    #1

    Weird Private print issue

    Hello all,

    I've run into a weird issue, that surprisingly not even KYOCERA can figure out. The customer has quite a number of Kyo devices. a mixture of A3 devices, and A4 devices. (Large ACCT)

    They have multiple departments, and have always used Kyocera TA devices. From Series 1 to the new series 4 devices. They now have majority series 4 devices that we have upgraded them to. Very few series 1, and 2 devices remain. 3 or 4.

    We have upgraded their drivers to the latest KX driver for all of the devices. However, they are running into an issue with Private print only on the series 4 devices when printing from the server.

    Specifically when printing Excel sheets, to the series 4 devices.

    The issue: When sending excel jobs via Private print, regardless of the pin that is entered at the pc? The only pin that releases the job at the device is: 0000

    We have purged all of the drivers from the server, so only the newest KX driver is installed. This issue is only happening with the driver that is shared out via GPO. Also with a local share from the same server.

    A new GPO was created with the installation of the new devices utilizing the new drivers BTW.

    If the driver is loaded locally on the workstations? It works perfectly fine!

    permissions on the server are set the same on all devices. We even set it allow the users to "Manage" the devices to no avail.

    The kicker? The series 1, and 2 devices that remain don't have this issue. They release jobs using the pin that is input at the workstation without issue.

    Has anyone seen this before? The customer doesn't have another server to push the driver out through. and the customer has about 300 or so users spread out across various departments; with various machines all doing the same thing. All series 4 devices are doing it. the series 1 and 2 devices are not!

    Usually this wouldn't be an issue for simple private print, but since they have quite a few users, loading the driver locally across 300 users would be a nightmare! Considering the users don't have admin rights!
  • ihatefinishers13
    Senior MFP Technician

    500+ Posts
    • Feb 2020
    • 677

    #2
    Originally posted by Jaycat718
    Hello all,

    I've run into a weird issue, that surprisingly not even KYOCERA can figure out. The customer has quite a number of Kyo devices. a mixture of A3 devices, and A4 devices. (Large ACCT)

    They have multiple departments, and have always used Kyocera TA devices. From Series 1 to the new series 4 devices. They now have majority series 4 devices that we have upgraded them to. Very few series 1, and 2 devices remain. 3 or 4.

    We have upgraded their drivers to the latest KX driver for all of the devices. However, they are running into an issue with Private print only on the series 4 devices when printing from the server.

    Specifically when printing Excel sheets, to the series 4 devices.

    The issue: When sending excel jobs via Private print, regardless of the pin that is entered at the pc? The only pin that releases the job at the device is: 0000

    We have purged all of the drivers from the server, so only the newest KX driver is installed. This issue is only happening with the driver that is shared out via GPO. Also with a local share from the same server.

    A new GPO was created with the installation of the new devices utilizing the new drivers BTW.

    If the driver is loaded locally on the workstations? It works perfectly fine!

    permissions on the server are set the same on all devices. We even set it allow the users to "Manage" the devices to no avail.

    The kicker? The series 1, and 2 devices that remain don't have this issue. They release jobs using the pin that is input at the workstation without issue.

    Has anyone seen this before? The customer doesn't have another server to push the driver out through. and the customer has about 300 or so users spread out across various departments; with various machines all doing the same thing. All series 4 devices are doing it. the series 1 and 2 devices are not!

    Usually this wouldn't be an issue for simple private print, but since they have quite a few users, loading the driver locally across 300 users would be a nightmare! Considering the users don't have admin rights!
    We have an account that had 4 3552, or 53's, I forget which. They never mentioned it to us, but they had to setup everyone locally as well instead of on their virtual server, due to weird issues printing slow, not printing at all, authentication issues, and a lot of them were with printing excel and out of other MSOffice products. Fast forward a few years, we install Sharp's latest series, on the virtual server, Print Release for all users (private print), and a few weeks in they complain of what ended up being very similar issues as they Kyocera's did. Thankfully one of our techs is a wizard with programming, and designed a print driver install package that allowed us to install all 4 printers LOCALLY, including presets, names, etc., it installs in seconds, and all you had to do was add the user code in for all 4 drivers. Absolute life saver with 50 PC's to touch.

    Their IT tried a few things, but the only thing that fixed it was getting it off of their virtual server. Not sure how your situation is setup, but at the end of the day their server didn't like the print drivers, and caused weird things to happen, and it wasn't just Kyocera drivers that it didn't like.

    Comment

    • Black Cloud
      Trusted Tech

      Site Contributor
      100+ Posts
      • Apr 2010
      • 136

      #3
      I would try the KX V4 Driver. It may behave.
      Net+ PDI+ @Remote

      Comment

      • craigster
        Trusted Tech

        100+ Posts
        • Apr 2016
        • 201

        #4
        in the print driver uncheck advance printing feature. This is at the advance tab in properties

        Comment

        • Ropariva
          Senior Tech

          500+ Posts
          • Mar 2016
          • 650

          #5
          Sounds like the kind of scenario that would be better served with Kyocera Print scan or Printix.
          Large installs are a pain but server based drivers and rollout with PIN codes and private print have always been problematic. We also create printer installers for these for this reason and load drivers locally if needed, but we have found most large sites prefer to manage their queues through Printix, Papercut or now Kyoceras Print Scan option.

          Comment

          • Jaycat718
            Technician

            50+ Posts
            • Oct 2013
            • 70

            #6
            Originally posted by craigster
            in the print driver uncheck advance printing feature. This is at the advance tab in properties

            Would this serve better at the server level? Or at the workstation level?

            image.png

            Comment

            • Jaycat718
              Technician

              50+ Posts
              • Oct 2013
              • 70

              #7
              Quick development, so the customer was able to resolve the issue, by checking the option: Print directly to printer, from the driver!

              Thanks to all of you guys for your suggestions!

              20 years in the industry, and i have only had to tick that option twice due to poorly performing/underpowered PC's that couldn't handle spooling the jobs properly!

              Comment

              • ihatefinishers13
                Senior MFP Technician

                500+ Posts
                • Feb 2020
                • 677

                #8
                Originally posted by Jaycat718
                Quick development, so the customer was able to resolve the issue, by checking the option: Print directly to printer, from the driver!

                Thanks to all of you guys for your suggestions!

                20 years in the industry, and i have only had to tick that option twice due to poorly performing/underpowered PC's that couldn't handle spooling the jobs properly!
                .....Wait, so you're telling me that works, which is telling us that their server can't handle it.. got it! haha

                Comment

                Working...