locked
Printer defaults not propogating down to clients RRS feed

  • Question

  • I've set up a copy of server 08 r2 as a print server for my organization. It is currently managing the print jobs for 5 printers, all Ricoh/Lanier. When I set up printer defaults like two-sided black and white the defaults do not show up on the print properties page for clients. I've replaced the driver by Ricoh/Laniers recommendation but the settings still do not apply to the clients. Any thoughts on how to force the settings out to desktop clients?
    Wednesday, February 23, 2011 8:45 PM

Answers

  • Some settings of the driver are not stored in the DEVMODE sturctures but in files. Those files are not moved over to the client, because the MS PnP mechanism does not permit this.

    So you will loose some settings due to limitations e.g. Usernames for lock printing or the tiles in the new Airface printer drivers.

    Also there are files and folders created in the ProgramData\RICOH\<queuename>\... you must asure that users may write there.

    The Inbox-drivers you can get via Windows Update are based on UNIDRV model and store everything in DEVMODE. So they should work okay.

     

     


    Joe Deussen - RICOH Germany - IT Solutions Support
    Thursday, March 24, 2011 1:39 PM
  • Hi Jason,

    sorry, there is a misunderstanding. Yes RICOH has "fully functional" drivers. The drivers you are probably looking for are the Mini-Drivers or the Inbox-Drivers. They work as you expect them to work.

    The monolithic drivers - or the UD - do use some enhanced functions to offer more comfort. Unfortunately this comfort is payed by some limitations if the drivers are used in a point-and-print environment. We are working very hard to resolve those issues.

    Okay, but there is one thing you might want to check as well: The version of UNIDRV and PSCRIPT.

    MS did try to retrofit the NT6 print system to NT5 but they did not propagate this via Windows Update but left this to the printer driver vendors and the .NET Framwork 3.5SP1 install.

    I have seen a lot of setups with your problems where either client or server had the old NT5 printing DLLs and the other part already had the NT6 files. When we upgraded all computers to the NT6 files (they carry a 0.3.x version stragely enough) deleted the connected drivers and reconnected again, everything was fine.

    It seems that there are some changes in the registry that move some settinsg to differnet bits/bytes so the defaults did not get picked up properly. At least the one coded into DEVMODE.

     


    Joe Deussen - RICOH Germany - IT Solutions Support
    Saturday, March 26, 2011 12:10 AM

All replies

  • Hi,

    Thanks for the post.

    Please make sure that you have configured the "printing defaults" on the print server instead of the "printing preferences".

    1. Right-click the printer for which you want to set the default printing preferences, and then click Properties.
    2. Click the Advanced tab, and then click the Printing Defaults button.

    Then please remove the network printer from one test client machine and then re-add it again.

    Does it work?

    Thanks,

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by MrFoppa Friday, February 27, 2015 8:11 AM
    Thursday, February 24, 2011 9:06 AM
  • Unfortunately that was the very first thing I did. The presets I added there weren't propagating down to the clients so I began this thread after calling Ricoh to make sure there wasn't something different with their driver.

    Jason Stamm Desktop support Specialist University of Miami
    Thursday, February 24, 2011 2:05 PM
  • If you have made any changes after the clients have already modified the per user device mode on their machines, the clients will need to delete and reconnect to pickup changes from the server.
    Alan Morris Windows Printing Team
    Thursday, February 24, 2011 4:05 PM
    Answerer
  • Already tried that as part of basic testing. I've even reimaged machines to be absolutely sure that wouldn't be an issue.

    Jason Stamm Desktop support Specialist University of Miami
    Thursday, February 24, 2011 4:53 PM
  • So ,you make changes to the private device mode for the printer on the Advanced tab of printer properties, take a new client that has never connected to the share, connect, and the Printing Preferences of the client connection does not reference the default settings you configured on the Advanced tab?

    Question 1) Does this happen for 32bit and 64bit clients?

    Question 2) When you use a Ricoh driver that is included with Server 2008 R2 does this happen for the same client mix?

    Question 3) Is the 32bit version of the driver installed on the print server the same version as the 64bit driver?

     


    Alan Morris Windows Printing Team
    Friday, February 25, 2011 12:26 AM
    Answerer
  • 1) Yes, both 32 and 64

    2) I haven't tried the windows driver, when I initially installed the printer before the Ricoh driver was installed it didn't recognize the duplex tray or color printing ability. It may have had something to do with this being a brand new printer released by Ricoh a week before we acquired it. The windows driver may not have recognized it correctly.

    3)I installed the 64 bit driver for the server OS and added the 32 as well as XP 32 and 64 bit drivers under the "Additional Drivers" feature.

     

    Yes, no matter what I've tried so far I can't get the settings to propagate down to clients.


    Jason Stamm Desktop support Specialist University of Miami
    Friday, February 25, 2011 7:03 PM
  • I suggest finding one of the drivers Ricoh provided in 2008 R2 that provides compatible support and verifing if that driver displays the same behavior.
    Alan Morris Windows Printing Team
    • Marked as answer by Miles Zhang Monday, February 28, 2011 2:39 AM
    • Unmarked as answer by Alan MorrisEditor Monday, February 28, 2011 4:24 PM
    Sunday, February 27, 2011 2:11 AM
    Answerer
  • As I stated in the previous response, the driver included in 2008r2 didn't recognize the printers features, it was missing color, duplex, and the sorting tray. At the time of purchase roughly three months ago it was a brand new printer model and Ricoh themselves had limited driver support. Typically I use their universal driver but that driver didn't offer support for the newest printer. It's worth noting that the other printers on that server, all different models from Ricoh, do not propagate custom settings either.
    Jason Stamm Desktop support Specialist University of Miami
    Monday, February 28, 2011 2:25 PM
  • I still have no answer to this question. I have tried all the troubleshooting steps described here and have had no success. Apparently this thread has been mistakenly marked "Answered". I assure you, it has not. Can anyone please provide assistance with this? I am rapidly running out of options to pursue.
    Jason Stamm Desktop support Specialist University of Miami
    Monday, March 7, 2011 8:04 PM
  • It's still not answered.  You need to determine why the client machines can not update the settings on the local system.  I'd start with process monitor and see where the failure is.

    If you have not used one of the Ricoh drivers included with Server 2008 R2 to verify that driver setting are reflected on the clients, you have missed a huge step in narrowing down the issue. 

    If the Ricoh drivers in Windows get device specific configuration to the clients, but the Ricoh.com drivers fail, you need to request new drivers from Ricoh that recognize the device features AND work with your client configuration.


    Alan Morris Windows Printing Team
    Monday, March 7, 2011 10:39 PM
    Answerer
  • I initially used one of the Ricoh drivers included in Server 08r2 but it couldn't recognize color or duplex. All it was capable of seeing was one sided black and white. I'll try testing with one but there's not much customizing I can do with single sided B&W. Also I'm not entirely sure what to look for in process monitor to see where the failure is. Can you describe briefly what I should be looking for? Thanks
    Jason Stamm Desktop support Specialist University of Miami
    Monday, March 7, 2011 10:47 PM
  • You need to verify that the problem is only with the .com drivers.   The printer you add to the server does not need to point to a real device.  Add the printer using the Ricoh driver from 2008 R2.  Change the print defaults on the Advanced tab so they no longer represent the defaults.  Connect a client to the share, verify when using the drivers included with Windows, the client obtains the updated settings.

    1) if this succeeds call Ricoh, ask for drivers that work for you for your devices.

    2) if this fails, run process monitor on the client machines using a driver provided in Windows to verify why the configuration is not updated when creating the connection.  Look for registry and file locations that you have changed from the default operating system configuration.  I'd look for access denied.

    Do not use the Ricoh.com drivers when using process monitor UNLESS you want to verify what the Ricoh.com drivers are doing. 


    Alan Morris Windows Printing Team
    Tuesday, March 8, 2011 12:02 AM
    Answerer
  • I set up the printer using the default win drivers and set a few custom presets. There were a few issues with this set up though, including inability to change duplexing options as well as inability to add other drivers. Moving on, I installed the printer on a client while running process mon and did not get the settings I created. I did not find any straight up Access Denied messages but I did see a few Name Not Found messages relating to HKLM\Sys\CCS\Power\PowerRequestOverride\Driver as well as a few Name Not Found related to C:\Win\CSC\v2.0.6\namespace\servername . There was also an error stating File Locked With Writers on a CreateFileMapping for C:\Win\inf\setupapi.app.log . I also saw a CreateFile fail for %user\AppData\Local\Temp\{xxxxxxxxxxxxxxx}\ricA5Hug.miz . The first two errors repeat quite a few times.
    Jason Stamm Desktop support Specialist University of Miami
    Tuesday, March 8, 2011 6:08 PM
  • I could not find any ricA5Hug.miz files that are included with Windows.  Which driver name are you using?  I assume you also started poking in the user local temp directory to verify they have write access.
    Alan Morris Windows Printing Team
    Wednesday, March 9, 2011 12:05 AM
    Answerer
  • I was using what I believe was a default windows driver. When I installed the printer under a different name I went through the select device and model prompt in the install driver dialog. As for write access, on the machine I'm testing with now I'm logging on with the same AD user as the server.
    Jason Stamm Desktop support Specialist University of Miami
    Wednesday, March 9, 2011 3:49 PM
  • The list you see in the manufacture / model page include any print drivers you have installed on the machine.

    In printmanagement, right click machine

    Add Printer ...

    Add a printer using an existing port:

    LPT1: (Printer Port) , Next

    Install a new driver, Next

    Ricoh 

    Ricoh Aficio MP 1100 PCL         <--the first one in the list of Ricoh drivers included in Windows

    RICOH, RICOH  < --  for printer and share name

    Complete the Wizard

    Change Device settings and install all the paper trays as well as the Finisher

    Apply

    Advanced

    Change Printing Defaults..

    Paper Size 11 x 17

    Resolutions 300dpi

    Connect a Windows 7 x64 machine to the shared printer

    Launch Wordpad

    File, Print

    Click Preferences

    Verify - Paper Size:  11 x 17

    Verify - Resolutions: 300dpi

     

     

     


    Alan Morris Windows Printing Team
    Wednesday, March 9, 2011 5:05 PM
    Answerer
  • Ok, the settings do propagate from this set up to the clients. Does this mean the issue lies in Ricoh's driver?
    Jason Stamm Desktop support Specialist University of Miami
    Wednesday, March 9, 2011 6:13 PM
  • The Ricoh driver is writing something to the user\AppData\Local\Temp directory.  If you have implemented policies that block user writes then their driver settings will fail. 

    As a user create a directory at the same location that the driver wants to write to, then copy some files there.  If this works for the user then the driver may be using a different token for the data write. 

    I think once you determine the permissions the driver wants to use for the settings data and you change the system to allow the call to complete successfully, the driver will be able to obtain the settings from the server.

    Ricoh may be able to help if you can pinpoint the failure, but it sounds like Ricoh does not typically deal with this so I'd first examine the client configuration settings.


    Alan Morris Windows Printing Team
    Wednesday, March 9, 2011 7:52 PM
    Answerer
  • We currently have no GPO's modifying write access, and the server itself is a member of our organizations global admin account. I logged in to the client machine with the same "god mode" credentials as the server and did not see any access denied errors when installing the Ricoh drivers in sys monitor. Just the file not found error I mentioned before. I was able to do whatever I wanted in the \app data\local\temp directory. I'm beginning to believe this is an issue with the driver Ricoh shipped but am dreading the thought, their support is terrible.
    Jason Stamm Desktop support Specialist University of Miami
    Wednesday, March 9, 2011 9:21 PM
  • I am seeing a very similar issue. Can I ask which Ricoh driver and version you are using?

    Thanks Steve
    Thursday, March 10, 2011 12:32 PM
  • I was using their universal print driver for most of the machines and a model specific driver for our MFC 3501 due to it not being included in their universal when I set it up.

     


    Jason Stamm Desktop support Specialist University of Miami
    Thursday, March 10, 2011 5:49 PM
  • Thanks Jason

     

    Any chance you know the version used i.e. UPD 3.3, 3.4, or 3.5? My issue also includes the UPD.

     

    Thanks Steve

    Thursday, March 10, 2011 10:07 PM
  • I apologize for the delay SGradowski, we tried both 3.3.000 and 3.4.000 of the UPD. I am currently trying to begin troubleshooting with a Ricoh/Lanier engineer to resolve the issue and will post back here when I have a solution.
    Jason Stamm Desktop support Specialist University of Miami
    • Proposed as answer by BC-- Wednesday, March 23, 2011 2:17 PM
    • Unproposed as answer by BC-- Wednesday, March 23, 2011 2:17 PM
    Monday, March 14, 2011 6:26 PM
  • We are experiencing the same issues with Ricoh drivers.  The univeral PCL6 driver locks up on about half of our workstations so we are working with the PCL5 and PCL6 drivers specific to the individual printers.  We are running both Windows XP and Windows 7 for clients, and we are running Win 2008 and Win 2008R2.  I am testing with 5 different Ricoh models.  Same issue with 32bit and 64bit servers.

    If I set the preferences on the server they do not push down to the client.  Can anybody shed light on this?  I have ongoing cases open on this with Ricoh and Microsoft.  I'll post if I find out anything useful.

    • Proposed as answer by BC-- Thursday, April 7, 2011 9:07 PM
    • Unproposed as answer by BC-- Thursday, April 7, 2011 9:07 PM
    Wednesday, March 23, 2011 2:29 PM
  • Some settings of the driver are not stored in the DEVMODE sturctures but in files. Those files are not moved over to the client, because the MS PnP mechanism does not permit this.

    So you will loose some settings due to limitations e.g. Usernames for lock printing or the tiles in the new Airface printer drivers.

    Also there are files and folders created in the ProgramData\RICOH\<queuename>\... you must asure that users may write there.

    The Inbox-drivers you can get via Windows Update are based on UNIDRV model and store everything in DEVMODE. So they should work okay.

     

     


    Joe Deussen - RICOH Germany - IT Solutions Support
    Thursday, March 24, 2011 1:39 PM
  • I was able to get the settings to propagate to the clients with a builtin windows driver however it only recognized B&W and no duplex. Are you saying that Ricoh does not have working drivers to support their machines for this functionality and I should look elsewhere for what amounts to basic functionality for a network printer? I have a very hard time believing that.
    Jason Stamm Desktop support Specialist University of Miami
    Thursday, March 24, 2011 4:07 PM
  • Hi Jason,

    sorry, there is a misunderstanding. Yes RICOH has "fully functional" drivers. The drivers you are probably looking for are the Mini-Drivers or the Inbox-Drivers. They work as you expect them to work.

    The monolithic drivers - or the UD - do use some enhanced functions to offer more comfort. Unfortunately this comfort is payed by some limitations if the drivers are used in a point-and-print environment. We are working very hard to resolve those issues.

    Okay, but there is one thing you might want to check as well: The version of UNIDRV and PSCRIPT.

    MS did try to retrofit the NT6 print system to NT5 but they did not propagate this via Windows Update but left this to the printer driver vendors and the .NET Framwork 3.5SP1 install.

    I have seen a lot of setups with your problems where either client or server had the old NT5 printing DLLs and the other part already had the NT6 files. When we upgraded all computers to the NT6 files (they carry a 0.3.x version stragely enough) deleted the connected drivers and reconnected again, everything was fine.

    It seems that there are some changes in the registry that move some settinsg to differnet bits/bytes so the defaults did not get picked up properly. At least the one coded into DEVMODE.

     


    Joe Deussen - RICOH Germany - IT Solutions Support
    Saturday, March 26, 2011 12:10 AM
  • Forgive my lack of knowledge on the details, but how would one go about checking the versions of UNIDRV and PSCRIPT and which version of the print system I'm currently running? I've kept this system as up to date as possible and am currently running .Net 4.0 with patches. Also I'm not sure if you read the entire thread but I'm not just running the universal drivers. When I initially set up the MPC 3501 the UD did not support this device so that machine is running on the standalone driver downloaded from Ricoh's support site while the rest of the machines are running the UD.
    Jason Stamm Desktop support Specialist University of Miami
    Monday, March 28, 2011 3:59 PM
  • UPDATE:  If we setup a printer on the server and the users then pick the printer they get the defaults.  If the user then changes the defaults on the local PC they stay that way indefinetly.

    We want the printer defaults to stick...After working with MS, we have found that the only way to do that is to use a GPO to deploy the printers using the replace option.  So, every time the gpo is updated, the existing printer is deleted and recreated, therefore forcing the default which have been set on the server.  This does not redeploy the driver, it just deletes and recreates the printer.  We will be testing over the next few weeks.

    This works for windows7 and it will work on XP if you install gpo client side extensions (kb943729)...there is a similar one for vista, but is anybody really running that anymore:)

    http://technet.microsoft.com/en-us/library/cc732092.aspx
    "Replace: Delete and recreate the shared printer connection. The net result of the Replace action overwrites all existing settings associated with the shared printer connection. If the shared printer connection does not exist, then the Replace action creates a new shared printer connection."

     

    • Proposed as answer by BC-- Thursday, April 7, 2011 9:21 PM
    Thursday, April 7, 2011 9:20 PM
  • We have similar issues at our site.  Ricoh devices currently in use here:  SP8200dn, MP C4501, MP 8001, soon to add MP2051, and some Lanier LD345 units going off lease later this year.  The device drivers that ship with Windows 7 do seem to work better in regards honoring system printing defaults configured in the control panel.

    For the MP C4501, Ricoh has a PCL mini-driver available for download, but there is no PostScript mini-driver avaialble.  Are there plans to release a PostScript mini-driver for Windows 7 (and perhaps Server 2008/2008R2)?

    Our Windows 7 systems are 64-bit hosts running Win 7 SP1.  unidrv.dll version 0.3.7601.17514/product version 6.1.7601.17514.  Same for pscript5.dll (I don't see a pscript.dll in C:\Windows\System32\spool\drivers\x64\3).

     

    John Perkins

    University of Wisconsin-Madison Department of Computer Sciences


    Friday, April 8, 2011 2:50 PM
  • We are having he same issue in our department. We purchased new Ricoh MC4501's and installed the PCL6 Driver (with the one-click presets). We could not get the printer default settings to propagate to the clients. However it DID, in our environment, propagate with the PCL5c drivers, but the driver "looks" very different and our users were already trained on the PCL6. The one-click presets are also handy for quick print configuration changes.

    The main problem we were having was the default settings were single sided color prints. That was a huge expense as we went through twice as much toner in the first month than our lease agreement allowed.

    We finally found that Ricoh had a print driver editor (http://support.ricoh.com/html_gen/util/PDE/PDE.html) and we were able to set some basic settings (forced B&W, Duplex, and Locked Print). Once we replaced the original PCL6 driver with the "edited" PCL6 all the users had the same defaults. Its a pretty successful workaround, its too bad the driver doesn't support propagation, it would be nice to set one-click presets for the users.

    Good luck. I hope they release a new driver soon, last I checked the PCL6 was released 4/12/11.

    • Proposed as answer by rgroom Thursday, July 7, 2011 4:52 PM
    Thursday, July 7, 2011 4:52 PM
  • Same issue here, I'm pulling my hair out at the moment. I've been trying everything. Windows 2008 R2 + XenApp 6.5 R01. Printer is a Ricoh MP C4000.

    - Native PCL6 driver from Ricoh site: Default printer settings do not propagate.
    - Native PCL5e driver from Ricoh site: same
    - PCL Mini driver: Driver is unsigned but works, settings propagate HOWEVER mutliple copies don't work, printer always prints one copy even though I select 2 or more (this seems like a minor problem but it's a show stopper in our environment).
    - Windows built-in driver (MP C4500): Same as PCL Mini driver, everything works, staple, punch, multiple copies don't.
    - All universal drivers: Settings don't propagate.

    Further more, when I connect to the printer as a user (also with an admin user) and click printing preferences and set my personal preference to B&W, when I click ok and go back to the preferences it's on color again. When I add the printer locally, using a LPT1 or Standard TCP/IP port (so don't connect to the printer using a network share) then suddenly it does remember the personal preferences.

    I've been working on this for two days now, didn't get any further and I had to roll back to the windows built-in driver MP C4500. That seems to work fine although now multiple copies don't work.

    So my conclusion, as it stands now there is NO fully functional driver for Windows 2008 R2 at this moment, when using it in a network printing configuration.

    Wednesday, August 1, 2012 2:20 PM
  • ok, so i'm currently suffering from some varrient of this problem.

    I have the pcl6 for universal print v3.3.0.0 both x86 and x64 installed on a win server 2003 r2 sp2 x86 box, and the driver settings propigate just fine to XP x86, and do not propigate to Win7 64bit.

    does anyone have any ideas to fix it?

    Friday, August 24, 2012 6:54 PM
  • "Universal Print" makes me think you're dealing with HP printers.  That's just a guess, though.

    We've given up on trying to make HP printer drivers work with Win7 64-bit.  Most of the printers we have in service are Ricoh, and replacing the remaining few isn't a big deal for us...so we've gone that route.  Make sure you use the PCL "mini" drivers, though, or your settings will likely get lost.  You may need to set the printer entry in your GPO to "replace" rather than "update", too.

    There is the HP PARK package that is supposed to allow you to configure defaults for printer drivers (Printer Administrator Resource Kit) that contains an Active Directory Template for UPD that might help.  I tried looking into that at one point, but it never quite did what I wanted it to do. John

    John

    Friday, August 24, 2012 7:30 PM
  • nope, there all ricoh copiers

    PCL6 Driver for Universal Print what is say the name of the driver is in the readme file

    the drivers package names i have are z46137L6 for the 64bit, and z46138L6 for 32bit

    Friday, August 24, 2012 7:55 PM
  • btw, why would i want to use the inferior mini driver insted of the full pcl6 or ps one?
    Friday, August 24, 2012 8:00 PM
  • "Universal Print" makes me think you're dealing with HP printers.  That's just a guess, though.

    We've given up on trying to make HP printer drivers work with Win7 64-bit.  Most of the printers we have in service are Ricoh, and replacing the remaining few isn't a big deal for us...so we've gone that route.  Make sure you use the PCL "mini" drivers, though, or your settings will likely get lost.  You may need to set the printer entry in your GPO to "replace" rather than "update", too.

    There is the HP PARK package that is supposed to allow you to configure defaults for printer drivers (Printer Administrator Resource Kit) that contains an Active Directory Template for UPD that might help.  I tried looking into that at one point, but it never quite did what I wanted it to do. John

    John

    The Ricoh drivers are just as bad, their universal driver is even worse than the one from HP and their PCL Mini-driver, which seems to work 'sort of' lacks functionality since their driver editor only works with their native PCL 6 driver (which is crap as well with 2008 R2). WIth the PCL Mini-driver you're gonna get problems with stuff like printing multiple copies, printing in landscape, printing with pincode and what not more but I'm stuck to it as well since it's their only driver that's stable.

    The only way we got some functionality working in Windows 2008 R2 (which probably applies to Windows 7 x64 as well) was to install the printer with the PCL6 edited drivers locally, printing directly to tcp/ip instead of connecting to a print queue, only then it would retain its default settings.

    And now I'm only talking about drivers, wait until you've printed a couple of thousand pages with these Ricoh machines and a Ricoh technician will be on your doorstep every week, I promise ;)

    Friday, August 24, 2012 8:04 PM
  • The "inferior" mini driver stores its driver data in a location that can be copied over to the client computer to maintain default settings on the client.  Full PCL drivers don't always store their data in the DEVMODE data structures (see JDeussen's posts above). 

    We don't even try the Universal Print drivers at our site because the printers are behind a firewall, and we do *NOT* want the drivers to try to send SNMP queries to the printers they can not contact directly (to find out the capabilities of the device).

    I did find I need to distribute the print processor DLLs via GPO along with a registry keys under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Ports for each network port (\\server\printer).  After that, printer defaults seemed to be passed down to client computers for the Ricoh products we're using (MP 8001, MP C2051, MP C4501, SP 8100DN, SP C320DN, MP 171, Lanier LD320d and LP331cn). 

    As for the Ricoh technician coming to visit, well, we had some older printers from them that were utter crap.  Newer printers seem to be much improved, and the copiers are all under maintenance here.

    Friday, August 24, 2012 9:35 PM
  • I am having similar problems to what is in this post. 2008 Print Server with Ricoh printers (MP 171's). Default preferences never propagate down from my server. I've tried the Universal Driver, the mini-driver, and the PCL6 driver. None of them propagate. I prefer the PCL6 driver because it offers the most functionality and my users are already familiar with it.

    To further on what everyone else has been trying. We would like to have a one click custom preset in the default preferences but since they never propagate down we were considering having our users just import a .json to get the one click preset, but in testing we have run into problems. After we import the new preset and the user logs off, the next time the user logs in the preset is missing. I dug a little deeper and found when you import the preset in, a folder is created in C:\ProgramData\RICOH\<Printer Model>\. This folder has a handful of folders in, but after drilling down into them I can find the .json that I imported. But after the user logs off this folder is gone instantly. The other interesting thing is that I only see this problem on 2008 and 2008 R2 servers. I can successfully import the .json on a Windows 7 or Server 2003 machine and it will stay after logging out and back in.

    This questions has been open a long time and there hasn't been recent activity so I'm guessing these problems are still fairly unresolved. Once again if the defualts propagated down we wouldn't have the problem with the ProgramData folder. But any other insight into this would be great.

    Wednesday, March 20, 2013 3:10 PM
  • I worked around this problem by not auto replicating the printer drivers (XenApp 6.5).

    Instead, I browse to my print server by UNC (\\printserver) right-click the printer and choose 'connect'.

    It then asks me a question if I want to install the printer driver, when I do that everything works and default settings are propagating, you only have to do this one time on every XenApp server for every different Ricoh driver.

    It's not ideal but for now it's a solution.

    Wednesday, March 20, 2013 3:29 PM
  • I worked around this problem by not auto replicating the printer drivers (XenApp 6.5).

    Instead, I browse to my print serveOkr by UNC (\\printserver) right-click the printer and choose 'connect'.

    It then asks me a question if I want to install the printer driver, when I do that everything works and default settings are propagating, you only have to do this one time on every XenApp server for every different Ricoh driver.

    It's not ideal but for now it's a solution.

    Ok but user can still adjust this setting and overrule the defaults set on the printserver. I tested this over and over.

    The only thing that works is modify the drivers so the settings are locked. But if you modify the driver you need to give it another drivername because importing drivers with identical name doesn't work.

    So you have to edit the .inf file and if you do that your drivers are not DIGITAL SIGNED!! 

    This will create another problem in a session printing environment that you'll get plenty of errors in the "Printserver - Admin" event.

    EVENTID: 600 & 601

    The print spooler failed to import the printer driver that was downloaded from \\Printserver\print$\x64\PCC\oemsetup.inf_amd64_neutral_ac28284c26f8d73e.cab into the driver store for driver Ricoh MPC3002 PCL6 UNI - Color. Error code= 800f0247. This can occur if there is a problem with the driver or the digital signature of the driver.
    The print spooler failed to download and import the printer driver from \\Printserver into the driver store for driver Ricoh MPC3002 PCL6 UNI - Color. Error code= 800f0247.

    Seriously, in the YEAR2013 Ricoh cannot even make proper drivers that can propegate the default settings in a point to print environment / session printer environment.

    I will ask for a discount for the time I need to spend on such bullshit.


    • Edited by to_murda Thursday, April 4, 2013 1:07 PM hiding printername
    Thursday, April 4, 2013 1:06 PM
  • One way to work around the problem is to modify the default Presets that are built-in to the driver.  The only downside (apart from the complexity) is that you have to push out a new print queue each time you want to change the Presets. See the proceedure below.

    1. Install the free 7-Zip file compression program
    2. Download the driver file from the Ricoh website
    3. Expand the driver files as normal
    4. Install the standard driver on a PC,
      1. Create the presets you want to make the default.
      2. Export the additional presets to a json text file using Manage Presets.
    5. Open the json files with a text editor,
      1.  make sure the name_id field matches the json filename without the extension.
    6. The folder where the driver is expanded to should contain file called rica66cf.cfz, (this file is actually a compressed directory).
    7. Open the 7-Zip program.
      1. Navigate to the rica66cf.cfz file,
      2. right click the file and select 7-Zip > extract
      3. Select the same folder as the driver files as the destination,
      4. a new folder called rica66cf will be created.
      5. In the decompressed folder navigate to the gui/shortcut folder.
      6. The folder will contain a list of the standard presets that come with the driver.
    8. Open the shortcut_settings.json file with a text editor (notepad)
      1. modify the factory_shortcuts field to include all the defaults you want to be included in the modified driver (separated with commas and enclosed in Quotations)
      2. make sure the name is the same as the json file without the  extension as per 5.1 above.
      3. Save the file.
    9. Using 7-Zip navigate back to the original rica66cf.cfz compressed file.
      1. Right click and select Open Outside.
      2. The directory structure of the compressed file is shown in 7-Zip,
      3. Navigate to the gui/shortcut  folder
    10. In windows explorer,  navigate to the expanded rica66cf folder
      1. Drag and drop your modified shortcut_settings.json file on to the open shortcut folder in 7-zip
      2. Confirm to replace the original Ricoh file.
      3. Also drag and drop the additional json shortcut files on to the same window, these will be added to the compressed folder.
      4. Close the 7-Zip window to save the compressed file.
    11. Open the OEMSETUP.INF file in the driver folder with a text editor,
      1. Modify the DriverVer field and increment the driver version  e.g from 12/14/2012,1.2.0.0 to 04/15/2013,1.2.0.1 .
      2. Save the file.
    12. You can now delete the uncompressed (rica66cf) folder
    13. Install the driver on the server by selecting the OEMSETUP.INF and share out as you would normally do.
    14. Presets should be installed.

    • Proposed as answer by Ger Somers Wednesday, April 17, 2013 3:08 PM
    Wednesday, April 17, 2013 3:07 PM
  • Hi nevernot,

    we had a similar problem, alltough on a 2008R2 terminalserver and not on desktop clients.

    For our Kyocera printers it also seamed that the printer setting where not pushed into the usersessions.  This caused the spool.exe on the TS to crash. There was a windows patch that helped us. Perhaps there might also be one for your dektop OS.

    See case http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/99c51100-2313-4ed2-8ef8-3c0f80b65ad0

    Hope this gets you on the right line!

    Nadine


    • Proposed as answer by Nadine Meins Tuesday, May 21, 2013 10:53 AM
    • Edited by Nadine Meins Tuesday, May 21, 2013 10:55 AM
    Tuesday, May 21, 2013 10:53 AM
  • Where can one download various Ricoh .json files?  Unable to come up with any search results on their website.
    Wednesday, June 26, 2013 4:03 PM
  • Ger, I just wanted to state how much this helped! I've spent the last six hours fighting with this to simply make Black & White the default and yours is the only one that worked for me. As an additional note, I noticed in the shortcut_settings.json file there was a setting at the very bottom called "edit_factory_shortcuts" that was set to false. Just for the hell of it I changed that to true and now I'm able to also delete/edit the factory presets in the GUI without going through all of the JSON editing you outlined, so that may be a shortcut for others to take.

    As a result of the changed value in "edit_factory_shortcuts" combined with rgrooms tip to use the Ricoh Print Driver Editor that I tried earlier, I believe this led to all of my presets now being in Black & White instead of just my custom one, but that's perfectly fine with me. My users know how to change to Color on a per job basis. For the record, this was for a Savin C9120.

    Once again, thank you!


    • Edited by sully213 Tuesday, September 10, 2013 7:14 PM
    Tuesday, September 10, 2013 7:13 PM
  • Is there any update from Ricoh about this ongoing issue?

    It's not normal I need to modify drivers for every thing which needs to be default and save it as:

    - RICHOH MPC 3002 - BW

    - RICOH MPC3002 - Color

    - RICOH MPC 4502 - BW

    - RICOH MPC 4502 - Color

    and this for every different type we have.

    Thursday, March 6, 2014 11:49 AM
  • We went through these steps. Installed the driver and then pushed it out but still the client pc did not retain what we wanted as a default. 

    We were just wanting Duplex to be the default. 

    Using RICOH UDP 4.6.

    Running out of options and Microsoft has told me to go with a model specific driver. 

    Wednesday, July 29, 2015 1:59 PM
  • It's frustrating to see that Ricoh has not resolved this after all these years.  The current version of the UPD (4.10) doesn't even allow a client to inherit a default setting of "Black and White".  The original statement that "some settings" are lost seems very generous.
    Friday, July 22, 2016 4:27 PM
  • I have implemented a solution that appears to be working in our environment. 

    While Ricoh printer drivers tend to ignore defaults set in the print server, you can specify them in the driver.  Each Ricoh driver comes with a mostly empty .RCF file.  This is an XML file that the driver will use to set the defaults. 

    The Printer Driver Packager (PDP) can be used to generate an .RCF file with your desired setting.  Note that the Printer Driver Packager is designed for more than this.  We only need it for creation of the .RCF file.  You can also hand edit the .RCF file if you know the correct values. I used PDP to generate an .RCF file and then copied the contents into the .RCF file from the driver download.

    Here is the .RCF file I created.  It sets the defaults to black and white and turns off duplexing:

    <?xml version="1.0" encoding="utf-8"?>
    <rcf version="1.0">
      <devicesettings drivername="PCL6 Driver for Universal Print" independent="yes">
        <item name="duplex" value="off"/>
        <item name="colorbw" value="blackandwhite"/>
      </devicesettings>
    </rcf>

    This alone actually worked well for us for several years. We use Group Policy Preferences (GPP) Printers to deploy printers throughout our domain.

    Then in the summer of 2016, one of the cumulative update packages Microsoft released broke this.  GPP was updated so that it will no longer install print drivers that do not have a valid signature.  No combination of adjusting the Point and Print settings could fix this. 

    The solution is to resign the printer driver.  If you have a code-signing certificate, you can use that.  If you have a certificate server in your domain, you can generate a code-signing certificate and use that.  A third option is to generate a self-signed certificate. 

    Windows OS Hub has an excellent article that shows the steps for the third option.  

    http://woshub.com/how-to-sign-an-unsigned-driver-for-windows-7-x64

    Note that while it says the process only works for Windows 7, I have confirmed it works for Windows 8 and 10 for this particular application.

    Friday, September 9, 2016 2:23 PM
  • This actually led me to the solution to my problem - a custom form size I created on the server was not seen on the clients.  On the server - I made the made the new form size the default in the Advanced taab - Apply/OK - there was a pause - and then the new form size was seen on the client.  I later went back to the server and changed the default form size back to C (for an engineering plotter) - thanks!
    Wednesday, June 20, 2018 12:43 PM