Forum Widgets
Latest Discussions
Ricoh Devices - Cannot MS UP and PrintUp after wake?
Greetings, We have configured a few (3) of our Ricoh devices for MS Universal Print. Printing works OK. The next day after returning to the office - if we print - the print job fails to output on the printer. When I check the Print Up app on the device - it doesn't show as active. I log in to the device MOP as admin - open the Print Up app - and all is good. We can print again. That is, until the next day. The device does sleep after a period of time. Ricoh support has disabled the hard sleep. Is this a common problem? Anyone have a solution that we might try. I appreciate any help.SolvedFloyds_on_GreenwoodApr 30, 2025Brass Contributor2KViews0likes5CommentsQuestion: What is the behind-the-scenes process when a network printer is installed?
Quick background: I work for an MSP providing Tier I support to Ricoh printers at a large healthcare facility. The enterprise has not moved to Universal Print - yet. I want to better understand the end-to-end process as it is now as I'm sure it will help me when the client begins to adopt Universal Printing. We have a mix of Windows 10 and 11 computers. They still use a print server and I recently had most of the Ricoh printers on it updated so they are associated with the PCL6 V4 Universal Print Driver from Ricoh. There are still a few left with either model specific V3 PCL drivers or the PCL6 Universal Print Driver (which is V3, too). However, the only V4 drivers on the computers are those built into the OS - Point and Print or Enhanced Point and Print from Microsoft. Users aren't allowed to install print drivers from Windows Update. Here's what I think is the process behind-the-scenes: User navigates to Printers & Scanners and clicks Add Printer. User selects the printer and it's installed. The print driver for that printer is associated by the OS searching in C:\Windows\System32\DriverStore\FileRepository for a folder (either oem..... or prnms.......) that is the most compatible. Hopefully its a driver from Ricoh (in my case) but it may be the Microsoft Point and Print driver. When the user attempts their first print with the new printer, some of the contents of the folder above (DLL files primarily) are moved or copied [I'm unsure which] to C:\Windows\System32\spool\drivers\x64\3. I think this is how it works for both V3 and V4 print drivers but would like clarification. I'm aware that the INF file is copied to C:\Windows\INF, and that CAB files for at least some of the installed printers are located in C:\Windows\System32\spool\drivers\x64\PCC. I don't understand the purpose for either of these. As for the process as I described it above, I'd appreciate any and all feedback so that I can better understand the process.Mike6877Apr 23, 2025Brass Contributor24Views0likes0CommentsUniversal printer says installed, but not in printer list
Hi, I had a universal printer but change the properties to colour. So I deleted the printer on a device to re add but now I cannot add it back, it reports its installed but does not appear in the printer list. Any ideas? tried looking at registry keys to remove but no luck.Solvedchiners_68Apr 23, 2025Brass Contributor10KViews0likes10CommentsPrinter Sharing Fails for all printers
Just ran into a situation where I cannot share any printers. After I've registered the printer on my connector, I can see the printer on the Azure portal as usual. However when I go share it, I get the error Same thing happens with other unshared printers. I also checked and the printer share names do not exist already. Any ideas?IanXApr 04, 2025Copper Contributor227Views2likes10CommentsUnable to share previously share printers after name change
After updating share names, I am unable to reshare printers. I have tested Readding share, different name. Fails. Unregistering and reregistering printer, share fails Error is below, no useful information. How do we resolve this?AshleySaundersApr 03, 2025Copper Contributor38Views1like0CommentsPrinter Sharing Fails for all printers
Just ran into a situation where I cannot share any printers. After I've registered the printer on my connector, I can see the printer on the Azure portal as usual. However when I go share it, I get the error Same thing happens with other unshared printers. I also checked and the printer share names do not exist already. Any ideas?IanXApr 01, 2025Copper Contributor22Views0likes0Commentson occasion print jobs stuck on pending
Hi All, When printing to our zebra label printer, on occasion feels like the connector loses connection and the jobs are stuck on pending. Testing printing from the print server works fine. The azure universal print portal occasional shows that it has not seen the printer for 15-20 minutes. I also notice high CPU activity with windows defender antimalware services and wonder if some kind of exceptions are required for the universal print connector. This issue appears to have become more frequent in the last 2-3 weeks. BTW we are printing to universal print via windows business central. The connector version we are running is 2.2.9203.40538 Appreciate any guidance / assistance on this matter. Thank you!OliverTrakoMar 28, 2025Copper Contributor56Views0likes1CommentDuplexing not working when printing to a printer connected via Universal Print
Hi, We push out our central office printer via UP and we have the default set on duplex as flip on long edge. However when users print to the printer it will not print double sided, the settings on the devices also say flip on long edge. Other default settings like greyscale work fine. If we install the Printer drivers manually and don't go through UP then the duplexing works fine. Thanks JoeJoeST1Mar 27, 2025Copper Contributor580Views0likes3Comments
Resources
Tags
- universal print20 Topics
- announcements13 Topics
- Universal Print Connector6 Topics
- UniversalPrint4 Topics
- question2 Topics
- Universal2 Topics
- Paper Size Mismatch2 Topics
- Intune2 Topics
- Cloud Print2 Topics
- Ricoh2 Topics