Page 3 of 3 FirstFirst 1 2 3
Results 21 to 30 of 30

Thread: Printing Defaults set on server not propagating to Windows 10 workstations on network

  1. #21
    adam1991 is offline Fiery Forum Expert Contributor adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful
    Join Date
    Feb 2010
    Posts
    1,029

    Default

    In general, it's good practice not to change mission-critical devices that are in production until and unless you know that the change won't affect production. That includes updates.

    Microsoft is doing its best to force you to take the updates no matter what, so you'll struggle with that under Win10. I don't know.

  2. #22
    Join Date
    Jun 2015
    Posts
    116

    Default

    Quote Originally Posted by jorgeseptien View Post
    Well back to the drawing board. I just created an HP printer using a postscript driver and set its printing defaults to print in grayscale on the server. I then installed it on my Windows 10 Anniversary Edition station and these settings did propagate. Any other suggestions? I am not being a wise ***. I am just wondering. Is there a file that saves these settings that can be copied to the individual workstations?
    Hi jorgeseptien,

    No worries, in fact, I very much appreciate you taking the time to test and report back. This kind of feedback is extremely helpful so I hope that you would continue to post on the forums.

    As for the HP PS driver in question, do you know if it uses the Microsoft PS core driver?

  3. #23
    Join Date
    Oct 2016
    Posts
    11

    Default

    Quote Originally Posted by Anthony.L View Post
    Hi jorgeseptien,

    No worries, in fact, I very much appreciate you taking the time to test and report back. This kind of feedback is extremely helpful so I hope that you would continue to post on the forums.

    As for the HP PS driver in question, do you know if it uses the Microsoft PS core driver?
    Not sure. How can I tell?

    I just printed out a test sheet and these were the drivers listed:

    PRINT DRIVER PROPERTIES
    Driver Name: HP Color LaserJet 4700 PS
    Driver Type: Type 3 - User Mode
    Driver Version: 61 .82.61 .41

    ADDITIONAL PRINT DRIVER FITES
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcp4700.C FG
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpc4700s.X ML
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcsc6de.D TD
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpc4700v.I NI
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcd mc64.DLL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpbcfgre.D LL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcui6de.D LL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcpe6de.D LL
    C:\WINDOWS\system 32\spool\DRIVERS\x64\3\hpcs16de.DLL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\cioum.dll
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\CIOUM64.ms i
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcst6de.D LL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcur16de. dll
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcsat.dll
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcsn6de.d em
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcls6de.D LL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcss6de.D LL
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpzfn6de.N TF
    C:\WINDOWS\system32\spool\DRIVERS\x64\3\hpcev6de.D LL

    Not sure if that is the way to figure this out.

  4. #24
    Join Date
    Aug 2014
    Posts
    2

    Default

    Workaround has been published by Microsoft in KB3201130


    https://support.microsoft.com/en-gb/kb/3201130


  5. #25
    adam1991 is offline Fiery Forum Expert Contributor adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful
    Join Date
    Feb 2010
    Posts
    1,029

    Default

    So, there's really nothing for a vendor like EFI to do at this point.

    As I said before, this is very, very typical of an update rollout--both in Windows and in Macintosh. "We told you to do X, you did X by the book, now it sucks to be you" says the vendor.

    One should never update production systems without thorough testing.

  6. #26
    Join Date
    Oct 2016
    Posts
    11

    Default

    Quote Originally Posted by towler100 View Post
    Workaround has been published by Microsoft in KB3201130


    https://support.microsoft.com/en-gb/kb/3201130

    Wow! Thanks. I will try it over the weekend and report back.

  7. #27
    Join Date
    Jun 2015
    Posts
    116

    Default

    Quote Originally Posted by towler100 View Post
    Workaround has been published by Microsoft in KB3201130


    https://support.microsoft.com/en-gb/kb/3201130

    Thanks for the find!

  8. #28
    Join Date
    Oct 2016
    Posts
    11

    Default

    This workaround did not work. I followed them carefully and it did not propagate the settings on the printing defaults from the server. I wasn't sure what they meant by "Make sure that the configuration file is same as the one that's available in Windows 10". Is there another file that holds the information from the printing defaults other than the four DLL files mentioned.

    Any help would be much appreciated.

  9. #29
    Join Date
    Oct 2016
    Posts
    11

    Default

    Nevermind. It did work. I had to reset the settings on the printer on the server. I had to reset to color and apply and then reset it to black and white and hit apply and then it did propagate. Thanks for all your help.

  10. #30
    Join Date
    Jun 2015
    Posts
    116

    Default

    Thank you for your tests and reports! Glad everything is working for now. We'll update everyone when we have a better solution.

Page 3 of 3 FirstFirst 1 2 3

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts